bo data service xi 3.2

SAP BusinessObjectsData ServicesInstallation Guide for Windows

SAP BusinessObjects Data Services XI 3.2 SP1 (12.2.1)

2009 SAP AG. All rights reserved.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge,ByDesign, SAP Business ByDesign, and other SAP products and services

Copyright

mentioned herein as well as their respective logos are trademarks or registeredtrademarks of SAP AG in Germany and other countries. Business Objects and theBusiness Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, WebIntelligence, Xcelsius, and other Business Objects products and services mentionedherein as well as their respective logos are trademarks or registered trademarksof Business Objects S.A. in the United States and in other countries. BusinessObjects is an SAP company.All other product and service names mentioned arethe trademarks of their respective companies. Data contained in this documentserves informational purposes only. National product specifications may vary.Thesematerials are subject to change without notice. These materials are provided bySAP AG and its affiliated companies ("SAP Group") for informational purposesonly, without representation or warranty of any kind, and SAP Group shall not beliable for errors or omissions with respect to the materials. The only warranties forSAP Group products and services are those that are set forth in the expresswarranty statements accompanying such products and services, if any. Nothingherein should be construed as constituting an additional warranty.

2009-10-24

ContentsPreparing to Install 9Chapter 1

Pre-installation overview............................................................................10

System requirements...........................................................................11

Network requirements..........................................................................11

User permission requirements.............................................................12

Choose components and determine component distribution...............13

Create a database for each repository.................................................17

Check port assignments.......................................................................18

Check network connections.................................................................21

Create a Windows cluster....................................................................21

Repository database requirements and preparation.................................23

Installing MySQL as the repository database.......................................24

To set up a database account..............................................................25

Setting up an empty database for the repository.................................26

Database-specific requirements for Data Cleanse...............................32

Installation scenarios.................................................................................34

Standard installation overview..............................................................34

Silent installation overview ..................................................................36

Standard Installation 37Chapter 2

Beginning your installation.........................................................................38

To accept the license agreement.........................................................38

To enter user information and a product keycode................................39

To specify the installation location........................................................39

To select which features to install.........................................................40

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

SAP BusinessObjects Data Services Installation Guide for Windows 3

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

To reuse an existing MySQL instance..................................................43

To configure an existing database server.............................................44

To configure a Job Server..........................................................................45

To specify login information..................................................................46

To configure an Access Server..................................................................46

To configure Metadata Integrator...............................................................47

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

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

To select a web application server.............................................................49

To configure your Tomcat application server........................................50

To configure an existing Web application server..................................50

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

Silent Installation 55Chapter 3

Overview of silent installation....................................................................56

Performing a scripted installation..............................................................56

To create a response file......................................................................57

To run a scripted installation.................................................................57

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

After Installation 63Chapter 4

Starting services automatically..................................................................64

Logging in to the Management Console....................................................64

Installing cleansing packages....................................................................64

Using the Repository Manager..................................................................65

To create or upgrade repositories........................................................66

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

Using the Server Manager.........................................................................69

To configure Job Servers......................................................................70

4 SAP BusinessObjects Data Services Installation Guide for Windows

Contents

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

To configure run-time resources...........................................................73

To configure Access Servers................................................................74

Verifying that Job and Access servers are running..............................76

Using the License Manager.......................................................................76

To start License Manager.....................................................................76

To view product activation keycodes....................................................77

To add product activation keycodes.....................................................77

To remove product activation keycodes...............................................78

To use License Manager from the command line................................78

Configuring Metadata Integrator ...............................................................80

Configuring Metadata Integrator in a local environment......................82

Configuring Metadata Integrator in a distributed environment.............83

To configure Metadata Integrator from the configuration wizard..........86

To install an SAP BusinessObjects Enterprise Job Server for MetadataIntegrator..............................................................................................90

To create a Program Job Server group................................................92

To configure the server group settings.................................................93

Metadata Integrator installation tips and troubleshooting.....................94

Connecting the Data Profiler......................................................................96

Installing the SAP BusinessObjects Accelerator Index Designer..............97

Troubleshooting installation problems.......................................................98

Repository problems............................................................................98

Management Console problems..........................................................98

Windows Vista and Server 2008 issues.............................................100

Verifying real-time connectivity...........................................................100

Control the Address Server.....................................................................108

Start the Address Server....................................................................108

Stop the Address Server to install data directories............................109


Contents

Citrix Support 111Chapter 5

Installing the software..............................................................................112

Initial installation.................................................................................113

Running components in multi-user mode................................................114

Serial access to the License, Server, and Repository Managers.......114

Parallel access to the Management Console, Locale Selector, andDesigner.............................................................................................114

Using shell scripts to access the Locale Selector and Designer........115

Publishing the software............................................................................117

To publish a component.....................................................................117

Connection management...................................................................120

Client setup........................................................................................120

Limitations................................................................................................120

Directory Data 123Chapter 6

Directory listing and update schedule......................................................124

U.S. Directory expiration..........................................................................127

U.S. Directory expiration schedule..........................................................128

U.S. National and Auxiliary files..............................................................128

