Business Intelligence Platform Installation Guide for Windows

Description
This document is intended for system administrators performing a full installation of the BI platform.

SAP BusinessObjects Business Intelligence platform
Document Version: 4.1 Support Package 6 – 2015-07-20
Business Intelligence Platform
Installation Guide for Windows
Content
1 Document History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.1 About this Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2 Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.3 Constraints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.4 Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.5 Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.6 Additional documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3 Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.1 New features and components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.2 Upgrade support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.3 Database servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.4 Languages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4 Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.1 System requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Account permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Network permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.2 Preparing the CMS system or Auditing Data Store database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Extra requirements for IBM DB2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Extra requirements for Sybase ASE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Extra requirements for SAP HANA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Extra requirements for CMS clustering with SQL Anywhere. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4.3 SAP support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Support for SAP System Landscape Directory (SLD). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Support for SAP Solution Manager Diagnostics (SMD). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Support for CA Wily Introscope. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Support for SAP BW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
4.4 Final checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.2 To download the server installation program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.3 To run an interactive installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
To select an install type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
While the installation program runs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
2 © 2015 SAP SE or an SAP affiliate company. All rights reserved.
Business Intelligence Platform Installation Guide for Windows
Content
When installation is complete. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
5.4 To run a silent installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Command-line switch parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Installation option parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6 Post-Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
6.1 Verifying your installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Checking the installed version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Troubleshooting login issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
6.2 Creating additional Adaptive Processing Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
6.3 Deploying web applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
6.4 SAP support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
To configure System Landscape Directory (SLD) Data Supplier (DS) post installation. . . . . . . . . . . .55
To configure SMD Agent post installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
To configure CA Wily Introscope Agent post installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
6.5 Third-party ERP integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
To enable Siebel Enterprise integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
To enable JD Edwards EnterpriseOne integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
To enable Oracle E-Business Suite (EBS) integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
6.6 Post-install diagnostic checks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
6.7 Making changes to the BI platform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
To modify the BI platform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
To repair the BI platform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
To remove the BI platform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Patching third-party solutions bundled with the BI platform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
6.8 When the administrator account password is lost. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
6.9 Post-installation configuration of fonts in the fontalias.xml file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
7 Installing BI Platform Client Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
7.1 Desktop client applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
Web Intelligence Rich Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Business View Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Report Conversion Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Universe design tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Query as a Web Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Information design tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Translation Management Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Data Federation Administration Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Widgets for the BI Platform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
7.2 To download the Client Tools installation program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
7.3 Client Tools installation prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
7.4 To run an interactive installation of Client Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Business Intelligence Platform Installation Guide for Windows
Content © 2015 SAP SE or an SAP affiliate company. All rights reserved. 3
7.5 To run a silent installation of Client Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Command-line silent install of Client Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Installation option parameters for Client Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
7.6 Making changes to Client Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
To modify Client Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
To repair a Client Tools installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
To remove Client Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
7.7 Upgrading Client Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
4 © 2015 SAP SE or an SAP affiliate company. All rights reserved.
Business Intelligence Platform Installation Guide for Windows
Content
1 Document History
The following table provides an overview of important document changes.
Version Date Description
SAP BusinessObjects Business
Intelligence platform 4.1
May, 2013 First release of this document.
SAP BusinessObjects Business
Intelligence platform 4.1 Support
Package 1
August, 2013
? Added instructions for updating
SAP BW systems in Support for
SAP BW [page 24].
? Added post-installation steps to
allow database access via
DataDirect in Configuring
DataDirect DSN connections. .
? Added Terminology [page 8]
section.
SAP BusinessObjects Business
Intelligence platform 4.1 Support
Package 2
November, 2013
? SAP System Landscape Directory
(SLD) is now a hidden feature and
automatically installed, so all
reference to the associated feature
code has been removed.
? Changed the section Checking the
installed version.
SAP BusinessObjects Business
Intelligence platform 4.1 Support
Package 4
June 2014
? Underscores ("_") are not allowed
in a SIA name.
SAP BusinessObjects Business
Intelligence platform 4.1 Support
Package 5
November, 2014 The following updates are made to the
Installation guide for Unix:
? Updated the list of required
libraries.
? Added a KBA 2065789 and
referenced to section Additional
requirements for Red Hat Linux.
? Updated the list of dependencies
for Redhat Linux 6.x, which needs
to be installed on the OS prior to
installing the product for full crystal
reports functionality.
The following update is made to the
Instllation guide for Unix and
Installation guide for Windows:
? You can manually edit the
fontalias.xml file to increase the
number of fonts available in Web
Intelligence. For more information,
Business Intelligence Platform Installation Guide for Windows
Document History © 2015 SAP SE or an SAP affiliate company. All rights reserved. 5
Version Date Description
see Post-installation configuration
of fonts in the fontalias.xml file
[page 62] .
SAP BusinessObjects Business
Intelligence platform 4.1 Support
Package 6
June, 2015 Updated the Language support topic for
modifying the BI platform installation.
6 © 2015 SAP SE or an SAP affiliate company. All rights reserved.
Business Intelligence Platform Installation Guide for Windows
Document History
2 Introduction
This document guides you through the installation of the BI platform.
2.1 About this Document
The following documentation provides administrators with information, procedures, and options for the
installation, removal, and modification of a BI platform server. Two versions of this guide exist:
? SAP BusinessObjects Business Intelligence Platform Installation Guide for Windows: for use with Microsoft
Windows operating systems (this document).
? SAP BusinessObjects Business Intelligence Platform Installation Guide for Unix: for use with Unix or Linux
operating systems.
This document also provides information and procedures for the installation of the BI platform Client Tools.
2.2 Purpose
This document is intended for system administrators performing a full installation of the BI platform. For
information on applying minor release, Support Package, or Patch updates to your existing installation, see the
Update installation guides athttp://help.sap.com/bobip41.
2.3 Constraints
This guide does not describe how to set up a supported host operating system, database, web application, or web
server. If you are planning to use a dedicated database, web application, or web server, it must be installed and
functioning before attempting to install the BI platform.
2.4 Variables
The following variables are used throughout this guide.
Business Intelligence Platform Installation Guide for Windows
Introduction © 2015 SAP SE or an SAP affiliate company. All rights reserved. 7
Variable Description
The directory where the BI platform is installed.
On Windows, the default directory is C:\Program Files
(x86)\SAP BusinessObjects\.
The hostname or IP of the web application server where BI
platform web applications are deployed.
2.5 Terminology
The following terms are used throughout the BI platform documentation:
Table 1:
Term Definition
add-on products Products that work with the BI platform but have their own in­
stallation program, such as SAP BusinessObjects Explorer
Auditing Data Store (ADS) The database used to store auditing data
BI platform An abbreviation for the SAP BusinessObjects Business
Intelligence platform
bundled database; bundled web application server The database or web application server shipped with the BI
platform
cluster (noun) Two or more Central Management Servers (CMSs) working
together and using a single CMS database
cluster (verb) To create a cluster.
For example, to create a cluster:
1. Install a CMS and CMS database on machine A.
2. Install a CMS on machine B.
3. Point the CMS on machine B to the CMS database on ma­
chine A.
cluster key Used to decrypt the keys in the CMS database.
You can change the cluster key in the CCM, but you cannot re­
set the key like a password. It contains encrypted content and
is important not to lose.
CMS An abbreviation for the Central Management Server
8 © 2015 SAP SE or an SAP affiliate company. All rights reserved.
Business Intelligence Platform Installation Guide for Windows
Introduction
Term Definition
CMS database The database used by the CMS to store information about the
BI platform
deployment The BI platform software installed, configured, and running on
one or more machines
installation An instance of BI platform files created by the installation pro­
gram on a machine
machine The computer on which the BI platform software is installed
major release A full release of the software, such as 4.0
migration The process of transferring BI content from a previous major
release (for example, from XI 3.1), using the upgrade manage­
ment tool.
This term does not apply to deployments with the same major
release. See promotion.
minor release A release of some components of the software, such as 4.1
node A group of BI platform servers that run on the same machine
and are managed by the same Server Intelligence Agent (SIA)
Patch A small update for a specific Support Package version
promotion The process of transferring BI content between deployments
with the same major release (for example, 4.0 to 4.0), using
the promotion management application
server A BI platform process. A server hosts one or more services.
Server Intelligence Agent (SIA) A process that manages a group of servers, including stop­
ping, starting, and restarting servers
Support Package A software update for a minor or major release
web application server A server that processes dynamic content. For example, the
bundled web application server for 4.1 is Tomcat 7.
upgrade The planning, preparation, migration, and post-processes re­
quired to complete a migration process
2.6 Additional documentation
Documents listed in the following table are relevant to deployment and installation. All 4.1 documents are available
for download athttp://help.sap.com/bobip41.
Business Intelligence Platform Installation Guide for Windows
Introduction © 2015 SAP SE or an SAP affiliate company. All rights reserved. 9
Table 2:
Document Description Document Title
Lists the supported platforms, databases, web applica­
tion servers, web servers, and other systems.
Product Availability Matrix (PAM)
Overview of SAP BusinessObjects Business Intelligence
platform documentation.
SAP BusinessObjects Business Intelligence Suite Master Guide
Overview of new features in SAP BusinessObjects
Business Intelligence platform.
SAP BusinessObjects Business Intelligence Platform What's New
Guide
Instructions to upgrade from a previous major release
such as XI 3.1
SAP BusinessObjects Business Intelligence Platform Upgrade Guide
Installation instructions on applying a 4.1 update to your
4.0 deployment.
SAP BusinessObjects Suite 4.1 Update Guide
Installation instructions on applying a Support Package
update to your 4.1 deployment.
SAP BusinessObjects Suite 4.1 Support Package Update Guide
Installation instructions on applying a Patch update to
your 4.1 deployment.
SAP BusinessObjects Suite 4.1 Patch Update Guide
Detailed instructions for deploying BI platform web ap­
plications to supported web application servers.
SAP BusinessObjects Business Intelligence Platform Web Application
Deployment Guide
Administrative documentation for setting up and main­
taining an SAP BusinessObjects Business Intelligence
platform server.
SAP BusinessObjects Business Intelligence Platform Administrator
Guide
10 © 2015 SAP SE or an SAP affiliate company. All rights reserved.
Business Intelligence Platform Installation Guide for Windows
Introduction
3 Planning
The BI platform can be installed on Windows, Unix, or Linux platforms.
Before installing:
? Ensure the operating system, application server, database server, and other components on which you will
install the BI platform are supported. See the SAP BusinessObjects BI 4.0 Product Availability Matrix (PAM)
athttp://service.sap.com/sap/support/pam?hash=pvnr=67837800100900006540 .
? Decide whether to use the included Sybase SQL Anywhere database server for the CMS and auditing
databases.
If you do not have a database server to use with the BI platform, the installation program can install and
configure one for you. It is recommended that you evaluate your requirements against information from your
database server vendor to determine which supported database would best suit your organization's
requirements.
Note
If you do not plan to use the default database that is included in the installation program, ensure the
database that you plan to use is configured before beginning the installation. The database must have user
accounts with the appropriate database privileges ready, and the appropriate drivers must be installed and
verified as working. The installation program will connect to and initialize the database.
The installation program will only install a database on the local machine. It cannot install across a network.
? Decide whether to use the included Tomcat web application server.
If you do not have a web application server system to host BI platform web applications, the installation
program can install and configure one for you. It is recommended that you evaluate your requirements
against information from your web application server vendor to determine which web application server
would best suit your organization's requirements. To use any other supported web application server, it must
be installed, configured, enabled, and accessible before you install the BI platform.
The installation program will only install Tomcat on the local machine. It cannot install across a network.
During installation, users need to provide details regarding the SIA or Node name, the Cluster Key, and the
Cluster name.SIA/Node name is an identifier only, it need not be a DNS resolvable hostname.It does need to
be unique within the cluster, so something like Node1 would be appropriate, or ProdNode1.Cluster Name also
need not be DNS resolvable. This is a user friendly name that identifies an overall environment which may
encompass dozens of BOE servers working together.For example: BOEProduction or BOEDev, BOETest. The
cluster name must be unique to each cluster of servers.This can be used to hide the real hostnames of
machines when users log into the environment for security and simplicity reasons.This also allows you to add
and remove hosts from the environment without making changes to the end user systems or
processes.Cluster Key is a string that is used to prevent accidentally clustering machines together. You can
think of it as a password that servers exchange behind the scene. Each cluster needs its own unique cluster
key. This cluster key is also used for some encryption functionality and can be changed over time as needed
with no impact to users.
Business Intelligence Platform Installation Guide for Windows
Planning © 2015 SAP SE or an SAP affiliate company. All rights reserved. 11
3.1 New features and components
The following features and components are new to the BI platform 4.1 installation program.
Sybase SQL Anywhere bundled database
Sybase SQL Anywhere is now the default, bundled database server for the CMS and Auditing Data Store.
If you are updating a 4.0 installation that uses the bundled Microsoft SQL Server Express database server to 4.1
with the update installation program, your SQL Server database is preserved and will still be used. You may
continue to use this bundled database server with no further action. Or you can choose to migrate your existing
databases to Sybase SQL Anywhere by following the steps described in “Migrating to Sybase SQL Anywhere” in
the SAP BusinessObjects Business Intelligence Suite 4.1 Support Package Update Guide.
Tomcat 7 bundled web application server
Tomcat 7.0 is now the default, bundled web application server.
If you are updating a 4.0 installation that uses the bundled Tomcat 6.0 web application server to 4.1 with the
update installation program, your system is automatically updated to Tomcat 7.0.
Note
Any custom settings you had applied in Tomcat 6.0 are migrated to Tomcat 7.0. It is recommended you verify
these custom settings in Tomcat 7.0 after applying the 4.1 update. Certain Tomcat 6.0 configuration files are
backed up automatically to:
\tomcat6ConfBackup\
Language support
You may now add or remove a language by modifying your BI platform installation.
To add or remove a language, go to Start Control Panel Programs and Features , select your BI platform
server or Client Tools product and click Uninstall/Change. Select the Modify option and add or remove languages
from the Choose Language Packs screen.
When you update your installation from a base version to a new version, all the languages that were available with
the base version are still displayed in the “Select Languages Pack” list. However, the languages that got added
only in the new version are not displayed in the “Select Languages Pack” list. For example: If you have updated
from a base version say, from 4.0 SPX to a newer version 4.1 SPX, in this case:
? Languages that were available with 4.0 SPX are still displayed in the “Select Languages Pack” list.
12 © 2015 SAP SE or an SAP affiliate company. All rights reserved.
Business Intelligence Platform Installation Guide for Windows
Planning
? Languages that got added only in the 4.1 SPX version are not displayed in the “Select Languages Pack” list.
If you want to install one of the those languages that got added in the new version, the only option is to
remove and re-install the new version of the product.
3.2 Upgrade support
Definition of Upgrade and Update
Update means adding support packages or patches to a 4.x release. Upgrade means moving a BusinessObject
Enterprise XI 3.1 release to a BI platform 4.0 or 4.1 release.
Updating from 4.x to a 4.1 Support Package
Use this table to select the correct update guide.
Note
You can install the 4.1 Support Package update directly on a BI platform 4.0 installation. You do not need to
install the 4.1 update first.
Table 3:
Type of update Example Guide
minor release update
? Installing 4.1 on a 4.0 release
BI Platform minor release update guide
Support Package update
? Installing 4.1 SP2 on a 4.1 SP1 re­
lease
? Installing 4.1 SP2 on a 4.0 release
Support Package update guide
Patch update for 4.1 release
? Installing 4.1 SP1 patch 3 on a 4.1
SP1 release
Patch 1.x Update Guide 4.1 SP1
Patch update for 4.0 release
? Installing 4.0 SP7 Patch 2 on a 4.0
SP7 release
Patch 0.x Update Guide 4.1
Upgrading from XI 3.1
To upgrade the SAP BusinessObjects Enterprise XI 3.1 or other 3.x release to the BI platform 4.1 SP5, you must
first perform a full installation of BI platform 4.1 SP5, then use the Upgrade management tool to migrate content
and settings from the 3.x installation. See the Business Intelligence Platform Upgrade Guide for more information.
You can perform a 3.x/4.x side-by-side installation, which installs the new version 4.x, leaving the previously
installed 3.x version intact. However, this is not a recommended installation scenario. In this case, ensure that you
Business Intelligence Platform Installation Guide for Windows
Planning © 2015 SAP SE or an SAP affiliate company. All rights reserved. 13
do not choose port numbers and directories that are already in use by the earlier install to perform installation to a
unique directory and not creating port conflicts. A machine can host more than one version of SAP
BusinessObjects Business Intelligence platform, although system performance may be degraded if both are
running at once.
3.3 Database servers
If you do not have a database server in place for use with the BI platform, the installation program can install and
configure one for you. It is recommended that you evaluate your requirements against information from your
database server vendor to determine which supported database would best suit your organization's
requirements.
Sybase SQL Anywhere is the default database server. Any other database server must be running and accessible
when you run the installation program.
Note
The database client and server must use the Unicode character set.
For a list of supported database versions, revision levels, and requirements, consult the SAP BusinessObjects BI
4.1 Product Availability Matrix (PAM), available athttp://service.sap.com/sap/support/pam?hash=pvnr
%3D67837800100900006540 .
Note
The CMS database should be on the local network, and not accessed accross a WAN connection.It should be
very responsive, on the order of less than 10ms response time, 5ms or faster.
3.4 Languages
The BI platform user interface has been translated into more than 40 languages. You can add support for different
languages by installing language packs, either during the full installation or when modifying the installation. We
recommend that you install only the language packs that are required because the installed size of language
packs can be large.
Note
You cannot add new languages that are released in an update unless you do a full installation.
14 © 2015 SAP SE or an SAP affiliate company. All rights reserved.
Business Intelligence Platform Installation Guide for Windows
Planning
Example
The Arabic language pack was added in the BI Platform 4.1 release. Suppose you are applying the BI Platform
4.1 update to your BI Platform 4.0 installation. You cannot add Arabic after the update installation, because
that language did not exist in the BI Platform 4.0 release. You can add Arabic if you do a 4.1 full installation.
Business Intelligence Platform Installation Guide for Windows
Planning © 2015 SAP SE or an SAP affiliate company. All rights reserved. 15
4 Preparation
This section details how to prepare for the installation of the BI platform.
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 Support Packages from the
SAP Service Marketplace as described in To download the server installation program [page 26]. In addition,
download:
? SAP HOST AGENT - a required software package for using SAP System Landscape Directory (SLD). For
details, see To enable SAP System Landscape Directory (SLD) support [page 22].
To download SAP HOST AGENT, go tohttp://support.sap.com/home.html Software Downloads
Support Packages and Patches Browse our Download Catalog SAP Technology Components SAP
HOST AGENT .
? SAPCAR - a compression utility used to compress and decompress downloaded packages in the .SAR
format from SAP Service Marketplace.
To download SAPCAR, go tohttp://support.sap.com/home.html Software Downloads Support
Packages and Patches Browse our Download Catalog SAP Technology Components SAPCAR .
3. If you plan to use SAP System Landscape Directory (SLD), ensure that the SAP Host Agent is installed before
installing the BI platform. For more information on SLD, see “Registration of SAP BusinessObjects Business
Intelligence platform in the System Landscape” in the SAP BusinessObjects Business Intelligence Platform
Administrator Guide. For information on SAP Host Agent, see To enable SAP System Landscape Directory
(SLD) support [page 22].
4. Decide the values for options you will set during 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:
? Product key.
? Folder where the BI platform will be installed.
? 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.
? Central Management Server (CMS) 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 version control system configuration to store configuration files.
16 © 2015 SAP SE or an SAP affiliate company. All rights reserved.
Business Intelligence Platform Installation Guide for Windows
Preparation
? Promotion management configuration.
? Installation type (Full, Custom / Expand, Web Tier). For an explanation of the different installation types,
see To select an install type [page 28].
4.1 System requirements
Use the following guidelines when you install the BI platform:
? Ensure that the operating system is supported. Only 64-bit operating systems are supported.
A supported version of Windows .NET Framework is required. Windows Installer 4.5 is also required.
? 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).
? If you install the deployment on the operating system partition, ensure that there is enough room for the
deployment and the operating system. It is recommended that you have at least 2 gigabytes available for
temporary files and web applications.
? If you have previously installed any SAP BusinessObjects BI Suite products, the installation program uses the
existing directory.
? Ensure that the file path of the directory where you run the installation program is less than 280 characters in
length.
For a detailed list of supported operating systems and hardware requirements, consult the Supported Platforms
documentation available athttps://support.sap.com/home.html .
4.1.1 Account permissions
To install the BI platform on a Windows host, a user must have the following permissions:
Category Required access
Operating system Local administrative privileges.
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.
Database
? Permission for the BI platform user account to create,
edit, and drop tables.
? Permission for the BI platform user account to create
stored procedures (required by the Central Management
Server (CMS) system database).
Note
You cannot install the deployment on a domain controller, or on a Windows host where the default local
Administrator group security settings have been modified.
Business Intelligence Platform Installation Guide for Windows
Preparation © 2015 SAP SE or an SAP affiliate company. All rights reserved. 17
4.1.2 Network permissions
Ensure that the upgrade management tool can communicate with the source and destination deployments. For
more information on network permissions, see the “Securing SAP BusinessObjects Business Intelligence
platform” chapter of the SAP BusinessObjects Business Intelligence platform Administrator’s Guide.
4.1.2.1 Choosing a 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.
The CMS can also be clustered, so that CMS server processes run on different host systems in the cluster. When
creating a CMS cluster, ensure that each machine experiences the same network latency to the CMS system or
Auditing Data Store.
Consult the “Clustering Central Management Servers” section of the SAP BusinessObjects Business Intelligence
Platform Administrator Guide for more information on clustering CMS server processes.
4.2 Preparing the CMS system or Auditing Data Store
database
To use a database server other than the default one, complete the following tasks before installing the BI platform.
? Create a database (or tablespace or schema, if applicable to your database), and account to store CMS
configuration and system information. A second tablespace or scheme is required to hold auditing
information. Record the database, tablespace, and account information so you can enter the details when
prompted by the BI platform installation program.
Caution
If you have an existing BI platform installation, you must create a fresh database and migrate existing
content after the install is complete.
? Ensure that your database server is configured to use Unicode character encoding (such as UTF-8).
? Ensure that the database accounts have privileges to create, modify, and delete tables, and to create stored
procedures.
? When using a database server on a network, the appropriate database client drivers must be installed and
verified as working before installing BI platform. Contact your database administrator to establish which
drivers are required for your database.
During your installation, you will be prompted for the connection and authentication credentials so that the
installation program can initialize the database. The table below shows which information is required for
supported databases:
18 © 2015 SAP SE or an SAP affiliate company. All rights reserved.
Business Intelligence Platform Installation Guide for Windows
Preparation
Table 4:
Database Information required by installation program
Microsoft SQL
Server using
ODBC
? ODBC DSN name (selected from the Windows System DSN list)
? Account username
? Account password
? Database name
? Use trusted connection checkbox
Note
? When using an ODBC connection with Windows NT authentication, a trusted connection is
used. You must select Use trusted connection during the installation and ensure that the sys­
tem account has access to the database.
? When using an ODBC connection with SQL Server authentication (username and password), a
trusted connection is not used. Ensure that Use trusted connection is unselected.
? Show system database checkbox
? Reset existing database checkbox (recommended setting)
MySQL
? CMS database name
? Server hostname
? Port number (default is 3306)
? Account username
? Account password
? Reset existing database checkbox (recommended setting)
IBM DB2
? DB2 Alias name
? Account username
? Account password
? Reset existing database checkbox (recommended setting)
Oracle
? Oracle TNSNAME connection identifier
? Account username
? Account password
? Reset existing database checkbox (recommended setting)
MaxDB
? CMS database name
? Server hostname
? Port number (default is 7210)
? Account username
? Account password
? Reset existing database checkbox (recommended setting)
Business Intelligence Platform Installation Guide for Windows
Preparation © 2015 SAP SE or an SAP affiliate company. All rights reserved. 19
Database Information required by installation program
Sybase ASE
? Service name
Note
? The Sybase Adaptive Server Enterprise (ASE) service name is a combination of the hostname
and the port number, set by your database administrator in the sql.ini and interfaces files.
? BI platform will connect to the default database for the user you specify. The default is set by
the database administrator.
? Account username
? Account password
? Reset existing database checkbox (recommended setting)
Sybase SQL Any­
where using
ODBC
? DSN
? Account username
? Account password
? Reset existing database checkbox (recommended setting)
4.2.1 Extra requirements for IBM DB2
IBM DB2 has requirements that must be met before installing the BI platform:
? Ensure that the DB2 database is created with the following settings:
Collating Sequence = "Identity"
Codeset = "UTF-8"
Territory = ""
Replace with the code that is appropriate for your location. Consult your DB2 documentation for more
information. If your DB2 database does not have the Collating Sequence = "Identity" setting, the
user and user group objects may not sort as expected in the CMC.
? Create a user temporary table space before installing the BI platform. If you do not create a user temporary
table space, the BI platform installation program will not be able to configure the DB2 database.
For more information on user temporary table spaces in IBM DB2, see DB2 Basics: Table spaces and buffer
pools in the IBM technical library:http://www.ibm.com/developerworks/data/library/techarticle/
0212wieser/0212wieser.html .
? When using IBM DB2 to host an Auditing Data Store database, ensure that the page size for the auditing table
space is set to a minimum of 8192 (8 KB).
? Ensure that the CMS system database is not partitioned. The Auditing Data Store database may be
partitioned.
4.2.2 Extra requirements for Sybase ASE
If you are using Sybase ASE for the CMS or auditing database:
20 © 2015 SAP SE or an SAP affiliate company. All rights reserved.
Business Intelligence Platform Installation Guide for Windows
Preparation
? Create a database with a page size of 8 KB. The default page size is 2KB, which is too small for the CMS
system database to run efficiently. The page size is set up during the database creation and cannot be
changed after the database is created.
? Use a Unicode character set, such as UTF-8.
4.2.3 Extra requirements for SAP HANA
If you are using SAP HANA for the CMS database, you must select the default database during installation then
export the data to an SAP HANA database. See To select SAP HANA as a CMS database in the SAP
BusinessObjects Business Intelligence platform Administrator's Guide.
4.2.4 Extra requirements for CMS clustering with SQL
Anywhere
If you are using the bundled SQL Anywhere database server for the CMS, there are two prerequisites before
adding a new node on a new machine to CMS cluster. On the machine hosting the new node:
1. You must install the SQL Anywhere Database Client.
Download the SQL Anywhere 12.0.1 client for your operating system at:http://scn.sap.com/docs/
DOC-35857
2. You must create an ODBC DSN connecting to the primary node SQL Anywhere CMS database.
On the primary node, right-click the SIA in the Central Configuration Manager (CCM) and select Properties.
The CMS DSN is found on the Configuration tab with details found in the Windows ODBC Data Source
Administrator. By default the DSN is BI4_CMS_DSN.
Consider the following example. A primary node with a CMS server and bundled SQL Anywhere database is
installed on one machine. To create a new CMS node on a new machine:
1. Install the SQL Anywhere Database Client. This installs the SQL Anywhere 12 database driver.
2. Create an ODBC DSN to the primary node SQL Anywhere CMS database using the SQL Anywhere 12 driver.
For example, assume the primary node host is 192.0.2.0 and uses default port and values for the SQL
Anywhere installation:
ODBC property SQL Anywhere value (primary node)
Data source name BI4_CMS_DSN
User ID dba
Password mypassword
Host 192.0.2.0
Port 2638
Server name BI4
Database name BI4_CMS
3. Run the BI platform server installation program and select Custom / Expand as the installation type. During
the installation select the following:
Business Intelligence Platform Installation Guide for Windows
Preparation © 2015 SAP SE or an SAP affiliate company. All rights reserved. 21
? On the Select Features page, select the Central Management Server feature. Unselect the Sybase SQL
Anywhere Database, Subversion, and WebTier features.
? On the Select New or Expand Installation page, select Expand an existing SAP BusinessObjects BI platform
deployment.
? On the Select Existing CMS Database Type page, select SAP Sybase SQL Anywhere using ODBC.
? On the Configure CMS Repository Database - SQL Anywhere (ODBC) page, select the ODBC DSN created
in step 2 and enter the “dba” account password.
? Proceed and complete the installation of the new CMS server node.
4.3 SAP support
4.3.1 Support for SAP System Landscape Directory (SLD)
SAP System Landscape Directory (SLD) is a directory service that maintains a list of installed SAP and
(optionally) non-SAP software. SLD provides two main categories of information:
? Software already installed
? Software that could be installed at a later time
SAP systems come with a data supplier (DS) component that automatically updates the landscape directory.
Non-SAP software that supports SLD registers through an open API. The information gathered on installed
software includes:
? Version
? Host information
? Connection information
To use SLD support, ensure that SAP Host Agent is installed and working on the system(s) that host the BI
platform. SAP Host Agent may be installed and configured before or after installing the BI platform.
4.3.1.1 To enable SAP System Landscape Directory (SLD)
support
If you plan on using SAP System Landscape Directory (SLD) or SAP Solution Manager Diagnostics (SMD), ensure
that the SAP Host Agent is installed and configured. The following steps walk you through installing SAP Host
Agent.
SAP Host Agent may be installed and configured before or after installing the BI platform. For more information
on SAP Host Agent, see “Registration of SAP BusinessObjects Business Intelligence platform in the System
Landscape” in the SAP BusinessObjects Business Intelligence Platform Administrator Guide.
Note
If you have installed SAP GUI or SAP Solution Manager Diagnostics (SMD), skip to step 4 below.
22 © 2015 SAP SE or an SAP affiliate company. All rights reserved.
Business Intelligence Platform Installation Guide for Windows
Preparation
Prior to installing support for SAP System Landscape Directory (SLD) there must be an sapadm user with
administrator privileges.
The SAP_LocalAdmin group must also exist, and the sapadm user must be a member. The sapadm user
password is required during the SAPHOSTCONTROL installation.
1. Download SAP Host Agent (SAPHOSTAGENT.SAR) from the SAP Software Distribution Center of the SAP
Service Marketplace (https://support.sap.com/swdc ).
Log on with your SAP Service Marketplace ID and locate the version of SAPHOSTAGENT.SAR appropriate for
your system.
2. Extract SAPHOSTAGENT.SAR by entering the following command:
sapcar -xvf SAPHOSTAGENT.SAR
3. Install SAPHOSTCONTROL by entering the following command:
saphostexec -install
4. Locate the sldreg tool, which is usually located in the following folder:
\SAP\hostctrl\exe
5. Create an SLD key with the following command:
sldreg –configure connect.key
You will be prompted to supply a username, password, host, port, and protocol for connecting to the SLD
server.
6. Enter the information requested.
The sldreg tool creates a connect.key file that will automatically be used by sld-ds to push information to
SLD server.
If you have already installed the BI platform, restart all SIA nodes in the Central Configuration Manager (CCM) to
register with the SLD.
4.3.2 Support for SAP Solution Manager Diagnostics (SMD)
SAP Solution Manager Diagnostics (SMD) monitors the performance of systems in the SAP System Landscape
Directory (SLD). Problems can be identified, analyzed, and resolved with the information gathered by SMD, which
includes:
? Performance monitoring
? Configuration management
? Log management
? Load testing
? Alerting
? Resource monitoring
Tools integrated into SMD include:
? CA Wily Introscope
For full instrumentation, both SMD and CA Wily Introscope should be used.
? SAP LoadRunner by HP
Non-SAP software with an SAP-certified integration is entered into a central repository and transferred
automatically to your SAP System Landscape Directories (SLD). SAP customers can then easily identify which
Business Intelligence Platform Installation Guide for Windows
Preparation © 2015 SAP SE or an SAP affiliate company. All rights reserved. 23
version of third-party product integration has been certified by SAP within their SAP system environment. This
service provides additional awareness for third-party products besides our online catalogs for third-party
products.
To use SMD, the SMD Agent must be installed. SMD Agent may be installed and configured before or after
installing the BI platform. During installation, the installation program prompts for the hostname and port number
of the SMD Agent. If you do not want to use SMD, or you will install SMD later, you can choose not to use SMD.
The SMD Agent can be configured later in the Central Management Console (CMC) Placeholders screen. For more
information, seeTo configure SMD Agent post installation [page 55].
SMD Agent is included in the COLLATERALS\DiagnosticsAgent7.3 folder of the installation directory. For
information on installing SMD agent, see SAP Note 1448655.
4.3.3 Support for CA Wily Introscope
CA Wily Introscope is included as a part of SAP Solution Manager Diagnostics (SMD). For full instrumentation,
both SMD and CA Wily Introscope should be used.
To use CA Wily Introscope and SMD, the SMD Agent must be installed. SMD Agent may be installed and
configured before or after installing the BI platform.
During installation, the installation program prompts for the hostname and port number of the Introscope Agent.
If you do not want to use Introscope, or you will install it later, you can choose not use Introscope. Introscope can
be configured later in the Central Management Console (CMC) Placeholders screen. For more information, seeTo
configure SMD Agent post installation [page 55].
4.3.4 Support for SAP BW
The BI platform can integrate with SAP BW. To get the best performance from SAP BW, follow the instructions in
these SAP Notes onhttps://service.sap.com :
? 1771995 - Incorrect number of hierarchy levels in Design Time
? 1750788 - BICS metadata service enhancement
? 1767351 - Missing metadata of characteristics in the fix filter
? 1776999 - Incorrect hierarchy sorting
? 1777544 - Metadata missing for node type attributes
? 1778347 - Attributes for node types are not read
? 1770434 - Dynamic filter of compound char. is incorrect
? 1762156 - Nodes in fixed filter in Design Time are incorrect
? 1776688 - Too many hierarchy levels are read
? 1798297 - Correction for issue found on Samsung queries
? 1806813 - Text of characteristic values is not read
? 1809517 - Correction for invalid variable order when retrieving the list of variables through the design time
services
? 1811124 - This note fixes the sorting of the of drill down characteristics returned by the design-time API so that
it matches the runtime sorting
24 © 2015 SAP SE or an SAP affiliate company. All rights reserved.
Business Intelligence Platform Installation Guide for Windows
Preparation
? 1812142 - This note fixes the sorting of the hierarchies returned by the design-time API so that it matches the
runtime sorting
? 1817482 - This note adds the feature for the Design Time API to choose whether members should be read
initially or not. By default, there are not read; this provides a performance enhancement for SL.
4.4 Final checklist
Prior to installing the BI platform, review the following checklist.
? Have you decided 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 directory when running the installation
program from the current working directory).
? Have you verified appropriate network connectivity between all machines that will be part of your
deployment?
? If you are using your own database server:
? Have you created a database, tablespace (if required), and accounts for the CMS system and Auditing
Data Store databases?
? Have you made sure you can log onto the database from the BI platform host?
? If you are using IBM DB2 or Sybase ASE, have you verified that your database was created with the
correct settings? (Some settings can't be modified after the database has been created.)
? Has the database client software been properly configured?
? If you are using your own web application server:
? Have you decided on which web application server to use?
? Has the server already been installed and configured?
? Have you ensured 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. For more information, seeSupport for SAP System Landscape Directory (SLD) [page 22].
? If you plan to use SAP Solution Manager Diagnostics (SMD), SMD Agent may have been installed and
configured before or after the BI platform. For more information, see Support for SAP Solution Manager
Diagnostics (SMD) [page 23].
Installation on Microsoft Windows requires a minimum screen solution of 1024 × 768.
Note
The BI platform installation program no longer installs Client Tools. Client Tools can only be installed with the
dedicated Client Tools installation program.
Business Intelligence Platform Installation Guide for Windows
Preparation © 2015 SAP SE or an SAP affiliate company. All rights reserved. 25
5 Installation
This chapter guides you through the installation of the BI platform.
5.1 Overview
There are two different methods of running the installation program for the BI platform:
? 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.
? Silent installation
Installation options are given on the command-line or in a text file. This option is useful if you want to install
the same configuration on multiple machines.
If the installation program encounters an unexpected condition, and is unable to continue, it will undo any work
completed up to that point, and return the system to the state that it was in before the installation started.
When the installation program detects an identical previously-installed version, it will enter maintenance mode,
allowing you to remove, repair, or modify the software.
The BI platform requires a database server and web application server to function. If you do not have an existing
database, the installation program automatically installs and configures a Sybase SQL Anywhere database. If you
do not have an existing web application server, the installation program automatically installs and configures a
Tomcat web application server.
Note
The installation program may take more than one hour to complete.
5.2 To download the server installation program
1. Go tohttps://support.sap.com/home.html > Software Downloads.
2. On the Find your software tab, under the A–Z Index, click Installations and Upgrades.
3. Select B SBOP BI platform (former SBOP Enterprise) SBOP BI PLATFORM (ENTERPRISE) SBOP BI
PLATFORM 4.1 .
4. Select Installation and Upgrade and then select your platform.
5. Select all of the packages titled SBOP BI PLATFORM SERVER plus any additional add-on products
you require, then follow the instructions on the website to download and extract the packages.
26 © 2015 SAP SE or an SAP affiliate company. All rights reserved.
Business Intelligence Platform Installation Guide for Windows
Installation
The software may take a long time to download, and you may need to contact the system administrator to ensure
your company's firewall will not terminate the download process.
Support Packages and Patches are installation programs that contain updates to BI platform software. You can
download them fromhttps://support.sap.com/home.html > Software Downloads. On the Find your software
tab, under the A–Z Index, click Support Packages and Patches. For more information on installing Support
Packages and Patches, see the SAP BusinessObjects BI Suite Update Guides.
Note
? Users need to use the SAP Download manager for download. When you download the server installation
program without the download manager, it results in failed or partial downloads.
? To extract the solaris and air tar files, users need to use gnu tar, or gtar, to extract, and not the default tar
utility. Else, the installation would fail.
5.3 To run an interactive installation
Before installing, ensure that the account being used has Administrator privileges. The installation requires that
the account being used is a member of the Windows Administrators group, and that the default privileges
assigned to the Administrators group have not been modified.
The installation program requires a minimum screen resolution of 1024 × 768 pixels. Using Microsoft Remote
Desktop Connection to run the installation program is supported, as long as a minimum screen resolution of 1024
× 768 pixels is used.
Note
The installation log file is saved to \InstallData\logs\
\setupengine.log.
1. Locate and run setup.exe.
2. Select the setup language.
The language setting is used by the installation program to display information to you in the language of your
choice. If you select a non-English language, the corresponding language pack is automatically installed on
the server.
Note
The installation program will automatically run in the same language as your operating system. The
language used by the installation program will determine the names used for Windows components
configured by the installation program, such as Windows service names and Start menu shortcuts. These
names cannot be changed later and are not affected by language settings once the installation is complete.
3. On the Check Prerequisites page, review the results and decide whether to continue with the installation, or
abort and correct any unmet requirements.
The installation program checks for required components and conditions. If a dependency prerequisite
condition is critical, the installation program will not allow the installation to proceed. If the missing or
Business Intelligence Platform Installation Guide for Windows
Installation © 2015 SAP SE or an SAP affiliate company. All rights reserved. 27
unsupported component is optional, you have the option to either continue with the installation or stop and
correct the condition.
4. Review the installation welcome page.
5. On the License Agreement page, review the agreement and select I accept the License Agreement.
6. On the Configure Product Registration page, enter the product key.
Tip
Store the product key in a safe place in case you need to re-install the product.
7. On the Select Language Packs page, select additional languages to install from the list.
The language currently being used by the operating system is selected automatically. English language
support cannot be deselected because it is used if a problem is detected with an individual language.
The Select Install Type page appears.
5.3.1 To select an install type
The Select Install Type page is used to select the type of installation to perform.
1. Select one of the following install type options:
? Full
Installs all required server components onto a single machine. Use this option to create a single-host
deployment, such as a pre-production development or test environment.
? Custom / Expand
Allows experienced users to select individual features. Use this option:
? When distributing server components between more than one host, such as creating a CMS cluster.
? When you want full control over which features are deployed to a host.
Note
If you are adding a new node to a CMS cluster that uses the bundled SQL Anywhere database server,
see Extra requirements for CMS clustering with SQL Anywhere [page 21] before proceeding with the
installation.
? Web Tier
The web tier includes web applications such as BI launch pad and the Central Management Console
(CMC). Use the Web Tier installation option to install Java web applications onto a dedicated Java web
application server.
If you already have a supported web application server installed, you can deselect the option to install
Tomcat, and only install the Java web applications.
2. Proceed to the next page to start configuring the selected installation.
On the Configure Destination Folder page, review the destination folder shown. This is the folder into which the
installation program will install the BI platform. If the folder does not exist, the installation program creates it.
Note
? The use of Unicode characters in the destination folder is not supported.
28 © 2015 SAP SE or an SAP affiliate company. All rights reserved.
Business Intelligence Platform Installation Guide for Windows
Installation
? Ensure that the destination folder is not set to the same folder in which the installation program has
been extracted.
? If you have already installed SAP BusinessObjects products, the Destination Folder Information field is
not editable, and the path to the existing folder is displayed.
? If you selected a Full installation, proceed to the following Full section.
? If you selected a Custom / Expand installation, proceed to the following Custom / Expand section.
? If you selected a Web Tier installation, proceed to the following Web Tier section.
5.3.1.1 Full installation
The following steps are performed for Full installations of the BI platform.
1. On the Select Default or Existing Database page, select a database option to store Central Management
Server (CMS) and Auditing Data Store (ADS) information.
Option Description
Configure and
install a Sybase
SQL Anywhere
database
If you do not have a database server in place for use with the BI platform, the installation program can
install and configure Sybase SQL Anywhere for you.
Note
Installation of third-party patches or updates is not supported for bundled software. For details, see
Patching third-party solutions bundled with the BI platform [page 62].
Configure an
existing
database
If you have an existing database server, the installation program prompts for information on the data­
base type and connection credentials for both the CMS system and auditing databases.
Note
An existing database must have user accounts with the appropriate privileges ready, and the appro­
priate drivers must be installed and verified as working. The installation program attempts to con­
nect to, and initialize, the database as a part of the installation process.
It is recommended that you evaluate your requirements against information from your database server
vendor to determine which supported database would best suit your organization's needs.
2. If you selected Configure an existing database:
a. On the Select Existing CMS Database Type page, select the database type of the existing CMS database.
b. On the Select Existing Auditing Database Type page, select the database type of the existing auditing
database.
If you do not want to use the auditing feature, select No auditing database.
3. On the Select Java Web Application Server page, select an option for hosting the BI platform web applications.
Business Intelligence Platform Installation Guide for Windows
Installation © 2015 SAP SE or an SAP affiliate company. All rights reserved. 29
Option Description
Install the default
Tomcat Java Web
Application Server and
automatically deploy
web applications
If you do not have a web application server in place for use with the BI platform, the installation
program can install and configure a Tomcat web application server for you. The BI platform web
applications are automatically deployed to Tomcat.
Note
Installation of third party patches or updates is not supported for bundled software. For de­
tails, see Patching third-party solutions bundled with the BI platform [page 62].
Manually deploy web
applications to a
supported Java Web
Application Server
after the installation
If you have an existing, supported Java web application server, select this option and then deploy
web applications to it later (after installation) using the WDeploy tool. For more information, see
the SAP BusinessObjects Business Intelligence Platform Web Application Deployment Guide
Note
The BI platform does not support the automatic deployment of web applications to any web
application server other than the bundled Tomcat web application server during the installa­
tion program.
Install the Web
Application Container
Server and
automatically deploy
web applications
If you do not want to use a Java application server to host your BI platform web applications,
then select this option to host them on Web Application Container Server (WACS).
It is recommended that you evaluate your requirements against information from your web application server
vendor to determine which supported web application server would best suit your organization's needs.
Note
When configuring a production environment, it is recommended that the web application server is hosted
on a separate system from the BI platform servers. Running the BI platform servers and a web application
server on the same host in a production environment may decrease performance.
4. One the Select Version Management page, decide whether to install and configure Subversion version control
system.
Option Description
Configure and install
Subversion
Installs and configures Subversion version control system.
Do not configure a version
control system at this time
If you have an existing, supported version control system, you must manually configure it
with the Central Management Console (CMC) after the installation is complete. For more in­
formation, see the “Version management” and “Promotion management” sections of the
Business Intelligence Platform Administrator Guide.
The BI platform can maintain different versions of BI resources that exist in the CMS repository in a version
control system, making it easier to revert to a previous configuration when needed using the CMC.
5. On the Configure Server Intelligence Agent (SIA) page, review the default name and port number for the SIA
node.
30 © 2015 SAP SE or an SAP affiliate company. All rights reserved.
Business Intelligence Platform Installation Guide for Windows
Installation
Option Description
Node
Name
This is the name that you will see in the Central Configuration Manager (CCM). Many CMS servers can be
managed by a single SIA.
The name must consist of English characters (A-Z, a-z, and 0-9) and contain no spaces or other punctuation.
Underscores ("_") are not allowed. The SIA name cannot start with a number.
SIA Port The port is used for the SIA to listen for incoming connections from the CMS. The SIA must be able to receive
incoming connections on this port, so ensure that your firewall is configured appropriately.
Port 6410 is a standard TCP/IP port number reserved for use with a BI platform SIA.
6. On the Configure Central Management Server (CMS) page, review the default value for the CMS port number.
This is the port on which the CMS listens for incoming connections from the web application server, web
server (if applicable), other CMS nodes (if applicable) and servers. The CMS must be able to receive incoming
connections on this port, so ensure that your firewall is configured appropriately.
Port 6400 is a standard TCP/IP port number reserved for use with the BI platform CMS.
7. On the Configure CMS Account page, enter and confirm the CMS Administrator account password and the
CMS cluster key.
The CMS Administrator is a super-user account in the BI platform authentication system, used only to
administer your server configuration. It is not part of any operating system or single sign-on authentication
system.
Communication between some CMS components is encrypted to provide a higher level of security when using
clusters.
Note
The administrator password entered during full install must always contain at least two of the following
character classes: Upper case letters and lower case letters.
Note
If the administrator password is not set in accordance with the password restrictions, installation fails.
8. Configure the CMS system database.
a. If you selected Configure and install a Sybase SQL Anywhere database, enter the account and port
information on the Configure Sybase SQL Anywhere page.
Enter the port number for Sybase SQL Anywhere to listen for incoming database queries. The database
must be able to receive incoming connections on this port, so ensure that your firewall is configured
appropriately. Also enter and confirm the database administrator account password.
b. If you selected Configure an existing database, enter the connection information for your existing
database to use for the CMS on the Configure CMS Repository Database - page.
If you're using an ODBC database driver, you must configure an ODBC data source. A system ODBC DSN
can be configured from: Start Control Panel Administrative Tools Data Sources (ODBC) .
c. If you selected Configure an existing database, and you plan to use auditing, enter the connection
information for your existing database to use for the ADS on the Configure Auditing Database page.
Business Intelligence Platform Installation Guide for Windows
Installation © 2015 SAP SE or an SAP affiliate company. All rights reserved. 31
9. If you selected Install the default Tomcat Java Web Application Server and automatically deploy web
applications, review the default port values on the Configure Tomcat page.
Option Description
Connection port The port on which the web application server listens for incoming connections from web clients.
Shutdown port The port that allows the web application to be shut down remotely.
Redirect port The port that enables redirects to secure web connections.
Tomcat must be able to receive incoming connections on the given port numbers, so ensure that your firewall
is configured appropriately.
10. On the Configure HTTP Listening Port page, review the HTTP Listening Port number on the page for WACS to
listen for incoming connections from web clients.
WACS must be able to receive incoming connections on the given port numbers, so ensure that your firewall
is configured appropriately.
11. If you selected Configure and install Subversion review the port number and enter a Subversion password
(user account is "LCM") on the Configure Subversion page.
12. On the Select Connectivity for Solution Management Diagnostics (SMD) Agent page, decide whether to
integrate the BI platform with an existing SMD Agent.
Option Description
Configure connectivity
to SMD Agent
The BI platform can integrate with your organization's deployment of SAP Solution Manager Di­
agnostics (SMD).
If you select this option, enter the SMD Agent hostname and port number on the following
Configure Connectivity to SMD Agent page.
Do not configure
connectivity to SMD
Agent
You can configure SMD Agent in the CMC Placeholders screen later after the installation pro­
gram is complete.
Note
To use SAP Solution Manager Diagnostics (SMD), SAP Host Agent and SMD Agent must be installed:
? For information on installing the SAP Host Agent before installing the BI platform, see To enable SAP
System Landscape Directory (SLD) support [page 22].
? For information on installing the SAP Host Agent after installing the BI platform, see To configure
System Landscape Directory (SLD) Data Supplier (DS) post installation [page 55].
? For information on installing SMD Agent before installing the BI platform, see Support for SAP Solution
Manager Diagnostics (SMD) [page 23].
? For information on installing SMD Agent after installing the BI platform, see To configure SMD Agent
post installation [page 55].
13. On the Select Connectivity to Introscope Enterprise Manager page, decide whether to integrate the BI platform
with an existing Introscope Enterprise Manager server.
Note
To use CA Wily Introscope Enterprise Manager, SMD Agent must be installed.
32 © 2015 SAP SE or an SAP affiliate company. All rights reserved.
Business Intelligence Platform Installation Guide for Windows
Installation
Option Description
Configure connectivity
to Introscope
Enterprise Manager
The BI platform can integrate with your organization's deployment of CA Wily Introscope Enter­
prise Manager.
If you select this option, enter the hostname and port number for the Introscope Enterprise Man­
ager server on the following Configure Connectivity to Introscope Enterprise Manager page.
Do not configure
connectivity to
Introscope Enterprise
Manager
You can configure Introscope Enterprise Manager in the CMC Placeholders screen later after the
installation program is complete.
The Start Installation page appears. Start the installation.
Proceed to While the installation program runs.
5.3.1.2 Custom / Expand installation
The following steps are performed for Custom / Expand installations of the BI platform.
1. On the Select Features page, select the features to install from the list.
Features are grouped under the following headings:
? Web Tier
The web tier components include web applications such as BI launch pad and the Central Management
Console (CMC) that allow end users and administrators to interact with BI content and the BI platform
installation.
If you do not have a web application server in place for use with the BI platform, the installation program
can install and configure a Tomcat web application server for you. It is recommended that you evaluate
your requirements against information from your web application server vendor to determine which
supported web application server would best suit your organization's needs.
If you already have a supported web application server installed, you can deselect the option to install
Tomcat, and only install the Java web applications
? Servers
Server features include the Business Intelligence platform servers (such as processing and scheduling
servers), major system components (such as the CMS, Event Server, bundled database, and a version
control system), and servers that integrate the BI platform into your organization's existing network
infrastructure, such as SAP BW or other Enterprise Resource Planning (ERP) systems.
Note
If you plan to use SAP BW authentication, ensure that the BW Publisher Server feature is selected in
the Integration Servers feature list.
? Administrator Tools
The Administrator Tools features help administrators maintain an installation. For example, the Upgrade
management tool allows you migrate BI content during an upgrade between different versions of the BI
platform.
? Developer Tools
Business Intelligence Platform Installation Guide for Windows
Installation © 2015 SAP SE or an SAP affiliate company. All rights reserved. 33
If you plan to develop your own applications with a the BI platform .NET Software Development Kit (SDK),
install the Developer Tools feature.
? Database Access
To access, analyze, and report on the data in your organization's existing databases, select the
appropriate Database Access features. If your organization does not use a particular database, you can
deselect it.
Note
? Integration for PeopleSoft Enterprise, JD Edwards EnterpriseOne, Siebel, or Oracle EBS Enterprise
Resource Planning (ERP) systems is not selected by default. If you plan to use an ERP single sign-
on authentication, or other ERP features, ensure that the appropriate ERP feature is selected in the
Data Access feature list.
? If you plan to use integration for SAP, SAP BW, or SAP R3 systems, ensure that the SAPBW and
SAP features are selected in the Data Access feature list.
? Samples
The samples features installs sample reports, templates, and reporting databases. If you do not need
samples, you can deselect it.
2. On the Select New or Expand Installation page, select the type of installation to perform.
Option Description
Start a new SAP BusinessObjects BI
platform deployment
Select if you are installing a stand-alone BI platform server, or the first server
in a cluster.
Expand an existing SAP BusinessObjects BI
platform deployment
Select if you already have a CMS and want to create a new server node as
part of a cluster.
If you selected Start a new SAP BusinessObjects BI platform deployment on the last page, proceed to Custom
(New) installation.
If you selected Expand an existing SAP BusinessObjects BI platform deployment on the last page, proceed to
Custom (Expand) installation.
5.3.1.2.1 Custom (New) installation
If you chose the Start a new SAP BusinessObjects BI platform deployment option for a Custom / Expand
installation:
1. If you deselected the Sybase SQL Anywhere Database feature in the Select Feature page:
a. On the Select Existing CMS Database Type page, select the database type to use for the CMS database.
b. On the Select Existing Auditing Database Type page, select the database type to use for the auditing
database.
If you do not want to use the auditing feature, select No auditing database.
2. On the Configure Server Intelligence Agent (SIA) page, review the default name and port number for the SIA
node.
34 © 2015 SAP SE or an SAP affiliate company. All rights reserved.
Business Intelligence Platform Installation Guide for Windows
Installation
Option Description
Node
Name
This is the name that you will see in the Central Configuration Manager (CCM). Many CMS servers can be
managed by a single SIA.
The name must consist of English alphanumeric characters (A-Z, a-z, and 0-9) and contain no spaces or other
punctuation. Underscores ("_") are not allowed. The SIA name cannot start with a number.
SIA Port The port is used for the SIA to listen for incoming connections from the CMS. The SIA must be able to receive
incoming connections on this port, so ensure that your firewall is configured appropriately.
Port 6410 is a standard TCP/IP port number reserved for use with a BI platform SIA.
3. On the Configure Central Management Server (CMS) page, review the default value for the CMS port number.
This is the port on which the CMS listens for incoming connections from the web application server, web
server (if applicable), other CMS nodes (if applicable) and servers. The CMS must be able to receive incoming
connections on this port, so ensure that your firewall is configured appropriately.
Port 6400 is a standard TCP/IP port number reserved for use with the BI platform CMS.
4. On the Configure CMS Account page, enter and confirm the CMS Administrator account password and the
CMS cluster key.
The CMS Administrator is a super-user account in the BI platform authentication system, used only to
administer your SAP BusinessObjects server configuration. It is not part of any operating system or single
sign-on authentication system.
Communication between some CMS components is encrypted to provide a higher level of security when using
clusters.
Note
The administrator password entered during custom (new) install must always contain at least two of the
following character classes: Upper case letters and lower case letters.
Note
If the administrator password is not set in accordance with the password restrictions, installation fails.
5. Configure the CMS system database.
a. If you selected the Sybase SQL Anywhere Database feature in the Select Feature page, enter the account
and port information on the Configure Sybase SQL Anywhere page.
Enter the port number for Sybase SQL Anywhere to listen for incoming database queries. The database
must be able to receive incoming connections on this port, so ensure that your firewall is configured
appropriately. Also enter and confirm the database administrator account password.
b. If you deselected the Sybase SQL Anywhere Database feature in the Select Feature page, enter the
connection information for your existing database to use for the CMS on the Configure CMS Repository
Database - page.
If you're using an ODBC database driver, you must configure an ODBC data source. A system ODBC DSN
can be configured from: Start Control Panel Administrative Tools Data Sources (ODBC) .
c. If you deselected the Sybase SQL Anywhere Database feature in the Select Feature page, and you plan to
use auditing, enter the connection information for your existing database to use for the ADS on the
Configure Auditing Database page.
Business Intelligence Platform Installation Guide for Windows
Installation © 2015 SAP SE or an SAP affiliate company. All rights reserved. 35
6. On the Select Automatic Server Start page, decide whether to start the servers as soon as the installation is
complete.
If you select No, the servers must be started manually with the Central Configuration Manager (CCM) after
the installation is complete.
7. If you selected the Tomcat feature in the Select Feature page , review the default port values on the Configure
Tomcat page.
Option Description
Connection port The port on which the web application server listens for incoming connections from web clients.
Shutdown port The port that allows the web application to be shut down remotely.
Redirect port The port that enables redirects to secure web connections.
Tomcat must be able to receive incoming connections on the given port numbers, so ensure that your firewall
is configured appropriately.
8. If you selected the Web Application Container Server or RESTful Web Service features in the Select Feature
page, review the HTTP Listening Port number on the Configure HTTP Listening Port page.
WACS must be able to receive incoming connections on the given port numbers, so ensure that your firewall
is configured appropriately.
9. If you selected the Subversion feature in the Select Feature page, review the port number and enter a
Subversion password (user account is "LCM") on the Configure Subversion page.
10. On the Select Connectivity for Solution Management Diagnostics (SMD) Agent page, decide whether to
integrate the BI platform with an existing SMD Agent.
Option Description
Configure connectivity
to SMD Agent
The BI platform can integrate with your organization's deployment of SAP Solution Manager Di­
agnostics (SMD).
If you select this option, enter the SMD Agent hostname and port number on the following
Configure Connectivity to SMD Agent page.
Do not configure
connectivity to SMD
Agent
You can configure SMD Agent in the CMC Placeholders screen later after the installation pro­
gram is complete.
Note
To use SAP Solution Manager Diagnostics (SMD), SAP Host Agent and SMD Agent must be installed:
? For information on installing the SAP Host Agent before installing the BI platform, see To enable SAP
System Landscape Directory (SLD) support [page 22].
? For information on installing the SAP Host Agent after installing the BI platform, see To configure
System Landscape Directory (SLD) Data Supplier (DS) post installation [page 55].
? For information on installing SMD Agent before installing the BI platform, see Support for SAP Solution
Manager Diagnostics (SMD) [page 23].
? For information on installing SMD Agent after installing the BI platform, see To configure SMD Agent
post installation [page 55].
11. On the Select Connectivity to Introscope Enterprise Manager page, decide whether to integrate the BI platform
with an existing Introscope Enterprise Manager server.
36 © 2015 SAP SE or an SAP affiliate company. All rights reserved.
Business Intelligence Platform Installation Guide for Windows
Installation
Note
To use CA Wily Introscope Enterprise Manager, SMD Agent must be installed.
Option Description
Configure connectivity
to Introscope
Enterprise Manager
The BI platform can integrate with your organization's deployment of CA Wily Introscope Enter­
prise Manager.
If you select this option, enter the hostname and port number for the Introscope Enterprise Man­
ager server on the following Configure Connectivity to Introscope Enterprise Manager page.
Do not configure
connectivity to
Introscope Enterprise
Manager
You can configure Introscope Enterprise Manager in the CMC Placeholders screen later after the
installation program is complete.
The Start Installation page appears. Start the installation.
Proceed to While the installation program runs.
5.3.1.2.2 Custom (Expand) installation
If you chose the Expand an existing SAP BusinessObjects BI platform deployment option for a Custom / Expand
installation:
1. On the Select Existing CMS Database Type page, select the database type of the existing, remote CMS
database.
2. On the Configure Server Intelligence Agent (SIA) page, review the default name and port number for the new
SIA node.
Option Description
Node
Name
This is the name that you will see in the Central Configuration Manager (CCM). Many CMS servers can be
managed by a single SIA.
The name must consist of English alphanumeric characters (A-Z, a-z, and 0-9) and contain no spaces or other
punctuation. Underscores ("_") are not allowed. The SIA name cannot start with a number.
SIA Port The port is used for the SIA to listen for incoming connections from the CMS. The SIA must be able to receive
incoming connections on this port, so ensure that your firewall is configured appropriately.
Port 6410 is a standard TCP/IP port number reserved for use with a BI platform SIA.
3. On the Existing CMS Deployment Information page, enter connection information for the existing, remote
CMS, including the Administrator password.
4. On the Configure CMS Account page, enter and confirm the CMS cluster key for the new CMS.
The CMS Administrator is a super-user account in the BI platform authentication system, used only to
administer your SAP BusinessObjects server configuration. It is not part of any operating system or single
sign-on authentication system.
Communication between some CMS components is encrypted to provide a higher level of security when using
clusters.
Business Intelligence Platform Installation Guide for Windows
Installation © 2015 SAP SE or an SAP affiliate company. All rights reserved. 37
5. On the Configure Central Management Server (CMS) page, review the default value for the CMS port number.
This is the port on which the CMS listens for incoming connections from the web application server, web
server (if applicable), other CMS nodes (if applicable) and servers. The CMS must be able to receive incoming
connections on this port, so ensure that your firewall is configured appropriately.
Port 6400 is a standard TCP/IP port number reserved for use with the BI platform CMS.
6. On the Configure CMS Repository Database - page, enter connection details for the CMS
system database.
If you are using the Sybase SQL Anywhere database bundled with the BI platform on the existing CMS, to
which you are attempting to connect, enter the system ODBC DSN connection for the existing CMS system
database.
If you are using a different previously installed database, enter connection credentials for the CMS to connect
to the database.
7. On the Select Automatic Server Start page, decide whether to start the servers as soon as the installation is
complete.
If you select No, the servers must be started manually with the Central Configuration Manager (CCM) after
the installation is complete.
8. If you selected the Tomcat 7.0 feature, review the default port values on the Configure Tomcat page.
Option Description
Connection port The port on which the web application server listens for incoming connections from web clients.
Shutdown port The port that allows the web application to be shut down remotely.
Redirect port The port that enables redirects to secure web connections.
9. On the Configure HTTP Listening Port page, review the HTTP Listening Port number on the page for WACS to
listen for incoming connections from web clients.
WACS must be able to receive incoming connections on the given port numbers, so ensure that your firewall
is configured appropriately.
10. If you selected the Subversion feature, review the port number and enter a Subversion password (user
account is "LCM") on the Configure Subversion page.
11. On the Select Connectivity for Solution Management Diagnostics (SMD) Agent page, decide whether to
integrate the BI platform with an existing SMD Agent.
Option Description
Configure connectivity
to SMD Agent
The BI platform can integrate with your organization's deployment of SAP Solution Manager Di­
agnostics (SMD).
If you select this option, enter the SMD Agent hostname and port number on the following
Configure Connectivity to SMD Agent page.
Do not configure
connectivity to SMD
Agent
You can configure SMD Agent in the CMC Placeholders screen later after the installation pro­
gram is complete.
Note
To use SAP Solution Manager Diagnostics (SMD), SAP Host Agent and SMD Agent must be installed:
38 © 2015 SAP SE or an SAP affiliate company. All rights reserved.
Business Intelligence Platform Installation Guide for Windows
Installation
? For information on installing the SAP Host Agent before installing the BI platform, see To enable SAP
System Landscape Directory (SLD) support [page 22].
? For information on installing the SAP Host Agent after installing the BI platform, see To configure
System Landscape Directory (SLD) Data Supplier (DS) post installation [page 55].
? For information on installing SMD Agent before installing the BI platform, see Support for SAP Solution
Manager Diagnostics (SMD) [page 23].
? For information on installing SMD Agent after installing the BI platform, see To configure SMD Agent
post installation [page 55].
12. On the Select Connectivity to Introscope Enterprise Manager page, decide whether to integrate the BI platform
with an existing Introscope Enterprise Manager server.
Note
To use CA Wily Introscope Enterprise Manager, SMD Agent must be installed.
Option Description
Configure connectivity
to Introscope
Enterprise Manager
The BI platform can integrate with your organization's deployment of CA Wily Introscope Enter­
prise Manager.
If you select this option, enter the hostname and port number for the Introscope Enterprise Man­
ager server on the following Configure Connectivity to Introscope Enterprise Manager page.
Do not configure
connectivity to
Introscope Enterprise
Manager
You can configure Introscope Enterprise Manager in the CMC Placeholders screen later after the
installation program is complete.
The Start Installation page appears. Start the installation.
Proceed to While the installation program runs.
5.3.1.3 Web Tier installation
The web tier contains web applications such as BI launch pad and the Central Management Console (CMC). Use
the Web Tier installation option to install BI platform web applications onto your web application server.
Note
? During the web tier installation, you are prompted to logon to an existing Central Management Server
(CMS) as the BI platform Administrator. You must have a CMS running remotely or on the same machine
to perform the web tier installation.
? If you plan to use a web tier with third-party authentication, or integration for Enterprise Resource Planning
(ERP) systems such as Siebel Enterprise, JD Edwards EnterpriseOne, or Oracle E-Business Suite, you must
perform a Custom / Expand installation and select the components you need.
For example, to perform a web tier installation with ERP support, select the following components from the
Custom / Expand feature list:
? Instances WebTier Java Web Applications
Business Intelligence Platform Installation Guide for Windows
Installation © 2015 SAP SE or an SAP affiliate company. All rights reserved. 39
? Instances WebTier Tomcat 7.0 (if you do not already have a web application server)
? Instances Database Access (select the name of the ERP system)
If you do not have a web application server to use with the BI platform, the installation program can install and
configure a Tomcat web application server for you. It is recommended that you evaluate your requirements
against information from your web application server vendor to determine which supported web application
server would best suit your organization's needs.
If you already have a supported web application server installed, you can deselect the option to install Tomcat,
and only install the Java web applications. This option will not deploy the web applications to your web application
server. To deploy web applications to a web application server after a web tier installation, use the WDeploy tool.
For more information on using the WDeploy tool, see the SAP BusinessObjects Business Intelligence Platform Web
Application Deployment Guide.
The following steps are performed for Web Tier installations of the BI platform.
1. On the Select Features page, select the features to install under Instances WebTier .
Option Description
Java Web Applications Installs the BI platform web applications to the machine.
Tomcat 7.0 Installs and configures the bundled Apache Tomcat web application server.
2. If you selected the Tomcat 7.0 feature, review the default port values on the Configure Tomcat page.
Option Description
Connection port The port on which the web application server listens for incoming connections from web clients.
Shutdown port The port that allows the web application to be shut down remotely.
Redirect port The port that enables redirects to secure web connections.
3. On the Existing CMS Deployment Information page, logon to an existing CMS.
4. On the Select Connectivity to Introscope Enterprise Manager page, decide whether to integrate the BI platform
with an existing Introscope Enterprise Manager server.
Note
To use CA Wily Introscope Enterprise Manager, SMD Agent must be installed.
? For information on installing SMD Agent before installing the BI platform, see Support for SAP Solution
Manager Diagnostics (SMD) [page 23].
? For information on installing SMD Agent after installing the BI platform, see To configure SMD Agent
post installation [page 55].
Option Description
Configure connectivity
to Introscope
Enterprise Manager
The BI platform can integrate with your organization's deployment of CA Wily Introscope Enter­
prise Manager.
If you select this option, enter the hostname and port number for the Introscope Enterprise Man­
ager server on the following Configure Connectivity to Introscope Enterprise Manager page.
40 © 2015 SAP SE or an SAP affiliate company. All rights reserved.
Business Intelligence Platform Installation Guide for Windows
Installation
Option Description
Do not configure
connectivity to
Introscope Enterprise
Manager
You can configure Introscope Enterprise Manager in the CMC Placeholders screen later after the
installation program is complete.
The Start Installation page appears. Start the installation.
Proceed to While the installation program runs.
5.3.2 While the installation program runs
The progress bar illustrates the progress of the installation as a whole.
Note
When performing an Expand installation, the existing CMS may be restarted automatically as a part of the
installation process.
5.3.3 When installation is complete
When the installation is complete, review the information in the Post Installation Steps screen. If you are not using
the bundled Tomcat web application server, you must deploy web applications with the WDeploy web application
deployment tool.
5.3.3.1 Reboot suppression
If a file is locked during the installation, you may be prompted to restart the server after the installation. You can
choose to reboot immediately, or later. However, if you choose to suppress the reboot, the system may be in an
unsupported state until the system is rebooted.
5.4 To run a silent installation
Every option in the installation wizard can be read from a response file invoked at the command-line. This type of
installation is called a silent install.
A response file is a text file containing installation option parameters in key-value format. When using a response
file to give installation options, the installation program is run from the command-line with the -r
parameter, where is the name of the response file.
Business Intelligence Platform Installation Guide for Windows
Installation © 2015 SAP SE or an SAP affiliate company. All rights reserved. 41
The response file contains multiple installation options, with one installation option per line. In the following
example, the response file is given as a parameter:
setup.exe [...] -r C:\response.ini [...]
For example, the installation option cmsport=6401 can be given on a line in the response file to set the CMS port
number to 6401, instead of the default value of 6400.
In the following example of giving the cmsport parameter in a response file, ellipses ([...]) are shown to
indicate where other installation options would normally be present:
[...]
cmsport=6401
[...]
Note
The installation program returns the cursor to the command-line prompt when it starts. To run the installation
program from a script, or to force the installation program to wait to complete before returning to the
command-line, use the Windows Command Interpreter start /wait command to invoke setup.exe.
For example:
start /wait setup.exe []
For a complete list of installation options, see Installation option parameters [page 44]. For an example of a
response file, see Response file example [page 51].
5.4.1 Command-line switch parameters
The following table lists the switch parameters that can be given to the installation program on the command-line
to perform a silent installation.
Table 5: Installation program command-line switch parameters
Switch parameter Description Example
-w Writes a response file to ,
containing the options selected from the in­
stallation wizard.
setup.exe -w "C:
\response.ini"
-r Reads installation options from a response
file named .
setup.exe -r "C:
\response.ini"
5.4.1.1 To use a response file
To use a response file, run the installation program with the -r Software Downloads. On the Find your software tab,
Business Intelligence Platform Installation Guide for Windows
Installing BI Platform Client Tools © 2015 SAP SE or an SAP affiliate company. All rights reserved. 69
under the A–Z Index, click Support Packages and Patches. For more information on installing Support Packages
and Patches, see the SAP BusinessObjects BI Suite Update Guides.
7.3 Client Tools installation prerequisites
Before installing or making changes to a Client Tools installation, ensure that:
? Any existing BI Suite client tools and products are closed before running the installation program. If any client
tool fails to start after the installation, running the installation program in repair mode should correct the
issue.
? All BI platform servers on the machine are stopped except the CMS and File Repository Servers (FRS).
? The account being used has Administrator privileges. The installation requires that the account being used is
a member of the Windows Administrators group, and that the default privileges assigned to the
Administrators group have not been modified.
? You are using a minimum screen resolution of 1024 × 768 pixels. Using Microsoft Remote Desktop
Connection to run the installation program is supported, as long as a minimum screen resolution of 1024 ×
768 pixels is used.
7.4 To run an interactive installation of Client Tools
Note
The installation log file is saved to \InstallData\logs\
\setupengine.log.
1. Locate and run setup.exe.
2. Select the setup language.
The language setting is used by the installation program to display information to you in the language of your
choice. If you select a non-English language, the corresponding language pack is automatically installed on
the server.
Note
The installation program will automatically run in the same language as your operating system. The
language used by the installation program will determine the names used for Windows components
configured by the installation program, such as Windows service names and Start menu shortcuts. These
names cannot be changed later and are not affected by language settings once the installation is complete.
3. On the Check Prerequisites page, review the results and decide whether to continue with the installation, or
abort and correct any unmet requirements.
The installation program checks for required components and conditions. If a dependency prerequisite
condition is critical, the installation program will not allow the installation to proceed. If the missing or
70 © 2015 SAP SE or an SAP affiliate company. All rights reserved.
Business Intelligence Platform Installation Guide for Windows
Installing BI Platform Client Tools
unsupported component is optional, you have the option to either continue with the installation or stop and
correct the condition.
4. Review the installation welcome page.
5. On the License Agreement page, review the agreement and select I accept the License Agreement.
6. On the Select Language Packs page, select additional languages to install from the list.
The language currently being used by the operating system is selected automatically. English language
support cannot be deselected because it is used if a problem is detected with an individual language.
7. On the Configure Destination Folder page, review the destination folder shown.
This is the folder into which the installation program will install the BI platform Client Tools. If the folder does
not exist, the installation program creates it.
Note
? The use of Unicode characters in the destination folder is not supported.
? Ensure that the destination folder is not set to the same folder in which the installation program has
been extracted.
? If you have already installed SAP BusinessObjects products, the Destination Folder Information field is
not editable, and the path to the existing folder is displayed.
8. On the Select Features page, select the features to install from the list.
Features are grouped under the following headings:
? Client components
Desktop client applications:
? Web Intelligence Rich Client
? Business View Manager
? Report Conversion Tool
? Universe Design Tool
? Query as a Web Service
? Information Design Tool
? Translation Management Tool
? Data Federation Administration Tool
? Widgets
? Developer Components
? SAP BusinessObjects BI platform Java SDK
? SAP BusinessObjects BI platform Web Services SDK
? SAP BusinessObjects BI platform .NET SDK
? Crystal Reports Java SDK
? SAP BusinessObjects Semantic Layer Java SDK
? Semantic Layer SDK
? Semantic Layer SDK Samples
? Data Access and Security
The individual drivers listed under this heading allow client tools to access supported reporting database
systems, or third-party authentication for Enterprise Resource Planning (ERP) systems.
The Start Installation page appears. Start the installation.
Business Intelligence Platform Installation Guide for Windows
Installing BI Platform Client Tools © 2015 SAP SE or an SAP affiliate company. All rights reserved. 71
7.5 To run a silent installation of Client Tools
Every option in the installation wizard can be given from the command-line. This type of installation is known as a
silent install.
Installation options can be given directly on the command-line as a parameter, or can be stored in a response file.
? Giving installation options on the command-line
Installation options can be passed directly to the setup program from the command-line as a parameter. For
example, the installation option CMSPort=6401 can be given on the command-line as a parameter when
running the installation program to set the CMS port number to 6401, instead of the default value of 6400.
In the following example of giving the CMSPort parameter on the command-line, ellipses ([...]) are shown
to indicate where other installation options would normally be present:
setup.exe [...] CMSPort=6401 [...]
? Giving installation options in a response file
Installation options can be stored in a response file, which is a text file containing installation option
parameters in key-value format. When using a response file to give installation options, the installation
program is run from the command-line with the -r parameter, where
is the name of the response file.
The response file contains multiple installation options, with one installation option per line. In the following
example, the response file is given as a parameter:
setup.exe [...] -r C:\response.ini [...]
For example, the installation option CMSPort=6401 can be given on a line in the response file to set the CMS
port number to 6401, instead of the default value of 6400.
In the following example of giving the CMSPort parameter in a response file, ellipses ([...]) are shown to
indicate where other installation options would normally be present:
[...]
CMSPort=6401
[...]
Note
The installation program returns the cursor to the command-line prompt when it starts. To run the installation
program from a script, or to force the installation program to wait to complete before returning to the
command-line, use the Windows Command Interpreter start /wait command to invoke setup.exe.
For example:
start /wait setup.exe []
For a complete list of installation options, seeInstallation option parameters for Client Tools [page 74]. For an
example of a response file, see Response file example [page 51].
72 © 2015 SAP SE or an SAP affiliate company. All rights reserved.
Business Intelligence Platform Installation Guide for Windows
Installing BI Platform Client Tools
7.5.1 Command-line silent install of Client Tools
You can install Client Tools with one command by giving parameters on the command-line. This is referred to as a
silent installation. When parameters are supplied on the command-line, the installation will not prompt for
information.
7.5.1.1 To use a response file
To use a response file, run the installation program with the -r