Sag Entry

System Administrators Guide
for SAP BusinessObjects applications

such as ACE, DataRight IQ, Label Studio,
Match/Consolidate, Presort, and more
Installation
Supported operating systems
System requirements on all platforms
Troubleshooting
System Administrators Guide, Edition 4.8

November 2011
Copyright
2011 SAP AG. All rights reserved.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge,
ByDesign, SAP Business ByDesign, and other SAP products and services mentioned
herein as well as their respective logos are trademarks or registered trademarks of
SAP AG in Germany and other countries. BusinessObjects and the Business Objects
logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence,
Xcelsius, and other SAP BusinessObjects products and services mentioned herein as
well as their respective logos are trademarks or registered trademarks of Business
Objects S.A. in the United States and in other countries. Business Objects is an SAP
company. All other product and service names mentioned are the trademarks of their
respective companies. Data contained in this document serves informational purposes
only. National product specifications may vary. These materials are subject to change
without notice. These materials are provided by SAP AG and its affiliated companies
("SAP Group") for informational purposes only, without representation or warranty of
any kind, and SAP Group shall not be liable for errors or omissions with respect to the
materials. The only warranties for SAP Group products and services are those that are
set forth in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an additional
warranty.
For trademarks that are owned by the United States Postal Service, see
http://ribbs.usps.gov/files/NCOALINK/TRADEMARKS.PDF
Contents
Preface .............................................................................................................5
Planning for installation ................................................................................7
Using applications on Windows ..................................................................19
Using applications on UNIX ........................................................................33
Using Remote Views.....................................................................................43
License Manager ..........................................................................................59
Index ..............................................................................................................63
Contents
Preface
About this guide
This System Administrators Guide is a planning guide and reference for those
who use certain SAP BusinessObjects applications on Windows and UNIX.
(Remote Viewsour Windows interface for UNIXis installed on both
systems.) This guide explains system requirements and how to set up your system
to run your applications. For information about installing our programs and
downloading directories and patches, see this guides platform-specific
installation sections.
Who this guide is for
In a network setting, new software and updates are normally installed by the
system administrator. If you are not the administrator of your network, you
should ensure that your system administrator has access to this guide.
In providing this guide, we assume that youre already familiar with your
hardware, operating system(s), software, and administrative procedures. If this is
not so, we encourage you to contact us.
Applications that this

guide covers
This guide explains installation and setup issues related to the following SAP
BusinessObjects products.
ACE Views and ACE Library

Adaptors
DataRight IQ Views and DataRight IQ Library
Global Match and Global Match Library
Label Studio
License Manager
Match/Consolidate Views and Match/Consolidate Library
Match Library
Presort Views
RAPID
Remote Views
ZipCount
Other products may be discussed in their own documentation intended for system
administrators.
Conventions
This guide adheres to the following documentation conventions.

Convention
Description
Bold
Used for file names, paths, emphasis, and text that you should type
exactly as shown. For example, Type cd\dirs.
Italics
Used for emphasis and text for which you should substitute your own
data or values. For example, Type a name for your file, and the .txt
extension (testfile.txt).
Preface
Convention
Description
Menu
commands
Indicates commands that you choose from menus in the following format: Menu Name > Command Name. For example, Choose File >
New.
Alerts you to important information and potential problems.

Points out special cases that you should know about.
Draws your attention to tips that may be useful to you.
Chapter 1:
Planning for installation
This chapter provides information about system requirements, disk space, and
work space requirements. In addition, it includes general information about
directories and file structure.
Chapter 1: Planning for installation
System information
This section provides information on currently supported operating systems and
compilers. For projected system information, see the next section.
Currently supported
operating systems
and compilers
SAP BusinessObjects Postalsoft solutions are supported on the operating systems

listed below.
For your operating system and compiler you should run the same version that
SAP BusinessObjects usesor a later version. You should also ensure that your
operating system, runtime environments, and compilers are updated to the
recommendations of the respective vendors. (For information about possible
future OS requirements, see the next section.)
Operating system
Systems tested
Compiler
Windows Server 2003 SP2

(32-bit build on Win x64)
Windows XP Pro SP2 (64-bit only)

Windows Vista SP1
Windows Vista SP2
Windows 7
Windows 7 SP1
Windows Server 2003 R2 SP2
Windows Server 2008
Windows Server 2008 R2 (64-bit only)
MS VS .NET 2005 SP1 (MS VC 8.0SP1)

Security patches:
Microsoft Visual Studio 2005 Professional Edition ENU Service Pack 1 (KB926601)
Security Update for Microsoft Visual Studio 2005
Professional Edition - ENU (KB937061)
Security Update for Microsoft Visual Studio 2005
Professional Edition - ENU (KB971023)
Linux Red Hat 4.0 32-bit
Red Hat 4 32-bit

Red Hat 5 32-bit
gcc 4.1.2
Linux Red Hat 4.0 64-bit
Red Hat 4 64-bit

Red Hat 5 64-bit
Red Hat 6 64-bit
gcc 4.1.2
Linux SuSE 9.0 32-bit
SuSE 9.0 32-bit
gcc 4.1.2
SuSE 9.0 64-bit
gcc 4.1.2
SuSE 10.0 32-bit
gcc 4.1.2
SuSE 10.0 64-bit

SuSE 11.0 64-bit
gcc 4.1.2
AIX V5.3 32-bit
AIX V5.3 32-bit
IBM XL C/C++ Enterprise Edition V10.1 for AIX

IBM XL C/C++ for AIX, V10.1
Version: 10.01.0000.0000
AIX V5.3 64-bit
AIX V5.3 64-bit

AIX V6.1 64-bit
AIX V7.1 64-bit
IBM XL C/C++ Enterprise Edition V10.1 for AIX

IBM XL C/C++ for AIX, V10.1
Version: 10.01.0000.0000
Solaris 9 32-bit
Solaris 9 32-bit
Solaris 10 32-bit
Sun Studio 12
Sun C++ 5.9
SunOS_sparc Patch 124863-01 2007/07/25
Operating system
Systems tested
Compiler
Solaris 9 64-bit
Solaris 9 64-bit
Solaris 10 64-bit
Sun Studio 12
Sun C++ 5.9
SunOS_sparc Patch 124863-01 2007/07/25
HP-UX 11.11 PA-RISC 32bit
HP 11.11 PA-RISC 32-bit

HP-UX 11.11 PA-RISC 64bit

HP-UX 11.23 Itanium 64bit
HP-UX 11.23 Itanium 64-bit

aCC: HP aC++ANSI C B3910B A.06.16
System notes
Library and RAPID users
Our products are compiled only from the C++ compiler. To compile C under
C++, you must use a flag to achieve a C compile (for details, see your vendor
documentation).
Viewing online help on

newer Windows operating
systems
If you use one of the newer Windows operating system (such as Windows Vista,
Windows 7, and Windows Server 2008), to view the online help for products that
use WinHelp (.hlp) you must download and install the WinHlp32.exe file from
Microsoft. This executable is not installed with your SAP BusinessObjects
applications.
For more information about this issue (including download and installation
instructions), go to http://support.microsoft.com/kb/917607.
Missing libraries when

using Red Hat Linux
During installation of your SAP BusinessObjects software, the installer may tell
you it cannot locate a library file. Because every system is different, its difficult
to anticipate what libraries are or are not installed on your system.
To install a library, youll need to contact your System Administrator to install the
proper libraries for your operating system. If you are an administrator, youll need
to install the proper RPM (Redhat Package Manager) to get the library you need.
RPMs are packages that contain files that are used to install software on Linux
based systems. For example, with Red Hat Linux:
If youre missing this
Install the following RPM
libc.so.6 library
glibc-2.12-1.7.el6.i686.rpm package
libGLU.so.1
mesa-libGLU-7.7-2.el6.x86_64.rpm package
If you receive an error, login to http://service.sap.com/notes to search the SAP

Notes Knowledge Base for a solution.
System informationprojected
This section provides information on the possible future support by SAP
BusinessObjects Postalsoft solutions for operating systems. For current support,
see the previous section or your products release notes.
Disclaimer: This information is subject to change without prior notice.

The information in this section is provided by SAP BusinessObjects as a
courtesy only, with the intent that it may help you plan for the future. As SAP
BusinessObjects cannot control what third-party vendors will do, we cannot
guarantee that this information will be accurate in the future.
For authoritative information, see your operating system provider.
Operating systems
and compilers
The progression of new operating systems from vendors ensures enhanced

support for each new generation of processors available. To ensure the investment
and ongoing protection of your operating environment, make sure that the
migration of operating systems and runtime environment is monitored and
proactively managed within your organization.
Operating system
upgrades
We at SAP BusinessObjects keep abreast of changes in all of the operating

systems that we support. Generally, we allow 6 to 18 months before we upgrade
our products to a new operating-system standard. This ensures that the new
operating system is stable, that you have had time to upgrade to it, and that the
version change date, where possible, is coordinated with your product release
dates.
Discontinued operating
systems
Its important that you stay current on the operating system versions and updates
that your vendor supplies. As vendors discontinue their support and add new
platforms, Postalsoft must also end support for the old versions in order to
support the current versions. If you use an older version of an operating system,
we recommend that you upgrade in the near future.
Being regulatory driven, SAP BusinessObjects Postalsoft solutions may release
frequent support and service packs. For the latest information on OS support, see
your products release notes.
Vendor support and

migration tips
10
Operating system
Comment
Red Hat 4
Vendor support has ended. (Production Support 1 ended on 31

March 2009. Production Support 2 ended on 16 February 2011.)
We recommend migration to Red Hat Linux 6.
SuSE 9
Vendor support has ended. (General support ended on 31

August 2011.)
We recommend migration to SuSE 11.
Solaris 9
Vendor support has ended. (Premier support ended in October

2011.) (CSR 2011 was the last supported release of Solaris 9.)
We recommend migration to Solaris 11 in conjunction with the
2012 release.
HP-UX
Vendor support has ended. However, SAP BusinessObjects

plans to continue support for HP-UX 11.31 on PA-RISC and
Itanium (update 4) for 64-bit only until mid-2013 and discontinue all support for HP-UX after that.
We recommend migration to Red Hat Linux 6 or SuSE 11.
AIX 5.3
Vendor support ends on 30 April 2012. (CSR 2011 was the last
supported release of AIX 5.3.)
We recommend migration to AIX 7.1.
General customer notice to migrate to 64-bit on Linux and UNIX.

AIX 6.1 and 7.1 will be available only as 64-bit libs/apps (AIX will no longer
support 32-bit after 5.3 support is deprecated).
Solaris 10 is the last 32-bit Solaris release.
Red Hat 6 will be available only as 64-bit libs/apps. Red Hat 5 is the last 32bit Red Hat Linux release.
SuSE 11 will be available only as 64-bit libs/apps. SuSE 10 is the last 32-bit
SuSE Linux release.
Supported operating
systemsprojected
Below is listed the platform support that is anticipated by mid-year of 2012.

Although subject to change, this list may help you plan for future server
requirements.
Windows

Windows Vista SP2
Windows 7
Windows 7 SP1
Windows Server 2008 R2
(64-bit only)
(64-bit only)
Red Hat Linux
Red Hat Linux 5

