5

Written by:
Crystal L Rhoades

[SAP BI 4.1 INSTALLATION GUIDELINES AND DEPLOYMENT

CHECKLIST]
The Purpose of this document is to provide installation guidelines and deployment checklist
specific to SAP BI 4.1 SP06

Version 1.0SAPBI 4.1 SP06 Installation Guidelines and Deployment Checklist

The Purpose of this document is to provide system administrators with quick guidelines
and deployment checklist for the installation of SAP Business Objects Enterprise Server.
Note: If planned to use a dedicated database, web application, or web server, it must be
installed and functioning before attempting to install SAP Business Objects Enterprise.

A)

Introduction:

1) SAP Business Objects Enterprise can be installed on Windows, UNIX, or Linux

platforms, with a combination of supported web servers, web application servers,
database servers, and web technologies.
2) A larger scale deployment might install individual server components on dedicated
systems to host individual server functions over a network. For example: a
dedicated host for a web application server; a dedicated host for the SAP Business
Objects Enterprise core system; and a dedicated host for the database.
3) An Administrator account must be used to install SAP Business Objects Enterprise
on Windows operating systems. However, installing SAP Business Objects
Enterprise on UNIX operating systems does not require root access.
Deployment on Windows:
1) Ensure the hosts do not use any of the following characters in their name: an
underscore, a period, or a slash. You must have Administrator rights to install SAP
Business Objects Enterprise on a Windows platform.
2) SAP Business Objects Enterprise supports both 32- and 64-bit Windows operating
systems.
3) To open ports and run daemon processes or services, SAP Business Objects
Enterprise must have the appropriate operating system account privileges.
Note: SAP Business Objects Enterprise can also be installed in the following
supported virtualized environments like VMware, AIX LPAR etc.
Clients installed by SAP Business Objects Enterprise Client Tools installation
program:
1)
2)
3)
4)
5)
6)
7)
8)

Interactive Analysis (formerly Web Intelligence)

Business View Manager
Report Conversion Tool
Universe design tool
Web Service query tool (formerly Query as a Web Service)
Information design tool (formerly Information Designer)
Translation Management Tool (formerly Translation Manager)
Widgets for SAP Business Objects Enterprise (formerly BI Widgets)

SAPBI 4.1 SP06 Installation Guidelines and Deployment Checklist

Page 2

Version 1.0SAPBI 4.1 SP06 Installation Guidelines and Deployment Checklist

Clients available separately:

1)
2)
3)
4)

SAP Crystal Reports

SAP Business Objects Dashboard Design (formerly Xcelsius)
SAP Business Objects Enterprise Advanced Analysis (formerly Voyager)
BI Workspaces (formerly Dashboard Builder)

IT departments can use data and system management tools that include:
1)
2)
3)
4)
5)
6)
7)
8)

Report Viewers
Central Management Console (CMC)
Central Configuration Manager (CCM)
Repository Diagnostic Tool (RDT)
Data Federation Administration Tool
Upgrade management tool (formerly Import Wizard)
Universe design tool (formerly Universe Designer)
SAP Business Objects Mobile

Note: While it is possible to use a mixture of Windows and UNIX or Linux platforms, it
is recommended that you do not mix operating systems for Central Management
Server (CMS) processes.

B)

Pre-Installation:

1) Review the systems to ensure they meet the basic requirements.

2) When setting up a deployment comprised of two or more hosts, ensure that the
hosts can communicate with each other across the network.
3) Decide whether to use the included Microsoft SQL Server database server.
Note:
An existing database must have database user accounts with the
appropriate database privileges ready, and the appropriate drivers must be
installed and verified as working. The setup program attempts to connect to, and
initialize, the database as a part of the installation process. The installation
program will only install a database on the local host. It cannot install across a
network.
Microsoft SQL Server 2008 is the default database server.
4) Decide whether to use the included Tomcat web application server.
5) Decide which installation option to use. The installation program has three
installation options:
a) "Full": Installs all available components, including a bundled web application
server and database server.
b) "Custom / Expand": Select and Install all or any of the available components.
c) "Web Tier": Installs web applications on a dedicated web application server.
You can use a previously installed web application server, or the bundled
Tomcat web application server.
6) Determine the location of the components to be installed. This includes the specific
subnet, machines, database, security, or cluster systems to be used.
SAPBI 4.1 SP06 Installation Guidelines and Deployment Checklist

Page 3

Version 1.0SAPBI 4.1 SP06 Installation Guidelines and Deployment Checklist

