Xi32 Ds Install Unix En

SAP BusinessObjectsData ServicesInstallation Guide for UNIX

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 7Chapter 1

Pre-installation overview..............................................................................8System requirements.............................................................................8Network requirements............................................................................9User permission requirements.............................................................10Kernel parameters and user resource limits........................................11Choose components and determine component distribution...............14Create a database for each repository.................................................18Check port assignments.......................................................................19Check network connections.................................................................22

Repository database requirements and preparation.................................22To set up a database account..............................................................23Setting up an empty database for the repository.................................23Database-specific requirements for Data Cleanse...............................29

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

Standard Installation 35Chapter 2

Beginning your installation.........................................................................36To accept the license agreement.........................................................36To specify the installation location........................................................37To enter a product keycode..................................................................37To select which features to install.........................................................37

To select a repository.................................................................................38To configure an existing database server.............................................39

SAP BusinessObjects Data Services Installation Guide for UNIX 3

To configure a Job Server..........................................................................41To configure an Access Server..................................................................41To select a web application server.............................................................42

To configure your Tomcat application server........................................43To configure an existing Web application server..................................44

To start the installation...............................................................................46

Silent Installation 49Chapter 3

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

To create a response file......................................................................50To run a scripted installation.................................................................51

After Installation 53Chapter 4

Setting environment variables...................................................................54Configuring additional database connectivity.......................................56

Starting services automatically..................................................................58High-availability support.............................................................................58

Using the software with HACMP..........................................................59Installing cleansing packages....................................................................62Using the Repository Manager..................................................................63Using the Server Manager.........................................................................66

To configure Job Servers......................................................................69To configure run-time resources...........................................................72To configure Access Servers................................................................73To start or stop the service...................................................................75To start or stop the Address Server......................................................76To configure SMTP email.....................................................................77

Using the License Manager.......................................................................77Setting up License Manager.................................................................77

4 SAP BusinessObjects Data Services Installation Guide for UNIX

Contents

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

Controlling the Tomcat application server..................................................81Troubleshooting installation problems.......................................................82

Designer-Job Server connection..........................................................82Server Manager problems....................................................................82Management Console problems..........................................................83Memory issues.....................................................................................84Threading issues..................................................................................85

Directory Data 87Chapter 5

Directory listing and update schedule........................................................88U.S. Directory expiration............................................................................91U.S. Directory expiration schedule............................................................91

U.S. National and Auxiliary files...........................................................91Where to copy directories..........................................................................92

Copy International directories files to a non-default location................93To install and set up Download Manager...................................................93To download directory files........................................................................94Unzip UNIX/Linux files with Info-Zip..........................................................94

Maintaining your installation 97Chapter 6

Upgrading the software..............................................................................98Maintenance installation.......................................................................98Migration installation.............................................................................99Upgrading cleansing packages..........................................................100

Uninstalling the software from UNIX........................................................101


Contents

Index 103


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.

• 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

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 document


Preparing to Install1 Pre-installation overview

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

includes specific version and patch-level requirements for databases,applications, web application servers, web browsers, and operating systems.

Before you can install SAP BusinessObjects Data Services, the 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.

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

Note:If your servers are firewalled, you may need to open the necessary ports toallow the client components to communicate with the servers.


1Preparing to InstallPre-installation overview

User permission requirements

To successfully install SAP BusinessObjects Data Services on UNIX, theuser running the setup program must have the permissions listed in the tablebelow.

Required permission(s)Category

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.

If your design, test, or production environment uses tightly controlled root-leveladministration, it's recommended that you install the Job Server while loggedon as a user without root-level access. Installing the Job Server withoutroot-level access ensures that root-level access is not required to administerfiles and processes created by the Job Server.

Only a few administration functions require root-level access as describedin the following table:

Required Permission(s)Function

Permission to access cronScheduling jobs

Autostart configuration edits need to be madeby a user with system-level authority.

Automatically restarting theJob Service on restart

Cron service

SAP BusinessObjects Data Services schedules UNIX-based jobs by usingthe UNIX cron utility. If cron security uses cron.allow, the account thatstarts the Job Server must have an entry in the cron.allow file.



cron.allow locationOperating system

/var/adm/cron/cron.allowHP-UX

/var/adm/cron/cron.allowAIX

/usr/lib/cron/cron.allowSolaris

/etc/cron.allowLinux

For more information, see your cronman pages.

Installing the Job Server without access to cron causes the following JobServer behavior:

• Job Server can operate normally.• The software cannot schedule a job to run on the Job Server.• You can manually execute and monitor jobs from the Designer.

Kernel parameters and user resource limits

It's recommended that you use the following kernel parameters and userresource limits when installing SAP BusinessObjects Data Services on UNIXplatforms.

Note:Besides the following recommendations, there is a requirement for a specialscenario. If you intend to use the USA Regulatory Address Cleanse transformwith caching of DPV and LACSLink directories, you must set your UNIXoperating system's Data Segment Size limit to Unlimited. This systemparameter must be set before starting the software.

HP-UX for Itanium 64-bit kernel configuration

For installations on HP-UX for Itanium 64-bit systems, it's recommended thatyou use the following kernel configuration:



CommentsValueKernel parame-ter

If you receive Cannot createthread run-time error message fromthe job, increase this value.

256max_thread_proc

Default value of 2048 is appropriateto use.

2048maxfiles

Enter the swap space configured onyour system.

0X400000000maxdsiz_64bit

Default value of 256 MB is appropriateto use.

0X10000000maxssiz_64bit

Default value of 1 GB is appropriateto use.

0X40000000maxtsiz_64bit

Default value of 256 MB is appropriateto start using. However, if you expectmany jobs to run at the same time,increase this value.

256maxuprc

This value gets calculated by HP-UXautomatically.