Red Hat Linux 6 64-bit
Linux SuSE
SuSE 10
SuSE 11 (64-bit only)
AIX
AIX 6.1 64-bit

AIX 7.1 64-bit
Solaris
Solaris 10
Solaris 11 64-bit
HP-UX (PA-RISC)
HP-UX 11.31 PA-RISC 64-bit
HP-UX (Itanium)

-update 4
11
Space requirements
Space for installing
your application
Other considerations
To install all the files related to an application, you need an adequate amount of
disk space on your system. The following guidelines for selected applications
include the job-file, RAPID, Library program files, and any associated Views
files. These guidelines dont include the space needed directories and other files.
Application
Disk space required
ACE
300 MB
DataRight IQ
350 MB
Label Studio
60 MB
Match/Consolidate
550 MB
Printform
40 MB
Presort
73 MB
In addition to the disk space needed for installation, plan for space for work files,
output data, and accompanying directories (see Using directories on page 15).
You can install our products to a single machine, although you may prefer to
distribute the processing across several machines in some cases. The important
consideration is whether the system can handle all the processing with reasonable
speed, and whether the system has room to store all applications, directories, and
data, as well as work files and output files.
Space for working
Our applications may create temporary work files that remain on disk as long as
your job is active. You select the directory in which to store the work files and
then clean it up when a job (not a session) is finished.
The size of all work files varies, depending on choices that the user makes during
job setup. A general guideline is to allocate processing space up to 2.5 times the
input. However, extremely intensive processing may require up to six times the
input. For example, if you sort the file by ZIP Code in our ACE application, you
can also improve processing. Here are additional work-space considerations:
Product
Work space guidelines
Match/Consol- A detailed formula for estimating Match/Consoldiate work space is

idate
documented in the Match/Consolidate User Guide.
Space for output files

and reports
12
Presort
To estimate work space for Presort, multiply the number of database

records by 100 bytes. For example, to process one million records, Presort requires 100 million bytes (96 MB) of disk space for work files.
Label Studio
Requires 48 bytes per record; so, one million records would require 48
million bytes (46 MB or more) for work files.
Our applications can produce output files and reports. No set formula is available
for estimating their size. However, the output file is typically larger than the input
file because our applications let you add new fields and data. The output file may
be smaller if you choose not to carry over all fields or records from the input to
the output file.
Oracle work file
requirements
If you use Match/Consolidate: If your users need to access an Oracle database

with our Match/Consolidate application, additional work files will be created in
the work file directory. One of these, the .db file, may be quite large, depending
on the size of fields and number of records.
To calculate how large this file may be, multiply the combined length of all
selected fields by the total number of selected records (or rows). This number (in
bytes) is roughly the size of the .db file.
For example, if the combined length of all selected fields is 150 characters, and
there are 200,000 selected records, then the size of your .db file would be roughly
30 million bytes (30 MB).
Make sure you have enough disk space to accommodate these work files. They
are named as follows:
jobname.xx.db
jobname.xx.rdb
jobname.xx.def
Jobname is the name of the job file, and xx is the input-file number.
Working with large
files on Windows
If you work with large files (over 4 GB), we recommend that your drives be
partitioned as NTFS rather than FAT32.
Some users have run into problems processing large files (more than 4 GB) when
their drives are partitioned FAT32. They receive an error message no write
space even though the amount of space available is many times that of the file.
After they partition their drive to NTFS, the problem goes away.
13
How disk space affects performance

Many of our applications use large directories and spend much of their processing
time reading data from, or writing data to, the hard disk. These processes are very
disk-intensive. The speed of some of our applications depends more on disk
input/output than on your computers CPU or memory.
For example, our ACE application must read input records, read data from the
directories, and write out processed records. All three operations happen at the
same time, almost constantly, which can result in drive conflict or read/write
conflict (which means that ACE tries to read from and write to the same drive at
the same time).
Minimize drive
conflict
To minimize drive conflict, store the input file on one physical disk drive, the
output file on another, and our directories on a third disk. This segregation
enables ACE to find data in the directory much more quickly.
An example
The following diagram

illustrates a typical PC
configuration. (UNIX users
would similarly split input and
output across file systems.)
If you use only three physical disks (rather than the four pictured), you could
logically partition one disk (for example, C, where the files may be read
only) and reserve the other two disks for output files and directories.
In addition, create subdirectories for directories, input, and output. Do not write
to a root directory. Ensure that you inform users about the new file locations so
that they can insert the correct paths in their applications.
Similarly, some applications (such as Match/Consolidate and Presort) create
large, complex work files, and they may run faster if you store the input files on
one drive and the work files on another.
For example, if your input files are stored on your D drive, you might instruct the
program to place its work files on your E drive or a network drive. You can do
this by setting a parameter in the job file. (Note: Placing work files on a network
drive can slow down an application and counteract the time savings you might
see by splitting the files to different drives.)
Performance
14
Product performance is a sum of the components in your system. Your processor,

RAM, and disk speed all affect performance. You may optimize performance by
selecting a better component, or using specific drive configurations.
Using directories
What are directories?
Directories are lookup files whose data ranges from ZIP Codes to change of
address information. Some applications require directories to run. And some
directories are shared by several applications.
We recommend that you install directories in a common area, such as in /disk_n/
postware/dirs on UNIX, where disk_n is the name or number of the disk where
you install software, or \pw\dirs on Windows.
!
Installing directories
Use up-to-date directories: Incompatible or out-of-date directories can

render applications unusable. The system administrator must install monthly
directory updates to ensure that they are compatible with the current software.
For complete information on updating monthly or quarterly directories, see the

directory update letters.
To access SAP BusinessObjects documentation
1. Go to the SAP Help Portal at http://help.sap.com/.

2. Click the SAP BusinessObjects tab at the top of the screen
3. Click on the All Products tab (or click the link on the left navigation pane)
4. Click the all products drop-down and choose Addressing Directories, for
example.
5. Click the all releases drop-down to choose the directory letter.
Using Adaptors with
our applications
If you use one of our Adaptors and one of our application products (such as ACE
or Match/Consolidate), you may need to install one set of directories for the
Adaptor product in one area of your computer, and another for the application
product in another area of your computer. For more information see the product
documentation.
Directory expiration
The company publishes and distributes the ZIP+4 and supporting directories
under a non-exclusive license from the USPS. The USPS requires that our
software disable itself when a user attempts to use expired directories. (Our ACE
product allows non-mailers to turn off directory expirations. For details, see your
ACE documentation.)
If you do not install new directories as they become available, our products issue
a warning when the directories are due to expire within 30 days. Its
recommended that you heed the warning and install the latest directories to
ensure that your jobs are based on up-to-date directory data.
15
Downloading service packs and fix packs

To download the software
1. Go to https://service.sap.com/bosap-support.
2. Sign in with your S-User ID and password.
3. Scroll to the Download Software & Directories section.
If you are a new customers, click New products releases, installations and
upgrades. If you are an existing customer, click Support packages: service
packs, fix packs, merge modules.
4. Click on the product name. You may need to click the name several times on
subsequent pages.
5. Click the operating system name.
6. In the Downloads box, select the items you want and follow the download
instructions.
7. After you download the ZIP or TGZ file, uncompress it in a temporary
location.
Windows
Unzip the downloaded file and extract the files into a folder. For installation
instructions, see Installing on a single PC on page 21 or Installing on your
network on page 23.
UNIX/Linux
After you use the following directions to uncompress your downloaded file, see
Installing the application on page 35.
TGZ files
1. To uncompress a TGZ file, use the gunzip filename.tgz command (for

example, gunzip pst800cSP3.tgz).
2. Copy the .tar file to the appropriate area to extract the installation files.
3. Open a command prompt and type tar -xvfo filename.tar (for example, tar xvfo pst800cSP3.tar).
ZIP files
To uncompress the ZIP file, use the unzip filename.zip command (for example,
unzip pst800cSP3.zip).
Troubleshooting
If the unzip command does not work, consider these troubleshooting tips:
16
Typically, the unzip executable is found in the /usr/bin directory which may
need to be added to your path.
Try executing unzip using the full path: /usr/bin/unzip filename.zip.
To search for unzip, use the command: find . -name unzip.
Another option to uncompress the ZIP file if java is installed: jar -xvf
filename.zip (then use chmod -R 777 *).
If you still cannot uncompress, contact your System Administrator to have

the unzip utility installed.
Who to contact for

assistance
For technical assistance, log a support message on the SAP Service Marketplace
by clicking the Help & Support tab and then clicking Report a Product Error.
Choose a component code to route the support message to the core applications
support team.
Component
Products
EIM-COR
ACE, DataRight IQ, Match/Consolidate
EIM-COM
DeskTop Mailer, Business Edition, Presort, PrintForm, Label Studio
If you need assistance with the Service Marketplace, contact the Customer
Interaction Center (CIC) by email at support.bosapamerica@sap.com or call
(866)890-7686.
17
18
Chapter 2:
Using applications on Windows
This section gives specific information about installing SAP BusinessObjects

applications on Windows, including setting path and pw_path for the different
Windows versions, Oracle database information for Match/Consolidate users, and
tips and troubleshooting.
Chapter 2: Using applications on Windows
19
System requirements on Windows

Keep in mind that the following information is subject to change.
Supported Windows
versions
The applications covered by this System Administrators Guide require that your
machines use specific operating systems. For the most up-to-date information
about current operating system versions, see System information on page 8.
DLLs
Applications install or update numerous shared DLLs.

Type of DLL
Location
DLLs that are part of the OS (mostly

older files, if needed for updating)
\system32
DLLs that are not part of the OS
c:\Program Files\Common Files\firstlogic

Or, for Windows 7:
c:\Program Files\Common Files (x86)\firstlogic
DLLs for License Manager
c:\Program Files\Common Files\business

objects\license manager
Or, for Windows 7:
c:\Program Files\Common Files (x86)\business
objects\license manager
Note: Installation programs require administrative rights.

Processor
Applications for supported Windows OSes require a supported Intel-based or

compatible Windows-certified processor. We recommend that you use a Pentium
or equivalent processor with a minimum 400 MHz clock speed (1.0 GHz
recommended) for workstation versions of the operating system. While
applications will run on older hardware, performance is typically proportional to
the performance of the hardware on which it runs.
SAP BusinessObjects applications can be CPU-intensive and many are multithreaded. Multiple processors can significantly increase processing speed.
RAM
Many factors can influence the amount of RAM you need.
For servers
If you install to a server, your Windows server should have at least 256 MB of
RAM. If you plan to process large databases or complicated jobs, you should
have 512 MB to 2 G of RAM (or even more) for optimal server performance.
For workstations
If you install to a workstation, you need to use an adequate amount of RAM for
running our Job applications on Windows. For workstations on which you run
Views only, see System requirements for Remote Views on page 45 for RAM
recommendations.
For ACE
If you use ACE, keep in mind that memory caching requires more RAM when
you use DPV, LACSLink, NCOALink, and so on. For more information, see your
ACE Technical Users Guide.
20
For multi-tasking
Multi-tasking demands more RAM. For example, if you simultaneously run a job
program while using e-mail and a word processor, or simultaneously run more
than one job program, you need at least the recommended RAM to maintain
acceptable performance. Also, you can expect that many users will want to add
even more RAM to improve their systems multi-tasking performance.
SCSI hard drives
If you use SCSI hard drives, be sure to use the driver that matches your SCSI
controller card. If you do not, your software may not run properly or. In some
cases, your software may not run at all.
Printer drivers
SAP BusinessObjects applications do not use the Windows printer drivers either
for program output or reports. Instead, report format (lines, width, and header
information) is controlled by settings in the report setup in your job file, not the
Windows Print Manager. The printer codes sent to the printer by the Job program
take precedence over print controls that are part of your Windows environment.
The job programs generate reports in plain fixed-ASCII text format so that they
are compatible with many different kinds of printers. Its recommended that you
periodically check with your hardware supplier for updated drivers for your
Windows system.
Installing on a single PC
You can install and run applications on a single PC. For download instructions,
see Downloading service packs and fix packs on page 16.
See the release notes. If your applications release notes include installation
directions, follow those instructions instead. For example, in some cases
service packs and fix packs are not full installations, and so their directions
may differ from whats written here.
To begin installing
1. Initiate the installer by running setup.exe from the uncompressed ZIP file.
2. Follow all on-screen installation instructions. For example:
Installation directory: The Setup program suggests a default installation