Where to copy directories........................................................................129

To copy International directory files to a non-default location ...........129

To install and set up Download Manager.................................................130

To download directory files......................................................................130

Extract directory files on Windows...........................................................131

Overview of wdeploy 133Chapter 7

Configure wdeploy...................................................................................134

Options for wdeploy.................................................................................135

Deploy all web components.....................................................................135


Contents

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

Verify deployment....................................................................................137

Undeploy all web components.................................................................137

Undeploy one web component at a time.................................................138

Maintaining your installation 141Chapter 8

Upgrading the software............................................................................142

Component upgrades.........................................................................142

Upgrading your system......................................................................144

Upgrading repositories.......................................................................148

Upgrading cleansing packages..........................................................149

After upgrading the software..............................................................151

Index 153


Contents


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 theSupported Platforms document available in the SAP BusinessObjectsSupport > Documentation > Supported Platforms/PARs 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

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 theinstallation 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 theseJob 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 Using the Repository Manager Advanced Development Guide: Multi-user development

Check port assignments

On each computer, verify that all ports to be used by SAP 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.xml

28080Supports communication be-tween web browsers and theManagement Console.

HTTP port

Tomcat conf\server.xml

28005

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

Supports communication forthe debugging feature.

Interactive Debug-ger port

Address Server



Component

To setDefaultDescriptionPort

LINK_DIR\bin\address_server\AddressServerConfig.txt

40010Supports communication forthe Address Server.Control port

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 Generic

Service, 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_clus

ter_conf.txt files from the bin directory on your primary clustercomputer.

b. Paste these files to each non-primary cluster computer and run thefollowing 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 -Ddomain when not using system account on primarynodejs_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

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.


1Preparing to InstallRepository database requirements and preparation

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

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:


Preparing to Install1 Repository database requirements and preparation

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 MySqlAdmin5folder at the same level as LINK_DIR. To start or stop the MySQL service,you can use the installed MySQL administration tools or the "Services" panellocated in the "Administrative Tools" section of the Windows Control Panel.

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

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, see the Supported Platforms document available in the SAPBusinessObjects Support > Documentation > Supported Platforms/PARssection of the SAP Service Marketplace: http://service.sap.com/bosap-support.

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

1. Create a new database.2. Create a new user account and password for the database to be used

by the software.3. Specify that the new user account has the required permissions to create,

modify, and delete tables and create procedures so that the 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 Quality



Management 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:System call to load and initialize functionsfailed for . Make sure the SHARED LIBRARYis installed and resides in the correct location.

(5.2) 02-05-02 14:55:23 (E) (26797:0001) REP-100108:Cannot perform operation on Repository because a connection to the repository was neveropened. A connection must be opened to the repositorybefore 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

MySQL database setup requirements

You must configure the following information prior to installation and supplyit 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.



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 doesnot match, 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 Microsoft SQL Server database setup requirements MySQL database setup requirements Oracle database setup requirements Sybase database setup requirements



Database-specific requirements for Data Cleanse

SAP BusinessObjects Data Services has specific requirements for thedatabase repository used by cleansing packages or custom Data Cleansedictionaries created using Universal Data Cleanse. For disk spacerequirements, see the Supported Platforms document available in the SAPBusinessObjects Support > Documentation > Supported Platforms/PARssection of the SAP Service 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_parametersWHEREPARAMETER = '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


Preparing to Install1 Installation scenarios

Documentation Components

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 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 Beginning your installation Using the Repository Manager Using the Server Manager


1Preparing to InstallInstallation scenarios

Using the License Manager Logging in to the Management Console

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


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

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.

3. Click Next to continue the installation.Related Topics Using the License Manager

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

2. Click Next to continue the installation.

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

Related Topics Using the Repository Manager

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

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.

4. Click Next to continue.Related Topics To configure Access Servers

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

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 Supported Platformsdocument available in the SAP BusinessObjects Support > Documentation> Supported Platforms/PARs section of the SAP Service Marketplace:http://service.sap.com/bosap-support.

Related Topics SAP Note 1347589

To configure your Tomcat application server

The "Configure Tomcat" screen is displayed during installation setup if 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

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.


2Standard InstallationTo start the installation

Note:If you are running the setup.exe program from the command line, andhave the -w filename parameter switch enabled, this is the point atwhich you 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.


Silent Installation3 Overview of silent installation

To create a response file

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

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.

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_MYSQL

ROOT

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.

DATABASEP

WD


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.

DATABASEDRIV

ER

Specifies the ODBC DSN for the repository database.DATABASEDSN

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

DATABASE

PORT

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_AU

DIT

Specifies the user ID for the database.

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

DATABASEUID_AU

DIT

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.

DATABSEP

WD_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_CON

NEC

TION_PORT

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

TOM

CAT_REDI

RECT_PORT

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

TOM

CAT_SHUT

DOWN_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

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. For more information, see theSupported Platforms document available in the SAP BusinessObjects Support> Documentation > Supported Platforms/PARs of the SAP ServiceMarketplace: 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 To create or upgrade repositories

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

bo data service xi 3.2

Documents