((16*(NPROC+16+MAXUSERS)/10)+32+2*(NPTY+NSTRPTY+NSTRTEL)

nfile

Default value of 4200 is appropriateto use.

4200nproc

AIX user resource limits

For installations on AIX systems, it's recommended that you use the followinguser resource limits. You can display these settings by running the ulimit-a command from your SAP BusinessObjects Data Services installationlogin.



CommentsValueUser resource limit

At least 2 GB4194302file (blocks)

unlimiteddata (kbytes)

At least 500 MB512000stack (kbytes)

At least 2 GB2097151memory (kbytes)

At least 20002000nofiles (descriptors)

Solaris user resource limits

For installations on Solaris systems, it's recommended that you use thefollowing user resource limits. You can display these settings by running theulimit -a command from your SAP BusinessObjects Data Services login.


unlimitedfile (blocks)

unlimiteddata (kbytes)

At least 8 K8192stack (kbytes)

unlimitedtime (seconds)

At least 1 K1024nofiles (descriptors)

unlimitedcoredump (blocks)

Unlimited, at least 2GB

unlimitedvmemory (kbytes)

Linux user resource limits

For installations on Red Hat Linux systems, it's recommended that you usethe following user resource limits. You can display these settings by runningthe ulimit -a command from your SAP BusinessObjects Data Serviceslogin.




unlimitedfile (blocks)

unlimiteddata (kilobytes)

At least 10 MB10240stack (kilobytes)

unlimitedtime (cpu-seconds)

1024nofiles (descriptors)

unlimitedcoredump (blocks)

unlimitedmemory (kilobytes)

4lockedmem (kilobytes)

7168processes

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)

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



DescriptionComponentFeature category

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.

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

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 22• Using the Repository Manager on page 63• 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.

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:


Preparing to Install1 Repository database requirements and preparation

• IBM DB2• 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 63

To set up a database account

To administer the repository database, you need to set up a databaseaccount. Complete the steps listed below 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• MySQL• Oracle


1Preparing to InstallRepository database requirements and preparation

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

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.

Related Topics• To prepare your database on page 27



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

The MySQL DSN should be set in $ODBCINI. During installation, input$ODBCINI. If $ODBCINI has been set before installation, the default valueis shown.

• Username• Password

Note:

• ODBC driver version 3.51.22 is recommended for use with MySQL.• For 64-bit UNIX platforms, the unixODBC driver is also required. If

unixODBC is not installed to the default location (/usr/lib),$DS_LIB_PATH must contain the path to the unixODBC driver location.The installation program adds $DS_LIB_PATH to the library pathautomatically if it is set.


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.


Tip:Export the ORACLE_HOME environment variable prior to installation. Theinstallation program will add this variable to the environment configuration,even if you choose to skip repository configuration during installation.


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.



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

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 25• MySQL database setup requirements on page 26• Oracle database setup requirements on page 26• Sybase database setup requirements on page 27



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.

Ensure that your ODBC connection entry in theodbc.ini file contains the line charset = 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• Web Tier Components• Message Client Components• Documentation Components


1Preparing to InstallInstallation scenarios

By default, Tomcat is installed as the web application server. You can alsochoose to use your own 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 14• 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 8• Beginning your installation on page 36• Using the Repository Manager on page 63• Using the Server Manager on page 66• Using the License Manager on page 77


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 50


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 ./install.sh. After the "Welcome"screen is displayed, press Enter 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 8

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. Press Y to accept the License Agreement.

You cannot continue unless you accept the License Agreement.

3. Press Enter to continue the installation.


Standard Installation2 Beginning your installation

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.The default location is $HOME/businessobjects.

Restriction:The installation location 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:The installation program creates an environment variable named$LINK_DIR for the dataservices directory created at this path. $LINK_DIRis used throughout the software documentation to refer to this directory.


To enter a product keycode

At the "Enter Product Keycode" screen, provide a product keycode for yourSAP BusinessObjects Data Services installation.

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


To select which features to install

At the "Select Components" screen, choose which components to install.

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


2Standard InstallationBeginning your installation

DescriptionFeature catego-ry

Includes the Job Server, Access Server, AddressServer, Technology Interfaces, and other adapters.

All server components install by default unless dese-lected.

Server 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

2. When you have made your component selections, pressEnter 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.• Use an existing database server• Skip configuration


Standard Installation2 To select a repository

You 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. Press Enter to continue.


To configure an existing database server

The "Local Repository Database Type" screen appears if you chose to usean existing database server as your repository for the new SAPBusinessObjects Data Services installation. At this screen, specify theconnection information for the database where the repository will be created.

1. Select a database type and press Enter to continue.Depending on your database type selection, corresponding input fieldsare displayed.

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


2Standard InstallationTo select a repository

System vari-able

Required informationDatabase type

$DB2DIRDB2 client location

DB2 alias name

DB2

$ODBCINIFull path of odbc.iniMySQL

$ORACLE_HOMEOracle client location

Oracle TNSNAME identifier

Oracle

$SYBASESybase client locationSybase ASE

Tip:The fields displayed support a maximum of 70 characters. However, ifthe required system variables have been exported prior to starting theinstallation setup program, they will be displayed in each field as $variable_name. By exporting the variables prior to installing, you can usevalues longer than 70 characters.

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

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

5. Press Enter to continue.6. If you are upgrading from an existing SAP BusinessObjects Data Integrator

or SAP BusinessObjects Data Services repository, select Upgrade tokeep and upgrade the existing repository. If you are creating a newrepository, 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.


Note:The SAP BusinessObjects Data Services installation setup programconfigures only the database connectivity for the repository, not additional


Standard Installation2 To select a repository

source or target databases. If you need to access other systems as databasesource or targets, you can configure them after installation.

Related Topics• Configuring additional database connectivity on page 56

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. Press Enter to continue.3. If you chose to configure a new Job Server, specify a name and port

number for the new server in the Job Server name and Job Server portfields.The default Job Server port is 3500.

4. If you need to enable SNMP support, select Enable SNMP.5. If you need to change the runtime resources for the Job Server, click Job

Server advanced configure.The Job Server details screen is displayed. Make any necessaryconfiguration changes.


Related Topics• To configure Job Servers on page 69

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:


2Standard InstallationTo configure a Job Server

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-timeand 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. Press Enter to continue.3. If you chose to configure a new Access Server, specify a directory and