directorysuch as c:\pw. Confirm the install directory or click Browse
to select a different directory.
Environment variables: The Setup program may ask if you want path and
pw_path set up for you. To have the paths configured automatically,
select Yes. If you select No, see Setting paths manually on page 27 to
set the paths manually.
License Manager: Depending on the products that youre installing, the

installation program may prompt you to run License Manager. For more
information about running License Manager, see the License Manager
appendix.
Remember, you must install the directories in order for the applications to work.
For more information, see Installing directories on page 24.
21
Preparing for network installation (Views and Job file)

You can install applications to an Intel-based or compatible Windows PC network
that consists of a Windows 2003 and 2008 server and Windows XP/Vista
workstations.
SAP BusinessObjects applications are tested on the Windows 2003 Server with
Service Pack 2, Windows 2008, and a combination of Windows XP Professional
and Vista workstations.
If you install an Adaptor product, see the Adaptor documentation for installation
information.
If you install an Adaptor product or RAPID in conjunction with a stand-alone
application like ACE or Presort, see Using an Adaptor or RAPID with a standalone application on page 25 for information about installing.
Planning for
performance
Installing to the
server and the
workstations
SAP BusinessObjects applications are disk-intensive. Any weakness in network

communication can negatively affect your output or work files. Follow these
guidelines:
Conduct a general assessment of the network infrastructure (cards, cables,

and so on).
Limit each drive partition to 2 GB if you use FAT 16 partitions. (If processing
larger files, its recommended that you use NTFS. For more information see
Two gigabyte partition limit (FAT only) on page 31.)
Install RAM sufficient for the system and application.
Distribute input and output in separate subdirectories (see the illustration on

page 14). Do not write to a root directory.
To run applications from a network, you must:

1. Install the applications, directories, and dictionaries on the server.
2. Install the Views application on the workstation. (Each workstation must
have DLLs specific to its operating system to operate.)
3. Use the client setup utility to prepare the workstations to run the applications.
When installation is complete, you set up jobs with Views on the workstation.
The job processes on the workstations processor, but the applications are stored
on the server.
22
Installing on your network

When you install applications on a network, you can prepare and run those
applications from any network workstation or from the server. First, you install
everything to the server and then you perform a client setup.
Setting up a network
configuration
For instructions on downloading the software, see Downloading service packs

and fix packs on page 16.
To begin installing
1. At your Windows server location, initiate the installer by running setup.exe

from the uncompressed ZIP file.
2. Follow all on-screen installation instructions. Define the server location (note
that location for later use). The installer prompts you to install the client
utility.
If you are installing at your Windows network server, and intend to run your
programs from a network workstation, click Yes to install the client utility.
Then, at the workstation(s), run the Client Setup utility to set up the
workstation(s) to access the program on the server.
If you plan to use the Client Setup utility, you must set up an appropriate
network share for the entire \pw directory, not just \pw\client.
3. The installation program may ask whether you want to install path and
pw_path.
Prepending the path. This prompt applies only to applications installed (for
example, C:\pw\ls; C:\pw\ace; and so on). Regardless of whether you answer
Yes or No to modifying variables, all of our program installers on Windows
automatically prepend c:/program files/common files/firstlogic to the path
environment variable.
When prompted to install path and pw_path, click Yes to automatically have
the paths configured, as necessary. If you click No, see Setting paths and
permissions manually on page 27.
4. Depending on the products that youre installing, the installation program

may prompt you to run License Manager. For more information about
running License Manager, see the License Manager appendix. (Keep in mind
that License Manager accesses keycodes on the local system only; you
cannot access the keycodes from a remote system.)
23
Setting up
workstations
After you install the application to your Windows server, go to the workstation
and set it up.
To set up a workstation
1. To make sure you have a clean environment, close all applications and reboot the workstation.
2. Be sure to share the pw directory on the server before you set up the
workstation.
3. From the client machine, map the pw directory or parent directory in the
server machine to a local drive (for example, x:) in the client machine.
4. Choose Start > Run.
5. At the Run prompt, type x: \pw\client\setup (x: is the mapped drive to which
this application was installed on the server. If you use a directory other than
pw, substitute that name for pw here.). Click OK.
The installation program copies the appropriate DLLs for the workstations
operating system and sets up the application icons.
Installing directories
Several applications use the same directory information. SAP BusinessObjects
recommends that you place the directories in a common area, such as \pw\dirs.
For a list of directories that are necessary for your application to run, see Using
directories on page 15.
24
Using an Adaptor or RAPID with a stand-alone application

Some users of an Adaptor or RAPID also use a stand-alone (batch) SAP
BusinessObjects application such as ACE or Presort.
Avoiding conflicts
If the Adaptor or RAPID and the stand-alone application are on the same
machine, conflicts may occur. What causes the conflicts? Your path and pw_path
environment variables point to locations of your products. If you try to run your
Adaptor or RAPID but your environment variable points to the stand-alone
application location first, the Adaptor or RAPID tries to use the software installed
for the stand-alone application, and vice versa.
To avoid this conflict
1. Set up different user profilesone for the Adaptor or RAPID and one for the
stand-alone application.
2. Set the environment variables in the Adaptor user profile to point to the
location of the Adaptor software as specified in the Adaptors users guide.
Likewise, set the environment variables in the RAPID profile to point to the
location of the RAPID software. See Setting paths and permissions
manually on page 27.
The environment variables in the stand-alone application user profile should
point to the location of the stand-alone application.
Using batch files
You can use Windows batch files to run the stand-alone application and the
Adaptor or RAPID from the same system. The following example shows a batch
file launching the ACE job file.
@echo off
set path=C:\pw\adm;C:\pw\ace;%path%
set pw_path=C:\pw\adm;C:\pw\ace;%pw_path%
pwace C:\pw\acejob.ace
This line launches the
ACE job-file program.
These two commands

insert the appropriate
paths to the ACErelated environment
variables before the
other paths.
When you use this procedure, the application that you run from the batch file uses
the environment that you set up in the batch file. All other applications that you
run use the normal environment variables that are set up for the user who is
logged in. A command-prompt window remains open until you close the
application that you launched from the batch file.
To use batch files
1. Set up the environment variables for your Adaptor or RAPID as specified in

the Adaptors Users Guide for Adaptor products, or in the appropriate
section for your Windows version later in this chapter.
2. Create a batch file that sets the proper environment variables for your standalone application and launches the job.
3. Create an additional batch file for each stand-alone application.
Use a shortcut? You can create a shortcut to the batch files and place it on the
desktop or Start menu. Just click the shortcut to run the batch file and launch
the stand-alone job.
25
Running Match/Consolidate and accessing Oracle

Match/Consolidate users can use an Oracle database, just as they use other types
of databases through your Oracle client. The Oracle server can be on Windows or
UNIX. However, to set up their Match/Consolidate job to access an Oracle
database, they need information from the RDB file that the system administrator
enters.
RDB file
Enabling and
disabling access
26
The RDB file contains descriptive information about the database. This file takes
the place of the input file and the FMT file in the Match/Consolidate job setup. To
run Match/Consolidate with Oracle access, users need to enter the following
information in their RDB file.
Setting
Description
UID
User name or identification, needed to access the Oracle database.
PWD
User password, needed to access the Oracle database.
DSN
Database file.
SELECT
Statement that tells Oracle the data to retrieve from the database.
To initiate or disable Oracle usage, run set_ora.bat. For more information, see
Accessing an Oracle database on page 40.
Setting paths and permissions manually

The installation software can automatically set your paths. If you choose to set
your paths manually or if you need to change your paths, continue with this
section.
Path and pw_path
Your Windows operating system uses a path to know where to look for installed
programs. This path lists all the directories that the operating system will search
in for an executable file. For the operating system to execute applications, your
pw directories must be included in the path statement.
In addition to an operating system path, our applications use pw_path, which
must include the name of the directory for each program that you are installing.
Setting paths
manually
The installation program prompts you to add our path and pw_path variables to
your operating systems path. However, at times you may need to enter or adjust
them manually. So, after you install our applications, you must edit the path
statement and add the pw_path statement.
The installation program for Views applications updates the system registry, but
underlying code requires that path and pw_path be set.
After you set path and pw_path for your applications, you dont need to set them
again for program revisions or updates. If you add another product, you need to
add only that products directory to the path and pw_path statements.
Environment variables
If you use a Windows operating system, you can set paths and other environment
variables as user or system variables.
Variable type
Discussion
User
A user variable is applicable only to a specific user. That is, it
applies only when the appropriate user name logs into the system.
System
A system variable is applicable to everyone who logs into the system. (Only a system administrator can set system variables in a supported Windows operating system.)
If you choose to set path and pw_path as user environment variables (rather than
as system variables), be sure to do so for each user who accesses applications.
27
Product directories
The purpose of setting path and pw_path statements is to tell your operating
system where to find installed applications. To help you do that, the table below
lists the syntax that you should type in the path and pw_path statements for each
product that you own (assuming that you installed in the default directory).
Separate entries with a semi-colon (;).
For more information about setting path and pw_path, see the specific
instructions for your Windows operating system on the following pages.
Permissions
The network administrator is responsible for setting access permissions after

completing installation. The installation program does not set network access or
multi-user permissions. The network administrator must ensure that users have
appropriate rights so that when a Views define options setting changes, Views can
write changes to the registry. Currently, Windows XP users need administrative
rights on their machine to support registry updates.
Your users will need Read and Execute access to the pw directory and each
subdirectoryadm, dirs, and so on. Normally, users should not have Write
access to those directories. However, make sure that they do have Write access to
the directories where they may write work files, output data, or reports.
Product path settings

Product
path and pw_path
All products
adm
All RAPID products
rapid
ACE
ace
ACE Library
acelib
DataRight IQ Library
dtr_iqlib
Global Match
gmatch
Global Match Library
mtc
Label Studio
ls;ls\system (Note that Label Studio requires two settings

for path and pw_path.)
Match Library
mtc
Match/Consolidate
mpg
Match/Consolidate Library mplib
28
Presort
pst
Remote Views
csgui
ZipCount
la
Setting path and pw_path in Windows XP