Process Flow:
1) Ensure that sufficient disk space is available. Allow for both the operating system
and the software to grow over time as patches or new components become
available.
2) Gather the installation media or download the latest release and any patches or
service packs
3) If you plan to use SAP System Landscape Directory (SLD), ensure that the SAP Host
Agent is installed before installing SAP Business Objects Enterprise.
4) Decide which options you will change select the installation process. In most cases,
you can accept the default values. More advanced installations require that you
plan the installation process. The installation program prompts for the following
information:
License information (the name of the user and company associated with your
SAP Business Objects Enterprise license).
Web application server configuration, including type, connection, and
authentication details.
Database server configuration, including type, connection, and authentication
details.
CMS system and Auditing Data Store configuration information, including type,
connection, and authentication details.
Folder where SAP Business Objects Enterprise will be installed.
Central Management Console (CMC) administrator account password and cluster
key.
CMS port number to receive incoming connections.
Server Intelligence Agent (SIA) name.
Server Intelligence Agent (SIA) port number for incoming connections.
SAP Solution Manager Diagnostics (SMD) configuration.
CA Wily Introscope Enterprise Manager configuration.
Subversion or ClearCase version control system configuration to store
configuration files.
Lifecycle management (LCM) configuration.
Installation type and components ("Full", "Custom / Expand", "Web Tier").

System Requirements:
1) Ensure that the operating system is supported. Only 64-bit operating systems are
supported. Windows .NET Framework 3.5 Service Pack 1 and Windows installation
program 4.5 are required.
2) Before you run the installation program, ensure that the destination partition has
enough room for the deployment to expand (when updates and new features are
added in the future).
SAPBI 4.1 SP06 Installation Guidelines and Deployment Checklist

Page 4

Version 1.0SAPBI 4.1 SP06 Installation Guidelines and Deployment Checklist

3) If you install the deployment on the operating system partition, ensure that there
is enough room for the deployment and the operating system.
Note: It is recommended that you have at least 2 gigabytes available for
temporary files and web applications.

Account Permissions:
1) Operating system:
Local administrative privileges.
2) Network :
Network connectivity through appropriate ports to all machines in the
deployment.
Access to shared file system directories for users of the deployment.
Appropriate network authentication privileges.
3) Database:
Permission for the SAP Business Objects user account to create, edit, and
drop tables.
Permission for the SAP Business Objects user account to create stored
procedures (required by the Central Management Server (CMS) system
database).

Network Permissions:
1) Servers running on all hosts must be able to communicate with each other.
2) Each machine must be able to communicate with the web application server, the
Central Management Server (CMS) host, all SIA hosts, and clients.
3) On any host with more than one network interface card (NIC), ensure that the
primary NIC is routable before running the installation program. If the primary NIC
is not routable, you will have to re-configure the networking settings after the
installation.
4) Each machine must use a fixed hostname. Fully-qualified hostnames are
supported.
5) Server Location: When planning a distributed installation, consider the latency
between servers. To maintain high CMS performance, place your CMS on the same
subnet as the CMS system and Auditing Data Store database servers.

Pre-Install Checklist:
1) Decide on the installation destination folder.
Note: The use of Unicode characters in the destination folder is not supported.
Ensure that the installation destination folder is not the same folder in which the
installation program has been extracted (do not install to the current working
SAPBI 4.1 SP06 Installation Guidelines and Deployment Checklist

Page 5

Version 1.0SAPBI 4.1 SP06 Installation Guidelines and Deployment Checklist

2)
3)

4)

5)

6)
7)
8)

directory when running the installation program from the current working
directory).
Verify appropriate network connectivity between all machines that will be part of
your deployment.
If you plan to use SAP Enterprise Resource Planning (ERP) integration for OLAP
Data Access(ODA), SAP Business Objects Analysis (formerly Voyager), or SAP
Business Warehouse (BW),ensure that SAP GUI is installed and configured before
SAP Business Objects Enterprise.
If you are using your own database server:
Create a database, table space (if required), and accounts for the CMS system
and Auditing Data Store databases
Make sure you can log onto the database from the SAP Business Objects
Enterprise host
If you are using DB2 or Sybase, verify that your database was created with the
correct settings (Some settings can't be modified after the database has been
created.)
Make sure database client software been properly configured.
If you are using your own web application server:
Decide on which web application server to use
Make sure server already been installed and configured
Ensure that your existing web application server has the required JDK installed.
If you plan to use SAP System Landscape Directory (SLD), ensure that SAP Host
Agent been installed and configured.
If you plan to use SAP Solution Manager Diagnostics (SMD), SMD Agent may been
installed and configured before or after SAP Business Objects Enterprise.
Installation on Microsoft Windows requires a minimum screen solution of 1024
768.
Note: Client Tools can only be installed with the dedicated Client Tools installation
program.