port number for the new server in the Access Server directory andAccess Server port fields.The default directory for the Access Server is LINK_DIR/bin/AccessServer_1 and the default port is 4000.

Restriction:The Access Server directory path cannot exceed 70 characters.


Related Topics• To configure Access Servers on page 73

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 an existing web application server• Install Tomcat application server


Standard Installation2 To select a web application server

2. Press Enter to continue.3. To use your current Web application server, choose your server type from

the drop-down list provided.

Tip:You can configure the server during the current installation process. 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 performthe 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.



2Standard InstallationTo select a web application server



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

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 the/bobje/tomcat/conf directory at the same level as $LINK_DIR.

To configure an existing Web application server

The "Select a Web Application Server to Deploy to" screen is displayedduring installation after you specify an existing server in the "Select WebApplication Server" screen.

1. Select the type of web application server that you want to use.2. Press Enter to continue.3. Specify the required configuration information for your existing web

application server.


Standard Installation2 To 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, /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, /bea/weblogic92/samples/domains/wl_server).

WebLogic 9

WebSphere 6.1


2Standard InstallationTo 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, /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, press CTRL + B. All entries are retained;you do not need to re-enter all the information.

Note:If you are running the ./install.sh program from the command line,and have the -w filename parameter switch enabled, this is the point


Standard Installation2 To start the installation

at which you can cancel the installation process to have the .ini filewritten with all the installation parameter information. This .ini file canthen be used in silent and scripted installations.

• Press Enter to start the final installation process.

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


2Standard InstallationTo start the installation


Standard Installation2 To start the installation

Silent Installation

3

Overview of silent installationThere is a method for running SAP BusinessObjects Data Servicesinstallations for UNIX directly from the command line:

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

Scripted installation can be used to automate installations across multiplemachines and requires you to specify 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. PressCTRL + X to abort the installation once you reach the final screen in theinstallation program.

To create a response file

1. Mount the device that contains the installation files.

Note:If you run the installation script without copying the files to a temporarylocation, you will be prompted to specify a temporary location for theinstallation.

2. In the command line, type ./install.sh -w and the file path for the responsefile you want to generate. For example:


Silent Installation3 Overview of silent installation

./install.sh -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. Press CTRL + X to abort the installation once you reach the "StartInstallation" screen in the installation program.

You can access the response file from the directory you specified in step 2.

To run a scripted installation

You need to have a response file residing in a known directory. 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. Mount the device that contains the installation files.

Note:If you run the installation script without copying the files to a temporarylocation, you will be prompted to specify a temporary location for theinstallation.

2. In the command line, type the following information:

install.sh -r response.ini -i /installDirectory/ -s /cd/setup/DISK_1/

• -r filename Specifies the name of the response file you want theinstallation program to read for installation parameters.

• -i INSTALLDIR Specifies the installation directory for the scriptedinstallation.

• -s SOURCEDIR This optional command specifies the location of thecd directory. The source directory must point to the location of DISK_1in the installation CD. If not specified, the CD directory setting in theresponse file will be used.

3. Press Enter to launch the installation.


3Silent InstallationPerforming a scripted installation


Silent Installation3 Performing a scripted installation

After Installation

4

Setting environment variablesThe Job Server requires that certain environment variables be set up. To setup these variables, users who run or administer Job Servers must run ascript (al_env.sh).

Run this script with the syntax required by your environment. For example:

$ cd $LINK_DIR/bin/$ . ./al_env.sh

You can also add this command to your login script so that it is alwaysconfigured. For example, add the following line to the .profile:

. $LINK_DIR/bin/al_env.sh

If the script fails to run, no error messages appear. To make sure that thevariables' values are properly set, check one or more of the following.

Tip:Use the echo command to verify environment variable settings.


After Installation4 Setting environment variables

DetailsVariable

SAP BusinessObjects Data Services installationdirectory (set by the installation program)

$LINK_DIR

For HP-UX. Must include $LINK_DIR/bin and thelocation of the database libraries.

If you want to use a 64-bit Oracle client,$LINK_DIR/bin must be listed before any 64-bitOracle shared library path.

$SHLIB_PATH

For Solaris or Linux. Must include $LINK_DIR/binand the location of the database libraries.


$LD_LIBRARY_PATH

For AIX. Must include $LINK_DIR/bin and thelocation of the database libraries.


$LIBPATH

Required for an Oracle source, target, or reposito-ry.

$ORACLE_SID

Required for an Oracle source, target, or reposito-ry.

If you want to use a 64-bit Oracle client, this mustpoint to the 64-bit Oracle installation.

$ORACLE_HOME

Required for a DB2 source, target, or repository.$DB2INSTANCE

Required for a DB2 source, target, or repository.$DB2DIR


4After InstallationSetting environment variables

DetailsVariable

Required for a Sybase ASE source, target, orrepository.

$SYBASE

Required for a Sybase ASE source, target, orrepository.

$SYBASE_OCS

Required for an ODBC source or target.$ODBCINI

Must include $LINK_DIR/bin and databasehome/bin.

$PATH

If the variable settings are not properly configured and you start any SAPBusinessObjects Data Services utility, error messages will appear to indicatethat database server files are missing.

If you see such an error, verify that al_env.sh contains commands to setthe appropriate database home locations. Run al_env.sh for the accountused by the Job Server, or start the Job Server using an account that hasall necessary environment variables defined in its .profile.

Configuring additional database connectivity

By default, the SAP BusinessObjects Data Services installation setup programconfigures database connectivity for the repository only. To access otherdatabase systems as sources and targets in your jobs, you need to add theappropriate configuration information to the al_env.sh file. The followingsections detail the information required for each database type.

Note:The following examples are for the Linux platform and useLD_LIBRARY_PATH. For AIX or HP-UX platforms, use LIBPATH orSHLIB_PATH respectively.


After Installation4 Setting environment variables

Attunity

export NAVROOT=your_Attunity_root_pathexport LD_LIBRARY_PATH=$NAVROOT/lib:$LD_LIBRARY_PATHexport PATH=$PATH:$NAVROOT/bin