Keep in mind that License Manager requires entries in both PATH and
PW_PATH. For more information see License Manager on page 59.
The directions for setting environment variables may vary slightly
depending on your version of the Windows operating system.
System versus user
variables
System variables are available to every user logged on the system. Administrative
rights are required to set system variables.
User variables apply only when the appropriate user name logs into the system. If
you decide to create path and pw_path as user variables, be sure to do so for each
user who accesses applications.
Setting the path

variable
To set the path
1. Click Start > Settings > Control Panel.

2. Click the System icon.
3. In the System Properties window, select the Advanced tab.
4. Click the Environment Variables button.
The Environment Variables window appears
5. In the System Variables section, look for the Path variable. You must edit this
variableor create and define it if the variable doesnt already exist.
To create the path variable
1. In the System Variables section of the Environment Variables window, click

New.
The New System Variable window appears.
2. In the Variable Name box, type Path.
3. In the Variable Value box, type directory names for only SAP
BusinessObjects products. (For a table of product directory names, see
Product directories on page 28.) Separate listings with a semi-colon and
include no spaces. For example:
c:\pw\adm;c:\pw\ace;c:\pw\mpg
4. To close the New System Variable window, click OK.
29
To edit the path variable
1. In the System Variables section of the Environment Variables window,

highlight the path and click Edit
The Edit System Variable window appears.
2. In the Variable Value box, add a product directory name for each product.
(For a table of product directory names, see Product directories on
page 28.) Separate values with a semi-colon and include no spaces. For
example:
3. To close the Edit System Variable window, click OK.

Setting pw_path
If this is the first installation of any programs, you do not yet have a pw_path
variable. You need to create and define the variable.
To create the pw_path variable
1. In the System Variables section of the Environment Variables window, click

New.
2. In the New Variable Name box, type pw_path.
3. In the Variable Value box, type a set of product directory names identical to
the ones you typed for the path variable. As you did with the path variable,
separate values with a semi-colon and include no spaces. For example:
If you use Label Studio, create these directories: c:\pw\ls;c:\pw\ls\

system
4. To close the New System Variable window, click OK.
5. To close the Environment Variables window and activate your changes, click
OK. You must close and re-open any running programs for environment
variable changes to take effect.
Verifying environment
variables
When you verify environment variables, you use the System Information utility.
To verify your environment variables
1. Choose Start > Run.

2. Type msinfo32.exe and click OK.
3. Click Software Environment.
4. In the System Information window, select Environment Variables.
The window displays all variables, their values, and the name of the user.
5. Scroll to or search for the path or pw_path entries. To verify both the system
and user variable entries, look at the User Name column (which may require
that you scroll to the right).
30
Uninstalling applications
You can uninstall any application that you installed in the recommended manner.
Your process may differ: The directions for uninstalling may vary slightly
depending on your version of the Windows operating system.
To uninstall
1. Choose Start > Settings > Control Panel.

2. At the Control Panel window, select Add/Remove Programs.
The Add/Remove Programs Property window appears.
3. Select the Install/Uninstall tab.
4. When searching for the application that you want to uninstall, look first for
the words Business Objects (or SAP BusinessObjects) and then for the
application name, listed alphabetically.
In order to completely remove a product, there may be multiple uninstalls
that need to be done for each product, so pay special attention to the
application names.
5. To remove one of our applications, select the program to delete and click the
Change or Remove Programs button.
6. Clean up, if necessary by using Explorer. (If user directories or data are
stored in the directory structure, the Uninstall utility cannot completely
remove the tree. You need to use Explorer to complete any cleanup on the
system.)
Troubleshooting and tips for Windows

Long file names
In batch files and some text files, a long file name that contains a space must be
enclosed in quotes.
Bookmarks
When we distribute an update to an online help file, it might not accommodate all
of the bookmarks that you have placed in the previous version of the on-line help.
You may need to re-enter bookmarks in the updated file.
Two gigabyte
partition limit (FAT
only)
Any FAT partition is limited to two gigabytes, whether the partition is local or on
a network drive. The NTFS system is not affected by this limit.
Network
troubleshooting
We may be able to help you with a basic assessment of some network issues.
However, we cannot serve as your network administrator. Serious network
problems may require the services of a consultant or systems engineer.
In addition, note that any Windows version could create a FAT partition and in
that event, the partition should not exceed two gigabytes.
31
If you report problems running our program(s) on your network, we will attempt
to reproduce the problem using the same server and workstation operating
systems that we use for testing.
Problems with work files
on network drives
Applications group
Some of our customers have reported intermittent problems accessing work files
when the files are stored on a network drive. If you use a PC-based server,
consider the following tips to ensure proper work-file storage on your network.
Verify network operation. System performance can be affected by your

choice of hardware components and how well they work together. Because
work-file storage on a network is a high-speed input/output process, your
network server must be able to handle this task.
Correct hardware deficiencies. Data issues can result from some simple
network problems, such as defective hard drive cables, terminators, network
cable, network cards, and related accessories. By correcting a problem with
any of these components, you can prevent losing valuable data.
Separate read and write. To minimize drive conflict, store the input file on
one physical disk drive, the output file on another, and SAP BusinessObjects
directories on a third disk.
Service Pack. Make sure that the correct Service Pack is installed to your
Windows operating system.
Memory. Make sure that enough memory is installed.
The first time you install a SAP BusinessObjects product, the setup utility adds an
Applications group in your Start menu. Most of our applications will be
represented there.
The appearance of your applications group may vary depending on your
applications and the version of your Windows operating system.
Samples subdirectory
The setup utility automatically defines the samples subdirectory as the working
directory for each product (in Windows, the working directory is referred to as the
start in property). Each samples subdirectory holds the quick tour files that
users can use when theyre first learning how to use products.
When users become familiar with SAP BusinessObjects products, you may want
to define the data directories as their working directory, rather than the samples
directory.
32
Chapter 3:
Using applications on UNIX
This section gives specific information about installing applications on UNIX or

Linux. If you use Remote Views, this section also helps to set the paths for the
following products:
ACE Views
DataRight IQ Views
Match/Consolidate Views
Presort Views
Label Studio
In addition, this chapter provides some tips and troubleshooting guidance.

System requirements
for UNIX
UNIX servers vary widely in the available combinations of processor and

memory configurations available. Therefore, SAP BusinessObjects cannot
provide you with a custom prescription in a multi-platform administrators guide.
Instead, contact one or more hardware vendors to compare the range of system
choices available to you and choose accordingly.
System recommendations
Although we cannot provide system requirements, below are guidelines for

selecting system components based on a specific minimum operating-system
version.
Item
Recommendation
Operating
system
For information about the UNIX platforms and versions that SAP
BusinessObjects supports, see System information on page 8.
Processor
Minimum. Use a minimum approximate processor speed of 400

megahertz (MHz).
Optimum. Use a multi-processor system to increase performance
(Match/Consolidate only). Our threaded implementations (that is,
Library and RAPID) gain the most benefit from this type of system.
RAM
Use 2 GB or more of RAM. This is the minimum in most current

UNIX systems. (Exception: 32-bit platforms such as the Intel-based
Linux operating system can operate in a 256 to 512 MB memory
range.)
If many users or
multi-tasking
If you plan to support a large number of users or if you plan to multitask, its recommended that you employ high processor speed and
advanced memory configurations.
For best performance, separate input, output, and directory locations
(see How disk space affects performance on page 14).
Chapter 3: Using applications on UNIX
33
Combining 32-bit and 64-bit applications on UNIX

Some applications are available in both 32-bit and 64-bit versions. In certain
situations you may need to use both versions together. The key to successfully
combining 32-bit and 64-bit applications on a 64-bit operating system is
identifying the following variables:
Variable
Note
Layer in the appli- Identifying this variable means that 32-bit data path can reliably
cation system used send data up to the 64-bit application. (Sending 64-bit data paths
to 32-bit applications is not recommended.)
Data path type of
communication
between the layers
A direct example
34
Is the type of communication indirect or direct?

Indirect communication does not require bit coordination. For
example, it is acceptable to have either a 32- or 64-bit TCP/IP
Client Server Packet regardless of what the application uses.
Direct communication requires 32-bit and 64-bit cooperation.
For an illustration of direct communication, see A direct
example below.
You can use Match/Consolidate with other job file products. In the scenario
below, notice that Match/Consolidate and Oracle are all 32-bit applications.
Preparing to install on UNIX

This section introduces the installation utility and describes how to use it to install
products on your UNIX system.
If youre installing an Adaptor product (previously known as a Connector or
Link), see the Adaptors documentation for installation information.
Installation creates
other subdirectories
We recommend that you install most of our products in /disk_n/postware. We

use /disk_n as an example for the documentation. It is a convention to refer to the
file system or disk where you choose to install the software.
The installation process sets up and names all subdirectories of .../disk_n/
postware. It creates product subdirectories (such as ace, dtr_iq, iace, merge,
presort, ls, and ls/system) only for those products that you install.
Note: Do not remove or rename the .../disk_n/postware directory or its
subdirectories. If you remove or rename these directories, SAP
BusinessObjects programs may not work. In addition, do not move files from
their subdirectory after installation.
For reasons of performance or disk space requirements, you may want to install
the large national ZIP+4 file (zip4us.dir) to a different disk.
Installing the application

See the release notes. If your applications release notes include installation
directions, follow those instructions instead. For example, in some cases
service packs and fix packs are not full installations, and so their directions
may differ from whats written here.
To install with install.bin
1. Download the software installation package from SAPs Service Marketplace

(SMP). For more information, see Downloading service packs and fix
packs on page 16.
2. Initiate the installer by running ./install.bin from the uncompressed ZIP or
TGZ file.
3. Read the introduction information and press Enter to continue.
4. When asked to read over the license agreement, type Y or N. Press Enter.
5. To accept the terms of the agreement, type Y and then press Enter.
6. Specify an installation directory.
Press Enter to install to the default directory. Or,
Type an installation directory name. Type Y to verify the path and then
press Enter to continue.
Do not include postware as part of the path; a postware subdirectory is
automatically added to the directory specified.
35
7. Install the product(s). By default, all products are selected.
To install all of the products, press Enter.
If you want to customize the products you want to install, type a comma
separated list of numbers representing the features that should be
deselected and press Enter (for example, 1, 3, 4).
The installer asks you to preview the list of products you want to install.
Press Enter to continue, or type back to go to the previous screen to change
your selection.
8. When all products are successfully installed on your machine, press Enter to
exit the console.
9. To complete the installation of your product you must also install the
directories. See Using directories on page 15.
Setting environment variables

.
Your operating system uses a path environment variable to know where to look
for installed programs. The path lists all the directories in which the operating
system will search for an executable file. In addition to an operating system path,
our products use pw_path, which also must include the name of the directory for
each of the installed programs.
License Manager: For information about setting environment variables for
License Manager, see the License Manager appendix. (License Manager is
required for ACE and Presort users.)
Setting paths
manually
You must manually set program directories to the operating systems path and
pw_path. After installing our programs, instruct users to edit the path statement
and add the pw_path statement in their login script file using the product names
shown below.
After you set path and pw_path for your programs, you do not need to set them
again for program updates. If you must maintain two versions of a program
simultaneously (for example, during a transition in postal regulations), you may
need to change path and pw_path statements. Be careful that only one version is
active at a time. If you purchase another Business Object product, add that
products directory to the existing path and pw_path statements.
Permissions
Its the responsibility of the network administrator to set access permissions after
installing programs. Users need read and execute access to the /disk_n/
postware directory and each subdirectory: adm, dirs, and so on. Normally, users
should not have write access to those directories; only to those that house their
data, jobs, and so on.
.
36
Separate directories: SAP BusinessObjects strongly recommends that you

