2011
Written by:
Varun Tottempudi, Comerit
Dr.Bjarne Berg, Comerit
[
]
The Purpose of this document is to provide installation guidelines and deployment checklist specific to SAP BI 4.0
Release.

Version 1.0 SAPBI 4.0 Installation Guidelines and Deployment Checklist
The Purpose of this document is to provide system administrators with quick guidelines and deployment checklist for theinstallation of SAP BusinessObjects 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 BusinessObjects Enterprise.
1) SAP BusinessObjects Enterprise can be installed on Windows, UNIX, or Linux platforms, with acombination 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 BusinessObjects Enterprise core system; and a dedicated host for the database.
3) An Administrator account must be used to install SAP BusinessObjects Enterprise on Windows operating systems. However, installing SAP BusinessObjects 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 BusinessObjects Enterprise on a
Windowsplatform.
2) SAP BusinessObjects Enterprise supports both 32- and 64-bit Windows operating systems.
3) To open ports and run daemon processes or services, SAP BusinessObjects Enterprise must have theappropriate operating system account privileges.
Note: SAP BusinessObjects Enterprise can also be installed in the following supported virtualized environments like VMware, AIX LPAR etc.
Clients installed by SAP BusinessObjects Enterprise Client Tools installation program:
1) Interactive Analysis (formerly Web Intelligence)
2) Business View Manager
3) Report Conversion Tool
4) Universe design tool
5) Web Service query tool (formerly Query as a Web Service)
6) Information design tool (formerly Information Designer)
7) Translation Management Tool (formerly Translation Manager)
8) Widgets for SAP BusinessObjects Enterprise (formerly BI Widgets)
SAPBI 4.0 Installation Guidelines and DeploymentChecklist Page 2

Version 1.0 SAPBI 4.0 Installation Guidelines and Deployment Checklist
Clients available separately:
1) SAP Crystal Reports
2) SAP BusinessObjects Dashboard Design (formerly Xcelsius)
3) SAP BusinessObjects Enterprise Advanced Analysis (formerly Voyager)
4) BI Workspaces (formerly Dashboard Builder)
IT departments can use data and system management tools that include:
1) Report Viewers
2) Central Management Console (CMC)
3) Central Configuration Manager (CCM)
4) Repository Diagnostic Tool (RDT)
5) Data Federation Administration Tool
6) Upgrade management tool (formerly Import Wizard)
7) Universe design tool (formerly Universe Designer)
8) SAP BusinessObjects 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.
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 cancommunicate 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 privilegesready, 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": Install’s all available components, including a bundled web application server and databaseserver. b) "Custom / Expand": Select and Install all or any of the available components. c) "Web Tier": Install’s 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.0 Installation Guidelines and DeploymentChecklist Page 3

Version 1.0 SAPBI 4.0 Installation Guidelines and Deployment Checklist
1) Ensure that sufficient disk space is available. Allow for both the operating system and the softwareto 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 isinstalled before installing SAP BusinessObjects Enterprise.
4) Decide which options you will change select the installation process. In most cases, you can acceptthe default values. More advanced installations require that you plan the installation process.
Theinstallation program prompts for the following information:
• License information (the name of the user and company associated with your SAPBusinessObjects
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, andauthentication details.
• Folder where SAP BusinessObjects 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").
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 forthe deployment to expand (when updates and new features are added in the future).
3) If you install the deployment on the operating system partition, ensure that there is enough room forthe deployment and the operating system.
Note: It is recommended that you have at least 2 gigabytesavailable for temporary files and web applications.
1) Operating system:
 Local administrative privileges.
SAPBI 4.0 Installation Guidelines and DeploymentChecklist Page 4

Version 1.0 SAPBI 4.0 Installation Guidelines and Deployment Checklist
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 BusinessObjects user account to create, edit, anddrop tables.

Permission for the SAP BusinessObjects user account to create stored procedures(required by the Central Management Server (CMS) system database).
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
ManagementServer (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 reconfigure 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.
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 installationprogram has been extracted (do not install to the current working directory when running theinstallation program from the current working directory).
2) Verify appropriate network connectivity between all machines that will be part of your deployment.
3) If you plan to use SAP Enterprise Resource Planning (ERP) integration for OLAP Data Access(ODA), SAP
BusinessObjects Analysis (formerly Voyager), or SAP Business Warehouse (BW),ensure that SAP GUI is installed and configured before SAP BusinessObjects Enterprise.
4) If you are using your own database server:
• Create a database, tablespace (if required), and accounts for the CMS system and Auditing Data Store databases
• Make sure you can log onto the database from the SAP BusinessObjects 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.
5) If you are using your own web application server:
• Decide on which web application server to use
SAPBI 4.0 Installation Guidelines and DeploymentChecklist Page 5

