Xi32 Ds Install Unix en

SAPBusinessObjectsData Services
Installation Guide for UNIX

SAP BusinessObjects Data Services XI 3.2 (12.2.0)
2009 SAP BusinessObjects. All rights reserved. SAP BusinessObjects and
its logos, BusinessObjects, Crystal Reports, SAP BusinessObjects Rapid Mart,
Copyright
SAPBusinessObjects Data Insight, SAPBusinessObjects Desktop Intelligence,
SAP BusinessObjects Rapid Marts, SAP BusinessObjects Watchlist Security,
SAP BusinessObjects Web Intelligence, and Xcelsius are trademarks or
registered trademarks of Business Objects, an SAP company and/or affiliated
companies in the United States and/or other countries. SAP is a registered
trademark of SAP AG in Germany and/or other countries. All other names
mentioned herein may be trademarks of their respective owners.
2009-06-03
Contents
Preparing to Install 7 Chapter 1
Pre-installation overview..............................................................................8
System requirements.............................................................................8
Network requirements............................................................................9
User permission requirements.............................................................10
Kernel parameters and user resource limits........................................11
Choose components and determine component distribution...............14
Create a database for each repository.................................................18
Check port assignments.......................................................................19
Check network connections.................................................................22
Repository database requirements and preparation.................................22
To set up a database account..............................................................23
Setting up an empty database for the repository.................................23
Database-specific requirements for Data Cleanse...............................29
Installation scenarios.................................................................................31
Standard installation overview..............................................................31
Silent installation overview ..................................................................33
Standard Installation 35 Chapter 2
Beginning your installation.........................................................................36
To accept the license agreement.........................................................36
To specify the installation location........................................................37
To enter a product keycode..................................................................37
To select which features to install.........................................................37
To select a repository.................................................................................38
To configure an existing database server.............................................39
SAP BusinessObjects Data Services Installation Guide for UNIX 3
To configure a Job Server..........................................................................41
To configure an Access Server..................................................................41
To select a web application server.............................................................42
To configure your Tomcat application server........................................43
To configure an existing Web application server..................................44
To start the installation...............................................................................46
Silent Installation 49 Chapter 3
Overview of silent installation....................................................................50
Performing a scripted installation..............................................................50
To create a response file......................................................................50
To run a scripted installation.................................................................51
After Installation 53 Chapter 4
Setting environment variables...................................................................54
Configuring additional database connectivity.......................................56
Starting services automatically..................................................................58
High-availability support.............................................................................58
Using the software with HACMP..........................................................59
Installing cleansing packages....................................................................62
Using the Repository Manager..................................................................63
Using the Server Manager.........................................................................66
To configure Job Servers......................................................................69
To configure run-time resources...........................................................72
To configure Access Servers................................................................73
To start or stop the service...................................................................75
To start or stop the Address Server......................................................76
To configure SMTP email.....................................................................77
Using the License Manager.......................................................................77
Setting up License Manager.................................................................77
4 SAP BusinessObjects Data Services Installation Guide for UNIX
Contents
To start License Manager.....................................................................78
To view product activation keycodes....................................................78
To add product activation keycodes.....................................................78
To remove product activation keycodes...............................................79
To use License Manager from the command line................................79
Controlling the Tomcat application server..................................................81
Troubleshooting installation problems.......................................................82
Designer-Job Server connection..........................................................82
Server Manager problems....................................................................82
Management Console problems..........................................................83
Memory issues.....................................................................................84
Threading issues..................................................................................85
Directory Data 87 Chapter 5
Directory listing and update schedule........................................................88
U.S. Directory expiration............................................................................91
U.S. Directory expiration schedule............................................................91
U.S. National and Auxiliary files...........................................................91
Where to copy directories..........................................................................92
Copy International directories files to a non-default location................93
To install and set up Download Manager...................................................93
To download directory files........................................................................94
Unzip UNIX/Linux files with Info-Zip..........................................................94
Maintaining your installation 97 Chapter 6
Upgrading the software..............................................................................98
Maintenance installation.......................................................................98
Migration installation.............................................................................99
Upgrading cleansing packages..........................................................100
Uninstalling the software from UNIX........................................................101
Contents
Index 103
Contents
Preparing to Install
1
Pre-installation overview
SAP BusinessObjects Data Services provides an open and flexible
architecture that supports a variety of deployment and configuration scenarios.
Before you install the software you should:
Ensure that your network and systems meet the basic requirements.
Obtain the software as well as any required licensing keycodes.
Review the Release Notes and the "Architecture" section of the Getting
Started Guide.
If you are upgrading from a previous version, review the Migration
Considerations.
Ensure that the user who will run the installation program has adequate
permissions to complete the installation tasks.
Decide which components to install and which of your own components
to integrate.
Determine where the components should be installed and consider how
you should prepare your infrastructure and set up your environment,
including server locations.
If you are using an existing database server, create a database instance
if you want to configure a repository during installation.
Check available port assignments and verify that all machines that will
be part of your deployment have the required network access to each
other.
Choose an installation method.
The following sections list the core software and system requirements, the
choices available within the core requirements, and the install methods
available to you for installing the software.
Related Topics
Getting Started Guide: Architecture
System requirements
For a detailed list of supported environments and hardware requirements,
see the Products Availability Report (PAR) available in the SAP
BusinessObjects Support > Supported Platforms section of the SAP
Service Marketplace: http://service.sap.com/bosap-support. This document
1
includes specific version and patch-level requirements for databases,
applications, web application servers, web browsers, and operating systems.
Before you can install SAP BusinessObjects Data Services, the following
components must be preinstalled and configured:
Web application server (unless you want to use the Tomcat installation
packaged with SAP BusinessObjects solution portfolio software, or you
do not want to install the Web Tier components)
Database software that is compatible with the SAP BusinessObjects Data
Services repository.
Note:
Only the database client tools or middleware needs to be installed on the
SAP BusinessObjects Data Services server; the database server itself
can reside on a separate physical machine accessible by network from
the SAP BusinessObjects Data Services server.
Note:
For the repository, the software requires a database that stores metadata
about all objects created with the Designer. For best Designer performance,
it's recommended that the repository database server and the Designer
computer reside in the same network.
Network requirements
When you install SAP BusinessObjects Data Services on multiple machines,
you must ensure that each machine can communicate over TCP/IP with the
machine running the database that contains the repository.
Client components, such as the Designer, require network access to the Job
Server(s).
Note:
If your servers are firewalled, you may need to open the necessary ports to
allow the client components to communicate with the servers.
1
User permission requirements
To successfully install SAP BusinessObjects Data Services on UNIX, the
user running the setup programmust have the permissions listed in the table
below.
Required permission(s) Category
TCP/IP access to all machines where you want to install
components. All specified ports must be available.
Network
Permissions to add and drop tables in the database, plus
permissions to read, write, and edit table rows.
Database
In addition, it's recommended that you use the same user account for
installing the software and your web application server.
If your design, test, or production environment uses tightly controlled root-level
administration, it's recommended that you install the Job Server while logged
on as a user without root-level access. Installing the Job Server without
root-level access ensures that root-level access is not required to administer
files and processes created by the Job Server.
Only a few administration functions require root-level access as described
in the following table:
Required Permission(s) Function
Permission to access cron Scheduling jobs
Autostart configuration edits need to be made
by a user with system-level authority.
Automatically restarting the
Job Service on restart
Cron service
SAP BusinessObjects Data Services schedules UNIX-based jobs by using
the UNIX cron utility. If cron security uses cron.allow, the account that
starts the Job Server must have an entry in the cron.allow file.
1
cron.allow location Operating system
/var/adm/cron/cron.allow HP-UX
/var/adm/cron/cron.allow AIX
/usr/lib/cron/cron.allow Solaris
/etc/cron.allow Linux
For more information, see your cronman pages.
Installing the Job Server without access to cron causes the following Job
Server 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 user
resource limits when installing SAP BusinessObjects Data Services on UNIX
platforms.
Note:
Besides the following recommendations, there is a requirement for a special
scenario. If you intend to use the USA Regulatory Address Cleanse transform
with caching of DPV and LACSLink directories, you must set your UNIX
operating system's Data Segment Size limit to Unlimited. This system
parameter must be set before starting the software.
HP-UX for Itanium 64-bit kernel configuration
For installations on HP-UX for Itanium64-bit systems, it's recommended that
you use the following kernel configuration:
1
Comments Value Kernel parame-
ter
If you receive Cannot create
thread run-time error message from
the job, increase this value.
256 max_thread_proc
Default value of 2048 is appropriate
to use.
2048 maxfiles
Enter the swap space configured on
your system.
0X400000000 maxdsiz_64bit
Default value of 256 MBis appropriate
to use.
0X10000000 maxssiz_64bit
Default value of 1 GB is appropriate
to use.
0X40000000 maxtsiz_64bit
Default value of 256 MBis appropriate
to start using. However, if you expect
many jobs to run at the same time,
increase this value.
256 maxuprc
This value gets calculated by HP-UX
automatically.
((16*(NPROC+16+MAXUSERS)/10)+32
+2*(NPTY+NSTRPTY+NSTRTEL)
nfile
Default value of 4200 is appropriate
to use.
4200 nproc
AIX user resource limits
For installations on AIX systems, it's recommended that you use the following
user resource limits. You can display these settings by running the ulimit
-a command from your SAP BusinessObjects Data Services installation
login.
1
Comments Value User resource limit
At least 2 GB 4194302 file (blocks)
unlimited data (kbytes)
At least 500 MB 512000 stack (kbytes)
At least 2 GB 2097151 memory (kbytes)
At least 2000 2000 nofiles (descriptors)
Solaris user resource limits
For installations on Solaris systems, it's recommended that you use the
following user resource limits. You can display these settings by running the
ulimit -a command from your SAP BusinessObjects Data Services login.
unlimited file (blocks)
unlimited data (kbytes)
At least 8 K 8192 stack (kbytes)
unlimited time (seconds)
At least 1 K 1024 nofiles (descriptors)
unlimited coredump (blocks)
Unlimited, at least 2
GB
unlimited vmemory (kbytes)
Linux user resource limits
For installations on Red Hat Linux systems, it's recommended that you use
the following user resource limits. You can display these settings by running
the ulimit -a command from your SAP BusinessObjects Data Services
login.
1
unlimited file (blocks)
unlimited data (kilobytes)
At least 10 MB 10240 stack (kilobytes)
unlimited time (cpu-seconds)
1024 nofiles (descriptors)
unlimited coredump (blocks)
unlimited memory (kilobytes)
4 lockedmem (kilobytes)
7168 processes
Choose components and determine component
distribution
You may choose to upgrade or install components on one or more computers
based on available resources and amount of system traffic.
Note:
You must install the Designer and Metadata Integrator on a supported
Windows platform. You can install the other components on Windows, UNIX,
or Linux platforms.
The installation program can install multiple feature categories.
1
Description Component Feature 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 (Java
Messaging System) and Sales-
force.com.
Technology Interfaces
Integration component that collects
metadata froman SAPBusinessObjects
Enterprise system for impact and lin-
eage analysis in the Management Con-
sole.
Metadata Integrator
(Windows only)
Graphical user interface that is used to
design and test all jobs.
Designer
(Windows only)
Client Components
Interface that creates and manages all
types of repositories (local, central, pro-
filer, and cleansing package).
Repository Manager
Web application server that can be used
to deploy SAP BusinessObjects solution
portfolio software. You can also use your
own existing web application server.
Tomcat application server
(optional)
Web Tier Compo-
nents
Web application that manages the SAP
BusinessObjects Data Services environ-
ment (monitors, executes, and sched-
ules jobs), as well as metadata reporting
(auto-documentation, Validation and
Operational dashboards, Data Quality
reports, and impact and lineage analy-
sis).
Management Console
1
Description Component Feature category
Message Client API that other applica-
tions can use to integrate with real-time
jobs.
Message Client
Components
Software product documentation.
Documentation
Components
For complete description of the components and how they interact, see
"Architecture" in the Getting Started Guide.
Note:
You can configure several Job Server and Access Server instances from
one Job Server or Access Server installation. Configure Job Server and
Access Server instances by using the Server Manager.
You can install components on one or more computers based on available
resources and the amount of traffic the system processes. Before installing
components, consider the following:
A local repository connects a Designer with a Job Server. You can install
a Job Server on the same computer as the repository, on a stand-alone
computer (with repository database client software), or on the same
computer as a Designer.
Any Designer can access any local repository and Job Server. Multiple
Designers cannot simultaneously access the same local repository.
Simultaneous access risks metadata corruption in the repository. Also,
you cannot link Designer to more than one local repository at any given
time.
Install database client software on the computer containing the Job Server
to support the repository associated with that Job Server. For example,
if the repository associated with a Job Server named oradev is an Oracle
database, then Oracle client software must be installed and configured
on the computer containing the oradev Job Server.
The following diagram depicts a simple distribution of components among
computers in a network. Note that you can install each component on one
or more computers. Also note that there are many possible connections
between components. Each box in the diagram represents a different
computer.
1
1
You can install the Management Console on any computer with or without
other components. The Management Console is Java-based; you have the
choice to deploy it to the packaged Tomcat server or a previously installed
application server.
Related Topics
Getting Started Guide: Distributed architecture
Create a database for each repository
SAP BusinessObjects Data Services uses several types of repositories:
Central
Supports multi-user development and allows for check-in and
check-out. Also provides versioning to keep and allow restore for
several versions for the same object.
Cleansing package
Stores dictionaries for the cleansing packages used by Data Cleanse
transforms.
Local
Working repositories where you create and modify applications.
Profiler
Stores profiling metadata when the built-in profiler is configured.
You associate each Job Server with one or more local repositories. There
is no relationship between central repositories and Job Servers.
Create local repositories before you install each Job Server, or configure
them after you install Job Servers by using the Repository Manager.
Note:
If you have Job Servers on more than one machine that connect to the same
local repository, then the repository database connection properties for these
Job Servers must be the same. A job will not run on a Job Server with
conflicting connection properties. The database connection properties for
different databases are shown in this table.
1
Connection property Database
DSN DB2
DSN MySQL
tnsnames Oracle
Sybase Server Name Sybase ASE
The number of databases you need depends on whether you want a
single-user or multi-user development environment:
To set up a single-user development environment, create a database for
the local repository.
To set up a multi-user development environment, create databases for
each local repository (one per user) and a database for the central
repository.
Note:
Multiple Designers can share the same profiler, profiler repository, or
cleansing package repository.
Related Topics
Repository database requirements and preparation 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 BusinessObjects
Data Services components are available and not in use by other programs.
For a development system, you can install many components on the same
computer. This simplifies many connections between components (the host
name is always the same), but you must still define connections based on
TCP/IP protocol.
This table details the default ports:
1
Component
To set Default Description Port
Job Server
Use Server Manager 3500
Receives commands from
Designer, Access Server,
and schedulers.
Job Server port or
TCP/IP port
Receives commands and
sends data to adapters.
Adapter/SNMP
communication
port
Packaged Tomcat Application Server
Tomcat conf\server.xml 28080
Supports communication be-
tween web browsers and the
Management Console.
HTTP port
Tomcat conf\server.xml 28005
Used to start and shut down
the Web Server which sup-
ports the Management Con-
sole.
Shutdown port
Access Server
Receives and sends mes-
sages from clients and ser-
vices.
Communication
port
Designer
Choose Tools > Options
in the Designer.
5001
Supports communication for
the debugging feature.
Interactive Debug-
ger port
Address Server
LINK_DIR\bin\ad
dress_server\Ad
dressServerConfig.txt
40010
the Address Server.
Control port
1
Component
To set Default Description Port
LINK_DIR\bin\ad
dress_server\Ad
dressServerConfig.txt
40011
the Address Server.
Application port
Example: Default configuration
The following configuration diagram shows default port numbers, as well
as the packaged Tomcat installation. Default ports for other web application
servers may differ.
1
Check network connections
Before you install SAP BusinessObjects Data Services components, check
the computers involved and verify network connections by executing the ping
command on each computer.
Example: Windows Designer and UNIX Job Server
If the Designer will be on a Windows computer and your Job Server will be
on a UNIX computer, from the Windows computer open the DOS prompt
and enter:
C:\> ping hostname
where hostname is the host name of the UNIX computer.
Then from the UNIX computer, log in as root and from the prompt, enter:
$ ping hostname
where hostname is the host name of the Windows computer.
Repository database requirements and
preparation
SAP BusinessObjects Data Services stores your design metadata for source
and target tables as well as database functions and definitions of built-in
objects in database tables. This set of database tables is called the repository.
You can create one repository during installation. If you want to create a
repository in an existing database, you must create space for the repository
before you run the installation program. The installation program connects
to the repository and populates it.
A repository requires a minimumof 20 MB of free disk space on the database
server.
The following sections detail required settings for:
1
Repository database requirements and preparation
IBM DB2
MySQL
Oracle
Sybase ASE
Before you install the software, you should review this information in order
to properly prepare your repository database.
Note:
You can also choose to skip creating a repository during installation, and
use the Repository Manager to create it at a later time.
Note:
If you want to use multi-byte metadata, such as Japanese column names
on imported tables or multi-byte data in Data Quality reports, your database
must be configured to use Unicode character encoding, such as UTF-8.
Related Topics
To set up a database account
To administer the repository database, you need to set up a database
account. Complete the steps listed below before you install the software.
1. Create or select a user account that provides the software with the
appropriate privileges to your database server.
2. Verify that you can log on to your database and carry out administrative
tasks using this account.
Setting up an empty database for the repository
If you want to use an existing database server, you must create a new
database on your database server before you install SAP BusinessObjects
Data Services.
The following database servers are supported for the repository database:
IBM DB2
MySQL
Oracle
1
Sybase ASE
Note:
For information related to supported database software and version
requirements, review the Products Availability Report (PAR) available in the
SAP BusinessObjects Support > Supported Platforms section of the SAP
Service Marketplace: http://service.sap.com/bosap-support.
To use your existing database with the software, you need to prepare it.
1. Create a new database.
2. Create a new user account and password for the database to be used
by the software.
3. Specify that the newuser account has the required permissions to create,
modify, and delete tables and create procedures so that the database
can be modified as necessary.
4. Record the name of the database, the user account, and the password
when you run the installation program.
During the installation, you can choose to reinitialize the existing database.
This will cause new tables to be created in your existing database to store
SAP BusinessObjects Data Services data. If you are unsure of the procedure
for creating a new database, consult your specific database server
documentation.
Note:
If you have an existing SAP BusinessObjects Data Services or SAP
BusinessObjects Data Integrator repository, you can upgrade the repository
during installation or use the Repository Manager to upgrade it after
installation. If you have an existing SAP BusinessObjects Data Quality
Management repository, create a new SAP BusinessObjects Data Services
repository and see the Migration Considerations.
32-bit and 64-bit notes
SAP BusinessObjects Data Services 32-bit and 64-bit software is supported
on a variety of operating systems. When you use a database client with the
32-bit software, the 32-bit database client libraries must be installed and
referenced in the library paths.
For example, the default installation of the Oracle 64-bit client includes
installation of the 32-bit client. For non-standard installations, these libraries
must be specified as part of the installation. After installation, the libraries
should be in the $ORACLE_HOME\lib32 directory.
1
If these 32-bit libraries are not present, you receive an error message stating
that the software cannot load the client library. Examples of error messages
include:
(5.2) 02-05-02 14:55:23 (E) (26797:0001) CON-120103: System
call <dlopen> to load and initialize functions failed for
<libclntsh.a>. Make sure the SHARED LIBRARY is installed and
resides in the correct location.
(5.2) 02-05-02 14:55:23 (E) (26797:0001) REP-100108: Cannot
perform operation on Repository<Default Repository> because a
connection to the repository was never opened. A connection
must be opened to the repository before performing any opera
tion.
When you use a database client with the 64-bit software, the 64-bit client
libraries must be installed and referenced in the library paths.
DB2 database setup requirements
A local or central SAP BusinessObjects Data Services repository requires
that you create a dedicated database and define a user with the following
rights:
To create a table
To start a session
To create a sequence
Install the DB2 Application Enabler software and use DB2 Control Center
and DB2 Script Center to verify the connection between the Designer
computer and the repository computer.
Note:
For a repository on DB2, the software also requires a temporary table space
with a page size of 8-16K.
When the database is created, you need to prepare it for the installation.
Related Topics
To prepare your database on page 27
1
MySQL database setup requirements
To log in to the Repository Manager and the Designer later, you must supply
the 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 value
is 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 path
automatically if it is set.
Related Topics
Oracle database setup requirements
that you create a dedicated database and define a user with the following
rights:
To create a table
To start a session
To create a sequence
Grant the user the connect and resource roles. For Oracle 10G/R2, also
grant the create view role.
Install the Oracle client software and use SQL*Plus to verify the connection
between the Designer computer and the repository.
1
Note:
To store multi-byte characters in a repository table when the repository is on
an Oracle database, you must change the Oracle database character set to
a code page that supports the multi-byte language that you plan to use or
you risk corrupting your metadata. For example, to store Japanese characters,
change the Oracle database character set to either SHIFT_JIS or UTF8.
Tip:
Export the ORACLE_HOME environment variable prior to installation. The
installation program will add this variable to the environment configuration,
even if you choose to skip repository configuration during installation.
Related Topics
Sybase database setup requirements
that you create a dedicated database and define a user.
Note:
For UNIX Job Servers, when logging in to a Sybase repository in the
Designer, the case you type for the database server name must match the
associated case in the SYBASE_Home\interfaces file. If the case does not
match, you might receive an error because the Job Server cannot
communicate with the repository.
Related Topics
To prepare your database
1. Create a new, empty database on your database server.
2. Create a new user and assign it a secure password.
3. Ensure that the new account has permission to create, modify, delete
tables and create procedures so that the software can modify the database
as required.
1
Note:
If you are not the owner of the database, you must have permissions to
perform the necessary operations.
4. Before you begin your installation, ensure the following are set up:
Information required Database type
DB2 database alias DB2
ODBC datasource name MySQL
tnsnames connect identifier Oracle
Sybase server name
Database name
Sybase ASE
Note:
The Sybase server name is a combination of the host name and the port
number which is set by your database administrator in the file sql.ini.
5. Record these details because you are required to provide them during
installation:
The name of your database, ODBC datasource name, Sybase server
name, Oracle tnsnames connect identifier, or DB2 database alias.
The user account and the password authorized to the database.
For information on how to create a new database, consult your database
server documentation or your database administrator.
Related Topics
DB2 database setup requirements on page 25
MySQL database setup requirements on page 26
Oracle database setup requirements on page 26
Sybase database setup requirements on page 27
1
Database-specific requirements for Data Cleanse
SAP BusinessObjects Data Services has specific requirements for the
database repository used by cleansing packages or custom Data Cleanse
dictionaries created using Universal Data Cleanse. For disk space
requirements, see the Products Availability Report (PAR) available in the
SAP BusinessObjects Support > Supported Platforms section of the SAP
Service Marketplace: http://service.sap.com/bosap-support.
Requirements for specific database server and client settings are described
in the following table:
1
Required settings Database type
Server settings
Code Page 1208
Character Set UTF-8
Note:
When creating a DB2 9 database, be sure to check the
Enable Database for XML option.
Client settings
DB2CODEPAGE 1208
You can use the db2set utility to configure this environ-
ment variable. For more information, see the DB2 docu-
mentation.
Note:
The DB2 client version must match the DB2 server version.
For example, if your server uses DB2 9, use the DB2 9
client.
DB2
The MySQL server and client must be configured with
UTF-8 as the default character set.
Ensure that your ODBC connection entry in the
odbc.ini file contains the line charset = utf8.
MySQL
Oracle
1
Required settings Database type
Server settings
NLS_CHARACTERSET AL32UTF8
NLS_NCHARSET AL16UTF16
To determine the currently configured character set, you
can use the following select statement on the Oracle
server:
Select * from nls_database_parameters WHERE
PARAMETER = 'NLS_CHARACTERSET' OR
PARAMETER = 'NLS_NCHAR_CHARACTERSET'
Client settings
NLS_LANG AMERICAN_AMERICA.AL32UTF8
Note:
The Oracle client version must match the Oracle server
version. For example, if your server uses Oracle 9, use
the Oracle 9 client.
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 exclude
some components, or install only a limited set of components.
The installable feature categories include:
Server Components
Web Tier Components
Message Client Components
Documentation Components
1
By default, Tomcat is installed as the web application server. You can also
choose to use your own web application server during the installation process.
Note:
During installation, you can choose whether to configure many of the
components, such as Job Servers and Access Servers. If you skip component
configuration during installation, you can use the configuration tools to
accomplish these tasks after installation has finished.
Related Topics
Choose components and determine component distribution on page 14
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 performany additional configuration needed using
the configuration tools. For example, you can:
Create additional local, central, or cleansing package repositories with
the Repository Manager.
Register any repositories in the Management Console.
Create and configure a profiler repository.
Configure additional Job Servers with the Server Manager.
Add any additional license keycodes with the License Manager.
Related Topics
Pre-installation overview on page 8
Beginning your installation on page 36
Using the Server Manager on page 66
Using the License Manager on page 77
1
Silent installation overview
You can run a silent installation to install SAP BusinessObjects Data Services
from the command line using a response file containing installation
parameters. This method is particularly useful when you need to perform
multiple installations or you do not want to interrupt people who are working
on machines in your system.
You can also incorporate the silent installation command into your own build
scripts. For example, if your organization uses scripts to install software on
machines, you can add the silent installation command to those scripts.
You may want to choose a silent installation when:
You are already familiar with the installation program.
You need an automated method for performing similar installations on
several machines.
You do not want to run the installation program.
Related Topics
Overview of silent installation on page 50
1
1 Installation scenarios
Standard Installation
2
Beginning your installation
The following instructions lead you through the initial steps of setting up your
SAP BusinessObjects Data Services installation. In this stage you will do
the following:
Agree to the license terms.
Enter the product activation keycode.
Select where to install the software.
Select which features to install.
When you perform the following installation, all the components that you
select are installed on the local machine.
You can start installation by running ./install.sh. After the "Welcome"
screen is displayed, press Enter to begin your installation.
Tip:
Before beginning your installation, review the pre-installation overview to
ensure that you have prepared all necessary systems.
Related Topics
Pre-installation overview on page 8
To accept the license agreement
At the "License Agreement" screen, reviewand accept the license agreement
for SAP BusinessObjects Data Services. You must accept the agreement
to continue with the installation.
1. Review the License Agreement.
2. Press Y to accept the License Agreement.
You cannot continue unless you accept the License Agreement.
3. Press Enter to continue the installation.
2
To specify the installation location
At the "Directory Selection" screen, enter the location for your SAP
BusinessObjects Data Services installation.
1. Specify where to install the components.
The default location is $HOME/businessobjects.
Restriction:
The installation location does not support multi-byte characters. To install
the software on a system with a multi-byte locale, you can specify the
installation location with single-byte characters or use the default location.
Note:
The installation program creates an environment variable named
$LINK_DIR for the dataservices directory created at this path. $LINK_DIR
is 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 your
SAP 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 you
need 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 you
do not want to install:
2
Description Feature catego-
ry
Includes the Job Server, Access Server, Address
Server, 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 Lineage
Analysis, Operational Dashboards, Data Quality
Dashboards, Auto Documentation, and Data Quality
Reports).
All Web Tier components install by default unless de-
selected.
Web Tier com-
ponents
Includes the C++ and Java libraries for integrating
external application with real-time jobs.
The Message Client components do not install by
default unless selected.
Message Client
components
Includes software documentation as PDF documents.
The Documentation components install by default
unless deselected.
Documentation
components
2. When you have made your component selections, press Enter to continue.
To select a repository
At the "Repository Selection" screen, choose which type of database to use
for the repository.
1. Select the type of repository that you want to configure.
Use an existing database server
Skip configuration
2
You can configure one local repository during installation. If you skip the
configuration, or you need more repositories, you can configure additional
repositories later by using the Repository Manager.
Caution:
It's recommended that you do not use database tools to attempt to quickly
replicate additional repositories. By using the Repository Manager to
create and seed multiple repositories individually, you can avoid potential
issues related to the configuration of repository objects.
2. Press Enter to continue.
Related Topics
To configure an existing database server
The "Local Repository Database Type" screen appears if you chose to use
an existing database server as your repository for the new SAP
BusinessObjects Data Services installation. At this screen, specify the
connection information for the database where the repository will be created.
1. Select a database type and press Enter to continue.
Depending on your database type selection, corresponding input fields
are displayed.
2. Provide the database-specific required information in the fields displayed.
2
System vari-
able
Required information Database type
$DB2DIR DB2 client location
DB2 alias name
DB2
$ODBCINI Full path of odbc.ini MySQL
$ORACLE_HOME Oracle client location
Oracle TNSNAME identifier
Oracle
$SYBASE Sybase client location Sybase ASE
Tip:
The fields displayed support a maximum of 70 characters. However, if
the required system variables have been exported prior to starting the
installation setup program, they will be displayed in each field as $vari
able_name. By exporting the variables prior to installing, you can use
values longer than 70 characters.
3. In the User name field, specify the user name for the account authorized
to use the database.
4. In the Password field, specify the password for the account authorized
to use the database.
6. If you are upgrading froman existing SAPBusinessObjects Data Integrator
or SAP BusinessObjects Data Services repository, select Upgrade to
keep and upgrade the existing repository. If you are creating a new
repository, select Create.
Caution:
If you choose to use Create on an existing repository, the repository
tables are recreated, and all data in the existing repository will be lost.
Note:
The SAP BusinessObjects Data Services installation setup program
configures only the database connectivity for the repository, not additional
2
source or target databases. If you need to access other systems as database
source or targets, you can configure them after installation.
Related Topics
Configuring additional database connectivity on page 56
To configure a Job Server
At the "Configure Job Server" screen, create a new job server.
1. Select the type of Job Server configuration to perform:
Configure a new Job Server (Default)
Skip Job Server configuration
If you skip the configuration, you can configure a Job Server later using
the Server Manager. Any existing Job Servers from a previous SAP
BusinessObjects Data Integrator or SAP BusinessObjects Data Services
installation will be retained, unless it has been uninstalled or DSCon
fig.txt has been removed.
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 port
fields.
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 necessary
configuration changes.
Related Topics
To configure Job Servers on page 69
To configure an Access Server
At the "Configure Access Server" screen, create a new access server.
1. Select the type of Access Server configuration to perform:
2
To 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 not
need real-time processing, skip Access Server configuration. Real-time
and transactional processing is not licensed in all SAP BusinessObjects
Data Services packages and is available as an option.
If you skip the configuration, you can configure an Access Server later
by using the Server Manager. Any existing Access Servers froma previous
SAP BusinessObjects Data Integrator or SAP BusinessObjects Data
Services installation will be retained, unless it has been uninstalled or
DSConfig.txt has been removed.
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 and
Access Server port fields.
The default directory for the Access Server is LINK_DIR/bin/AccessServ
er_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 server
If you chose to install the Web Tier Components, you need to provide
information about the web application server that will work with your software.
Use the "Select Web Application Server" screen to either install Tomcat as
your application server, or to work with your existing web application server.
To configure your web application server for SAP BusinessObjects Data
Services, you need account information along with port information.
1. Select one of the following options:
Use an existing web application server
Install Tomcat application server
2
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. You
will need to provide access information for this server in a subsequent
screen.
Note:
You can use the Manual Deploy option to install the SAP BusinessObjects
Data Services web application WARfiles and then manually deploy the WAR
files to a supported web application server after installation. You must perform
the manual deployment on the same machine where Data Services is
installed.
For manual deployment instructions for a specific web application server,
refer to SAP Note 1347589 in the SAP Service Marketplace.
For a list of supported web application servers, see the Products Availability
Report (PAR) available in the SAP BusinessObjects Support > Supported
Platforms section of the SAP Service Marketplace: http://ser
vice.sap.com/bosap-support
Related Topics
SAP Note 1347589
To configure your Tomcat application server
The "Configure Tomcat" screen is displayed during installation setup if you
choose to install Tomcat as the web application server for your current SAP
BusinessObjects Data Services installation. At this screen, configure Tomcat.
1. In the fields provided, specify which port numbers will be used by Tomcat
for connection, shutdown, and redirect.
Tip:
You can accept the default values for each port setting.
2
Note:
If you need to change the Tomcat port settings after installation, you can
modify the Tomcat setup.xml file. By default, this file is installed to the
/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 displayed
during installation after you specify an existing server in the "Select Web
Application Server" screen.
1. Select the type of web application server that you want to use.
3. Specify the required configuration information for your existing web
application server.
2
Required information Web Application
Server
Server Instance: Name of the current web application server instance
(for example, localhost).
Application Server Installation Directory: The directory where the web
application server is installed.
Apache Tomcat
5.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.
Password: Password for account with administration rights to the appli-
cation server. This is mandatory for Weblogic.
(for example, mserver1).
Application Server Installation Directory: The directory for the web
application server instance (for example, /bea/weblogic10/samples/do
mains/wl_server).
WebLogic 10
Port: Administration port of the application server (for example, 7001).
Username: User name with administration rights to the application server.
cation server. This is mandatory for Weblogic.
(for example, mserver1).
application server instance (for example, /bea/weblogic92/samples/do
mains/wl_server).
WebLogic 9
WebSphere 6.1
2
Required information Web Application
Server
Port: Administration port of the WebSphere application server (that is,
the SOAP port). If not specified, the default SOAP port will be used.
Username: User name with administration rights to the WebSphere ap-
plication server.
Note:
If Admin is Secure is not selected, you do not need to specify a username
or a password.
cation server.
(for example, server1).
Virtual Host: The virtual host to which the application must be bound
(for example, default_host).
Admin is Secure: Select this option to enable security requiring admin-
istrative access credentials to the application. If WebSphere was installed
with the secure option, this is required.
application server instance (for example, /WebSphere/AppServer/pro
files/AppSrv01).
Note:
To deploy the Management Console to a web server farm, run the SAP
BusinessObjects Data Services installation program on each web server in
the farm.
To start the installation
The "Start Installation" screen is the final screen in the installation program.
Reviewthe 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
2
at which you can cancel the installation process to have the .ini file
written with all the installation parameter information. This .ini file can
then be used in silent and scripted installations.
Press Enter to start the final installation process.
Note:
To ensure proper operation, it's recommended that you restart the computer
after you install or uninstall SAP BusinessObjects Data Services.
2
2 To start the installation
Silent Installation
3
Overview of silent installation
There is a method for running SAP BusinessObjects Data Services
installations for UNIX directly from the command line:
Silent installation using a response file referred to as a scripted
installation in this guide
Scripted installation can be used to automate installations across multiple
machines and requires you to specify a response file.
Silent installation is particularly useful when you need to perform multiple
installations, as you can save time and avoid being prompted for information
by the installation program. You can also integrate the scripts and commands
into your own installation scripts.
Performing a scripted installation
While setting up an installation process, you can write installation settings
to a specified response file. The file is generated once the installation setup
program is ready to start the installation.
The response file supports the standard installation type available for SAP
BusinessObjects Data Services.
Tip:
You do not start the installation process to generate the response file. Press
CTRL + X to abort the installation once you reach the final screen in the
installation 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 temporary
location, you will be prompted to specify a temporary location for the
installation.
2. In the command line, type ./install.sh -w and the file path for the response
file you want to generate. For example:
Silent Installation
3
Overview of silent installation
./install.sh -w responseFilePath/responseFileName
Note:
You must include both the path and file name for the response file you
want to generate.
3. Press Enter to launch the installation program.
4. Followthe 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 "Start
Installation" 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. The
MACHINE NAME parameter must be specified in the response file if you are
replicating an installation. If the parameter is not specified, the local server
name will be used by default.
1. Mount the device that contains the installation files.
Note:
If you run the installation script without copying the files to a temporary
location, you will be prompted to specify a temporary location for the
installation.
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 the
installation program to read for installation parameters.
-i INSTALLDIR Specifies the installation directory for the scripted
installation.
-s SOURCEDIR This optional command specifies the location of the
cd directory. The source directory must point to the location of DISK_1
in the installation CD. If not specified, the CD directory setting in the
response file will be used.
3. Press Enter to launch the installation.
3
Silent Installation
Performing a scripted installation
Silent Installation
3 Performing a scripted installation
After Installation
4
Setting environment variables
The Job Server requires that certain environment variables be set up. To set
up these variables, users who run or administer Job Servers must run a
script (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 always
configured. 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 the
variables' values are properly set, check one or more of the following.
Tip:
Use the echo command to verify environment variable settings.
After Installation
4
Details Variable
SAP BusinessObjects Data Services installation
directory (set by the installation program)
$LINK_DIR
For HP-UX. Must include $LINK_DIR/bin and the
location of the database libraries.
If you want to use a 64-bit Oracle client,
$LINK_DIR/bin must be listed before any 64-bit
Oracle shared library path.
$SHLIB_PATH
For Solaris or Linux. Must include $LINK_DIR/bin
and the location of the database libraries.
$LD_LIBRARY_PATH
For AIX. Must include $LINK_DIR/bin and the
location 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 must
point 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
4
After Installation
Details Variable
Required for a Sybase ASE source, target, or
repository.
$SYBASE
Required for a Sybase ASE source, target, or
repository.
$SYBASE_OCS
Required for an ODBC source or target.
$ODBCINI
Must include $LINK_DIR/bin and database
home/bin.
$PATH
If the variable settings are not properly configured and you start any SAP
BusinessObjects Data Services utility, error messages will appear to indicate
that database server files are missing.
If you see such an error, verify that al_env.sh contains commands to set
the appropriate database home locations. Run al_env.sh for the account
used by the Job Server, or start the Job Server using an account that has
all necessary environment variables defined in its .profile.
Configuring additional database connectivity
By default, the SAPBusinessObjects Data Services installation setup program
configures database connectivity for the repository only. To access other
database systems as sources and targets in your jobs, you need to add the
appropriate configuration information to the al_env.sh file. The following
sections detail the information required for each database type.
Note:
The following examples are for the Linux platform and use
LD_LIBRARY_PATH. For AIX or HP-UX platforms, use LIBPATH or
SHLIB_PATH respectively.
After Installation
4
Attunity
export NAVROOT=your_Attunity_root_path
export LD_LIBRARY_PATH=$NAVROOT/lib:$LD_LIBRARY_PATH
export PATH=$PATH:$NAVROOT/bin
DB2
export LD_LIBRARY_PATH=your_DB2_client_path/sqllib/lib:$LD_LI
BRARY_PATH
ODBC
The syntax for an ODBC connection varies depending on the type of
database. For example, for a MySQL ODBC connection:
LD_LIBRARY_PATH=MySQL_Driver:unixODBC_library_path:$LD_LI
BRARY_PATH
export ODBCINI=your_odbc.ini_file
Oracle
export ORACLE_HOME=your_Oracle_home
export LD_LIBRARY_PATH=$ORACLE_HOME/lib:$ORACLE_HOME/net
work/lib:$LD_LIBRARY_PATH
Teradata
export LD_LIBRARY_PATH=/usr/odvc/drivers:/usr/odbc/lib:/opt/ter
adata/client/transporter/lib:$LD_LIBRARY_PATH
export PATH=/opt/teradata/client/bin:/opt/teradata/client/trans
porter/bin:$PATH
export COPERR=/opt/teradata/client/lib
export ODBCINI=your_odbc.ini_file
Sybase ASE
For Sybase ASE version 12.5 on UNIX platforms, you must first run a script
to generate the shared bulk load library. By default, the script is installed to
LINK_DIR/AWSybase/buildlbk.sh. For additional information, see
LINK_DIR/AWSybase/readme.txt.
4
After Installation
Starting services automatically
To start Job and Access Servers automatically when the server restarts, you
must 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 support
If you run SAP BusinessObjects Data Services on AIX and you have High
Availability Clustered Multi-Processing (HACMP) software version 4.4.0, use
HACMPsoftware to minimize downtime of your system. The software includes
start 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 systems
to guarantee backup of essential services. Within HACMP software, you
define each complete system as a resource group. When a component fails
in a resource group, HACMP software quickly restores essential services by
starting the failed system on an alternate computer, called a node, or group
of 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 HACMP
software and AIX operating system manages).
2. Install the necessary components to support the system on duplicate
hardware systems, creating clusters or nodes that can support identical
services that the system processes.
3. Define takeover relationships that determine which cluster or node
supports the resource group at any given time. There are three types of
takeover relationships:
Cascading
After Installation
4
Starting services automatically
Clusters are listed along with a priority rank. Control of the resource
group goes to the active cluster with the highest priority ranking.
Control can change due to failure or to the reactivation of a cluster
with a higher priority rank.
Concurrent
Multiple clusters support the resource group at the same time.
Rotating
Clusters are listed along with a priority rank. Control of the resource
group 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 that
support HACMP software. These scripts run when a newcluster takes control
of the software resource group. The start script:
Identifies jobs scheduled before the previous cluster failed and launches
those jobs in recovery mode
Identifies jobs scheduled to start during cluster down time and launches
those jobs
Synchronizes the cron file on the new cluster with the cron file on the
previous cluster
When using the software with HACMP, you should be aware of several
requirements and restrictions:
There can be no single point of failure, or the additional availability
provided by HACMP is compromised.
You must use the same user ID on all clusters where you install the
software.
The database systems that support jobsthe repository, sources, and
targetsmust also be highly available.
You cannot use a concurrent takeover relationship for the software
resource 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.
4
After Installation
To use the software with HACMP
1. Install the Job Server on a file system in the shared volume group from
a 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 made
available for the rest of the cluster nodes.
3. Copy the start and stop scripts (acta_start.sh and acta_stop.sh) from
the $LINK_DIR/hacmp directory to the HACMP scripts directory on each
of 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 Installation
4
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 Resource
Group **
------------------------------------------------------------------
Service IP Label Domain Name
---------------- -----------
aixserver1
------------------------------------------------------------------
e: Edit Configuration y: Re-sync all repos q: Quit
4. Configure HACMP.
4
After Installation
Description Command
Specifies the Service IP Label used while configuring
SAP BusinessObjects Data Services' resource group.
When you finish configuration, the software resynchro-
nizes all repositories and the configurations for the SNMP
agent 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 and
adapters, and reschedule batch jobs.
E
Manually resynchronizes all repositories.
Note:
Resynchronizing all repositories is not required unless you
see an error message after editing the configuration. For
example, a repository might not get updated to use the
configured Service IP Label if the associated database is
unavailable. After correcting the problem, you can use this
option to resynchronize the repository.
Y
5. Enter q and then x to exit the Server Manager.
Installing cleansing packages
Installing a cleansing package prepares your system to use Data Cleanse
to control parsing of name and firm data for the specific cleansing package
language. Ensure that your environment meets the database-specific
codepage and disk space requirements. See the Products Availability Report
(PAR) available in the SAP BusinessObjects Support > Supported Platforms
section of the SAP Service Marketplace: http://service.sap.com/bosap-sup
port.
Note:
For custom Data Cleanse dictionaries you plan to create using Universal
Data Cleanse, you do not need to install a cleansing package. You can use
After Installation
4
Installing cleansing packages
the local or central repository. However, you must ensure that the repository
you use meets the database-specific codepage and version requirements.
1. Install the cleansing package data on both the client and server systems
by running ./install_console from the cleansing package installation
disc or downloaded location.
If you are using a systemthat has XWindows, you can run the installation
program in graphical mode by running ./install_gui.
The cleansing package installer lays down the required reference data
to LINK_DIR/DataQuality/datacleanse.
2. Use the Repository Manager to load the cleansing package files into your
repository.
Related Topics
Database-specific requirements for Data Cleanse on page 29
Using the Repository Manager
You can use the executable called repoman (stored in the $LINK_DIR/bin
directory) to create or update repositories after SAP BusinessObjects Data
Services 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)
4
After Installation
-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:
Description Flag
Repository login user
This parameter is required for all database types.
-U
Repository login password
-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
-S
Repository database type:
DB2
Oracle
Sybase
MySQL
-N
Repository database name
This parameter is required only for Sybase ASE, and in cleansing
package mode for MySQL.
-Q
After Installation
4
Description Flag
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 with
the database
GetVersionInfo
Reads the dictionary name and version information from the
zip file
-m
Cleansing package source zip file name -z
Database port number -p
4
After Installation
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 cleansing
package mode.
Note:
To upgrade a cleansing package, first export any dictionary changes using
the Designer. After loading the newcleansing package, reapply the dictionary
changes with the bulk load feature. Additionally, it's recommended that you
use the new rule file included with a new cleansing package. Using the new
rule file with an older dictionary may cause unpredictable results.
Related Topics
Upgrading cleansing packages on page 100
Using the Server Manager
Use the Server Manager to create, edit, or delete Job Servers and Access
Servers after installation.
The Server Manager displays the following:
After Installation
4
Job Server information
Description Option
This name uniquely identifies the Job Server. The Job
Server name cannot be changed.
Server name
The port number is a TCP/IP port that the Job Server uses
to receive commands from the Designer and an Access
Server. If a computer hosts multiple Job Servers, each Job
Server must have a unique port number. Choose a port
number that is not used by another process on the comput-
er. It's recommended that you use 3500. If you are unsure
of which port number to use, use the default port number
and increment it for each additional Job Server you config-
ure.
TCP/IP port num-
ber
If this computer hosts adapters or the SNMP agent, you
must designate one (and only one) Job Server to support
them. Once a Job Server is set to support adapters and
SNMP communication (a port is entered and saved), it is
marked on the Job Server Configuration screen with this
label.
Supports adapter
andSNMPcommu-
nication on port
This option enables SNMP support on the Job Server. After
one Job Server per computer is set as the one supporting
adapters and SNMP, it and additional Job Servers can be
enabled for SNMP.
Enable SNMP
Run-time resource information
Description Option
This directory contains the pageable cache that the software
uses for memory-intensive operations and for file transfer
types when Automatic is specified in the Data_Transfer
transform.
Pageable cache
directory
The software uses this starting port number for peer-to-peer
communication between data flows or sub data flows that
are running on different Job Servers. The default is 1025.
Start port
Access Server information
4
After Installation
Description Option
Server number This sequence number uniquely identifies the Access
Server on this machine. The Access Server number cannot
be changed.
The directory containing Access Server information. Directory
This port number is used to communicate between the
Access Server and the Administrator. The default is 4000.
Communication
port
Additional parameters used by the Access server
View Access Server parameters by typing AL_Ac
cessServer 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
Description Option
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
Description Option
The name or IP address of the SMTP server (for example,
mail.company.com)
Server
The e-mail address that will appear in the Fromfield of the
e-mail.
Sender
After Installation
4
To configure Job Servers
$ cd $LINK_DIR/bin/
$ . ./al_env.sh
$ ./svrcfg
Note:
2. Enter 3 to configure a Job Server
The Job Server information screen appears.
------------------------------------------------------------
** Current Job Server information **
------------------------------------------------------------
S# Job Server Name TCP Port Enable Repository
SNMP Information
-- --------------- -------- ------ ----------
1* Server1 19111 Y USR1@SVR1_ORACLE
2 Server2 19112 N USR2@SVR1_ORACLE
*:JobServer <S1> supports adapter and SNMP communication
on port:19110
------------------------------------------------------------
c: Create a new JOB SERVER entry a: Add a REPO to job
server
e: Edit a JOB SERVER entry y: Resync a REPO
d: Delete a JOB SERVER entry r: Remove a REPO from
job server
u: Update a REPO s: Set default REPO
q: Quit
The repository information is displayed as User@DatabaseConnec
tion__DatabaseType. For example, if the repository user is DSXI32,
the repository is an Oracle database, and the database connection name
is DSORCL, the repository information is shown as DSXI32@DSOR
CL_ORACLE.
3. Configure or delete a Job Server.
4
After Installation
Description Command
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 JobServ
er?
To disable SNMP for a job server, choose Y when
prompted with the following question:
Do you want to Disable SNMP for this JobServ
er?
e
Deletes an existing Job Server entry. d
Adds a repository connection to an existing Job Server. a
After Installation
4
Description Command
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 a
repository.
You must resynchronize your Job Server and repository
when:
You have uninstalled SAP BusinessObjects Data
Services and are reinstalling the same version without
creating 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 with
a repository, you must re-add a connection for this
repository to the Administrator. For more information, see
the Management Console: Administrator Guide.
y
When you add or edit a repository connection, you must specify the
database 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 password
except when creating a Job Server or adding a repository. To update the
repository password in the DSConfig.txt file, enter u. All options use
the updated password from DSConfig.txt file.
4
After Installation
To configure run-time resources
$ cd $LINK_DIR/bin/
$ . ./al_env.sh
$ ./svrcfg
Note:
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 Port
LINK_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, and
Detailed 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 concurrently
running jobs or data flows and the amount of pageable cache required
by each concurrent data flow.
After Installation
4
Exists on a separate disk or file systemfromthe SAP BusinessObjects
Data Services system and operating system.
Limits the disk space that data flows consume. The pageable cache
uses all available disk space on the file system that contains the
pageable cache directory. To limit the disk space that data flows
consume, create a file system with a limited size. Use the new file
system 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 of
ports used by the software for peer-to-peer communications. The default
values are 1025 and 32767, respectively.
The software uses these ports for peer-to-peer communications when
sending data between data flows or sub data flows that are running on
different Job Servers.
Related Topics
Performance Optimization Guide: Using grid computing to distribute data
flow execution
To configure Access Servers
$ cd $LINK_DIR/bin/
$ . ./al_env.sh
$ ./svrcfg
Note:
2. Enter 4 to configure an Access Server.
4
After Installation
The Access Server information screen appears.
--------------------------------------------------------------
** Current Access Server information **
--------------------------------------------------------------
S# Directory Communication Port Enable
-- --------------- ------------------ ----------
1 export/AStest1 7897 Y
2 export/AStest2 7898 Y
c: Create a new access server entry e: Edit an access
server entry
d: Delete an access server entry q: Quit
3. Configure or delete an Access Server.
After Installation
4
Description Command
Creates a new Access Server.
Enter the directory, port numbers, and parameters, and
indicate whether you want to enable the access server.
You can configure more than one Access Server on the
same computer, but each must have separate ports. If
you enter a port number already in use, an error message
appears.
Note:
Access Server parameters can be viewed by typing AL_Ac
cessServer 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 are
stopped. When you exit the Server Manager, the remaining
Access Servers restart.
d
To start or stop the service
The SAP BusinessObjects Data Services service (AL_JobService) is a
daemon associated with $LINK_DIR that starts locally-configured Job Servers
and Access Servers and then monitors them and attempts to restart them if
they are not running.
4
After Installation
After exiting the Server Manager, AL_JobService automatically retrieves any
changes made to Job Servers or Access Servers. You do not need to restart
AL_JobService.
$ cd $LINK_DIR/bin/
$ . ./al_env.sh
$ ./svrcfg
Note:
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 running
the 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.
After Installation
4
To configure SMTP email
The Server Manager can be used to specify SMTP server settings for the
smtp_to email function. For more information, see "To define and enable
the smtp_to function" in the Reference Guide.
Using the License Manager
License Manager lets you manage your product activation keycodesthe
alphanumeric codes that are referred to each time that you run certain
software. By using License Manager, you can view, add, and remove product
activation keycodes for SAP BusinessObjects solution portfolio software
(such as SAP BusinessObjects Data Services) that require them.
Note:
License Manager accesses keycodes on the local system only; you cannot
access the keycodes froma remote system. When updating keycodes, make
the changes on all SAP BusinessObjects Data Services computers by
launching License Manager on each computer, including Designer and Job
Server computers.
Setting up License Manager
Before you can use License manager, you need to set the environment
variable BOE_REGISTRYHOME. Although you can use a different setting, it's
strongly 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
4
After Installation
To start License Manager
You can run License Manager after the SAP BusinessObjects Data Services
installation has completed.
Run LicenseManager from the command-line without specifying any
options.
$ cd $LINK_DIR/bin
$ ./LicenseManager
Note:
If X-Windows is not available, you can use License Manager in
command-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) sorted
alphabetically.
2. Select a licensed product or feature in the Registered Keycodes tree to
view detailed information:
Product or feature keycode
Whether the keycode is a trial version
Whether the keycode is expired
Number of days remaining until the keycode expires
To add product activation keycodes
2. In the Product Activation Keycodes text box, enter the keycode(s) that
you want to add (each keycode must be on a separate line) and click
Add.
After Installation
4
The keycodes that will be added are displayed in the Registered
Keycodes tree and highlighted.
3. When you are satisfied with the changes that will be made, click Save.
The keycode highlighting is removed.
Tip:
If you do not want to save the keycode changes, close License Manager
without saving the changes.
4. After you have saved your changes, click Close to exit License Manager.
5. To make sure the new keycode(s) take effect, restart the software.
To remove product activation keycodes
2. In the Registered Keycodes tree, select the keycode(s) that you want
to remove and click Remove.
The keycodes that will be removed are crossed out, and any affected
nodes are highlighted.
3. When you are satisfied with the changes that will be made, click Save.
The crossed-out keycodes are removed.
Tip:
If you do not want to save the keycode changes, close License Manager
without saving the changes.
4. After you have saved your changes, click Close to exit License Manager.
5. Restart the software.
To use License Manager from the command line
License Manager includes a command-line mode that you can use if you
don't want to use the graphical interface, or need to script License Manager
operations.
4
After Installation
Syntax
LicenseManager [-v | -a keycode | -r keycode [-l location]]
Description Parameter
Displays the stored product activation keycodes in a
format similar to the License Manager graphical inter-
face. For example:
------ Registered Keycodes ------
EIM Titan
Suite 12.0
Data Services XI 3.1 Premium
Keycode: 00000-0000000-0000000-0000
Trial Option: Yes
Expired: No
Days Remaining: 54
-v or --view
Adds the specified license keycode, and displays the
stored keycodes in a format similar to the License
Manager graphical interface. Returns status messages
for the following conditions:
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 key
code
After Installation
4
Description Parameter
Removes the specified product activation keycode,
and displays the stored keycodes in a format similar
to the License Manager graphical interface. If loca
tion is specified, the removal is restricted to that
node. Returns status messages for the following
conditions:
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 key
code [-l location]
Controllingthe Tomcat applicationserver
SAP BusinessObjects Data Services includes shell scripts to start and stop
the packaged Tomcat application server.
To start the Tomcat application server, run tomcatstartup.sh with the
syntax required by your environment. For example:
$ cd $LINK_DIR/
$ ../bobje/tomcatstartup.sh
To stop the Tomcat application server, run tomcatshutdown.sh with the
syntax required by your environment. For example:
$ cd $LINK_DIR/
$ ../bobje/tomcatshutdown.sh
4
After Installation
Controlling 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 the
computer 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 you
cannot ping by name, contact your local network administrator.
Check how long netstat -a takes to run and expect at least that amount
of time to configure SAP BusinessObjects Data Services services.
Server Manager problems
If you encounter any of the following situations, reset all SAPBusinessObjects
Data Services processes:
Five to ten minutes after starting the Server Manager, you still receive
messages 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 Installation
4
3. Wait at least 30 seconds for the AL_JobService and other processes to
shut down. This time period might be longer if there are many instances
of Job Servers and Access Servers in the installation.
4. Verify that the AL_JobService, al_jobserver, and AL_AccessServer
processes 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 installation
problems include:
The Management Console login page cannot be found.
4
After Installation
This problem can occur when the web application service is not running
or 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 the
application port, you may need to modify the link to the Management
Console. In LINK_DIR/ext/DataServices.html, replace 9080 in the
following line with your WebSphere application port:
<META HTTP-EQUIV=Refresh CONTENT= "0; URL=http://host
name:9080/DataServices/">
Auto Documentation or Impact and Lineage do not work on a Tomcat
application server.
This problemcan occur when the Tomcat application server is not correctly
configured to use multi-byte data. You can correct this problemby adding
useBodyEncodingForURI="true" to your Tomcat server.xml
configuration 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's
Windows installer, which does not include certain files needed by the
wdeploy process used by the SAP BusinessObjects Data Services
installation program. You can correct this problemby downloading Tomcat
in a zip file from the Apache website. Extracting the zip file and copy any
missing files to the existing Tomcat installation location.
Memory issues
As with any computer on which a Job Server is running, reserve enough
space for the SAP BusinessObjects Data Services engine to cache tables
After Installation
4
and extract all data necessary to perform hierarchy flattening, sorts, or
lookups.
If you see memory-related errors, consider changing the following system
settings:
Maximum virtual memory per process
If this setting is low enough to interfere with software operations, you
might see messages describing low-memory errors.
Maximum number of files per process
If this setting is low enough to interfere with software or database server
operations, you might see messages describing file open errors.
Maximum stack size per process
might see messages describing segmentation- violation errors.
Maximum data segment size per process
might 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 an
error 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-RISC
32-bit and 1024 on HP-UX for Itanium64-bit. If you receive additional errors,
contact Technical Customer Assurance.
4
After Installation
After Installation
4 Troubleshooting installation problems
Directory Data
5
What are directories?
To correct addresses and assign codes with SAP BusinessObjects Data
Services, the Address Cleanse transformrelies on directories, or databases.
When Address Cleanse uses the directories, its similar to the way that you
use the telephone directory. A telephone directory is a large table in which
you look up something you knowsomeones nameand locate something
that you dont knowtheir phone number.
You may not need to use all of the reference files depending on which
transforms or options you use. Depending on which option you own, some
disks or online packages that you receive may contain extra files in addition
to your directories. For example, you may see an Extract folder. If you do
not need these extra files, do not copy themto your computer. For information
about extra folders, see the ReadMe.txt file included with the reference files.
Directory listing and update schedule
Updated Monthly
(M)
Bimonthly (B)
Quarterly (Q)
Approximate
Size
Directory filename Directory type
MB 699 MB zip4us.dir ZIP4 and Auxiliary Directories
MB
2 MB
2 MB
1 MB
97 MB
4 MB
cityxx.dir
zcfxx.dir
revzip4.dir
zip4us.rev
zip4us.shs
Auxiliary Directories
Weekly 1 MB ewyymmdd.dir Early Warning System Directory
M 653 MB dpv_path DPV Data
M 486MB elot.dir Enhanced Line of Travel Directory
Directory Data
5
Updated Monthly
(M)
Bimonthly (B)
Quarterly (Q)
Approximate
Size
M 42 MB
canada.dir
cancity.dir
canfsa.dir
canpci.dir
Canada engine - Address Data
MQ 200 MB
apc.dir
aucity.dir
aus.dir
Australia engine - Address Data
Q up to 12.2 GB
(for all countries)
all files Global Address engine and EMEA
Engine - Data
Note:
You will receive files only for those
countries your company has pur-
chased.
Q 720 MB cgeox.dir Centroid Level Geo Data
Q 4.67 GB ageox.dir Address Level Geo Data
5
Directory Data
Updated Monthly
(M)
Bimonthly (B)
Quarterly (Q)
Approximate
Size
Q
Canada: 1.6
GB
Canada: 1 MB
France: 1.6 GB
France: 6 MB
USA: < 2 GB
USA: < 2 GB
geo_addr_ca_ven
dorx .dir
geo_cent_ca_ven
dorx .dir
geo_addr_fr_ven
dorx .dir
geo_cent_fr_ven
dorx .dir
geo_addr_us_ven
dorx<num> .dir
geo_cent_us_ven
dorx<num> .dir
Geocoder
M 199 MB z4change.dir Z4Change Data
461 MB all files LACSLink
Q
248 MB ga_re
gion_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 Global
Suggestion Lists
Directory Data
5
U.S. Directory expiration
We publish and distribute the ZIP4 and supporting directory files under a
non-exclusive license from the USPS. The USPS requires that our software
disable itself when a user attempts to use expired directories.
If you do not install new directories as you receive them, the software issues
a warning in the log files when the directories are due to expire within 30
days. To ensure that your projects are based on up-to-date directory data,
it's recommended that you heed the warning and install the latest directories.
Note:
Incompatible or out-of-date directories can render the software unusable.
The directories are lookup files used by SAP BusinessObjects solution
portfolio software. The systemadministrator must install monthly or bimonthly
directory updates to ensure that they are compatible with the current software.
U.S. Directory expiration schedule
You can choose to receive updated U.S. national directories on a monthly
or bimonthly basis. Bimonthly updates are distributed during the even months.
Directory expiration guidelines are:
ZIP4 and Auxiliary Directories expire on 1st day of the fourth month after
directory creation. When running in Non-Certified mode, Zip4 and Auxiliary
directories expire on first day of the fourteenth month after directory
creation.
LACSLink directories expire 105 days after directory creation.
U.S. National and Auxiliary files
The U.S. National and Auxiliary file self-extracting files are named as follows.
5
Directory Data
U.S. Directory expiration
Zip file name Directory name
us_dirs_2004.exe 2004-2008 U.S. National
directory
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 directories
We recommend that you install the directory files in a common file system
directory local to the system in which SAP BusinessObjects Data Services
is installed. By default, the software looks for directories in
LINK_DIR/DataQuality/reference_data. If you place your directories in
a different location, you must update your substitution file.
Note:
Installing Global Address Cleanse directory files on file servers may lead to
speed loss and lock problems. The target directory name may contain blank
characters, but no umlauts.
Directory Data
5
Where to copy directories
Copy International directories files to a non-default
location
If you use the EMEA engine or Global Suggestion Lists and store your data
directories in a location other than the default (LINK_DIR/DataQuality/ref
erence_data), do the following:
1. Stop any dataflows that use the EMEA engine, Global engine, or Global
Suggestion Lists.
2. Stop the Address Server.
3. Copy the following files from LINK_DIR/DataQuality/reference_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 software
update, copy the reference files from the default location to where you
store your directories.
4. Update the REFERENCE_DATA_DIRECTORY parameter in the Ad
dressServerConfig.txt file located in LINK_DIR/bin/address_server/
to the new reference directory location.
5. Update the RefFilesAddressCleanse substitution parameter configuration
to the new reference directory location.
Related Topics
To start or stop the Address Server on page 76
To install and set up Download Manager
Before you can download directory files, you need to install and set up
Download Manager.
5
Directory Data
To install and set up Download Manager
To install and set up Download Manager:
1. Access the SAPService Marketplace (SMP): http://service.sap.com/bosap-
support
2. Select Downloads.
3. Select Download Basket.
4. Click the Get Download Manager button.
5. Follow the steps to install and set up the Download Manager.
To download directory files
The directories are available for download fromthe SAP Service Marketplace
(SMP).
To download directories:
1. Access the SAP Service Marketplace (SMP) site: http://ser
vice.sap.com/bosap-support
2. Select Downloads.
3. From the left pane, select Downloads > SAP Software Distribution
Center > Downloads > Installations and Upgrades > My Company's
Application Components.
A list of your company's applications and any license-free products or
components appear.
4. Select the files you want to download and add them to the Download
Basket.
The files you select are placed in the Download Basket.
5. To access the Download Basket, click Download Basket.
6. To access the Download Manager documentation, click Get Download
Manager.
7. Follow the steps included in the Download Manager documentation to
download the directory files.
Unzip UNIX/Linux files with Info-Zip
The steps listed here describe how to install the zipped directories using
Info-Zip for UNIX/Linux. If you use a different unzip tool, see the unzip
procedure included with that tool.
Directory Data
5
To download directory files
1. Copy the zipped directory files manually fromthe CDto the location where
you keep your directories.
2. Type unzip filename.zip -d outputfolder.
For ZIP4US, type unzip us_dirs_2004.zip -d /Business
Objects/BusinessObjects Data Services/DataQuality/reference_data).
3. For each required file, repeat steps 1 and 2.
5
Directory Data
Unzip UNIX/Linux files with Info-Zip
Directory Data
5 Unzip UNIX/Linux files with Info-Zip
Maintaining your installation
6
Upgrading the software
To upgrade from an existing SAP BusinessObjects Data Integrator or SAP
BusinessObjects Data Services installation, install the new components and
then upgrade your repositories. To upgrade from an existing SAP
BusinessObjects Data Quality Management installation, see the Migration
Considerations.
Maintenance installation
When the SAP BusinessObjects Data Services installation program detects
that you are installing to the same location as an existing installation, it allows
you to perform a maintenance installation.
A maintenance installation differs froma standard installation in several ways:
The installation program automatically detects and retrieves the first
existing base keycode.
The installation program automatically detects which components are
installed, and selects them for the maintenance installation. You can still
choose to change the installed components, however.
Note:
If the server components are already installed, their configuration screens
will be skipped and the existing configuration is retained. Job Servers
and Access Servers will still be working after the update. Web applications
must 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, Job
Service, and packaged Tomcat processes. If you use other processes in
your installation, such as the Address Server, stop them before starting
a maintenance installation.
Maintenance installation removes all deployed web applications, as well
as the packaged Tomcat application server, if it is installed. If you have
6
third-party web applications deployed to the packaged Tomcat application
server, undeploy them before starting a maintenance installation, and
re-deploy them after installation has finished.
Migration installation
When the SAP BusinessObjects Data Services installation program detects
that you are installing to the same location as an existing installation, it allows
you to perform a migration installation.
The installation program allows a migration installation under the following
conditions:
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 is
merged into the new DSConfig.txt file.
Note:
If you choose to reuse the configuration, the Job Server and Access
Server configuration screens will be skipped and the existing configuration
is retained.
After installation, a newal_env.sh file is created, and the old file is moved
to LINK_DIR/bin/al_env.sh.old. You can merge database environment
information 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 Access
Servers are not restarted automatically.
The installation program performs several directory modifications.
For example, if your SAP BusinessObjects Data Integrator installation
was located at /home/BusinessObjects/DataIntegrator/ and the
migration installation location is /home/BusinessObjects/, the migration
6
installation creates newbobje, setup, tmp, and dataservices directories
under /home/BusinessObjects/.
A previous installation of SAP BusinessObjects Data Integrator may have
set the CATALINA_HOME environment variable. The packaged Tomcat
application server uses this environment variable, and may not start if the
value does not match its location.
Before starting the packaged Tomcat application server, unset the
CATALINA_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 customizations
as well as all custom dictionaries created using Universal Data Cleanse. If
upgrade is required, it is critical that you export your dictionary changes prior
to uninstalling your current version of the software in order to be able make
the dictionary information available in the upgraded version. Specific upgrade
information is included in the Release Notes. For more information, see the
Release Notes.
In upgrades between versions of SAP BusinessObjects Data Services when
a cleansing package upgrade is not required (in other words, the cleansing
package upgrade is optional), you may still want to upgrade your existing
dictionaries to take advantage of the updated data in the new cleansing
package version. Updated data may include additional name or firm entries
or secondary information.
For custom dictionaries and rule files created with Universal Data Cleanse,
if the cleansing package upgrade is optional (not required), you need not
upgrade it. After upgrading your SAPBusinessObjects Data Services version,
in the Designer, choose Dictionary > Manage Connection to point to and
continue using the existing dictionary repository.
6
To upgrade cleansing packages
1. Choose Dictionary > Export Dictionary Changes in the Designer.
Your dictionary customizations are exported to an XML file.
2. Archive all files in LINK_DIR/DataQuality/datacleanse by moving them
to a different location.
3. Upgrade your SAP BusinessObjects Data Services version.
4. Run the cleansing package installer to install the new dictionary data and
rule file.
Note:
Run the cleansing package installer on both the server and client systems.
5. Use the Repository Manager to load the newcleansing package dictionary
into the repository.
6. Depending on your environment, do one of the following:
For custom dictionaries created with Universal Data Cleanse, choose
Dictionary > Bulk Load in the Designer to import the XML file created
in Step 1.
For cleansing package person_firm dictionaries, test your job with the
updated cleansing package data.
If the parsing results are not better or at par with previous results, try
importing your customizations from the previous cleansing package.
a. Choose Dictionary > Bulk Load in the Designer to import the XML
file created in Step 1.
b. Compare the rule file archived in Step 2 with the rule file installed
with the updated cleansing package.
c. Copy any rule customizations you made from the archived rule file
to the updated rule file.
Related Topics
Uninstalling the software from UNIX
1. Stop the service.
6
2. Remove automatic startup of the SAP BusinessObjects Data Services
service 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 files
recursively in $LINK_DIR.
rm -R $LINK_DIR
Related Topics
To start or stop the service on page 75
6
Index
A
Access Server
configuring 41, 73
B
Batch jobs
high availability support on AIX 59
C
cleansing package
repository 29
requirements 29
upgrading 101
cleansing packages
installing 62
upgrading 100
components
distribution 14
ports 19
configuring
Access Server 41
Job Server 41
Tomcat 43
web application server 44
cron utility 10
D
database
preparing 27
repository 27
database connectivity
configuring 56
database server
configuring 39
existing 39
Designer
connection to Job Server 82
directories
list 88
location 92
non-default location 93
U.S. directory expiration 91
unzipping 94
update schedule 88
directory data 88
E
environment variables 54
H
High Availability Clustered Multi Processing
(HACMP)
configuring for 61
support for on AIX 58
using 60
HP-UX
access permissions 10
memory 84
I
installation
beginning 36
overview 31
silent 33
standard 31, 32
starting 46
installation location
specifying 37
installed features
selecting 37
installing
cleansing packages 62
J
Job Server
configuring 41, 69
connection to Designer 82
high availability support for batch jobs 58
K
kernel configuration, recommended 11
L
license agreement
accepting 36
License Manager
environment variable 77
M
Management Console
troubleshooting 83
memory, HP-UX 84
N
network connections
checking 22
network requirements 9
P
ports
default numbers 19
description 19
processes
resetting 82
troubleshooting 82
product keycode 37
R
repository
central 18
creating 18
creating, multiple 63
local 18
repository database
configuring DB2 25
configuring MySQL 26
configuring Oracle 26
configuring Sybase 27
preparing 27
selecting 38
requirements
cleansing package repository 29
Data Cleanse 29
network 9
system 8
response file
creating 50
run-time resources
configuring 72
Index
S
scripted installation
performing 50
running 51
Server Manager
configuring Access Servers 73
configuring Job Servers 69
configuring run-time resources 72
configuring SMTP 77
starting or stopping the service 75
troubleshooting 82
using 66
services
starting automatically 58
silent installation
overview 33, 50
SMTP
configuring 77
standard installation
overview 31
performing 32
starting
services 58
system requirements 8
T
threading
HP-UX 85
troubleshooting 85
Tomcat
configuring 43
Tomcat (continued)
starting 81
stopping 81
troubleshooting
Designer to Job Server connection 82
resetting processes 82
Server Manager 82
threading issues 85
U
UNIX Job Server
upgrading
maintenance installation 98
migration installation 99
paths 98
user information 37
user resource limits
AIX 12
Linux 13
Solaris 13
V
variables, UNIX Job Server 54
W
web application server
configuring 44
selecting 42
Index
Index

Xi32 Ds Install Unix en

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Xi32 Ds Install Unix en

Hochgeladen von

Copyright:

Verfügbare Formate

SAPBusinessObjectsData Services

Installation Guide for UNIX

Das könnte Ihnen auch gefallen