keep data and jobs separate from program directories.
Product path settings
Setting path and

pw_path
Product
path and pw_path
All products
adm
All RAPID products
rapid
ACE
ace
ACE Library
acelib
DataRight IQ
dtr_iq
dtr_iqlib
Label Studio
ls;ls/system
Global Match
gmatch
Global Match Library
gmtc
Match Library
mtc
Match/Consolidate
merge
Match/Consolidate Library
mplib
Presort
presort
Remote Views
csgui
ZipCount
la
(Note that Label Studio requires two settings for

path and pw_path.)
How you set environment variables may differ depending on the shell you use.
The following instructions show how Bourne and C shell users can set path and
pw_path.
If this is the first time that you have installed any application, add the pw_path
line. Then, if you purchase another product later, just add the entry for that
product to the existing lines. For the correct product abbreviations, see Product
path settings on page 37.
Bourne shell
If you use Bourne shell, add product entries to your .profile or .login file. For
example:
PW_PATH=/disk_n/postware/adm:/disk_n/postware/dtr:/disk_n/
postware/ace
PATH=$PATH:$PW_PATH
export PATH PW_PATH
37
Bourne shell
(Label Studio specific)
If you use the Label Studio application, enter the following:

LS_INSTALL_PATH=/disk_n/postware/ls
export LS_INSTALL_PATH
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/disk_n/postware/adm
export LD_LIBRARY_PATH
PW_PATH=/disk_n/postware/adm:/disk_n/postware/csgui:/disk_n/
postware/ls
export PW_PATH
PATH=$PATH:$PW_PATH
export $PATH
C shell
If you use C shell (Berkeley), add product entries to your .cshrc file. For
example:
setenv PW_PATH /disk_n/postware/adm:/disk_n/postware/ace
setenv PATH ${PATH}:${PW_PATH}
C shell
(Label Studio specific)
If you use the Label Studio application, enter the following:

setenv LS_INSTALL_PATH=/disk_n/postware/ls
setenv LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/disk_n/postware/adm
setenv PW_PATH=/disk_n/postware/adm:/disk_n/postware/csgui:/
disk_n/postware/ls
38
Accessing shared libraries

Setting the shared
library path
In addition to setting path and pw_path, you must also set the shared library path
environment variable for each user in the appropriate login script. This ensures
that products use the correct files from the product folders in the /disk_n/
postware/ directory.
To set the shared library path
1. Determine the appropriate shared library path from the table.

Platform
Environment
AIX
LIBPATH
HP-UX
SHLIB_PATH
Linux
LD_LIBRARY_PATH
Solaris
LD_LIBRARY_PATH
2. If there is no shared library path, create one referring to

/disk_n/postware/product.
3. If there is an existing shared library path, append a path to
/disk_n/postware/product at the end of your existing entries.
For example, if your business has ACE Library on Solaris, your shared
library path using a Bash shell may look like this:
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/disk1/postware/acelib
Shared library path

settings
Here is a list of the shared library product path settings. Select the path name for
the product(s) that you own.
Product
path and pw_path
all products
postware/adm
ACE Library
acelib
DataRight IQ
dtr_iq
dtr_iqlib
Match Library
mtc
Match/Consolidate Library
mplib
39
Running Match/Consolidate and accessing Oracle

Perform this setup regardless of whether you plan to use an Oracle database.
This setup applies to you only if you want to run Match/Consolidate and you use
any of the following platforms: Solaris, HP-UX, or AIX
Setting the shared
library path
You must set the shared library path environment variable for each user in the
appropriate login script. If you use Match/Consolidate Remote Views, you also
need to set the shared library path environment variable in the system start script.
This ensures that Match/Consolidate uses the right libfloci files from the /disk_n/
postware/adm subdirectory. The libfloci is Match/Consolidates link to your
Oracle client software.
To set the shared library path
1. Determine the appropriate shared library path from the table below. Then
perform step 2 or 3.
Platform
Environment
Solaris
LD_LIBRARY_PATH
HP-UX
LD_LIBRARY_PATH (64-bit) or SHLIB_PATH (32-bit)
AIX
LIBPATH
2. If there is no shared library path, create one referring to

/disk_n/postware/adm.
3. If there is an existing shared library path, append a path to
/disk_n/postware/adm at the end of the existing entries.
Your shared library path may look like this:
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/disk_n/postware/adm:
Accessing an Oracle
database
To enable users to access an Oracle database from Match/Consolidate
1. Set the environment variables for your system (for more information, see
Setting path and pw_path on page 37).
2. Set the shared library path environment variable (as shown previously).
3. Log out and log in again to activate the changes. Log in as the user whose
script was updated.
4. At a command prompt, type the echo $environment variable to confirm that
the shared library path variable is set. For example, type:
echo $LD_LIBRARY_PATH
Your system should display the following response:
.../disk_n/postware/adm.
40
5. From the .../disk_n/postware/adm directory, run set_ora to copy the

necessary files to your system. To copy files to the correct location, choose
from the following prompts.
0
Exit without changing anything
No Oracle support
Oracle 10g support
Oracle 9i support
6. Instruct users to enter the following information in their RDB file:

Information
Description
UID
User name or identification, needed to access the Oracle database.
PWD
User password, needed to access the Oracle database.
DSN
Database file.
SELECT
Statement that tells Oracle the data to retrieve from the database.
The RDB file contains descriptive information about the database. It takes
the place of the FMT file in the Match/Consolidate job setup.
Disabling access
To disable access to Oracle databases from Match/Consolidate, run set_ora as

described above and select 1 for no Oracle support.
Troubleshooting and tips for UNIX

Installing on Solaris
To install on Solaris, run install.bin (for more instructions, see Installing the
application on page 35). If this method doesnt work, try one of the following
methods.
Option 1:
Set file permissions
Before you run install.bin, set all file permissions to a minimum of 755. For
example, type chmod 755* at the command line.
Option 2:
Install with JRE
If you have a Java Runtime Environment (JRE) version 1.4.2 or newer on your
system, run the install using that JRE. To do this, run install.bin passing in the
path to the JRE executable. For example, you would type install.bin /opt/java/
bin/java at the command line.
DPV processing on the

AIX platform
The Object Data Manager (ODM) processes DPV records. If you use AIX, you
need to make sure that the ODMDIR variable is set before processing. To display
the path to the ODM directory (for example, /usr/lib/objrepos), type the
following command: echo $ODMDIR. If the path does not exist, you need to set it.
41
Match/Consolidate on
Solaris, and HP-UX
For UNIX applications, the shared-library-path environment variable

(LD_LIBRARY_PATH) must be set in order for Match/Consolidate to use Oracle
databases. See Running Match/Consolidate and accessing Oracle on page 40.
If you use a Solaris or HP-UX, you must set this shared library path environment
variable if you plan to use Match/Consolidateregardless of whether or not you
will use Oracle databases.
Oracle work files
When you run Match/Consolidate with an Oracle database, additional work files
are created in the work file directory. One of these (the .db file) may become very
large, depending on the size of fields and number of records that you work with.
To calculate how large this file may be, multiply the combined length of all
selected fields by the total number of selected records (or rows). This number (in
bytes) is roughly the size of the .db file. For example, if the combined length of
all selected fields is 150 characters, and there are 200,000 selected records, then
the size of your .db file would be roughly 30 million bytes, or 30 MB.
Make sure that you have enough disk space to accommodate these work files:
jobname.xx.db
jobname.xx.rdb
jobname.xx.def
Jobname is the name of the job file and xx is the input file number.
Using RAPID with a

stand-alone
application
Some users of RAPID also use a stand-alone (batch) application such as ACE or
Presort. If RAPID and the stand-alone application are on the same machine, you
may encounter conflicts.
What causes the conflict?
Your path and pw_path environment variables point to locations of your

applications. If you try to run RAPID but your environment variable points to the
stand-alone application location first, RAPID tries to use the software installed
for that application, and vice versa.
Different user profiles
To avoid this conflict, its recommended that you set up different user profiles:
one for RAPID and one for the stand-alone application. Set the environment
variables in the RAPID profile to point to the location of the RAPID software as
shown in Product path settings on page 37.
The environment variables in the stand-alone application user profile should
point to the location of the stand-alone application, as specified in Setting
environment variables on page 36.
42
Chapter 4:
Using Remote Views
This section contains specific information about Remote Views such as installing,
setting multiple instances of the server, and using the Remote Views client.
Remote Views is an additional module that is included with the UNIX job-file
versions of select products. SAP BusinessObjects offers the following Remote
Views applications:
ACE Views
DataRight IQ Views
Presort Views
Label Studio
The Remote Views module allows a Windows client to configure and run jobs on
a UNIX server. Remote Views supports batch processing only.
Chapter 4: Using Remote Views
43
Introduction to Remote Views

Remote Views is a client/server application. You set up jobs through the Views
interface on a Windows client, but you take advantage of powerful batch
processing on a UNIX server.
Using the Remote Views interface, you can create the job filea text file that
contains the instructions used by batch versions of applications. With Remote
Views, you dont need to use UNIX editors and command-line telnet sessions
(except for creating DEF and FMT files).
Remote Views client
Your users need to learn only the client side of Remote Views. After they create
and verify a job file in their Views interface, they issue the Run Job command,
still from within Views. The UNIX server processes their instructions and issues
progress messages to the Windows client.
Remote Views server
Only you, as the system administrator, need to be concerned with the technical
details about how the server side of Remote Views works. Here are some of those
details:
Remote Views installs one Remote Views Server (vserve), which spawns a
process for each product.
Product
Process
ACE Views
vserveace
DataRight IQ Views
vservediq
Label Studio
vservels
vservempg
Presort Views
vservepst
These child processes split the processing workload among Views

applications.
44
The system administrator activates the server side (vserve) with root
permissions. Root is needed so that vserve can use key UNIX system
services, such as user and password authentication (for network security
reasons, information known only to root). After the login authentication
process is complete, vserve changes user from root to the user who requests a
task.
Remote Views can support 64-bit applications. However, if you use 32- and
64-bit applications together, you must install the 32-bit applications first. For
more information, see Combining 32-bit and 64-bit applications on UNIX
on page 34.
System requirements for Remote Views

To use Remote Views, you need a UNIX server and a Windows client that meet
the minimum system requirements detailed below.
UNIX server
Use a UNIX server that has a supported operating system. For the most up-to-date
information about supported versions and patches, see System information on
page 8.
Your UNIX server should meet the following system requirements (in addition to
the system requirements listed in the Windows section of this documentation):
TCP/IP enabled.
Adequate disk space for Remote Views: approximately 12 MB, plus space
for the job file software. See Space requirements on page 12.
Adequate disk space for directories. See Using directories on page 15.
64-bit operating systems receive a 64-bit executable for the UNIX server. If you
need to update your shipments, contact your SAP BusinessObjects account
manager. Windows clients remain 32-bit because those are 32-bit operating
systems. However, if you have a 64-bit UNIX application on a 64-bit UNIX
operating system, a job runs at 64-bit.
When you combine 32- and 64-bit installations to the same system, always
install the 32-bit product versions first.
Windows client
Your client workstation should meet the following minimum system