DB2

export LD_LIBRARY_PATH=your_DB2_client_path/sqllib/lib:$LD_LIBRARY_PATH

ODBC

The syntax for an ODBC connection varies depending on the type ofdatabase. For example, for a MySQL ODBC connection:

LD_LIBRARY_PATH=MySQL_Driver:unixODBC_library_path:$LD_LIBRARY_PATHexport ODBCINI=your_odbc.ini_file

Oracle

export ORACLE_HOME=your_Oracle_homeexport LD_LIBRARY_PATH=$ORACLE_HOME/lib:$ORACLE_HOME/network/lib:$LD_LIBRARY_PATH

Teradata

export LD_LIBRARY_PATH=/usr/odvc/drivers:/usr/odbc/lib:/opt/teradata/client/transporter/lib:$LD_LIBRARY_PATHexport PATH=/opt/teradata/client/bin:/opt/teradata/client/transporter/bin:$PATHexport COPERR=/opt/teradata/client/libexport ODBCINI=your_odbc.ini_file

Sybase ASE

For Sybase ASE version 12.5 on UNIX platforms, you must first run a scriptto generate the shared bulk load library. By default, the script is installed toLINK_DIR/AWSybase/buildlbk.sh. For additional information, seeLINK_DIR/AWSybase/readme.txt.


4After InstallationSetting environment variables

Starting services automaticallyTo start Job and Access Servers automatically when the server restarts, youmust install the actaservices script with root privileges.

Run the $LINK_DIR/bin/autostrt.sh script:

# cd $LINK_DIR/bin/# autostrt.sh $LINK_DIR

High-availability supportIf you run SAP BusinessObjects Data Services on AIX and you have HighAvailability Clustered Multi-Processing (HACMP) software version 4.4.0, useHACMP software to minimize downtime of your system. The software includesstart and stop scripts that support HACMP software.

About HACMP software

HACMP software makes applications and software systems highly available,restoring essential services when a system component or application fails.To support HACMP software, you replicate software and hardware systemsto guarantee backup of essential services. Within HACMP software, youdefine each complete system as a resource group. When a component failsin a resource group, HACMP software quickly restores essential services bystarting the failed system on an alternate computer, called a node, or groupof networked computers, called a cluster.

To use HACMP software to make a system highly available:

1. Define the system as a resource group (a logical group that the HACMPsoftware and AIX operating system manages).

2. Install the necessary components to support the system on duplicatehardware systems, creating clusters or nodes that can support identicalservices that the system processes.

3. Define takeover relationships that determine which cluster or nodesupports the resource group at any given time. There are three types oftakeover relationships:Cascading


After Installation4 Starting services automatically

Clusters are listed along with a priority rank. Control of the resourcegroup goes to the active cluster with the highest priority ranking.Control can change due to failure or to the reactivation of a clusterwith a higher priority rank.

ConcurrentMultiple clusters support the resource group at the same time.

RotatingClusters are listed along with a priority rank. Control of the resourcegroup goes to the active cluster with the highest priority ranking.Control only changes due to the failure of a cluster.

Using the software with HACMP

SAP BusinessObjects Data Services contains start and stop scripts thatsupport HACMP software. These scripts run when a new cluster takes controlof the software resource group. The start script:

• Identifies jobs scheduled before the previous cluster failed and launchesthose jobs in recovery mode

• Identifies jobs scheduled to start during cluster down time and launchesthose jobs

• Synchronizes the cron file on the new cluster with the cron file on theprevious cluster

When using the software with HACMP, you should be aware of severalrequirements and restrictions:

• There can be no single point of failure, or the additional availabilityprovided by HACMP is compromised.

• You must use the same user ID on all clusters where you install thesoftware.

• The database systems that support jobs—the repository, sources, andtargets—must also be highly available.

• You cannot use a concurrent takeover relationship for the softwareresource group.

• You can use HACMP only with batch jobs.• You must enable automatic recovery for all scheduled jobs.• You must also enable the recurrent option for all scheduled jobs.


4After InstallationHigh-availability support

To use the software with HACMP

1. Install the Job Server on a file system in the shared volume group froma single cluster node.

2. On each cluster node, define the same mount point for the file system.SAP BusinessObjects Data Services and its configuration is madeavailable for the rest of the cluster nodes.

3. Copy the start and stop scripts (acta_start.sh and acta_stop.sh) fromthe $LINK_DIR/hacmp directory to the HACMP scripts directory on eachof the cluster nodes.

4. In the HACMP software:a. Define the software as a resource group (a logical group that the

HACMP software and AIX operating system manages).b. Define takeover relationships that determine which cluster or node

supports the software resource group at any given time.c. Designate the start and stop scripts as the start and stop scripts for

the software resource group.

5. Configure the software to use HACMP.


After Installation4 High-availability support

To configure the software to use HACMP

1. Run the Server Manager.

$ cd $LINK_DIR/bin/$ . ./al_env.sh$ ./svrcfg

Note:The second command sets required environment variables before./svrcfg starts the Server Manager.

The Server Manager main screen appears.

2. Enter 1 and stop the Job Service.3. Enter 7 to configure HACMP.

The HACMP configuration screen appears.

------------------------------------------------------------------** Current HACMP Configuration for Data Services ResourceGroup **------------------------------------------------------------------

Service IP Label Domain Name---------------- -----------aixserver1

------------------------------------------------------------------

e: Edit Configuration y: Re-sync all repos q: Quit

4. Configure HACMP.


4After InstallationHigh-availability support

DescriptionCommand

Specifies the Service IP Label used while configuringSAP BusinessObjects Data Services' resource group.

When you finish configuration, the software resynchro-nizes all repositories and the configurations for the SNMPagent with the current Service IP Label and domain name.This means:• The Job Service must be stopped prior to editing the

configuration.• You must re-add repository connections to the Man-

agement Console, reconfigure real-time services andadapters, and reschedule batch jobs.

E

Manually resynchronizes all repositories.