Version 1.0 SAPBI 4.0 Installation Guidelines and Deployment Checklist
• Make sure server already been installed and configured
• Ensure that your existing web application server has the required JDK installed.
6) If you plan to use SAP System Landscape Directory (SLD), ensure that SAP Host Agent been installed and configured.
7) If you plan to use SAP Solution Manager Diagnostics (SMD), SMD Agent may been installed and configured before or after SAP BusinessObjects Enterprise.
8) Installation on Microsoft Windows requires a minimum screen solution of 1024 × 768.
Note: Client Tools canonly be installed with the dedicated Client Tools installation program.
There are two different methods of running the installation program for SAP BusinessObjects 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.
1) Launching the CMC
2) Troubleshooting login issues
3) Creating additional Adaptive Processing Servers
4) Deploying web applications
5) Post-install diagnostic checks
6) Client tools Installation
Note: SAP BusinessObjects Enterprise Client Tools can only be installed by a dedicated installationprogram.
This checklist is for identifying the major tasks to be completed for the planning phase of your
SAPBusinessObjects Enterprise deployment.
Status – Y/N Checklist Item
Understand the tiers that make up the SAP BusinessObjects 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)
SAPBI 4.0 Installation Guidelines and DeploymentChecklist Page 6

Version 1.0 SAPBI 4.0 Installation Guidelines and Deployment Checklist
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 BusinessObjects Enterprise
The following table lists the recommended order that SAP BusinessObjects Enterprise system components should be installed.
Order
1
2
3
4
5
6
7
8
9
Component
Database server
Database firewall
SAP BusinessObjects
Enterprisedatabase drivers
SAP BusinessObjects
Enterpriseserver or cluster
Server firewall
Web application server orcluster
Description
To use your own database server to store SAP BusinessObjects
Enterprise data, rather than the database installedby the installation program, at least one databaseserver must be available for the CMS to use. A seconddatabase is required to enable auditing. In addition,
SAPBusinessObjects Enterprise requires a connection to yourorganization's own database, to act as source materialagainst which to run reports.
To protect your database behind a firewall, install thefirewall after the databases are configured and verifiedto be working. Ensure that access through the firewall isworking in both directions.
Install the appropriate database drivers on your SAPBusinessObjects
Enterprise server systems and ensurethat the database servers can be accessed through thefirewall.
Install your SAP BusinessObjects Enterprise server orcluster using the SAP BusinessObjects Enterprise installationprogram. You need to enter connection informationfor all databases during the install.
To protect your SAP BusinessObjects Enterprise serveror cluster behind a firewall, install the firewall after theservers are configured and verified to be working. Ensurethat access through the firewall is working in both directions.
To use your own web application server instead of theversion of
Tomcat installed by the installation program,install the web application server or cluster and verifynetwork connectivity between it and the SAP BusinessObjectsEnterprise server.
Web application files
Web application server firewall
When your web application server is verified to be working,deploy the SAP BusinessObjects Enterprise webapplication files.
To protect your web application server or cluster behinda firewall, install the firewall after the servers are configuredand verified to be working. Ensure that accessthrough the firewall is working in both directions.
Web server/Cluster To use split web and web application servers so thatserver static
SAPBI 4.0 Installation Guidelines and DeploymentChecklist Page 7

Version 1.0
10
11
12
SAPBI 4.0 Installation Guidelines and Deployment Checklist
Web server firewall To protect your web server behind a firewall, install thefirewall after the servers are configured and verified to beworking. Ensure that access through the firewall is workingin both directions.
Reverse proxy When using a reverse proxy server, configure the reverseproxy to once access through the web or web applicationserver firewall has been verified.
External firewall content can be off-loaded from the web app servers, configure your web server or clusterand ensure connectivity to the web application server.When using a load balancer, configure the load balancerafter the web servers or cluster are verified to be working
To protect your entire deployment behind a firewall, installthe firewall after the entire system is configured and verifiedto be working. Ensure that access through the firewallis working in both directions.
SAPBI 4.0 Installation Guidelines and DeploymentChecklist Page 8