C)

Installation:

There are two different methods of running the installation program for SAP Business
Objects Enterprise:
1) Interactive installation: An interactive wizard prompts for all information related to
the installation. Use this option to select individual installation options from a
series of screens. This is the default installation method.
2) Silent installation: Installation options are given on the command-line, which
override the installation program's default values. The command-line can be used
to give some or all installation options. When an installation option is not given on
the command-line, the installation program uses a default value.

D) Post-Installation:
SAPBI 4.1 SP06 Installation Guidelines and Deployment Checklist

Page 6

Version 1.0SAPBI 4.1 SP06 Installation Guidelines and Deployment Checklist

1)
2)
3)
4)
5)
6)

E)

Launching the CMC

Troubleshooting login issues
Creating additional Adaptive Processing Servers
Deploying web applications
Post-install diagnostic checks
Client tools Installation
Note: SAP Business Objects Enterprise Client Tools can only be installed by a
dedicated installation program.

Deployment Checklist:
This checklist is for identifying the major tasks to be completed for the planning
phase of your SAP Business Objects Enterprise deployment.
Checklist Item

Status
Y/N

Understand the tiers that make up the SAP Business Objects

Enterprise architecture
Understand the components and how they communicate
Architecture overview
with each other
Understand the workflows (how information travels through
Information Workflows the architecture)
Identify the Operating system you are deploying the system on
Choose the database servers will you be accessing
Choose a web application server
Identify potential performance problems
Choose whether or not to design for high availability and failover
support
Choose an architecture that meets all of these needs
Review the installation order for SAP Business Objects Enterprise

F)

Installation Order:

The following table lists the recommended order that SAP Business Objects Enterprise
system components should be installed.
Orde
r
1

Component

Description

Database server

To use your own database server to store SAP Business

Objects
Enterprise data, rather than the database installed by
the installation program, at least one database server
must be available for the CMS to use. A second
database is required to enable auditing. In addition,
SAP Business Objects Enterprise requires a connection

SAPBI 4.1 SP06 Installation Guidelines and Deployment Checklist

Page 7

Version 1.0SAPBI 4.1 SP06 Installation Guidelines and Deployment Checklist

10

to your organization's own database, to act as source

material against which to run reports.
Database
To protect your database behind a firewall, install the
firewall
firewall after the databases are configured and verified
to be working. Ensure that access through the firewall
is working in both directions.
SAP Business
Install the appropriate database drivers on your SAP
Objects
Business Objects Enterprise server systems and ensure
Enterprise
that the database servers can be accessed through the
database drivers firewall.
SAP Business
Install your SAP Business Objects Enterprise server or
Objects
cluster using the SAP Business Objects Enterprise
Enterprise
installation program. You need to enter connection
server or cluster information for all databases during the install.
Server firewall
To protect your SAP Business Objects Enterprise server
or cluster behind a firewall, install the firewall after the
servers are configured and verified to be working.
Ensure that access through the firewall is working in
both directions.
Web application To use your own web application server instead of the
server or cluster version of Tomcat installed by the installation program,
install the web application server or cluster and verify
network connectivity between it and the SAP Business
Objects Enterprise server.
Web application When your web application server is verified to be
files
working, deploy the SAP Business Objects Enterprise
web application files.
Web application To protect your web application server or cluster
server firewall
behind a firewall, install the firewall after the servers
are configured and verified to be working. Ensure that
access through the firewall is working in both
directions.
Web
To use split web and web application servers so that
server/Cluster
server static content can be off-loaded from the web
app servers, configure your web server or cluster and
ensure connectivity to the web application server.
When using a load balancer, configure the load
balancer after the web servers or cluster are verified to
be working
Web server
To protect your web server behind a firewall, install the
firewall
firewall after the servers are configured and verified to
be working. Ensure that access through the firewall is

SAPBI 4.1 SP06 Installation Guidelines and Deployment Checklist

Page 8

Version 1.0SAPBI 4.1 SP06 Installation Guidelines and Deployment Checklist

11

Reverse proxy

12

External firewall

working in both directions.

When using a reverse proxy server, configure the
reverse proxy to once access through the web or web
application server firewall has been verified.
To protect your entire deployment behind a firewall,
install the firewall after the entire system is configured
and verified to be working. Ensure that access through
the firewall is working in both directions.

SAPBI 4.1 SP06 Installation Guidelines and Deployment Checklist

Page 9