Note:Resynchronizing all repositories is not required unless yousee an error message after editing the configuration. Forexample, a repository might not get updated to use theconfigured Service IP Label if the associated database isunavailable. After correcting the problem, you can use thisoption to resynchronize the repository.

Y

5. Enter q and then x to exit the Server Manager.

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.

Note:For custom Data Cleanse dictionaries you plan to create using UniversalData Cleanse, you do not need to install a cleansing package. You can use


After Installation4 Installing cleansing packages



the 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 ./install_console from the cleansing package installationdisc or downloaded location.If you are using a system that has XWindows, you can run the installationprogram in graphical mode by running ./install_gui.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 29• Using the Repository Manager on page 63

Using the Repository ManagerYou can use the executable called repoman (stored in the $LINK_DIR/bindirectory) to create or update repositories after SAP BusinessObjects DataServices installation. Specify parameters using a command prompt.

$ ./repoman

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-t<Type> : Repository type: local, central,

profiler, cp (cleansing package)-b : Check database connectivity-c : Repository create-u : Repository upgrade-v : Repository version-d : Show details-a : Repository security-l : Create log file-z : Create error file

(local, central, profiler modes)-m<Operation> : Cleansing package mode operations-z<ZipFile> : Source zip file

(cleansing package mode)


4After InstallationUsing the Repository Manager

-p<PortNumber> : Database port number(cleansing package mode)

For example:

./repoman -Usa -P -NDB2 -SServer -QJake -c -tcentral -d

or

./repoman -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 Oracle: TNSNAME defined in tnsnames.ora

• 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:• DB2• Oracle• Sybase• MySQL

This parameter is required for all database types.

-N

Repository database name

This parameter is required only for Sybase ASE, and in cleansingpackage mode for MySQL.

-Q


After Installation4 Using the Repository Manager

DescriptionFlag

Repository type:• local• central• profiler• cp (cleansing package)

-t

Operation mode: Creates repository-c

Operation mode: Upgrades repository-u

Operation mode: Gets repository version-v

Operation mode: Shows details-d

Central repository security-a

Overwrite existing repository-o

Cleansing package mode operations:• VerifyDB

Verifies the cleansing package database connection

• Create

Loads zip file data into the database

• GetVersion

Compares the version information stored in the zip file withthe database

• GetVersionInfo

Reads the dictionary name and version information from thezip file

-m

Cleansing package source zip file name-z

Database port number-p


4After InstallationUsing the Repository Manager

Note:For cleansing package mode, only the following parameters are required:

-U, -P, -S, -N, -Q (MySQL only), -t, -m, -z, -p (MySQL only)

Other parameters (-c, -u, -v, -d, -a, -o) are not applicable for cleansingpackage mode.

Note:To upgrade a cleansing package, first export any dictionary changes usingthe Designer. After loading the new cleansing package, reapply the dictionarychanges with the bulk load feature. Additionally, it's recommended that youuse the new rule file included with a new cleansing package. Using the newrule file with an older dictionary may cause unpredictable results.

Related Topics• Upgrading cleansing packages on page 100

Using the Server ManagerUse the Server Manager to create, edit, or delete Job Servers and AccessServers after installation.

The Server Manager displays the following:


After Installation4 Using the Server Manager

Job Server information

DescriptionOption

This name uniquely identifies the Job Server. The JobServer name cannot be changed.

Server name

The port number is a TCP/IP port that the Job Server usesto receive commands from the Designer and an AccessServer. If a computer hosts multiple Job Servers, each JobServer must have a unique port number. Choose a portnumber that is not used by another process on the comput-er. It's recommended that you use 3500. If you are unsureof which port number to use, use the default port numberand increment it for each additional Job Server you config-ure.

TCP/IP port num-ber

If this computer hosts adapters or the SNMP agent, youmust designate one (and only one) Job Server to supportthem. Once a Job Server is set to support adapters andSNMP communication (a port is entered and saved), it ismarked on the Job Server Configuration screen with thislabel.

Supports adapterandSNMPcommu-nication on port

This option enables SNMP support on the Job Server. Afterone Job Server per computer is set as the one supportingadapters and SNMP, it and additional Job Servers can beenabled for SNMP.

Enable SNMP

Run-time resource information

DescriptionOption

This directory contains the pageable cache that the softwareuses for memory-intensive operations and for file transfertypes when Automatic is specified in the Data_Transfertransform.

Pageable cachedirectory

The software uses this starting port number for peer-to-peercommunication between data flows or sub data flows thatare running on different Job Servers. The default is 1025.

Start port

Access Server information


4After InstallationUsing the Server Manager

DescriptionOption

Server number This sequence number uniquely identifies the AccessServer on this machine. The Access Server number cannotbe changed.

The directory containing Access Server information.Directory

This port number is used to communicate between theAccess Server and the Administrator. The default is 4000.

Communicationport

Additional parameters used by the Access server

View Access Server parameters by typing AL_AccessServer at the command line. For more information,see "Real Time Performance" in the Management Con-sole: Administrator Guide.

Parameters

Enter Y to activate the Access Server.Enable

Job service information

DescriptionOption

The directory containing AL_JobService information.Service exe-cutable path

Status of the SAP BusinessObjects Data Services service:• Running• Not running

Status

SMTP Server information

DescriptionOption

The name or IP address of the SMTP server (for example,mail.company.com)

Server

The e-mail address that will appear in the From field of thee-mail.

Sender



To configure Job Servers





2. Enter 3 to configure a Job ServerThe Job Server information screen appears.

------------------------------------------------------------** Current Job Server information **------------------------------------------------------------

S# Job Server Name TCP Port Enable RepositorySNMP Information

-- --------------- -------- ------ ----------1* Server1 19111 Y USR1@SVR1_ORACLE2 Server2 19112 N USR2@SVR1_ORACLE

*:JobServer <S1> supports adapter and SNMP communicationon port:19110

------------------------------------------------------------

c: Create a new JOB SERVER entry a: Add a REPO to jobserver