requirements:
TCP/IP enabled
512 MB RAM
These requirements assume that Views is the only application that you run on the
client workstation. If you run additional applications, see the Windows section in
this guide.
45
Preparing to install Remote Views

If you havent done so already, follow the instructions in the UNIX section to
install all of the UNIX media received:
When you combine applications on the same system, install the 32-bit
applications first, followed by the 64-bit applications.
Install the directories.
In most cases, Remote Views installs with all supported UNIX media for ACE,
DataRight IQ, Presort, Label Studio, and Match/Consolidate.
To install the Windows Views application on each Windows client workstation,
follow the information in Installing on a single PC on page 21.
Updating your Remote
Views application
When you receive an update of your Remote Views application, you need to
reinstall your application and the server and client.
To update your Remote Views application
1. Stop the Views server (vserve). See Stopping the Views server on page 51.
2. Reinstall the server software. See one of the following:
a) Installing on a single PC on page 21.
b) Installing on your network on page 23.
3. Reinstall the client software. See one of the following:
a) Installing on a single PC on page 21.
b) Installing on your network on page 23.
c) Installing client software on page 52.
4. Restart vserve. See one of the following:
a) Starting the Views server manually on page 50.
b) Starting Remote Views automatically on page 51.
When you complete the previous steps, your system should be ready to run
your Remote Views application again.
46
Configuring the Remote Views server

With your Remote Views server application on UNIX, SAP BusinessObjects
supplies a template for the configuration file (named params.cs.new). This
configuration file accomplishes the following:
Editing the
configuration file
(params.cs)
It controls how the Remote Views server opens the TCP/IP communication
ports that clients use to activate the Remote Views server
It sets locations for the Run Job log file and the Match/Consolidate Match
Percent dictionary
It controls whether open job files are saved when the network connection is
lost
To configure the application, you need to edit the parameters in the server
configuration file.
To edit the configuration file
1. Locate params.cs.new in the /disk_n/postware/csgui directory.

2. Make a copy of the file, name it params.cs, and store it in the same
/disk_n/postware/csgui directory.
With each new release, our setup application will place a new
params.cs.new file in the /disk_n/postware/csgui directory. If you edit the
parameters in params.cs.new without first making a copy, it will be
overwritten with each new release.
3. Open params.cs (an example is shown below).
SERVER PORT NUMBER= 2050
ENGINE PORT NUMBER RANGE (STARTING RANGE OF PORTS FOR ENGINES TO CONNECT TO)= 2150
ENGINE PORT NUMBER RANGE (ENDING RANGE OF PORTS FOR ENGINES TO CONNECT TO) = 2160
ACTIVE/COMPLETED JOBS FILE LOCATION (PATH)=/postware/csgui/status
JOBFILE SAVE SETTING ON LOST CONNECTION (1-SAVE;0-NO SAVE)= 1
MATCH/CONSOLIDATE MATCH PERCENT DICTIONARY (PATH + FILENAME) = /postware/merge/matchpct.dct
4. Edit the parameters (you must supply an entry for the first five parameters).
For information about the first five parameters, see the following table.
Caution: If your file contains commented lines, params.cs will not run.
47
Parameter
Discussion
Server Port Number
Type the port number on which the Views server listens.

Note: the Views client will connect to this port; therefore, enter the same port number in
the vws_hsts.dat file on the Windows client.
Engine Port Number

Range
Enter the range of port numbers that will support the Run Job menu option from the
client. The engine sends progress messages and needs a range of available port numbers
for multiple instances of the Run Job command. We recommend that you start by
reserving 10 ports.
If you define an inadequate number of ports, the client may fail to connect. It is rarebut
possiblefor the client to connect under these circumstances but to still receive incorrect
progress messages. Although the screen display would be incorrect in this case, the job
will actually process correctly. To prevent this, calculate the number of multiple instances
of Run Job that is likely to be initiated in a multi-user environment and reserve one port
per instance.
Select different port numbers for the server and engine ports.
Active/Completed
Jobs File Location
Type the name of the directory on your UNIX server in which to store the Run Job status
log. This location must be accessible to all users (for example,
/disk_n/postware/csgui/status). If the content that is output by vserve exceeds
preferred application disk space, you may place the status directory elsewhere, provided
that it has permissions accessible to all Remote Views users.
The first time the client activates the Run Job option, the server creates a single Run Job
status log file per user. It names the file using the format username.jobslog.log. It
appends entries to the file regardless of which Views product you run.
In the status log file, youll find the following data:
status (A, active; C, completed; F, failed; T, terminated)

user name
product
job name
job log-file name
date
Remote Views client users can view their own status logs only within the application.
However, by specifying a central directory, you can view all status logs, if necessary,
with any UNIX text editor. Do not edit the file; if you do, Run Job status messages may
not appear properly in the Remote Views client.
Jobfile Save Setting on This parameter controls the disposition of job files that are open when a network
Lost Connection
connection between client and server is lost. If you want to save any pending changes to
such job files, type 1. To discard any changes and revert to the last saved version of the
job file, type 2.
Match/Consolidate
Match Percent
Dictionary
48
Type the full path and file name for the Match/Consolidate Match Percent dictionary.
This dictionary is used by only Match/Consolidate Views. If you did not install Match/
Consolidate Views, leave this parameter blank.
Configuring the root environment

Setting path and
pw_path in the profile
You can add path and pw_path to your root profile. In this way vserve can be
started without setting up the environment. For syntax examples, see Setting
path and pw_path on page 37.
Creating the
environment file
By following the steps below, you create an environment file in the roots home
directory called .flprofile. You execute it by using the dot command before each
time the vserve process is started.
To create the environment file
1. Log in as root. Type cd $HOME

2. Create a file called .flprofile and type the information appropriate to the
Remote Views products that you use.
DataRight IQ, ACE, and
Presort
PW_PATH=/disk_n/postware/adm:/disk_n/postware/csgui:/disk_n/postware/dtr_iq:/
disk_n/postware/ace:/disk_n/postware/presort
export PW_PATH
PATH=$PATH:$PW_PATH
export $PATH
Match/Consolidate
This example shows the shared library setting for Solaris. For the equivalent
HP-UX and AIX variable names, see Setting the shared library path on
page 40.
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/disk_n/postware/adm:
export LD_LIBRARY PATH
PW_PATH=/disk_n/postware/adm:/disk_n/postware/csgui:/disk_n/postware/merge
export PW_PATH
PATH=$PATH:$PW_PATH
export $PATH
Label Studio (Bourne

shell)
LS_INSTALL_PATH=/disk_n/postware/ls
export LS_INSTALL_PATH
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/disk_n/postware/adm
PW_PATH=/disk_n/postware/adm:/disk_n/postware/csgui:/disk_n/postware/ls
export PW_PATH
PATH=$PATH:$PW_PATH
export $PATH
49
Label Studio (C shell)

setenv LS_INSTALL_PATH=/disk_n/postware/ls
setenv LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/disk_n/postware/adm
setenv PW_PATH=/disk_n/postware/adm:/disk_n/postware/csgui:/disk_n/postware/ls
Activating the Remote Views server from root

Before you can edit or create jobs using the client interface, the server must be
active.
Currently, Remote Views is not a daemon. So, to ensure that the vserve process
does not stop when the root logs out, do one of the following:
use su to change to the root

invoke vserve with the nohup command.
At this step, SAP BusinessObjects recommends that you start the server manually
first (as explained below). When you are sure that the server is ready to accept
connections, add it to your UNIX server startup.
Starting the Views
server manually
To start the Views server manually and receive on-screen messaging
1. Log in as root on the UNIX server.

2. Create a .flprofile script. (For instructions, see Creating the environment
file on page 49.)
3. Type the appropriate path:
If you use C shell, type source ./.flprofile
If you use Bash, Korn, and Bourne shell, type . ./.flprofile
Remember, if you dont want messages to display on the console, you can
start with the nohup command.
4. Change the directory to /disk_n/postware/csgui
5. At the command prompt type one of the following lines:
vserve params.cs &
./vserve params.cs &
When the manual instance of the server starts properly, you may see the
following message echoed in the shell:
Views Server ready to accept connections
Viewing the error

report
50
If the Remote Views server detects an error during processing, it writes an error
report to a server log file. This log file is located in the current working directory
where vserve is initiated (for example, /disk_n/postware/csgui). Remote
Views does not create the log file when the server is initialized; it does so only
when it records a processing error.
The server names the log file as follows:
vserve.log.xxxxxx.mmddyyhhmmss (where xxxxxx is a random string)
Correcting errors
If you encounter difficulties in correcting an error, before you contact Customer

Assurance, see Troubleshooting and tips for Remote Views on page 56 for
diagnosticand contactinformation.
Adding multiple
instances
Most network users will find a single server (vserve) adequate to support Remote
Views, because vserve internally spawns additional processes. If a single instance
proves inadequate to handle a high volume of Views activity, see Creating
additional instances of the server on page 54.
Stopping the Views

server
If you need to stop the Remote Views server, you (as user root) must find the
process ids for any active, running vserve instances (for example, ps -ef|grep
vserve) and issue the UNIX kill command to stop the process(es) (for example,
kill -9 pid).
Before you can restart automatically, you need to stop the vserve that you
started manually. If you dont do this, you receive the message:
vserve: gis_init failed... program terminated.
Starting Remote
Views automatically
You can set up the Remote Views server to start automatically whenever the
server is re-booted and to continue to operate when the root logs out. To do so,
include these instructions in your UNIX servers preferred systems start
instructions. (See Creating the environment file on page 49.)
Here is an example:
. ./.flprofile
cd /disk_n/postware/csgui
./vserve params.cs &
For the path name (/disk_n/postware/csgui) and the command line start
instruction (vserve params.cs & for C shell; nohup vserve params.cs & for
Bourne shell), do the following:
Place each command on a separate line in the start script.

Make sure that the path and pw_path variable has been set for root.
If vserve fails to start, type ENV to review the environment set by .flprofile
and compare against the information in Creating the environment file on
page 49. See also Troubleshooting and tips for Remote Views on page 56.
Job file environment

variables
When you install Remote Views, you also copy job file versions of ACE, Match/
Consolidate, and/or DataRight IQ to the UNIX server. You must properly
configure that job file software for Remote Views to be able to issue the Run Job
command from the client.
51
Configuring the Remote Views client

Remote Views allows a user to set up a job on a Windows client and then run the
job on a UNIX system. After you set up the Remote Views server, its time to set
up the client(s).
To set up your Remote Views client
1. Install the client software. (See Installing on a single PC on page 21.)

2. Configure the client as shown in this section.
Note: In the Windows environment, the directory structure is referred to
as c:\pw rather than the /disk_n/postware conventions used on UNIX.
Installing client
software
After you install the server software and the server is ready to communicate,
install the client software to each Windows workstation. Before you install the
client software, at each client machine, enable TCP/IP communication protocol
within the operating system.
To obtain the client software
1. Download the software installation package from SAPs Service Marketplace