e: Edit a JOB SERVER entry y: Resync a REPOd: Delete a JOB SERVER entry r: Remove a REPO from

job serveru: Update a REPO s: Set default REPOq: Quit

The repository information is displayed as User@DatabaseConnection__DatabaseType. For example, if the repository user is DSXI32,the repository is an Oracle database, and the database connection nameis DSORCL, the repository information is shown as DSXI32@DSORCL_ORACLE.

3. Configure or delete a Job Server.



DescriptionCommand

Creates and specify details for a new Job Server entry.c

Edits an existing Job Server entry.• To enable SNMP for a job server, choose Y when

prompted with the following question:

Do you want to Enable SNMP for this JobServer?

• To disable SNMP for a job server, choose Y whenprompted with the following question:

Do you want to Disable SNMP for this JobServer?

e

Deletes an existing Job Server entry.d

Adds a repository connection to an existing Job Server.a



DescriptionCommand

Removes a repository connection from a Job Server.r

Sets the default repository connection for a Job Server.s

Resynchronizes a Job Server configuration with arepository.

You must resynchronize your Job Server and repositorywhen:• You have uninstalled SAP BusinessObjects Data

Services and are reinstalling the same version withoutcreating a new repository.

• You have created a new repository using the Reposi-tory Manager after installing the software.

If you resynchronize your Job Server configuration witha repository, you must re-add a connection for thisrepository to the Administrator. For more information, seethe Management Console: Administrator Guide.

y

When you add or edit a repository connection, you must specify thedatabase connection information:• For Oracle - the TNSNAME specified in tnsnames.ora

• For MySQL - the DSN entry specified in odbc.ini

• For Sybase - the Sybase server name specified in the Interfaces file• For DB2 - the DB2 instance name

Note:The UNIX Server Manager does not prompt for the repository passwordexcept when creating a Job Server or adding a repository. To update therepository password in the DSConfig.txt file, enter u. All options usethe updated password from DSConfig.txt file.




To configure run-time resources





2. To configure run-time resources, enter 4.The run-time resource information screen appears.

--------------------------------------------------------------** Current Runtime Resource information **--------------------------------------------------------------

Pageable Cache Directory Start Port End PortLINK_DIR\Log\PCache 1025 32767

e: Edit Runtime Resources q: Quit

Enter Option:

3. To edit the run-time resource configuration, enter e.4. Accept the default Pageable Cache Directory, or specify a different

location.

Restriction:The Pageable Cache Directory path cannot exceed 70 characters.

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 of

space required, consider factors such as the number of concurrentlyrunning jobs or data flows and the amount of pageable cache requiredby each concurrent data flow.



• Exists on a separate disk or file system from the SAP BusinessObjectsData Services system and operating system.

• Limits the disk space that data flows consume. The pageable cacheuses all available disk space on the file system that contains thepageable cache directory. To limit the disk space that data flowsconsume, create a file system with a limited size. Use the new filesystem as the pageable cache directory.

The software uses this directory in the following situations:• For pageable caching, the default cache type for data flows. For more

information, see the Performance Optimization Guide.• When the software selects a file transfer type and Automatic is

specified in the Data_Transfer transform.

5. Change the values for Start port and End port to restrict the number ofports used by the software for peer-to-peer communications. The defaultvalues are 1025 and 32767, respectively.The software uses these ports for peer-to-peer communications whensending data between data flows or sub data flows that are running ondifferent Job Servers.


Related Topics• Performance Optimization Guide: Using grid computing to distribute dataflow execution

To configure Access Servers





2. Enter 4 to configure an Access Server.



The Access Server information screen appears.

--------------------------------------------------------------** Current Access Server information **--------------------------------------------------------------

S# Directory Communication Port Enable-- --------------- ------------------ ----------1 export/AStest1 7897 Y2 export/AStest2 7898 Y

c: Create a new access server entry e: Edit an accessserver entryd: Delete an access server entry q: Quit

3. Configure or delete an Access Server.



DescriptionCommand

Creates a new Access Server.

Enter the directory, port numbers, and parameters, andindicate whether you want to enable the access server.

You can configure more than one Access Server on thesame computer, but each must have separate ports. Ifyou enter a port number already in use, an error messageappears.

Note:Access Server parameters can be viewed by typing AL_AccessServer at the command line. For more information,see "Real Time Performance" in the Management Console:Administrator Guide.

c

Edits an existing Access Server.

Enter the number of the Access Server you want to edit.

e

Deletes an existing Access Server.

Enter the number of the Access Server you want to delete.

Note:When you delete an Access Server, all Access Servers arestopped. When you exit the Server Manager, the remainingAccess Servers restart.

d


To start or stop the service

The SAP BusinessObjects Data Services service (AL_JobService) is adaemon associated with $LINK_DIR that starts locally-configured Job Serversand Access Servers and then monitors them and attempts to restart them ifthey are not running.



After exiting the Server Manager, AL_JobService automatically retrieves anychanges made to Job Servers or Access Servers. You do not need to restartAL_JobService.





2. Enter 1 to control the service (Job service).3. Start or stop the Job service.

• Enter s to start the Job service.• Enter o to stop the Job service.


To start or stop the Address Server


$ cd $LINK_DIR/BIN/$ . ./al_env.sh$ ./svrcfg

Note:The second command sets required environment variables before runningthe Server Manager.


2. Enter 2 to control the Address Server.3. Start or stop the Address Server.

• Enter s to start the Address Server.• Enter o to stop the Address Server.




To configure SMTP email

The Server Manager can be used to specify SMTP server settings for thesmtp_to email function. For more information, see "To define and enablethe smtp_to function" in the Reference Guide.

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.

Setting up License Manager

Before you can use License manager, you need to set the environmentvariable BOE_REGISTRYHOME. Although you can use a different setting, it'sstrongly recommended that you use /var/opt for BOE_REGISTRYHOME.

If you use Bourne shell, add product entries to your .profile or .login file.

BOE_REGISTRYHOME=/var/opt ; export BOE_REGISTRYHOME

If you use C shell (Berkeley), add product entries to your .cshrc file.