(SMP). Go to http://service.sap.com/ and access the SAP BusinessObjects
downloads area.
2. When its downloaded, uncompress the ZIP file in a temporary location.
To begin installing
1. Initiate the installer by running setup.exe from the uncompressed ZIP file.
2. Follow all on-screen installation instructions.
Note: We do not currently support the client setup utility from within Views,
nor do we support shared use of the Views software for Remote Views users.
As a result, you must install the client software on each workstation from
which you might use it.
Editing the
configuration file
The vws_hsts.dat file is the source of connection data from the Remote Views
client (you cannot add server names from within the Views application). Each
line in vws_hsts.dat represents a UNIX server port where the Remote Views
server is waiting for data from the client.
With your client software, we supply a template for the configuration file
(vws_hsts.dat.new). To configure the software, you must edit the file.
Configuring the client
To edit the file
1. Locate vws_hsts.dat.new in the c:\pw\csgui directory.

2. Make a copy of the file, name it vws_hsts.dat, and store it in the same c:\pw\
csgui directory.
In future software releases, our setup program will place a new
vws_hsts.dat.new file in the /disk_n/postware/csgui directory. If you edit
the parameters in vws_hsts.dat.new without first making a copy, it will be
overwritten with each new release.
52
3. Open vws_hsts.dat and edit the file (for more information see Editing the
vws_hsts.dat file on page 53).
When you start a Remote Views application, a drop-down list appears in the List
of Servers window, from which you must select the appropriate server port. The
drop-down list reflects each line of connection data that you configure in this file.
Editing the
vws_hsts.dat file
When you edit the vws_hsts.dat file, use the following guidelines:
Use each line of the file to identify a server hostname. Define only one server
hostname per line. (Note: If you have only one server to connect to, you need
only one line.)
For each hostname define three parameters (see the table below).
Parameter
Direction
Hostname
description
Type a user-friendly description for the hostname. This need not

be the network host alias. (This description is not actually used
by the Remote Views client.)
Hostname
Type the hostnameor the IP addressof the Remote Views

server as it is known to the network.
Port number
Type the port number on which the Remote Views server is listening. On the server, this is defined as the server port number in
params.cs. For details about the Remote Views servers
params.cs file, see Configuring the Remote Views client on
page 52.
Type a comma to separate each value.
Add spaces for legibility, if you want. But keep in mind that spaces are
truncated in processing.
Commenting lines
When you place an asterisk (*) as the first character in a line, the Remote Views
client will not process that line. Therefore, you may add comments to your file by
adding an asterisk as the first character of the line. Remote Views ignores blank
lines.
Example
Heres an example of a completed vws_hsts.dat file that allows connection to

four UNIX servers or four instances of remote views server:
server1,s4259,2050
server2,172.41.110.131,2051
aix1,s123a,2025
Solaris2,s1234,2060
As the Remote Views client reads each line in vws_hsts.dat, it skips over the
hostname description, and passes hostname and port number values to its
Windows client to connect to the Remote Views server.
After you complete a vws_hsts.dat file, copy it to c:\pw\csgui for any
additional Remote Views client that will share the same server.
53
Creating additional instances of the server

Editing from the client is not a resource-intensive task. Therefore, one instance of
the Remote Views server is generally sufficient to support your users. (SAP
BusinessObjects has no specific recommendation about the maximum number of
clients per instance of the Remote Views server.)
However, if the Remote Views server experiences a high volume of simultaneous
Run Job commands issued from Windows clients, you may need to create
multiple instances of the Remote Views server to accommodate the traffic. Each
additional instance opens another TCP/IP port for traffic between the server and
workstations. This port primarily supports packets that contain progress
messages.
Note: You may set up additional instances only if your license agreement
accommodates multiple users (to be sure, check your purchase agreement).
To create an additional instance of the Remote Views server
1. In the /disk_n/postware/csgui subdirectory, make a copy of params.cs

(you might name it params2.cs).
2. Edit params2.cs to specify new TCP/IP ports for Server Port and Engine
Port, and to identify the range for Engine Start and Engine End ports.
3. Add a new line to your UNIX servers system start instructions to start the
second instance.
Shell
Type this
C shell
vserve params2.cs &
Bourne shell
nohup vserve params2.cs &
Note: On some systems, ./ must precede the command (for example,

./vserve or nohup ./vserve).
54
Using a Remote Views client

For instructions on operating a Remote Views application, see our Views Quick
Start Guide and the applications online help. For instructions on operating Label
Studio, see the Label Studio Users Guide or online help.
Login by individual
When users work at a Windows client workstation, they should use their own
login. If they use a shared login, it may result in a jobs log file that is too large
per user for the UNIX server to manage.
In addition, SAP BusinessObjects recommend that users edit their own jobs. If
they share jobs, you must review directory and permission rights on the UNIX
server.
Editing jobs
Remote Views client users edit jobs in remote mode much like Windows users
edit their jobs, with the following exceptions:
If the Windows system is set up for Remote Views, select the Remote mode
from the Select Views Connection window. If Local Mode is not licensed, the
Remote Views client assumes remote processing. It will skip the mode
selection screen, and proceed directly to the List of Servers window.
In Remote mode, Remote Views prompts the user for their UNIX username
and password to log in to the server.
The browse command finds and selects UNIX path-style names on the UNIX
server.
Jobs are saved on the UNIX server.
The Run Jobs command will activate the UNIX servers job file software.
The Job Status menu option enables you to view and manage the contents of
the Run Job status file. The users view is restricted to their own status log.
Each user may opt to delete a log entry, delete a log entry with the
corresponding job files log file, or terminate a job that is in progress.
The File Transfer menu option is a handy, simplified tool, useful for
transferring small files between the server and client (for example, if a client
session creates a job locally). However, it can transfer ASCII files only. If a
user needs to transfer other file types or large files, we recommend that you
help them by using the file transfer protocol (FTP) utilities enabled on your
UNIX servers operating system.
If the server and client do not communicate, before you call Customer Assurance
for assistance, see Troubleshooting and tips for Remote Views on page 56.
55
Troubleshooting and tips for Remote Views

If you need to contact Customer Assurance, be ready to provide the contents of
the following files:
the most recent vserve.log.* file (if it exists) from the UNIX server
params.cs from the UNIX server
the client configuration file vws_hsts.dat (if you have completed the client
installation steps)
Windows
When this guide uses the term Windows in the section, it refers to the
workstation edition of the operating system because, generally, a Windows client
would be a workstation rather than a server.
Server and client

connections failure
Problem: You dont receive a Ready to accept connections response from the
Remote Views server (vserve).
Symptom
Remedy
Vserve not found Be sure that /disk_n/postware/csgui is set in pw_path and check
whether your system requires the syntax ./vserve params.cs &.
Pwsysmsg.4b not Be sure that /disk_n/postware/adm is set in pw_path. Also,
found
check if the system requires the syntax ./vserve params.cs &.
gis_init failed...
program terminated
Connection failure
56
This occurs if you attempt to restart vserve while the Remote Views
server is still running. Either stop the vserve (see Stopping the
Views server on page 51) or configure an additional vserve (see
Creating additional instances of the server on page 54).
Problem: A Remote Views client fails to establish a connection and work with
the Remote Views server.
Symptom
Remedy
pvmsg.txt not
found
Check the client and server configuration files (params.cs and

vws_hsts.dat) to ensure that you have assigned the TCP/IP port
numbers correctly. This message can occur when two servers
attempt to address the same port numbers simultaneously.
Unable to locate
vws_hsts.dat
Check that you have properly set up the vws_hsts.dat file and
placed it in the proper location. Also, check that you have included
c:\pw\csgui in pw_path on the client.
Hostname not
found
One of the following options may solve your problem:

You need to enter your hostname as hostname.domain (for
example, hostname.businessobjects.com)
You need to register your hostname with the IP alias in the PCs
hosts file or the UNIX hosts file. Some systems require hosts to
be registered for UNIX to non-UNIX communication.
Ping the UNIX server from the Windows client to ensure that
the TCP/IP network communication is working.
Symptom
Remedy
Invalid password
If, on remote login, the user name works, but the password fails,
vserve might not be able to find the shadowed or hidden password
files on the UNIX server. Ensure that vserve started as user root.
Provide vserve with read privileges to the password file.
Unable to open job

file
In Remote Views, job files edited from the PC client carry UNIX
directory and file permissions. One user cannot open another
users jobs unless the UNIX system administrator provides shared
permissions. Start the server from root; it will change to the proper
user permissions as it receives requests to edit files.
Verifying hostnames
To find the local hostname of your UNIX system, at a UNIX command prompt
type hostname and then press the Enter key.
Verifying domain
names
The Domain Name System (DNS) provides a standard naming convention for
machines on IP-based systems. As networks grow, your company may develop a
variety of domain names, usually in a hierarchical arrangement.
Remote Views needs to use your higher-level domain name (for example,
yourcompany.com). Increasingly, Windows-based systems refer to this higherlevel domain name as your DNS suffix.
Verify the higher-level domain name of the UNIX server, and then test the
hostname.domain server name from the Windows client with the ping command.
Type ping hostname and then press the Enter key.
In most cases, a successful ping responds with the format hostname.domain, as in
the following example:
PING hostname.yourcompany.com: (111.11.1.1): 56 data bytes
64 bytes from 111.11.1.1:icmp_seq=0 ttl=255 time=5ms
64 bytes from 111.11.1.1:icmp_seq=1 ttl=255 time=0 ms
Tip: You may need to press Ctrl C to stop the ping test. If hostnames fail, you
might be able to achieve suitable results by substituting the IP Address. If you
substitute the IP address, exercise care, because some networks use dynamic
addressing, which changes the IP Address of a system to meet system
requirements.
Verifying between
systems
You can verify data on either the system on which you are working (by using the
local hostname or IP address) or a remote system (by using the hostname or IP
address of the remote system). You can verify this data by using Ping, a network
communication utility.
Ping is especially useful for testing communication between systems when you
believe you have identified the correct hostname and domain name.
In general, you can verify the communication activity of either your own
hostname or the remote host to which you are trying to connect from Remote
Views. You can use Ping to verify the address and existence of the remote host
when you receive an error message from within Remote Views.
57
Using Ping
Try to ping the remote UNIX server from the Windows client to verify that the
hostname.domain construction in vsw_hsts.dat is a live connection. Type:
ping hostname and then press Enter
or
ping IP address and then press Enter
For detailed instructions on using the Ping command, see your operating system
documentation.
If Ping works
If Ping is enabled and the command is successful, you see a result similar to the
following:
Pinging hostname.yourcompany.com [111.11.111.111] with 32 bytes of
data:
Reply from 111.11.111.111: bytes=32 time<10ms TTL=128
Ping statistics for 111.11.111.111:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
If Ping fails
When the Ping utility cannot locate the remote host, it responds with an error
message (for example, Bad IP address hostname).
If the ping fails, reverify the hostname.domain string as you have identified it in
vws_hsts.dat. If the ping command fails to connect again with the verified
hostname.domain name, confirm that the remote host is active and that your TCP/
IP is properly configured on both the remote host and local client.
Performing DPV
processing on the AIX
platform
The Object Data Manager (ODM) processes DPV records. If you are running
AIX, you need make sure the ODMDIR variable is set before processing. Type
the following command to display the path to the ODM directory (for example, /
usr/lib/objrepos):
echo $ODMDIR
If the path does not exist, you need to set the path.
58
Appendix A:
License Manager
What is License
Manager
License Manager is a SAP BusinessObjects application that lets you manage your
product activation keycodesthe numeric codes that are referred to each time
that you run certain products.
By using the License Manager application, you can view, add, and remove
product activation keycodes for products (such as ACE and Presort) that require
them.
Local system only. License Manager accesses keycodes on the local system
only; you cannot access the keycodes from a remote system.
Whats different
Before the release of ACE version 7.81c and Presort version 7.82c, some
products were keyed using the old Firstlogic system. Now these products are
protected (or keyed) in a way that lets you unlock their functionality more
efficiently.
In the old system, when you purchased another product or feature later, you were
sent an additional product CD that contained your new product or feature. With
this new system, when you purchase a new product or feature, you can
immediately activate that new functionality with the new product activation
keycode that SAP BusinessObjects provides.
59
Installing License Manager