setenv BOE_REGISTRYHOME /var/opt


4After InstallationUsing the License Manager

To start License Manager

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

• Run LicenseManager from the command-line without specifying anyoptions.

$ cd $LINK_DIR/bin$ ./LicenseManager

Note:If X-Windows is not available, you can use License Manager incommand-line mode.

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

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

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.


After Installation4 Using the License Manager

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


4After InstallationUsing the License Manager

Syntax

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

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


After Installation4 Using 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]

Controlling theTomcat application serverSAP BusinessObjects Data Services includes shell scripts to start and stopthe packaged Tomcat application server.

To start the Tomcat application server, run tomcatstartup.sh with thesyntax required by your environment. For example:

$ cd $LINK_DIR/$ ../bobje/tomcatstartup.sh

To stop the Tomcat application server, run tomcatshutdown.sh with thesyntax required by your environment. For example:

$ cd $LINK_DIR/$ ../bobje/tomcatshutdown.sh


4After InstallationControlling the Tomcat application server

Troubleshooting installation problems

Designer-Job Server connection

If the computer on which the Designer is running is unable to connect to thecomputer on which the Job Server is running, then verify that you can ping,by name, from the Designer's computer to the Job Server's computer. If youcannot ping by name, contact your local network administrator.

Check how long netstat -a takes to run and expect at least that amountof time to configure SAP BusinessObjects Data Services services.

Server Manager problems

If you encounter any of the following situations, reset all SAP BusinessObjectsData Services processes:

• Five to ten minutes after starting the Server Manager, you still receivemessages that the AL_JobService is in active mode.

• After starting the Server Manager, the menu does not appear.• The AL_JobService log states that the server configuration is active when

the Server Manager is not running.• Job Servers, Access Servers, or the AL_JobService continue to run after

you stop the Job service.

To reset all processes

1. Obtain the process ID of AL_JobService.

$ ps -fu UnixLoginId

2. Kill the AL_JobService process.

$ kill -15 AL_JobServicePID


After Installation4 Troubleshooting installation problems

3. Wait at least 30 seconds for the AL_JobService and other processes toshut down. This time period might be longer if there are many instancesof Job Servers and Access Servers in the installation.

4. Verify that the AL_JobService, al_jobserver, and AL_AccessServerprocesses were stopped.

$ ps -fu UnixLoginId

5. Kill any processes that still exist.• For each instance of the process al_jobserver:

$ kill -9 al_jobserverPID

• For each instance of the process AL_AccessServer:

$ kill -9 AL_AccessServerPID

• For the process AL_JobService:

$ kill -9 AL_JobServicePID

• For SNMP:

$ kill -9 al_snmpPID

6. Remove the file $LINK_DIR/log/AL_JobService.PID

7. If the svrcfg exists, kill the process.

$ kill -9 svrcfgPID

Management Console problems

Common Management Console and web application-related installationproblems include:

• The Management Console login page cannot be found.


4After InstallationTroubleshooting installation problems

This problem can occur when the web application service is not runningor needs to be restarted. Restart the web application server.

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

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.

Memory issues

As with any computer on which a Job Server is running, reserve enoughspace for the SAP BusinessObjects Data Services engine to cache tables



and extract all data necessary to perform hierarchy flattening, sorts, orlookups.

If you see memory-related errors, consider changing the following systemsettings:

• Maximum virtual memory per process

If this setting is low enough to interfere with software operations, youmight see messages describing low-memory errors.

• Maximum number of files per process

If this setting is low enough to interfere with software or database serveroperations, you might see messages describing file open errors.

• Maximum stack size per process

If this setting is low enough to interfere with software operations, youmight see messages describing segmentation- violation errors.

• Maximum data segment size per process

If this setting is low enough to interfere with software operations, youmight see messages describing segmentation-violation errors.

For more information, see your UNIX system administration documentation.

Threading issues

If you are running the Job Server on the HP-UX platform and you receive anerror that reads Cannot Start Thread, check the Kernel Parameter(max_thread_proc) on HP-UX. Set the value to 256 on HP-UX for PA-RISC32-bit and 1024 on HP-UX for Itanium 64-bit. If you receive additional errors,contact Technical Customer Assurance.


4After InstallationTroubleshooting installation problems



Directory Data

5

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 Data5 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


5Directory 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 Data5 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 files

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


5Directory 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

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 inLINK_DIR/DataQuality/reference_data. If you place your directories ina different location, you must update your substitution file.

Note:Installing Global Address Cleanse directory files on file servers may lead tospeed loss and lock problems. The target directory name may contain blankcharacters, but no umlauts.


Directory Data5 Where to copy directories

Copy International directories files to a non-defaultlocation

If you use the EMEA engine or Global Suggestion Lists and store your datadirectories in a location other than the default (LINK_DIR/DataQuality/reference_data), do the following:

1. Stop any dataflows 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 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.

Related Topics• To start or stop the Address Server on page 76

To install and set upDownloadManagerBefore you can download directory files, you need to install and set upDownload Manager.


5Directory DataTo install and set up Download Manager

To install and set up Download Manager:

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

2. Select Downloads.3. Select Download Basket.4. Click the Get Download Manager button.5. Follow the steps to install and set up the Download Manager.

To download directory 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.

Unzip UNIX/Linux files with Info-ZipThe steps listed here describe how to install the zipped directories usingInfo-Zip for UNIX/Linux. If you use a different unzip tool, see the unzipprocedure included with that tool.


Directory Data5 To download directory files





1. Copy the zipped directory files manually from the CD to the location whereyou keep your directories.

2. Type unzip filename.zip -d outputfolder.For ZIP4US, type unzip us_dirs_2004.zip -d /BusinessObjects/BusinessObjects Data Services/DataQuality/reference_data).

3. For each required file, repeat steps 1 and 2.


5Directory DataUnzip UNIX/Linux files with Info-Zip


Directory Data5 Unzip UNIX/Linux files with Info-Zip

Maintaining your installation

6

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.

Maintenance installation