License Manager is automatically installed when you install a product that
requires it.
On Windows
On Windows, find License Manager at c:\Program Files\Common Files\

Business Objects\License Manager.
On UNIX
On UNIX, find License Manager at <install directory>/postware/adm

(This is the default location. You can change it, but its strongly recommended
that you use this location. If you install to a different location, be sure to set your
BOE_REGISTRYHOME value accordingly.)
Setting up License Manager

Before you can run License Manager on its own (that is, not during the
installation process), you may need to do some setup.
On Windows
If you use Windows, you dont need to perform any manual setup of License
Manager. Environment variables are set when License Manager is installed.
On UNIX
If you use UNIX (ACE and Presort users only), you need to set the environment
variable (BOE_REGISTRYHOME) for License Manager.
Although you can use a different setting, its strongly recommended that you use
/var/opt for BOE_REGISTRYHOME.
If you use Bourne shell, add product entries to your .profile or .login file. For
example:
BOE_REGISTRYHOME=/var/opt ; export BOE_REGISTRYHOME
If you use C shell (Berkeley), add product entries to your .cshrc file. For
example:
setenv BOE_REGISTRYHOME /var/opt
60
Starting License Manager

On Windows
You can run License Manager either as part of the installation process (the
installation program prompts you to start License Manager) or later. If you choose
to run License Manager later, you can either locate where its installed or access it
through the Start menu.
To start License Manager (Windows)
On UNIX
ACE or Presort: On the Start menu, go to Programs > Business Objects

Applications > License Manager.
Business Edition: On the Start menu, go to Programs > Postalsoft > License
Manager.
To run License Manager on UNIX, you need to locate where its installed and
then execute its shell script.
To start License Manager (UNIX)
Go to <install directory>\postware\adm and execute LicenseManager
Running License Manager

You can run License Manager to view, add, or remove your product activation
keycodes.
To view product activation keycodes
Start License Manager. When you click the shortcut on the Start menu (Windows)
or execute the shell script (UNIX), the License Manager window displays your
key code(s) sorted alphabetically.
To add a product activation keycode
1. In the Add Key Codes text box, type the keycode(s) that you want to add
(each keycode must be on a separate line) and click Add.
2. When you have added your key code(s), click Done.
3. To make sure the new keycode(s) take effect, restart your application.
To remove a product activation keycode
1. In the Registered Keycodes text box, select the keycode(s) that you want to
remove and click Remove.
2. When you have removed your keycode(s), click Done.
3. Restart your application.
61
62
Index
Numerics
32-bit operating system, and 2GB file size, 42
A
activating Remote Views server, 50
Active/completed jobs file location, parameter, 48
Adaptors, 15
AIX, 41
creating in Remote Views, 49

environment variables, 42
Remote Views, 51
UNIX, 36
Windows, 27
F
files
batch for RAPID and Adaptors, 25
DLL, 20
B
Bourne shell, setting boe_registryhome, 60
Bourne shell, setting path and pw_path, 37
C
C shell, setting boe_registryhome, 60
C shell, setting path and pw_path, 38
client
configuration file, 52
guidelines for using, 55
Remote Views, 52
system requirements, 45
compilers, 8
configuration file
Remote views, 52
configuring
Remote Views client, 52
root, 49
server, 47
connection
server and client, 56
verifying, 57
H
hostname, 53, 57
I
installation
directories, 15
on Solaris, 41
planning
Remote Views, 46
UNIX, 35
Windows network, 22
Remote Views client, 52
Windows
applications on network, 23
applications on single PC, 21
instances, multiple server, 54
invalid password, 56
J
Job file save setting on lost connection, parameter, 48
directories
Adaptors, 15
expiration, 15
installation, 15
Windows, 24
introduction, 15
product names, 28
disk space
performance, 14
Remote Views, 45
requirements, 12
domain, verifying, 57
drive conflict, minimizing, 14
License Manager, 59
installing, 60
setting up, 60
starting, 61
Links
stand-alone application on UNIX, 42
stand-alone application on Windows, 25
login, Remote Views, 55
E
editing jobs, Remote Views, 55
engine port number, parameter, 48
environment file
M
Match percent dictionary, parameter, 48
Match/Consolidate
Oracle on UNIX, 40
Oracle on Windows, 26
multiple instances, 54
creating, 54
Remote Views, 51
Index
63
O
operating systems, 8
Oracle, 42
Match/Consolidate on UNIX, 40
Match/Consolidate on Windows, 26
work file requirements, 13
P
path
product names, 37
setting
manually on Windows, 27
Remote Views, 49
UNIX, 37
Windows XP, 29
variables
Windows XP, 29
performance
how disk space affects, 14
optimizing, 14
ways to boost, 35
Windows, 22
permissions, 28
setting on UNIX, 36
setting on Windows, 27
ping, 57
platforms, 8, 10
processing
improving speed, 14
product path names, 37
projected system requirements, 10
psinstall
creates subdirectories, 35
pw_path
setting
Remote Views, 49
UNIX, 37
Windows XP, 29
variables
Windows XP, 29
R
RAM, 45
RAPID
stand-alone application on UNIX, 42
stand-alone application on Windows, 25
user profile on UNIX, 42
Remote Views
activating, 43
activating server, 50
client, 44
client/server connection, 56
configuring
client, 52
root, 49
server application, 47
connection, 56, 57
creating
environment file, 49
editing jobs, 55
64
environment variables, 51
error report, 50
hostname, 53
individual login, 55
introduction, 44
list of products, 43
manually starting server, 50
server, 44
setting path and pw_path, 49
starting automatically, 51
stopping server, 51
troubleshooting, 56
using client, 55
removing the product, 31
requirements
disk space, 12
Oracle work file space, 13
output file space, 12
Remote Views system, 45
report file space, 12
space, 12
system, 7, 8
UNIX, 33
operating system, 33
processor requirements, 33
Windows
operating system, 20
printer drivers, 21
processor requirements, 20
RAM, 20
SCSI hard drive, 21
work space, 12
S
server
manually starting, 50
multiple instances of, 54
stopping, 51
server port number, parameter, 48
shared libraries, 39
accessing, 39
path settings, 39
Solaris, 42
installation, 41
space requirements, 12
subdirectories, created by psinstall, 35
system requirements, 7, 8
Remote Views, 45
Windows, 20
T
troubleshooting
Remote Views, 56
UNIX, 41
Windows, 31
U
UNIX
installing
applications, 35
Solaris, 41
operating system requirements, 33
Oracle, 40
planning for installation, 35
setting environment variables, 36
setting permissions, 36
troubleshooting, 41
using 32- and 64-bit applications, 34
using applications, 33
V
vserve, 51
not found, message, 56
vws_hsts.dat
cant locate, 56
configuration files, 52
W
Windows, 19
batch files, 25
DLLs, 20
installing
directories, 24
network, 23
single PC, 21
manually setting paths, 27
network troubleshooting, 31
operating system requirements, 20

operating systems support, 20
Oracle with Match/Consolidate, 26
partition size limit, 31
performance, 22
planning for network installation, 22
requirements
printer driver, 21
processor, 20
RAM, 20
SCSI hard drive, 21
setting environment variables, 27
setting workstations, 24
supported versions, 20
troubleshooting, 31
uninstallation, 31
using applications on, 19
Windows XP
variables, 29
verifying environment variables, 30
work files
Match/Consolidate accessing Oracle, 42
work space requirements, 12
Z
zip4us.dir, 35
Index
65

Sag Entry

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Sag Entry

Uploaded by

Copyright:

Available Formats

System Administrators Guide

for SAP BusinessObjects applications

System Administrators Guide, Edition 4.8

System Administrators Guide

System Administrators Guide

About this guide

Who this guide is for

Applications that this

ACE Views and ACE Library

This guide adheres to the following documentation conventions.

Alerts you to important information and potential problems.

System Administrators Guide

Chapter 1: Planning for installation

SAP BusinessObjects Postalsoft solutions are supported on the operating systems

Windows Server 2003 SP2

Windows XP Pro SP2 (64-bit only)

MS VS .NET 2005 SP1 (MS VC 8.0SP1)

Linux Red Hat 4.0 32-bit

Red Hat 4 32-bit

Linux Red Hat 4.0 64-bit

Red Hat 4 64-bit

Linux SuSE 9.0 32-bit

SuSE 9.0 32-bit

Linux SuSE 9.0 64-bit

SuSE 9.0 64-bit

Linux SuSE 10.0 32-bit

SuSE 10.0 32-bit

Linux SuSE 10.0 64-bit

SuSE 10.0 64-bit

AIX V5.3 32-bit

AIX V5.3 32-bit

IBM XL C/C++ Enterprise Edition V10.1 for AIX

AIX V5.3 64-bit

AIX V5.3 64-bit

IBM XL C/C++ Enterprise Edition V10.1 for AIX

System Administrators Guide

HP-UX 11.11 PA-RISC 32bit

HP 11.11 PA-RISC 32-bit

HP-UX 11.11 PA-RISC 64bit

HP 11.11 PA-RISC 64-bit

HP-UX 11.23 Itanium 64bit

HP-UX 11.23 Itanium 64-bit

aCC: HP aC++ANSI C B3910B A.06.16

Viewing online help on

Missing libraries when

Install the following RPM

If you receive an error, login to http://service.sap.com/notes to search the SAP

Chapter 1: Planning for installation

Disclaimer: This information is subject to change without prior notice.

The progression of new operating systems from vendors ensures enhanced

We at SAP BusinessObjects keep abreast of changes in all of the operating

Vendor support and

Vendor support has ended. (Production Support 1 ended on 31

Vendor support has ended. (General support ended on 31

Vendor support has ended. (Premier support ended in October

System Administrators Guide

Vendor support has ended. However, SAP BusinessObjects

General customer notice to migrate to 64-bit on Linux and UNIX.

Below is listed the platform support that is anticipated by mid-year of 2012.

Windows XP Pro SP2 (64-bit only)

Red Hat Linux

Red Hat Linux 5

AIX 6.1 64-bit