When the SAP BusinessObjects Data Services installation program detectsthat you are installing to the same location as an existing installation, it allowsyou to perform a maintenance installation.

A maintenance installation differs from a standard installation in several ways:

• The installation program automatically detects and retrieves the firstexisting base keycode.

• The installation program automatically detects which components areinstalled, and selects them for the maintenance installation. You can stillchoose to change the installed components, however.

Note:If the server components are already installed, their configuration screenswill be skipped and the existing configuration is retained. Job Serversand Access Servers will still be working after the update. Web applicationsmust always be re-deployed.

• Log information is preserved. The LINK_DIR/log directory is not removed.• The software binaries are updated to the new version.

Limitations

When performing a maintenance installation, there are several limitations:

• The installation program can only stop Job Server, Access Server, JobService, and packaged Tomcat processes. If you use other processes inyour installation, such as the Address Server, stop them before startinga maintenance installation.

• Maintenance installation removes all deployed web applications, as wellas the packaged Tomcat application server, if it is installed. If you have


Maintaining your installation6 Upgrading the software

third-party web applications deployed to the packaged Tomcat applicationserver, undeploy them before starting a maintenance installation, andre-deploy them after installation has finished.

Migration installation

When the SAP BusinessObjects Data Services installation program detectsthat you are installing to the same location as an existing installation, it allowsyou to perform a migration installation.

The installation program allows a migration installation under the followingconditions:• The specified installation location does not contain a valid installation.• The LINK_DIR environment variable is detected.• The specified installation location is the same as the parent directory of

the LINK_DIR environment variable.

A migration installation differs from a standard installation in several ways:• The installation program asks if you want to reuse your DSConfig.txt

configuration. If you choose yes, the existing configuration information ismerged into the new DSConfig.txt file.

Note:If you choose to reuse the configuration, the Job Server and AccessServer configuration screens will be skipped and the existing configurationis retained.

• After installation, a new al_env.sh file is created, and the old file is movedto LINK_DIR/bin/al_env.sh.old. You can merge database environmentinformation from the old file into the new file manually.

Limitations

When performing a migration installation, there are several limitations:

• After a migration installation, the Job Service, Job Servers, and AccessServers are not restarted automatically.

• The installation program performs several directory modifications.

For example, if your SAP BusinessObjects Data Integrator installationwas located at /home/BusinessObjects/DataIntegrator/ and themigration installation location is /home/BusinessObjects/, the migration


6Maintaining your installationUpgrading the software

installation creates new bobje, setup, tmp, and dataservices directoriesunder /home/BusinessObjects/.

• A previous installation of SAP BusinessObjects Data Integrator may haveset the CATALINA_HOME environment variable. The packaged Tomcatapplication server uses this environment variable, and may not start if thevalue does not match its location.

Before starting the packaged Tomcat application server, unset theCATALINA_HOME environment variable.

Related Topics• Migration Considerations: UNIX $LINK_DIR directories

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.


Maintaining your installation6 Upgrading the software

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.


Uninstalling the software from UNIX1. Stop the service.


6Maintaining your installationUninstalling the software from UNIX

2. Remove automatic startup of the SAP BusinessObjects Data Servicesservice at restart (if it is enabled) by executing the script as root user.

$LINK_DIR/bin/uninstall_root

3. Remove SAP BusinessObjects Data Services directories and filesrecursively in $LINK_DIR.

rm -R $LINK_DIR

Related Topics• To start or stop the service on page 75


Maintaining your installation6 Uninstalling the software from UNIX

IndexAAccess Server

configuring 41, 73

BBatch jobs

high availability support on AIX 59

Ccleansing package

repository 29requirements 29upgrading 101

cleansing packagesinstalling 62upgrading 100

componentsdistribution 14ports 19

configuringAccess Server 41Job Server 41Tomcat 43web application server 44

cron utility 10

Ddatabase

preparing 27repository 27

database connectivityconfiguring 56

database serverconfiguring 39existing 39

Designerconnection to Job Server 82

directorieslist 88location 92non-default location 93U.S. directory expiration 91unzipping 94update schedule 88

directory data 88

Eenvironment variables 54

HHigh Availability Clustered Multi Processing

(HACMP)configuring for 61support for on AIX 58using 60

HP-UXaccess permissions 10environment variables 54memory 84


Iinstallation

beginning 36overview 31silent 33standard 31, 32starting 46

installation locationspecifying 37

installed featuresselecting 37

installingcleansing packages 62

JJob Server

configuring 41, 69connection to Designer 82high availability support for batch jobs 58

Kkernel configuration, recommended 11

Llicense agreement

accepting 36License Manager

environment variable 77

MManagement Console

troubleshooting 83memory, HP-UX 84

Nnetwork connections

checking 22network requirements 9

Pports

default numbers 19description 19

processesresetting 82troubleshooting 82

product keycode 37

Rrepository

central 18creating 18creating, multiple 63local 18

repository databaseconfiguring DB2 25configuring MySQL 26configuring Oracle 26configuring Sybase 27preparing 27selecting 38

requirementscleansing package repository 29Data Cleanse 29network 9system 8

response filecreating 50

run-time resourcesconfiguring 72


Index

Sscripted installation

performing 50running 51

Server Managerconfiguring Access Servers 73configuring Job Servers 69configuring run-time resources 72configuring SMTP 77starting or stopping the service 75troubleshooting 82using 66

servicesstarting automatically 58

silent installationoverview 33, 50

SMTPconfiguring 77

standard installationoverview 31performing 32

startingservices 58

system requirements 8

Tthreading

HP-UX 85troubleshooting 85

Tomcatconfiguring 43

Tomcat (continued)starting 81stopping 81

troubleshootingDesigner to Job Server connection 82resetting processes 82Server Manager 82threading issues 85

UUNIX Job Server

environment variables 54upgrading

maintenance installation 98migration installation 99paths 98

user information 37user resource limits

AIX 12Linux 13Solaris 13

Vvariables, UNIX Job Server 54

Wweb application server

configuring 44selecting 42


Index


Index

Documents

Xi32 Ds Install Unix En