XI4 Install Unix En

Business Intelligence Platform Installation Guide■ SAP BusinessObjects Business Intelligence platform 4.0 SP2

2011-10-11

© 2011 SAP AG. All rights reserved.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAPBusinessObjects Explorer, StreamWork, and other SAP products and services mentioned herein as

Copyright

well as their respective logos are trademarks or registered trademarks of SAP AG in Germany andother countries.Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports,Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and servicesmentioned herein as well as their respective logos are trademarks or registered trademarks of BusinessObjects Software Ltd. Business Objects is an SAP company.Sybase and Adaptive Server, iAnywhere,Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well astheir respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAPcompany. All other product and service names mentioned are the trademarks of their respectivecompanies. Data contained in this document serves informational purposes only. National productspecifications may vary.These materials are subject to change without notice. These materials areprovided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only,without representation or warranty of any kind, and SAP Group shall not be liable for errors oromissions with respect to the materials. The only warranties for SAP Group products and servicesare those that are set forth in the express warranty statements accompanying such products andservices, if any. Nothing herein should be construed as constituting an additional warranty.

2011-10-11

Contents

Introduction.............................................................................................................................5Chapter 1

About this Document...............................................................................................................51.1Document History....................................................................................................................51.1.1Purpose...................................................................................................................................61.2Integration................................................................................................................................61.3Constraints..............................................................................................................................61.4Information Available in SAP Service Marketplace....................................................................71.5

Planning..................................................................................................................................9Chapter 2

New features and components...............................................................................................102.1Enterprise Resource Planning (ERP) integration.....................................................................112.1.1Upgrade support....................................................................................................................122.2Object types and feature requirements..................................................................................122.2.1Product co-existence.............................................................................................................132.2.2Web application servers.........................................................................................................142.3Web servers..........................................................................................................................152.4Database servers...................................................................................................................152.5

Preparation............................................................................................................................17Chapter 3

System requirements.............................................................................................................183.1Account permissions..............................................................................................................183.1.1Network permissions.............................................................................................................203.1.2Preparing the CMS system or Auditing Data Store database.................................................213.2Extra requirements for IBM DB2............................................................................................233.2.1Extra requirements for Sybase...............................................................................................253.2.2Set ulimit to unlimited.............................................................................................................253.3SAP support..........................................................................................................................253.4Support for SAP System Landscape Directory (SLD)............................................................253.4.1Support for SAP Solution Manager Diagnostics (SMD).........................................................273.4.2Support for CA Wily Introscope.............................................................................................283.4.3Final checklist.........................................................................................................................283.5

2011-10-113

Installation.............................................................................................................................31Chapter 4

To run an interactive installation.............................................................................................314.1To select an install type..........................................................................................................334.1.1While the installation program runs.........................................................................................444.1.2When installation is complete.................................................................................................444.1.3To run a silent installation.......................................................................................................454.2Command-line switch parameters..........................................................................................464.2.1Installation option parameters.................................................................................................484.2.2

Post-Installation....................................................................................................................61Chapter 5

Launching the CMC...............................................................................................................615.1Troubleshooting login issues..................................................................................................615.2Creating additional Adaptive Processing Servers...................................................................625.3Deploying web applications....................................................................................................635.4SAP support..........................................................................................................................635.5To configure System Landscape Directory (SLD) Data Supplier (DS) post installation...........635.5.1To configure SMD Agent post installation..............................................................................645.5.2To configure CA Wily Introscope Agent post installation........................................................645.5.3Third-party ERP integration.....................................................................................................655.6To enable Siebel Enterprise integration..................................................................................655.6.1To enable JD Edwards EnterpriseOne integration...................................................................665.6.2To enable Oracle E-Business Suite (EBS) integration.............................................................665.6.3Post-install diagnostic checks.................................................................................................675.7Making changes to SAP BusinessObjects Business Intelligence platform..............................685.8To modify SAP BusinessObjects Business Intelligence platform............................................685.8.1To repair SAP BusinessObjects Business Intelligence platform..............................................695.8.2To remove SAP BusinessObjects Business Intelligence platform...........................................695.8.3When the administrator account password is lost..................................................................705.9To reset the SAP BusinessObjects Business Intelligence platform administrator accountpassword...............................................................................................................................71

5.9.1

More Information...................................................................................................................73Appendix A

Index 75

2011-10-114

Contents

Introduction

This document guides you through the installation of SAP BusinessObjects Business Intelligenceplatform.

1.1 About this Document

The following documentation provides administrators with information, procedures, and options for theinstallation, removal, and modification of an SAP BusinessObjects Business Intelligence platform server.Two versions of this guide exist:• SAP BusinessObjects Business Intelligence Platform Installation Guide for Unix: for use with Unix

or Linux operating systems (this document).

• SAP BusinessObjects Business Intelligence Platform Installation Guide for Windows: for use withMicrosoft Windows operating systems.

1.1.1 Document History

The following table provides an overview of important document changes.

2011-10-115

Introduction

DescriptionDateVersion

First release of this document.30, November20110

SAP BusinessOb-jects 4.0

The HP operating system is no longer supported, so this topicwas removed: "Installing SAP BusinessObjects Business Intelli-gence platform on an HPUX 64-bit system". References to HPcommands were removed from the section To enable OracleE-Business Suite (EBS) integration .

27 May, 2011SAP BusinessOb-jects 4.0 SP2

1.2 Purpose

This document is intended for system administrators installing SAP BusinessObjects Business Intelligenceplatform. For the latest information, patches, and other information, visit the SAP BusinessObjectssupport site: service.sap.com/bosap-support.

1.3 Integration

SAP BusinessObjects Business Intelligence platform is a suite of enterprise-level business intelligenceanalysis and reporting systems.

The suite will integrate into your existing network, database, authentication, security, and operatingsystems. For an overview of the technologies and architecture used in SAP BusinessObjects BusinessIntelligence platform, and how they can fit into your organization's existing infrastructure, read the SAPBusinessObjects Business Intelligence Platform Planning Guide.

1.4 Constraints

This guide does not describe how to set up a supported host operating system, database, webapplication, or web server. If you are planning to use a dedicated database, web application, or webserver, it must be installed and functioning before attempting to install SAP BusinessObjects BusinessIntelligence platform.

2011-10-116

Introduction

https://service.sap.com/bosap-support

1.5 Information Available in SAP Service Marketplace

Information on the following areas is available in the SAP Service Marketplace.

Documentation

TitleInternet AddressDescription

SAP BusinessOb-jects Business Intelli-gence Platform Mas-ter Guide

service.sap.com/bosap-supportOverview of SAP BusinessObjectsBusiness Intelligence platform documen-tation.

SAP BusinessOb-jects Business Intelli-gence PlatformWhat's New Guide

service.sap.com/bosap-supportOverview of new features in SAP Busi-nessObjects Business Intelligenceplatform.

SAP BusinessOb-jects Business Intelli-gence Platform Up-grade Guide

service.sap.com/bosap-supportHow to upgrade an existing installationto the most current version of SAPBusinessObjects Business Intelligenceplatform.

SAP BusinessOb-jects Business Intelli-gence Platform WebApplication Deploy-ment Guide

service.sap.com/bosap-supportDetailed instructions for deploying webapplications to supported web applica-tion servers.

SAP BusinessOb-jects Business Intelli-gence Platform Ad-ministrator Guide

service.sap.com/bosap-supportAdministrative documentation for settingup and maintaining an SAP BusinessOb-jects Business Intelligence platformserver.

For a detailed list of specific platform, database, web application server, web server, and other systemssupported by SAP BusinessObjects Business Intelligence platform, consult the Supported PlatformsGuide, available at http://service.sap.com/bosap-support.

2011-10-117

Introduction

http://service.sap.com/bosap-support/

2011-10-118

Introduction

Planning

SAP BusinessObjects Business Intelligence platform can be installed on Windows, Unix, or Linuxplatforms, with a combination of supported web servers, web application servers, database servers,and web technologies.

You decide how the components that make up SAP BusinessObjects Business Intelligence platformwill be deployed. A small development deployment might use the setup program's default options toinstall SAP BusinessObjects Business Intelligence platform, a database, and a web application serveron a single computer system. A larger scale deployment might install individual server components ondedicated systems to host individual server functions over a network.

For example: a dedicated host for a web application server; a dedicated host for the SAP BusinessObjectsBusiness Intelligence platform core system; and a dedicated host for the database.

Before installing:• Review your systems to ensure they meet the basic requirements.

For a detailed list of supported environments and hardware requirements, consult the SupportedPlatforms Guide available on the SAP BusinessObjects Business Intelligence platform support siteat service.sap.com/bosap-support. This document includes specific version and patch-levelrequirements for web application servers, web browsers, databases, and operating systems.

For more information on how to plan your installation, see the “Architecture” section of the SAPBusinessObjects Business Intelligence Platform Planning Guide. For more information on thedocumentation available, see the SAP BusinessObjects Business Intelligence platform Master Guide.Both guides are available on the SAP BusinessObjects Business Intelligence platform support siteat service.sap.com/bosap-support.

• When setting up a deployment comprised of two or more hosts, ensure that the hosts cancommunicate with each other across the network.

• Decide whether to use the included DB2 database server.

If you do not have a database server in place for use with SAP BusinessObjects Business Intelligenceplatform, the installation program can install and configure one for you. It is recommended that youevaluate your requirements against information from your database server vendor to determinewhich supported database would best suit your organization's requirements.

Note:An existing database must have database user accounts with the appropriate database privilegesready, and the appropriate drivers must be installed and verified as working. The setup programattempts to connect to, and initialize, the database as a part of the installation process.

The installation program will only install a database on the local host. It cannot install across anetwork.

2011-10-119

Planning



• Decide whether to use the included Tomcat web application server.

If you do not have a web application server system to serve SAP BusinessObjects BusinessIntelligence 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 applicationserver vendor to determine which supported database would best suit your organization'srequirements. To use any other supported web application server, it must be installed, configured,enabled, and accessible before you install SAP BusinessObjects Business Intelligence platform.

The installation program will only install Tomcat to the local machine. It cannot install to remotesystems across a network.

• Decide which installation option to use.

The installation program offers three installation options:1. "Full": install all available components, including a bundled web application server and database

server.2. "Custom / Expand": select and install all or any of the available components.3. "Web Tier": install web applications on a dedicated web application server. You can use an

previously installed web application server, or the bundled Tomcat web application server.

• Determine the location of the components to be installed.

This includes the specific subnet, machines, database, security, or cluster systems to be used.

2.1 New features and components

The following components are now integrated into the SAP BusinessObjects Business Intelligenceplatform 4.0 installation program, and no longer require a separate installation:• Enterprise Resource Planning

The installation program now includes support for ERP integration (SAP Business Warehouse (BW),Siebel Enterprise, PeopleSoft Enterprise, JD Edwards EnterpriseOne) and portals (MicrosoftSharePoint, WebLogic Portal, WebSphere Portal, Oracle Portal Server).

For more information, see Enterprise Resource Planning (ERP) integration.

• Lifecycle Management

The Lifecycle management console now included in SAP BusinessObjects Business Intelligenceplatform and enables you to move Business Intelligence (BI) resources from one system to anotherwithout affecting resource dependencies. It also enables you to manage different versions of BIresources, manage dependencies of BI resources, and roll back a promoted resource to restore thedestination system to an earlier state.

The installation program can install and configure the Subversion version control system, or use anexisting installation of Subversion or ClearCase.

Lifecycle management console replaces Upgrade Management Tool for promotion workflows.

2011-10-1110

Planning

• SAP Solution Manager support

The installation program can now integrate SAP BusinessObjects Business Intelligence platforminto the SAP Solution Manager infrastructure. This allows system inventory and performanceinstrumentation tools like SAP System Landscape Directory (SLD), SAP Solution Manager Diagnostics(SMD), and CA Wily Introscope, and IBM Tivoli.

• Data Federation

Data federation enables multi-source universes by distributing queries across disparate data sources,and lets you federate data through a single data foundation.

• Mobile server support

Mobile server support allows your users to remotely access business intelligence (BI) reports, metrics,and real-time data from a wireless device.

• SAP BusinessObjects Dashboard Design (formerly Xcelsius) server support

SAP BusinessObjects Dashboard Design is a tool for data visualization and the creation of dynamic,interactive dashboards.

• Language support

Supported languages are now only installed by the installation program.

Note:Carefully consider which languages need to be installed for your organization before installing them.To add or remove language support later requires that you remove and re-install SAP BusinessObjectsBusiness Intelligence platform.

• SAP BW publishing servers

The ability to publish reports to SAP BW no longer requires a separate installation.

• WDeploy command-line and GUI tools

The WDeploy tool is now installed with both command-line and graphical user interface (GUI) support.

Note:The SAP BusinessObjects Business Intelligence platform installation program no longer includes ClientTool components. To install Client Tools, use the dedicated SAP BusinessObjects Business IntelligencePlatform Client Tools installation program.

2.1.1 Enterprise Resource Planning (ERP) integration

An Enterprise Resource Planning (ERP) application supports the essential functions of an organization'sprocesses by collecting real-time information related to day-to-day operations. SAP BusinessObjectsBusiness Intelligence platform supports single sign-on and reporting from the following ERP systems:• SAP ERP and Business Warehouse (BW)

2011-10-1111

Planning

Note:SAP GUI must be installed before using OLAP Data Access (ODA), SAP BusinessObjects Analysis(formerly Voyager), or BW connections.

• Siebel Enterprise• Oracle E-Business Suite• JD Edwards EnterpriseOne• PeopleSoft Enterprise

Note:

• SAP ERP and BW support is installed by default. Use the Custom / Expand installation option todeselect SAP integration support if you do not want support for SAP ERP or BW.

• Support for Siebel Enterprise, Oracle E-Business Suite, JD Edwards EnterpriseOne, or PeopleSoftis not installed by default. Use the "Custom / Expand" installation option to select and install integrationfor non-SAP ERP systems.

For detailed information on the specific versions supported by SAP BusinessObjects Business Intelligenceplatform, consult the Supported Platforms Guide, available at service.sap.com/bosap-support.

To configure ERP integration, see the SAP BusinessObjects Business Intelligence Platform AdministratorGuide.

2.2 Upgrade support

To upgrade to SAP BusinessObjects Business Intelligence platform 4.0, you must install SAPBusinessObjects Business Intelligence platform 4.0, then migrate settings and content using the Upgrademanagement tool.

For information on how to upgrade from a previous version, see the SAP BusinessObjects BusinessIntelligence Platform Upgrade Guide.

When the installation program detects a previously installed version of SAP BusinessObjects BusinessIntelligence platform, it presents the option to perform a side-by-side installation, which installs the newversion, leaving the previously installed version intact. A system can host more than one version ofSAP BusinessObjects Business Intelligence platform, although system performance may be degradedif both are running at once.

2.2.1 Object types and feature requirements

2011-10-1112

Planning

https://service.sap.com/bosap-support/

Ensure that the machine on which you run the upgrade management tool has the SAP BusinessObjectsBusiness Intelligence platform features that correspond to the object types that you want to upgrade.The following table lists the available object types and the features associated with them.

Remember:If a feature is not installed on the machine, the corresponding object type will not be upgraded.

Required featureObject type

BI workspace ServicesBI workspaces (Dashboards)

noneCrystal reports

noneDashboard Design and Presentation Design(Xcelsius) data

noneExplorer

Connectivity Processing ServicesWeb Intelligence documents and publications

Platform Processing Services or PlatformScheduling Services

Lifecycle management console (LifeCycle Manag-er) data

CMS plugin for MobileMobile

Connectivity Processing ServicesUniverses, connections

noneAnalysis, edition for OLAP workspaces

Connectivity Processing ServicesWeb service query tool (QaaWS)

2.2.2 Product co-existence

Several SAP BusinessObjects Business Intelligence platform products can exist on the same host.

Note:All SAP BusinessObjects Business Intelligence platform products installed at your organization musthave the same patch level. For example, if your organization upgrades SAP BusinessObjects BusinessIntelligence platform server products to a service pack or fix pack, all add-ons, Client Tools, andstand-alone products must also be upgraded. Similarly, if one product is downgraded, all other productsshould also be downgraded.

To install add-on products, ensure that any required server components are present. A dependencycheck that identifies missing or outdated components is run by SAP BusinessObjects installationprograms. If a dependency requirement is not met, the installation program identifies and suggestsways to meet the requirement. An add-on product which requires server components will not installuntil the appropriate server components are available.

2011-10-1113

Planning

Mid-market server products, such as SAP Crystal Reports Server OEM Edition, cannot be installed onthe same host as SAP BusinessObjects Business Intelligence platform XI 4.0.

When installing SAP BusinessObjects Business Intelligence platform products, the user has the optionto select a custom destination parent folder, into which the software is installed. Subsequent installationsof other SAP BusinessObjects Business Intelligence platform products uses the same folder given forthe original installation, and cannot be changed.

If an SAP BusinessObjects Business Intelligence platform product is removed from a host, any remainingSAP BusinessObjects Business Intelligence platform product installation will be unaffected. Anycomponent shared by the both installations will remain, and will only be removed when the last productthat requires the shared component is removed.

Add-on products with dependencies on other products should be removed before the product on whichthey depend.

2.3 Web application servers

You can integrate SAP BusinessObjects Business Intelligence platform with a Java web applicationserver.

If you do not have a web application server in place for use with SAP BusinessObjects BusinessIntelligence platform, the installation program can install and configure a Tomcat 6.0 web applicationserver for you. It is recommended that you evaluate your requirements against information from yourweb application server vendor to determine which supported web application server would best suityour organization's requirements.

Note:When configuring a production environment, it is recommended that the web application server is hostedon a separate system. Running SAP BusinessObjects Business Intelligence platform and a webapplication server on the same host in a production environment may decrease performance.

If Tomcat 6.0 does not meet your organization's requirements, the following web application serversare supported:

• Tomcat (5.5)• JBoss• Oracle Application Server• SAP NetWeaver Application Server• Sun Java System Application Server• WebLogic• WebSphere

For a detailed list of supported web application servers, versions, and patch levels, consult the SupportedPlatforms Guide available at http://service.sap.com/bosap-support.

2011-10-1114

Planning


Note:

• To use a supported web application server other than the bundled version of Tomcat 6.0, it must berunning and accessible before you attempt to install.

• The "Web Tier" option installs only web applications to a supported Java web application server.This is useful for deploying web applications to nodes in a web application server cluster.

2.4 Web servers

You can use a dedicated web server to host static web content, such as images, HTML, or multimediafiles. This is known as a split deployment. Split deployments increase the performance of the webapplication server as it no longer needs to serve static content, and returns dynamic content only whenrequired.

The WDeploy tool is able to separate static dynamic content for deployment to separate web and webapplication servers. For more information on split deployments, see the SAP BusinessObjects BusinessIntelligence Platform Web Application Deployment Guide.

The web and web application servers can run on the same machine, or on separate machines acrossa network. SAP BusinessObjects Business Intelligence platform supports the following combinationsof web servers and web application servers:

• Apache web server with Tomcat• Apache web server with WebLogic• IBM IHS web server with WebSphere• Sun Java System Web server with Sun Java System Application Server

For a detailed list of supported web servers, versions, and patch levels, consult the Supported PlatformsGuide available at http://service.sap.com/bosap-support.

2.5 Database servers

If you do not have a database server in place for use with SAP BusinessObjects Business Intelligenceplatform, the installation program can install and configure one for you. It is recommended that youevaluate your requirements against information from your database server vendor to determine whichsupported database would best suit your organization's requirements.

IBM DB2 is the default database server. Any other database server must be running and accessiblewhen you run the installation program. SAP BusinessObjects Business Intelligence platform alsosupports the following database servers:• MySQL• Oracle

2011-10-1115

Planning


• MaxDB• Sybase

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 SupportedPlatforms Guide, available at http://service.sap.com/bosap-support.

2011-10-1116

Planning


Preparation

This section details how to prepare for the installation of SAP BusinessObjects Business Intelligenceplatform.

Process Flow1. Ensure that sufficient disk space is available. Allow for both the operating system and the software

to grow over time as patches or new components become available.2. Gather the installation media or download the latest release and any patches or service packs from

the support portal at http://service.sap.com/bosap-support.• To download SAPCAR, go to http://service.sap.corp/bosap-support > Software Downloads

> Support Packages and Patches > Browse our Download Catalog > SAP TechnologyComponents > SAPCAR.

• To download SAP HOST AGENT, go to http://service.sap.corp/bosap-support > SoftwareDownloads > Support Packages and Patches > Browse our Download Catalog > SAPTechnology Components > SAP HOST AGENT

3. If you plan to use SAP System Landscape Directory (SLD), ensure that the SAP Host Agent isinstalled before installing SAP BusinessObjects Business Intelligence platform. For more informationon SLD, see “Registration of SAP BusinessObjects Business Intelligence platform in the SystemLandscape” in the SAP BusinessObjects Business Intelligence Platform Administrator Guide. Forinformation on SAP Host Agent, see To enable SAP System Landscape Directory (SLD) support.

4. Decide which options you will change select the installation process. In most cases, you can acceptthe default values. More advanced installations require that you plan the installation process. Theinstallation program prompts for the following information:• License information (the name of the user and company associated with your SAP

BusinessObjects Business Intelligence platform license).• Web application server configuration, including type, connection, and authentication details.• Database server configuration, including type, connection, and authentication details.• CMS system and Auditing Data Store configuration information, including type, connection, and

authentication details.• Folder where SAP BusinessObjects Business Intelligence platform will be installed.• Central Management Console (CMC) administrator account password and cluster key.• CMS port number to receive incoming connections.• Server Intelligence Agent (SIA) name.• Server Intelligence Agent (SIA) port number for incoming connections.• SAP Solution Manager Diagnostics (SMD) configuration.• CA Wily Introscope Enterprise Manager configuration.• Subversion or ClearCase version control system configuration to store configuration files.• Lifecycle management (LCM) configuration.

2011-10-1117

Preparation

http://service.sap.com/bosap-support

• Installation type and components ("Full", "Custom / Expand", "Web Tier").

3.1 System requirements

Use the following guidelines when you install SAP Crystal Server:• Ensure that the operating system is supported. Only 64-bit operating systems are supported.• 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 gigabytesavailable for temporary files and web applications.

• If you have previously installed any SAP BusinessObjects products, the installation program usesthe existing directory.

For a detailed list of supported operating systems and hardware requirements, consult the SupportedPlatforms documentation available at http://service.sap.com/bosap-support.

3.1.1 Account permissions

To install SAP BusinessObjects Business Intelligence platform on a Unix or Linux host, a user musthave the following permissions:

2011-10-1118

Preparation


Required accessCategory

• Permission to read, write, and execute scripts in the destination directory.• For a system install, root access is required (the installation program creates

start-up run control scripts in /etc/rc that start or stop the servers when thehost machine is started or stopped).

Operating system

• Network connectivity through appropriate ports to all machines in the deploy-ment.

• Access to shared file system directories.• Appropriate network authentication privileges.

Network

• Permission for the SAP BusinessObjects user account to create, edit, anddrop tables.

• Permission for the SAP BusinessObjects user account to create stored proce-dures (required by the Central Management Server (CMS) system database).

Database

3.1.1.1 Additional Unix and Linux requirements

User accountCreate a user account and group under which the software's background processes can run. Use thisaccount to perform the installation and run the software. The account does not require root privileges.

LocaleBefore you install, set the installing account's environment to use a supported UTF-8 locale and ensurethat your console software supports UTF-8 character sets. To ensure that your operating system usesthe correct locale, set the LC_ALL and LANG environment variables to your preferred locale in yourlogin environment.

For example, the following bash shell commands set the locale to the United States English UTF-8locale:export LANG=en_US.utf8export LC_ALL=en_US.utf8

Tip:Type locale to check that all of the related locale environment variables (such as LC_MONETARY,LC_NUMERIC) were properly set by LC_ALL.

For a detailed list of supported Unix and Linux environments, see the Supported Platforms guideavailable on the SAP BusinessObjects Business Intelligence platform support site service.sap.com/bosap-support.

2011-10-1119

Preparation



See the section on International Deployments in the Administrator Guide for information on deployingto a multilingual audience.

CommandsIn order for the installation program to run correctly, the following utilities must be installed on yoursystem and available on the path:

touchreadpwd/bin/sh

sedhostnameexpruname

tailgrepchownawk

gzipdirnameidtar

pingwhichulimitstty

If one of them is not available on your system, install a version from your operating system vendorrather than a third-party vendor (such as the GNU project).

Note:The output from a GNU version of a utility can differ significantly from the version provided by youroperating system vendor. To prevent the installation program from encountering output in an unexpectedformat, ensure that no GNU utilities are used in the installing user account's environment.

InstallationsA new installation can be one of two different types.• User installation

The installed software is owned by the account that was used to run the installation program. Thisaccount must be used to start and stop the servers. Access to the root user account is not requiredto perform a user installation, and installation program will exit if it detects that it is being run as root.

• System installation

A system installation is a finished user installation with system startup and shutdown run controlscripts added. These scripts automatically start and stop SAP BusinessObjects Business Intelligenceplatform server functions as the operating system starts up or shuts down. The script to install therun control scripts must be run with root privileges after a user installation has completed.

3.1.2 Network permissions

When you install SAP BusinessObjects Business Intelligence platform across multiple machines, usethe following guidelines to ensure your network functions properly:

2011-10-1120

Preparation

• Servers running on all hosts must be able to communicate with each other.• Each machine must be able to communicate with the web application server, the Central Management

Server (CMS) host, all SIA hosts, and clients.• On any host with more than one network interface card (NIC), ensure that the primary NIC is routable

before running the installation program. If the primary NIC is not routable, you will have to re-configurethe networking settings after the installation. For information on how to bind to routable NICs, seethe “Managing and Configuring Servers” chapter of the SAP BusinessObjects Business Intelligenceplatform Administrator’Guide.

• Each machine must use a fixed hostname. Fully-qualified hostnames are supported.

Note:Ensure that deployment hostnames do not include any of the following characters: underscore (_),period (.), backslash (\), or forward-slash (/).

• If you run the installation program behind a firewall, see the “Securing SAP BusinessObjects BusinessIntelligence platform” chapter of the SAP BusinessObjects Business Intelligence platformAdministrator’s Guide.

3.1.2.1 Choosing a server location

When planning a distributed installation, consider the latency between servers. To maintain high CMSperformance, place your CMS on the same subnet as the CMS system and Auditing Data Store databaseservers.

The CMS can also be clustered, so that CMS server processes run on different host systems in thecluster. When creating a CMS cluster, ensure that each machine experiences the same network latencyto the CMS system or Auditing Data Store.

Consult the “Managing and Configuring Servers” section of the SAP BusinessObjects BusinessIntelligence Platform Administrator Guide for more information on clustering CMS server processes.

3.2 Preparing the CMS system or Auditing Data Store database

To use a database server other than the database bundled with SAP BusinessObjects BusinessIntelligence platform, the following tasks must be completed before installing SAP BusinessObjectsBusiness Intelligence 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 holdauditing information. Record the database, tablespace, and account information so you can enterthe details when prompted by the SAP BusinessObjects Business Intelligence platform installationprogram.

2011-10-1121

Preparation

Caution:If you have an existing SAP BusinessObjects Business Intelligence platform installation, you mustcreate 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 SAP BusinessObjects Business Intelligence platform. Contactyour 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 thatthe installation program can initialize the database. The table below shows which information is requiredfor supported databases:

Information required by installation programDatabase

• MySQL database name• Server hostname• Port number (default is 3306)• Account username• Account password• "Reset existing database" checkbox (recommended setting)

MySQL

• DB2 Alias name• Account username• Account password• "Reset existing database" checkbox (recommended setting)

IBM DB2

• Oracle TNSNAME connection identifier• Account username• Account password• "Reset existing database" checkbox (recommended setting)

Oracle

• Database name• Server hostname• Port number (default is 7210)• Account username• Account password• "Reset existing database" checkbox (recommended setting)

MaxDB

2011-10-1122

Preparation

Information required by installation programDatabase

• Service name

Note:

• The Sybase service name is a combination of the hostname and the portnumber, set by your database administrator in the sql.ini and interfacesfiles.

• SAP BusinessObjects Business Intelligence platform will connect to the defaultdatabase for the user you specify. The default is set by the database adminis-trator.

• Account username• Account password• "Reset existing database" checkbox (recommended setting)

Sybase

3.2.1 Extra requirements for IBM DB2

IBM DB2 has requirements that must be met before installing either SAP BusinessObjects BusinessIntelligence platform with the integrated IBM DB2 database, or your own IBM DB2 database.

If you plan to use the integrated IBM DB2 database bundled with SAP BusinessObjects BusinessIntelligence platform, or you plan to install and use your own IBM DB2 database server for use withSAP BusinessObjects Business Intelligence platform:• Ensure that the ID of the user account used to host the DB2 database meets the following

requirements from IBM. For more information an IBM's requirements for Unix or Linux systemshosting DB2, see DB2 users and groups (Linux and UNIX) in the Database Fundamentals sectionof the “DB2 Solution Information Center” at http://www.ibm.com/support.

• Must have a primary group other than guests, admins, users, or local• Can include only lowercase letters (a-z), numbers (0-9), or the underscore character (_)• Cannot be longer than eight characters• Cannot begin with IBM, SYS, SQL, or a number• Cannot be a DB2 reserved word (USERS, ADMINS, GUESTS, PUBLIC, or LOCAL), or an SQL

reserved word• Cannot use any user IDs with root privilege for the DB2 instance ID, DAS ID, or fenced ID.• Cannot include accented characters• If existing user IDs are specified instead of creating new user IDs, ensure that the user IDs:

• Are not locked• Do not have expired passwords

• The primary group of the user must meet the following requirements:

2011-10-1123

Preparation

http://www.ibm.com/support

• Cannot be one of guests, admins, users, or local• Cannot start with sql or ibm• Cannot start with a number• Must contain only lowercase letters (a-z), or numbers (0-9) .

If you plan to install and use an IBM DB2 database server for use with SAP BusinessObjects BusinessIntelligence platform:• Ensure that the DB2 database is created with the following settings:

Collating Sequence = "Identity"Codeset = "UTF-8"Territory = "XX"

Replace XX with the code that is appropriate for your location. Consult your DB2 documentation formore 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 SAP BusinessObjects Business Intelligenceplatform. If you do not create a user temporary table space, the SAP BusinessObjects BusinessIntelligence 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 spacesand 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 theauditing 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 bepartitioned.

3.2.1.1 Interprocess Communications (IPC) settings when using the bundled DB29.7 FP1 database

The database bundled with SAP BusinessObjects Business Intelligence platform is IBM DB2 9.7 FP1.If using the bundled database, prior to installation, ensure the following IPC parameters have been setwith a value equal to or greater than the following minimum values:

2011-10-1124

Preparation

http://www.ibm.com/developerworks/data/library/techarticle/0212wieser/0212wieser.html

http://www.ibm.com/developerworks/data/library/techarticle/0212wieser/0212wieser.html

Enforce minimum settingIPC kernel parameter

1 073 741 824 (64-bit kernel)kernel.shmmax (SHMMAX)

1 024kernel.sem (SEMMNI)

1 024kernel.msgmni (MSGMNI)

65 536kernel.msgmax (MSGMAX)

65 536kernel.msgmnb

3.2.2 Extra requirements for Sybase

If you are using Sybase for the CMS or auditing database:• Create a database with a page size of 8 KB. The Sybase database default page size is 2KB, which

is too small for the CMS system database to run efficiently. The page size is set up during thedatabase creation and cannot be changed after the database is created.

• Use a Unicode character set, such as UTF-8.

3.3 Set ulimit to unlimited

To successfully build and deploy SAP BusinessObjects Business Intelligence platform web applications,the host operating system or user account ulimit setting must be configured as unlimited.

Set the ulimit configuration with the ulimit command, or modify the system configuration file/etc/security/limits.conf. For more information about the ulimit setting, see thedocumentation included with your operating system.

3.4 SAP support

3.4.1 Support for SAP System Landscape Directory (SLD)

2011-10-1125

Preparation

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 landscapedirectory. Non-SAP software that supports SLD registers through an open API. The information gatheredon 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 hostSAP BusinessObjects Business Intelligence platform. SAP Host Agent may be installed and configuredbefore or after installing SAP BusinessObjects Business Intelligence platform.

3.4.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 throughinstalling SAP Host Agent.

SAP Host Agent may be installed and configured before or after installing SAP BusinessObjects BusinessIntelligence platform. For more information on SAP Host Agent, see “Registration of SAP BusinessObjectsBusiness Intelligence platform in the System Landscape” in the SAP BusinessObjects BusinessIntelligence Platform Administrator Guide.

Note:If you have installed SAP GUI, skip to step 4 below.

Prior to installing support for SAP System Landscape Directory (SLD) there must be an sapadm userwith root privileges.

The SAP_LocalAdmin group must also exist, and the sapadm user must be a member. The sapadmuser 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 ( http://service.sap.com/swdc).Log on with your SAP Service Marketplace ID and locate the version of SAPHOSTAGENT.SARappropriate 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

2011-10-1126

Preparation

http://service.sap.com/swdc

4. Locate the sldreg tool, which is usually located in the following folder:

/usr/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 tothe SLD server.

6. Enter the information requested.The sldreg tool creates a connect.key file that will automatically be used by sld-ds to pushinformation to SLD server.

If you have already installed SAP BusinessObjects Business Intelligence platform, restart all SIA nodesin the Central Configuration Manager (CCM) to register with the SLD.

3.4.2 Support for SAP Solution Manager Diagnostics (SMD)

SAP Solution Manager Diagnostics (SMD) monitors the performance of systems in the SAP SystemLandscape Directory (SLD). Problems can be identified, analyzed, and resolved with the informationgathered 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 transferredautomatically to your SAP System Landscape Directories (SLD). SAP customers can then easily identifywhich version of third-party product integration has been certified by SAP within their SAP systemenvironment. This service provides additional awareness for third-party products besides our onlinecatalogs for third-party products.

To use SMD, the SMD Agent must be installed. SMD Agent may be installed and configured before orafter installing SAP BusinessObjects Business Intelligence platform. During installation, the installationprogram 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

2011-10-1127

Preparation

in the Central Management Console (CMC) "Placeholders" screen. For more information, see Toconfigure SMD Agent post installation.

For more information on SMD, or to download SMD, visit the SAP Service Marketplace at: service.sap.com/swdc.

3.4.3 Support for CA Wily Introscope

CA Wily Introscope is included as a part of SAP Solution Manager Diagnostics (SMD). For fullinstrumentation, 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 installedand configured before or after installing SAP BusinessObjects Business Intelligence platform.

During installation, the installation program prompts for the hostname and port number of the IntroscopeAgent. 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, see To configure SMD Agent post installation.

3.5 Final checklist

Prior to installing SAP BusinessObjects Business Intelligence 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 theinstallation program from the current working directory).

• Have you verified appropriate network connectivity between all machines that will be part of yourdeployment?

• If you plan to use SAP Enterprise Resource Planning (ERP) integration for OLAP Data Access(ODA), SAP BusinessObjects Analysis (formerly Voyager), or SAP Business Warehouse (BW),ensure that SAP GUI is installed and configured before SAP BusinessObjects Business Intelligenceplatform.

• 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 SAP BusinessObjects Business

Intelligence platform host?

2011-10-1128

Preparation



• If you are using DB2 or Sybase, have you verified that your database was created with the correctsettings? (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 beeninstalled and configured. For more information, see Support for SAP System Landscape Directory(SLD).

• If you plan to use SAP Solution Manager Diagnostics (SMD), SMD Agent may been installed andconfigured before or after SAP BusinessObjects Business Intelligence platform. For more information,see Support for SAP Solution Manager Diagnostics (SMD).

On Unix, the TZ environment variable must be set for all SAP BusinessObjects Enterprise servers inorder to ensure the timestamps on future scheduled jobs are correct. If the TZ environment variable isnot set correctly then the time zone rules default to US-standard which may cause problems in otherlocations.

The TZ variable must be set in order to provide the start and end information about DST.

Example:

An example TZ setting is as follows: TZ='EST-10EDT-11,M10.1.0/02:00:00,M4.1.0/03:00:00'. Formore details on the format, please refer tohttp://www.opengroup.org/onlinepubs/007908799/xbd/envvar.html

Note:Setting the TZ variable conforms with POSIX 1003.1, section 8.1.1 For more details on the format,please refer to "http://www.opengroup.org/onlinepubs/007908799/xbd/envvar.html ".

2011-10-1129

Preparation

2011-10-1130

Preparation

Installation

There are two different methods of running the installation program for SAP BusinessObjects BusinessIntelligence platform:• Interactive installation

An interactive wizard prompts for all information related to the installation. Use this option to selectindividual installation options from a series of screens. This is the default installation method.

• Silent installation

Installation options are given on the command-line, which override the installation program's defaultvalues. The command-line can be used to give some or all installation options. When an installationoption is not given on the command-line, the installation program uses a default value.

Installation options can be given in a response file rather than directly on the command-line. Thistype of silent installation uses the -r command-line parameter to read installation options from theresponse file. Use this option if you want to install multiple machines with the same configuration.Installation options stored in a response file can be overridden by giving them on the command-line.

When the -q (quiet mode) switch is used, the installation program does not prompt for any userinput during the installation.

If the installation program encounters an unexpected condition, and is unable to continue, it will undoany work completed up to that point, and return the system to the state that it was in before the installationstarted.

4.1 To run an interactive installation

Load, mount, or download the SAP BusinessObjects Business Intelligence platform installation media.Ensure that LC_ALL has been set to a supported UTF-8 character set, such as en_US.utf8. Forexample:export LANG=en_US.utf8export LC_ALL=en_US.utf8

The installation log file will be saved to <BOE_INSTALL_DIR>/InstallData/logs/<DATE>/InstallDU<COMPONENT>.log.1. Change directory to the folder containing the setup.sh installation program.

2011-10-1131

Installation

Use the InstallDir=<DESTINATION_DIR> parameter to set the destination folder from thecommand line. For example, to install SAP BusinessObjects Business Intelligence platform into thefolder /opt/sap, use the command ./setup.sh InstallDir=/opt/sap.

2. Choose a language for the setup program to use during the installation process. The languagesetting is used by the installation program to display information to you in the language of yourchoice. If you select a non-English language, the corresponding language pack is automaticallyinstalled on the server.

Note:The installation program will automatically run in the same language as your operating system. Thelanguage used by the installation program will determine the names used for components configuredby the installation program. These names cannot be changed later and are not affected by languagesettings once the installation is complete.

3. Review the destination folder shown. This is the folder into which the installation program will installSAP BusinessObjects Business Intelligence platform. If the folder does not exist, the installationprogram creates it.

Note:

• The use of Unicode characters in the destination folder is not supported.• Ensure that the 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 programfrom the current working directory).

4. The installation program checks for required components and conditions. Review the results anddecide whether to continue with the installation, or abort and correct any unmet requirements.If a dependency prerequisite condition is critical, the installation program will not allow the installationto proceed. If the missing or unsupported component is optional, you have the option to eithercontinue with the installation or stop and correct the condition.

5. Review the installation welcome screen.6. Review and accept the license agreement.7. Enter the product keycode. The product keycode was given to you when you purchased SAP

BusinessObjects Business Intelligence platform. Store the keycode and registration information ina safe place in case you need to re-install.

8. To install support for a language, select it from the list.

Note:Carefully consider which languages need to be installed for your organization. To add or removelanguage support later requires that you remove and re-install SAP BusinessObjects BusinessIntelligence platform.

The language currently being used by the operating system is selected automatically. Englishlanguage support cannot be deselected because SAP BusinessObjects Business Intelligence platformfalls back to using English if a problem is detected with an individual language.

9. Select one of the following install type options:• User install

2011-10-1132

Installation

A user installation causes the installation program to install the software as a self-containedpackage within a directory, where the software must be started and stopped manually from thecommand-line.

• System install

A system installation causes the installation program to install start-up and shutdown scripts inthe run control (rc) folder of the operating system (/etc/rc or similar) so that the software willstart and stop automatically with the operating system.

Note:A system installation requires root user privileges.

The "Choose Install Type" screen appears.

4.1.1 To select an install type

SAP BusinessObjects Business Intelligence platform requires a database server and web applicationserver to function. If you do not have an existing database, the installation program can automaticallyinstall and configure an IBM DB2 database. If you do not have an existing web application server, theinstallation program can automatically install and configure a Tomcat web application server.

The "Choose Install Type" screen is used to select the installation component options.1. Select one of the following install type options:

• Full

Installs all required server components onto a single machine. Use this option to create asingle-host deployment, such as a pre-production development or test environment.

• Custom / Expand Install

Allows experienced users to select individual components. 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 components are deployed to a host.

• Web Tier

The web tier hosts web applications and serves content to users over the web. Use the WebTier installation option to install Java web applications onto a dedicated Java web applicationserver.

If you do not have a web application server in place for use with SAP BusinessObjects BusinessIntelligence platform, the installation program can install and configure a Tomcat web applicationserver for you. It is recommended that you evaluate your requirements against information fromyour web application server vendor to determine which supported web application server wouldbest suit your organization's needs.

2011-10-1133

Installation

If you already have a supported web application server installed, you can deselect the option toinstall Tomcat, and only install the Java web applications

2. Proceed to the next screen to start configuring the selected installation.

You may return to the install type options screen at any time later.

3. If you selected a "Full" installation, proceed to the following Full section.4. If you selected a "Custom / Expand" installation, proceed to the following Custom / Expand section.5. If you selected a "Web Tier" installation, proceed to the following Web Tier section.

4.1.1.1 Full installation

The following steps are performed for Full installations of SAP BusinessObjects Business Intelligenceplatform.1. A database is required to store Central Management Server (CMS) configuration and run-time

information. A second database is required for Auditing Data Store (ADS) information.If you do not have a database server in place for use with SAP BusinessObjects Business Intelligenceplatform, the installation program can install and configure one for you. It is recommended that youevaluate your requirements against information from your database server vendor to determinewhich supported database would best suit your organization's needs.To install the bundled database server, select Install and use the default database.

IBM DB2 will be installed and configured to store Central Management Server (CMS) and auditingdata.To use an existing supported database server, select Use an existing database server. Theinstallation program prompts for information on the database type and connection credentials forboth the CMS system and Auditing Data Store databases.

Note:An existing database must have user accounts with the appropriate privileges ready, and theappropriate drivers must be installed and verified as working. The installation program attempts toconnect to, and initialize, the database as a part of the installation process.

2. If you selected Use an existing database server:a. Select the database type to use for the CMS database.b. Select the database type to use for the Auditing database (Auditing Data Store).

If you do not want to use the auditing feature, select No Auditing Database.

3. A Java web application server is required to host SAP BusinessObjects Business Intelligence platformweb applications.

If you do not have a web application server in place for use with SAP BusinessObjects BusinessIntelligence platform, the installation program can install and configure a Tomcat web applicationserver for you. It is recommended that you evaluate your requirements against information from

2011-10-1134

Installation

your web application server vendor to determine which supported web application server would bestsuit your organization's needs.

Note:When configuring a production environment, it is recommended that the web application server ishosted on a separate system. Running SAP BusinessObjects Business Intelligence platform and aweb application server on the same host in a production environment may decrease performance.

Note:This release of SAP BusinessObjects Business Intelligence platform does not support the automaticdeployment of web applications to any web application server other than the bundled Tomcat webapplication server. To deploy web applications to a different supported web application server, usethe WDeploy tool. For more information, see the SAP BusinessObjects Business Intelligence platformWeb Application Deployment Guide.

To use the bundled Tomcat Java web application server, select Install Tomcat application serverand automatically web applications and services to it.To manually deploy web applications to an existing supported Java web application server later,using the WDeploy tool, select Manually deploy to a preinstalled web application server.If you have already set up a Java web application server, or you only require support for the CentralManagement Server (CMS) or BI launch pad applications, select Install Web Application ContainerServer and automatically deploy web applications and services to it.

4. Decide whether to install and use the Subversion version control system to keep track of configurationversions with the SAP Lifecycle Manager. To use an existing version control system, you mustmanually configure the Lifecycle Manager after the installation is complete.Lifecycle Manager stores each configuration change in a version control system, making it easierto revert to a previous configuration when needed.

5. Enter a name and port number for the System Intelligence Agent (SIA) node. The name must consistof English alphanumeric characters (A-Z, a-z, and 0-9) and contain no spaces or other punctuation.The SIA name cannot start with a number.This is the name that you will see in the Central Configuration Manager (CCM). Many CMS serverscan be managed by a single SIA.The port is used for the SIA to listen for incoming connections from the CMS. The SIA must be ableto 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 an SAP BusinessObjects BusinessIntelligence platform SIA.

6. Review the default value for the Central Management Server (CMS) port number. This is the porton which the CMS listens for incoming connections from the web application server, web server (ifapplicable), other CMS nodes (if applicable) and servers. The CMS must be able to receive incomingconnections on this port, so ensure that your firewall is configured appropriately.Port 6400 is a standard TCP/IP port number reserved for use with SAP BusinessObjects BusinessIntelligence platform CMS systems.

7. Enter and confirm the CMS Administrator account password and the CMS cluster key.

2011-10-1135

Installation

Note:The CMS Administrator is a super-user account in the SAP BusinessObjects Business Intelligenceplatform authentication system, used only to administer your SAP BusinessObjects serverconfiguration. 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 securitywhen using clusters.

8. Configure the CMS system database.a. If you chose to install the bundled database, the installation program uses your choices to install

and configure the database for use with SAP BusinessObjects Business Intelligence platform.

Enter the port number for DB2 to listen for incoming database queries. The DB2 database mustbe able to receive incoming connections on this port, so ensure that your firewall is configuredappropriately.

b. If you deselected the Integrated Database option in the feature list, enter the connectioninformation for an existing database to use for the CMS system database.

c. If you deselected the Integrated Database option in the feature list, and you plan to use auditing,enter the connection information for the Auditing Data Store (ADS) database.

9. Decide whether to start the servers as soon as the installation is complete. If you do not start theservers after the installation process is complete, the servers must be started manually with theCentral Configuration Manager (CCM).

10. Configure the web application server.If you selected Tomcat 6.0 in the feature list, review the default values for the web application serverconnection port number, the shutdown port number, and the redirect port number.• The Connection port is the port on which the web application server listens for incoming

connections from web clients.• The Shutdown port allows the web application to be shut down remotely.• The Redirect port enables redirects to secure web connections.

11. If you chose to install the bundled Subversion version control system for use with Lifecycle Manager,confirm the port number and enter and confirm a password for SAP BusinessObjects BusinessIntelligence platform to use when accessing the Subversion repository.

12. SAP BusinessObjects Business Intelligence platform can integrate with your organization's deploymentof SAP Solution Manager Diagnostics (SMD). If your organization uses SAP SMD, selectConfigureconnectivity to SAP SMD Agent. You will be prompted for information. If you chose not toconfigure SMD at this time, you can configure SMD Agent in the Central Management Console(CMC) "Placeholders" screen later.

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 SAP BusinessObjects Business

Intelligence platform, see To enable SAP System Landscape Directory (SLD) support.• For information on installing the SAP Host Agent after SAP BusinessObjects Business Intelligence

platform, see To configure System Landscape Directory (SLD) Data Supplier (DS) post installation.• For information on installing SMD Agent before SAP BusinessObjects Business Intelligence

platform, see Support for SAP Solution Manager Diagnostics (SMD).

2011-10-1136

Installation

• For information on installing SMD Agent after SAP BusinessObjects Business Intelligence platform,see To configure SMD Agent post installation.

a. If you chose to integrate with SMD, enter the SMD Agent hostname and port number.

13. SAP BusinessObjects Business Intelligence platform can integrate with your organization's deploymentof CA Wily Introscope Enterprise Manager. If your organization uses Introscope Enterprise Manager,select Integrate connectivity to Introscope Enterprise Manager. You will be prompted forinformation.

Note:To use CA Wily Introscope Enterprise Manager, SMD Agent must be installed:• For information on installing SMD Agent before SAP BusinessObjects Business Intelligence

platform, see Support for SAP Solution Manager Diagnostics (SMD).• For information on installing SMD Agent after SAP BusinessObjects Business Intelligence platform,

see To configure SMD Agent post installation.

a. If you chose to integrate with Introscope Enterprise Manager, enter the hostname and port numberfor the Introscope Enterprise Manager server.

The "Start Installation" screen appears. Click "Next" to install.

Proceed to While the installation program runs.

4.1.1.2 Custom / Expand installation

The following steps are performed forCustom / Expand installations of SAP BusinessObjects BusinessIntelligence platform.The "Select Features" screen displays selectable components that can be installed.1. Review the list of features to install. Only features with a selected checkbox are installed.

Features are grouped under the following headings:• Web Tier

The web tier components serve content to web browsers.

If you do not have a web application server in place for use with SAP BusinessObjects BusinessIntelligence platform, the installation program can install and configure a Tomcat web applicationserver for you. It is recommended that you evaluate your requirements against information fromyour web application server vendor to determine which supported web application server wouldbest suit your organization's needs.

If you already have a supported web application server installed, you can deselect the option toinstall Tomcat, and only install the Java web applications

• Servers

Server features include the Business Intelligence platform servers (such as processing andscheduling servers), major system components (such as the CMS, Event Server, bundled

2011-10-1137

Installation

database, and a version control system), and servers that integrate SAP BusinessObjects BusinessIntelligence platform into your organization's existing network infrastructure, such as SAP BW orother Enterprise Resource Planning (ERP) systems.

Note:If you plan to use SAP BW authentication, ensure that the BW Publisher Server feature isselected in the Integration Servers feature list.

• Administrator Tools

The Administrator Tools features help administrators maintain an installation.

Note:If you plan to use the upgrade management tool to upgrade objects from an older version of SAPBusinessObjects Business Intelligence platform, see Object types and feature requirements.

• Database Access

To access, analyze, and report on the data in your organization's existing databases, select theappropriate 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 EBSEnterprise Resource Planning (ERP) systems is not selected by default. If you plan to use anERP single sign-on authentication, or other ERP features, ensure that the appropriate ERPfeature 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 SAPBWand SAP features are selected in the Data Access feature list.

• Samples

The samples features installs sample reports, templates, and reporting databases. If you do notneed samples, you can deselect it.

2. Select the type of installation being performed.If you are installing a stand-alone server, or the first server in a cluster, select Start a new SAPBusinessObjects Enterprise deployment. If you already have a CMS and want to create a newserver as part of a cluster, select Expand an existing SAP BusinessObjects Enterprisedeployment.

If you selected Start a new SAPBusinessObjects Enterprise deployment on the last screen, proceedto Custom (New) installation.

If you selected Expand an existing SAPBusinessObjects Enterprise deployment on the last screen,proceed to Custom (Expand) installation.

2011-10-1138

Installation

4.1.1.2.1 Custom (New) installation

If you chose the Start a new SAP BusinessObjects Enterprise deployment option for a "Custom /Expand" installation:1. If you deselected the Integrated Database option in the feature selection screen:

a. Select the type of database to use for the CMS system database.b. Select the type of database to use for the Auditing Data Store (ADS) database. If you do not

want to use auditing, select No Auditing Database.

Note:An existing database must have database user accounts with the appropriate database privilegesready, and the appropriate drivers must be installed and verified as working. The installation programattempts to connect to, and initialize, the database as a part of the installation process.

2. Enter a name and port number for the System Intelligence Agent (SIA) node. The name must consistof English alphanumeric characters (A-Z, a-z, and 0-9) and contain no spaces or other punctuation.The SIA name cannot start with a number.This is the name that you will see in the Central Configuration Manager (CCM). Many CMS serverscan be managed by a single SIA.The port is used for the SIA to listen for incoming connections from the CMS. The SIA must be ableto 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 an SAP BusinessObjects BusinessIntelligence platform SIA.

3. Review the default value for the Central Management Server (CMS) port number. This is the porton which the CMS listens for incoming connections from the web application server, web server (ifapplicable), other CMS nodes (if applicable) and servers. The CMS must be able to receive incomingconnections on this port, so ensure that your firewall is configured appropriately.Port 6400 is a standard TCP/IP port number reserved for use with SAP BusinessObjects BusinessIntelligence platform CMS systems.

4. Enter and confirm the CMS Administrator account password and the CMS cluster key.

Note:The CMS Administrator is a super-user account in the SAP BusinessObjects Business Intelligenceplatform authentication system, used only to administer your server. It is not part of any operatingsystem or single sign-on authentication system.

Communication between some CMS components is encrypted, to provide a higher level of securitywhen using clusters.

5. Configure the CMS system database.a. If you chose to install the bundled database, the installation program uses your choices to install

and configure the database for use with SAP BusinessObjects Business Intelligence platform.

Enter the port number for DB2 to listen for incoming database queries. The DB2 database mustbe able to receive incoming connections on this port, so ensure that your firewall is configuredappropriately.

2011-10-1139

Installation

b. If you deselected the Integrated Database option in the feature list, enter the connectioninformation for an existing database to use for the CMS system database.

c. If you deselected the Integrated Database option in the feature list, and you plan to use auditing,enter the connection information for the Auditing Data Store (ADS) database.


7. Configure the web application server.If you selected Tomcat 6.0 in the feature list, review the default values for the web application serverconnection port number, the shutdown port number, and the redirect port number.• The Connection port is the port on which the web application server listens for incoming


8. If you chose to install the bundled Subversion version control system for use with Lifecycle Manager,confirm the port number and enter and confirm a password for SAP BusinessObjects BusinessIntelligence platform to use when accessing the Subversion repository.

9. SAP BusinessObjects Business Intelligence platform can integrate with your organization's deploymentof SAP Solution Manager Diagnostics (SMD). If your organization uses SAP SMD, selectConfigureconnectivity to SAP SMDAgent. You are prompted for information. If you chose not to configureSMD at this time, you can configure SMD Agent in the Central Management Console (CMC)"Placeholders" screen later.






a. If you chose to integrate with SAP Solution Manager Diagnostics (SMD), enter the SMD Agenthostname and port number.

10. SAP BusinessObjects Business Intelligence platform can integrate with your organization's deploymentof CA Wily Introscope Enterprise Manager. If your organization uses Introscope Enterprise Manager,select Integrate connectivity to Introscope Enterprise Manager. You are prompted forinformation.


platform, see Support for SAP Solution Manager Diagnostics (SMD).

2011-10-1140

Installation

• For information on installing SMD Agent after SAP BusinessObjects Business Intelligence platform,see To configure SMD Agent post installation.




4.1.1.2.2 Custom (Expand) installation

If you chose the Expand an existing SAP BusinessObjects Enterprise deployment option for a"Custom / Expand" installation:1. The expand host must be able to connect to the CMS database. Select the type of server used for

the CMS system database.The installation program prompts for information on the CMS database type and connectioncredentials.

Note:The appropriate drivers must be installed and verified as working on the expand host.

2. Enter a name and review the port number for the System Intelligence Agent (SIA) node. The namemust consist of English alphanumeric characters (A-Z, a-z, and 0-9) and contain no spaces orpunctuation. The SIA name cannot start with a number.This is the name that you will see in the Central Configuration Manager (CCM). Many CMS serverscan be managed by a single SIA.The port is used for the SIA to listen for incoming connections from the CMS. The SIA must be ableto 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 SAP BusinessObjects BusinessIntelligence platform SIA.

3. Enter connection information for the existing CMS.This includes the hostname and port number of the primary CMS. Fully qualified domain names aresupported.

4. Enter and confirm a value for the CMS cluster key.Communication between some CMS components is encrypted to provide a higher level of security.

5. Review the default value for the new Central Management Server (CMS) port number. This is theport on which the new CMS listens for incoming connections from the web application server, webserver (if applicable), other CMS nodes (if applicable) and servers. The CMS must be able to receiveincoming 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 SAP BusinessObjects BusinessIntelligence platform CMS systems.

6. If you are installing the bundled database, enter a database administrator account password andan Enterprise user account name and password. If you are using a previously installed database,enter connection credentials for the CMS to connect to the database.

2011-10-1141

Installation

The installation program uses your choices to install, configure the database for use with SAPBusinessObjects Business Intelligence platform.


8. Review the default values for the web application server connection port number, the shutdown portnumber, and the redirect port number. The web application server must be able to receive incomingconnections on these ports, so ensure that your firewall is configured appropriately.• The Connection port is the port on which the web application server listens for incoming


9. Review the port number and provide a password for SAP BusinessObjects Business Intelligenceplatform to use when accessing the Subversion repository.

10. SAP BusinessObjects Business Intelligence platform can integrate with your organization's deploymentof SAP Solution Manager Diagnostics (SMD). If your organization uses SAP SMD, selectConfigureconnectivity to SAP SMDAgent. You are prompted for information. If you chose not to configureSMD at this time, you can configure SMD Agent in the Central Management Console (CMC)"Placeholders" screen later.






a. If you chose to integrate with SAP Solution Manager Diagnostics (SMD), enter the SMD Agenthostname and port number.

11. SAP BusinessObjects Business Intelligence platform can integrate with your organization's deploymentof CA Wily Introscope Enterprise Manager. If your organization does not use Introscope EnterpriseManager, select Do not integrate connectivity to Introscope Enterprise Manager.





The "Start Installation" screen appears. Select "Next" to install.

2011-10-1142

Installation


4.1.1.3 Web Tier installation

The web tier hosts web applications and serves content to users over the web. Use the "Web Tier"installation option to install Java web applications onto a dedicated Java web application server.

Note:

• If you plan to use a web tier with third-party authentication, or integration for Enterprise ResourcePlanning (ERP) systems such as SAP BW, Siebel Enterprise, JD Edwards EnterpriseOne, or OracleE-Business Suite, you must perform a "Custom / Expand" installation and select the componentsyou need.

For example, to perform a web tier installation with SAP BW and SAP authentication support, selectthe following components from the "Custom / Expand" feature list:• Instances > WebTier > Java Web Applications• Instances > WebTier > Tomcat 6.0 (if you do not already have a web application server)• Instances > Database Access > SAPBW• Instances > Database Access > SAPTo perfom a Web Tier installation with support for a different ERP system, select:• Instances > WebTier > Java Web Applications• Instances > WebTier > Tomcat 6.0 (if you do not already have a web application server)• Instances > Database Access (select the name of the ERP system)

• A web tier installation does not deploy web applications to the web application server. To deployweb applications to a web application server after a web tier installation, use the WDeploy tool. Formore information on using the WDeploy tool, see the SAP BusinessObjects Business Intelligenceplatform Web Application Deployment Guide.

If you do not have a web application server in place for use with SAP BusinessObjects BusinessIntelligence platform, the installation program can install and configure a Tomcat web application serverfor you. It is recommended that you evaluate your requirements against information from your webapplication server vendor to determine which supported web application server would best suit yourorganization's needs.

If you already have a supported web application server installed, you can deselect the option to installTomcat, and only install the Java web applications

The following steps are performed for Web Tier installations of SAP BusinessObjects BusinessIntelligence platform.1. Review the list of features to install. Only features with a selected checkbox are installed.

Web Tier components:• Java Web Applications: Central Management Console (CMC), BI launch pad, and other web

applications

2011-10-1143

Installation

• Tomcat 6: the Apache Tomcat web application server.

2. If you chose to install the Tomcat 6 web application server, review the default values for the webapplication server connection port number, the shutdown port number, and the redirect port number.The web application server must be able to receive incoming connections on these ports, so ensurethat your firewall is configured appropriately.• The Connection port is the port on which the web application server listens for incoming


3. SAP BusinessObjects Business Intelligence platform can integrate with your organization's deploymentof CA Wily Introscope Enterprise Manager. If your organization uses Introscope Enterprise Manager,select Integrate connectivity to Introscope Enterprise Manager. You will be prompted forinformation.







4.1.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 ofthe installation process.

The installation program installs SAP activity and resource monitoring tools. These tools enable you toprovide detailed technical information about your installation in the event of a problem.

4.1.3 When installation is complete

2011-10-1144

Installation

When the installation is complete, review the information in the "Post Installation Steps" screen. If youare not using the bundled Tomcat web application server, you must deploy web applications with theWDeploy web application deployment tool.

4.2 To run a silent installation

Every option in the installation wizard can be given from the command-line. This type of installation isknown as a silent install.

Installation options can be given directly on the command-line as a parameter, or can be stored in aresponse file.• Giving installation options on the command-line

Installation options can be passed directly to the setup program from the command-line as aparameter. For example, the installation option CMSPort=6401 can be given on the command-lineas a parameter when running the installation program to set the CMS port number to 6401, insteadof 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.sh [...] 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 optionparameters in key-value format. When using a response file to give installation options, the installationprogram is run from the command-line with the -r <RESPONSE_FILE> parameter, where <RESPONSE_FILE> is the name of the response file.

The response file contains multiple installation options, with one installation option per line. In thefollowing example, the response file is given as a parameter:

./setup.sh [...] -r $HOME/response.ini [...]

For example, the installation option CMSPort=6401 can be given on a line in the response file toset 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 ([...]) areshown to indicate where other installation options would normally be present:[...]CMSPort=6401[...]

For a complete list of installation options, see Installation option parameters. For an example of aresponse file, see Response file example.

2011-10-1145

Installation

4.2.1 Command-line switch parameters

The following table lists the switch parameters that can be given to the installation program on thecommand-line to perform a silent installation.

Table 4-1: Installation program command-line switch parameters

ExampleDescriptionSwitch parameter

./setup.sh -w "$HOME/response.ini"

Writes a response file to <FILENAME>, containing the options select-ed from the installation wizard.

-w <FILENAME>

./setup.sh -r "$HOME/response.ini"

Reads installation options from a re-sponse file named <FILENAME>.

-r <FILENAME>

./setup.sh -q -r"$HOME/response.ini"

When performing a silent installation,this switch causes the installationprogram to install with no consoleoutput or prompting. If a problem isencountered, the installation programwill write a message to the installationlog file and exit. This switch must al-ways be used in combination with the-r <FILENAME> switch parameter.

-q

4.2.1.1 To use a response file

To use a response file, run the installation program with the -r <RESPONSE_FILE> parameter. Theinstallation program reads all installation options from the response file, and no further input is required.

For example, the following command reads installation options from the response file $HOME/response.ini:./setup.sh -r $HOME/response.ini

To override an installation option in a response file, give that option on the command-line. Installationoptions given on the command-line take precedence over the options in the response file. For a completelist of installation options, see Installation option parameters below.

2011-10-1146

Installation

If an unexpected condition is encountered, an error message is written to the installation log file andthe installation program exits. Installation activity, warnings, and errors are written to the installation logfile in the folder:

<BOE_INSTALL_DIR>/InstallData/logs/<DATE>/InstallDU<COMPONENT>.log

If the <BOE_INSTALL_DIR> folder has not been created by the time the installation program exits,look for install.log in the temporary folder specified by the system TEMP environment variable.

4.2.1.1.1 To write a response file

To create a response file, run the installation program with the -w <RESPONSE_FILE> parameter andselect the desired installation options with the installation wizard. When the wizard completes, theinstallation program exits and the response file is created. The response file can then be used for futureinstallations.

For example, the following command creates the response file $HOME/response.ini:./setup.sh -w $HOME/response.ini

Once created, the response file can be updated with a text editor.

Note:When creating a response file with the GUI installation program, passwords entered via the GUI willbe written to the response file in plain text format.

4.2.1.1.2 To read a response file

A response file installation is started on the command-line, but installation options are read from a ASCIItext file with the options stored in key-value format. This is useful when setting up a cluster, or forcreating development or test environments with standardized options.

When an option is given both on the command-line and in a response file, the command-line optionstake precedence over the response file options. This allows an administrator to override an option in aresponse file when required. This provides three levels precedence for installation options:1. Installation options given on the command-line take highest precedence, and will always override

response file and default values.2. Installation options given in a response file are used when not given on the command-line, and

override default values.3. Installation option default values are used when not given on the command-line or in a response

file.

For example, the following command reads installation options from the response file $HOME/response.ini, but overrides the response file's setting for the installation destination folder:./setup.sh -r $HOME/response.ini InstallDir=/opt/sap/sap_bobj/

2011-10-1147

Installation

4.2.1.2 Quiet mode installations

A quiet mode installation is a command-line installation that does not prompt for installation options.Installation options must be provided on the command-line or in a response file. Any installation optionsnot provided on the command-line or in a response file are left at their default values.

The -q switch bypasses the installation program's installation wizard, and allows an installation to beperformed with no human input and no console output.

For example, the following command uses the default values for all installation options, except for theinstallation destination folder (set to /opt/sap/sap_bobj instead of the current working folder).setup.exe -q InstallDir=/opt/sap/sap_bobj/

If an unexpected condition is encountered, an error message is written to the installation log file andthe installation program exits. Installation activity, warnings, and errors are written to the installation logfile in the folder:

<BOE_INSTALL_DIR>/InstallData/logs/<DATE>/InstallDU<COMPONENT>.log

If the <BOE_INSTALL_DIR> folder has not been created by the time the installation program exits,look for a file named setupengine.log in a timestamp folder in the temporary folder specified by thesystem TEMP environment variable.

4.2.2 Installation option parameters

The following table lists the parameters that can be used to select installation options on both thecommand-line and in response files.

See the table Installation option parameters specific to Unix or Linux for parameters specific to Unix orLinux operating systems.

2011-10-1148

Installation

Table 4-2: Installation option parameters

DescriptionParameter

Determines which language for the installation program to use duringthe installation. Substitute the language code where <CODE> is:• Czech: CS• Danish: DA• Dutch: NL• English: EN• Finnish: FI• French: FR• German: DE• Hungarian: HU• Italian: IT• Japanese: JA• Korean: KO• Norwegian Bokmal: NB• Polish: PL• Portuguese: PT• Russian: RU• Simplified Chinese: zh_CN• Slovak: SK• Spanish: ES• Swedish: SV• Thai: TH• Traditional Chinese: zh_TW• Turkish: TR

SetupUILanguage=<CODE>

Destination folder into which the setup program will install.

Note:The use of Unicode characters in the destination folder is not sup-ported.

• The use of Unicode characters in the destination folder is notsupported.

• Ensure that the destination folder is not the same folder in whichthe installation program has been extracted (do not install to thecurrent working directory when running the installation programfrom the current working directory).

InstallDir=<PATH>

2011-10-1149

Installation


Installs language support for users and administrators to interactwith SAP BusinessObjects Business Intelligence platform in a sup-ported language. If more than one language pack is to be installed,use a semi-colon delimited list without spaces, within quotes, toseparate each code. In the following example, language support forEnglish, Japanese, Simplified Chinese, and Thai will be installed:SelectedLanguagePacks="en;ja;zh_CN;th"

Substitute the following language codes where <CODE> is:• Czech: CS• Danish: DA• Dutch: NL• English: EN• Finnish: FI• French: FR• German: DE• Hungarian: HU• Italian: IT• Japanese: JA• Korean: KO• Norwegian Bokmal: NB• Polish: PL• Portuguese: PT• Russian: RU• Simplified Chinese: zh_CN• Slovak: SK• Spanish: ES• Swedish: SV• Thai: TH• Traditional Chinese: zh_TW• Turkish: TR

SelectedLanguagePacks=<CODE>

Determines whether Introscope support will be enabled or not. Toenable Introscope integration, set <VALUE> to integrate. Todisable Introscope integration, set <VALUE> to nointegrate.

ChooseIntroscopeIntegration=<VALUE>

Password to use for the CMS Administrator account. Substitute<PASSWORD> with the password.

CMSPassword=<PASSWORD>

Password confirmation for the CMS Administrator account. Substitute<PASSWORD> with the password.

CMSPasswordConfirm=<PASSWORD>

Hostname of the Introscope server. Substitute <HOSTNAME> withthe Introscope server hostname.

Introscope_ent_host=<HOSTNAME>

2011-10-1150

Installation


Network TCP listening port number used by the Introscope server.Substitute <PORT> with the Introscope server port number.

Introscope_ent_port=<PORT>

Determines whether SAP Solution Manager Diagnostics (SMD)Agent support will be enabled or not. To enable SMD integration,set <VALUE> to integrate. To disable SMD integration, set<VALUE> to nointegrate.

ChooseSMDIntegration=<VALUE>

Hostname of the SMD Agent. Substitute <HOSTNAME> with theagent hostname.

SMDAgent_host=<HOSTNAME>

Network TCP listening port number used by the SMD Agent. Substi-tute <PORT> with the agent port number.

SMDAgent_port=<PORT>

Name of the user to whom the software is registered. Substitute<NAME> with the name.

RegisteredUser=<NAME>

Name of the company to whom the software is registered. Substitute<NAME> with the name.

RegisteredCompany=<NAME>

Product license key issued when you purchased the software.Substitute <KEY> with the product key in the format XXXXX-XXXXXX-XXXXXX-XXXX.

ProductKey=<KEY>

Network TCP listening port number used by the CMS for incomingconnections. Substitute <PORT> with the port number. The defaultvalue is 6400.

CMSPort=<PORT>

Cryptographic key used to encrypt secure CMS cluster communica-tions. Substitute <KEY> with the key string.

ClusterKey=<KEY>

Cryptographic key conformation. Substitute <KEY> with the keystring.

ClusterKeyConfirm=<KEY>

Determines whether or not the CMS servers will be started automat-ically after the installation is complete. To enable servers automati-cally after the installation, set <SWITCH> to 1. To not enable theservers, so that they must be started manually at a later time, set<SWITCH> to 0.

EnableServers=<SWITCH>

Hostname of the SAP Lifecycle management server.

Note:Do not change this value.

LCMName=LCM_Repository

Network TCP listening port number used by the SAP Lifecyclemanagement server. Substitute <PORT> with the port number.

LCMPort=<PORT>

2011-10-1151

Installation


Username to access SAP Lifecycle management server.

Note:Do not change this value.

LCMUsername=LCM

User password to access SAP Lifecycle management server. Sub-stitute <PASSWORD> with the password.

LCMPassword=<PASSWORD>

User password confirmation. Substitute <PASSWORD> with thepassword.

LCMPasswordConfirm=<PASSWORD>

Determines whether or not the installation is a new LCM on a freshserver, or an expand installation used to create a CMS cluster. Toperform a new installation, set <VALUE> to new. To perform an ex-pand installation, set <VALUE> to expand.

NewOrExpandLCM=<VALUE>

Determines whether or not the bundled database will be installed.To install the bundled database, set <VALUE> to 1.

The bundled database is IBM DB2.

SelectIntegratedDatabase=<VALUE>

Name of the Server Intelligence Agent (SIA) node create for thisinstallation. The name must be alphanumeric and cannot start witha number. Substitute <NAME> with the SIA name.

SIAName=<NAME>

Network TCP listening port number used by the SIA. Substitute<PORT> with the port number.

SIAPort=<PORT>

Network TCP listening port number used by the Tomcat web appli-cation server for inbound connections. Substitute <PORT> with theport number.

TomcatConnectionPort=<PORT>

Network TCP listening port number used by the Tomcat web appli-cation server to trigger a server shutdown. Substitute <PORT> withthe port number.

TomcatShutdownPort=<PORT>

Network TCP listening port number used by the Tomcat web appli-cation server for server request redirection. Substitute <PORT>withthe port number.

TomcatRedirectPort=<PORT>

Determines whether or not the installation program should selectinstallable components based upon the default settings, customsettings (allows you to select components), or settings used for in-stalling web tier components (when installing to a web applicationserver). To install the default components, set <VALUE> to default.To install a custom selection of components, set <VALUE> to custom. To install a web tier components, set <VALUE> to webtier.

InstallType=<VALUE>

2011-10-1152

Installation


Sets the web application server to use for web application deploy-ment. The default value is tomcat. Before deploying web applica-tions with the WDeploy tool, you must still manually update theWDeploy configuration files. For more information, see the SAPBusinessObjects Business Intelligence platform Web ApplicationDeployment Guide.

WebAppServerType=<VALUE>

List of components to install. Used in combination with the InstallType=custom or InstallType=webtier parameter. This param-eter should not be modified manually. Features must be selectedthrough the installation program user interface when creating a re-sponse file.

For a complete list of feature codes, see Feature codes.

Features=<CODE>

Table 4-3: Installation option parameters specific to Unix for Linux


Network TCP listening port number used by the DB2 databaseserver bundled with SAP BusinessObjects Business Intelligenceplatform. Substitute <PORT> with the database server port number.

DB2PortNumber=<PORT>

4.2.2.1 Feature codes

The following feature codes to select features for installation. Multiple features are separated withcommas.

• root: install all features• WebTier: install all web tier components

Note:If you plan to use a web tier with third-party authentication, or integration for Enterprise ResourcePlanning (ERP) systems such as SAP BW, Siebel Enterprise, JD Edwards EnterpriseOne, orOracle E-Business Suite, you must perform a "Custom / Expand" installation and select thecomponents you need.

For example, to perform a web tier installation with SAP BW and SAP authentication support,select the following components from the "Custom / Expand" feature list:• Instances > WebTier > Java Web Applications

2011-10-1153

Installation

• Instances > WebTier > Tomcat 6.0 (if you do not already have a web application server)• Instances > Database Access > SAPBW• Instances > Database Access > SAPTo perfom a Web Tier installation with support for a different ERP system, select:• Instances > WebTier > Java Web Applications• Instances > WebTier > Tomcat 6.0 (if you do not already have a web application server)• Instances > Database Access (select the name of the ERP system)

• JavaWebApps1 Java Web Applications• tomcat60 Tomcat 6.0

• Servers: install all server components• PlatformServers: install all platform servers

• CMS (Central Management Server)• FRS (File Repository Servers)• PlatformServers.IntegratedDB.DB2 (installs bundled IBM DB2 server)

• DashboardAnalyticsServer (BI Workspace)• PlatformServers.EventServer• PlatformServers.SystemLandscapeSupplier (SLD)• PlatformServers.WebAppContainerService (WACS)• AdaptiveProcessingServer (platform processing)• AdaptiveJobServer (scheduling)• Subversion (Subversion version control system)

• ConnectionServices: install connectivity components• ConnectionProcService

• DataFederatorServices: install all data federation components• DataFederatorQueryService

• AdvancedAnalysisServices: install all Analysis components• MultidimensionalAnalysisServices (MDAS)• BExWebApplicationsService

• CrystalReportsServers: install all SAP Crystal Reports components• CrystalReportsProcServices (SAP Crystal Reports Processing)• CrystalReportSchedulingServices• CrystalReport2011ProcServices (SAP Crystal Reports 2011 Processing)• CrystalReport2011SchedulingServices (SAP Crystal Reports 2011 Scheduling)

• WebIServers: install all Web Intelligence components• WebIProcServer (Web Intelligence Processing)• WebISchedulingServices (Web Intelligence Scheduling)

• XcelsiusServers (Dashboard Design)• MobileServices

• MobileServers

2011-10-1154

Installation

• MobileAddon (CMS plugin for Mobile)• IntegrationServers: install all integration components

• BWPublisherServer (SAP BW authentication and SAP BW Publisher support)

• AdministratorTools: install all administrator tools• UpgradeManager (Upgrade management tool)

Note:If you plan to use the upgrade management tool to upgrade objects from an older version ofSAP BusinessObjects Business Intelligence platform, see Object types and featurerequirements.

• DataAccess install all database access components• DataAccess.DataFederator• DataAccess.HPNeoView• DataAccess.MySQL• DataAccess.GenericJDBC• DataAccess.GenericODBC• DataAccess.GenericOLEDB• DataAccess.OptionalDataDirectODBC• DataAccess.MaxDB• DataAccess.Salesforce (Salesforce.com)• DataAccess.Netezza• DataAccess.Microsoft_AnalyticalServices• DataAccess.MicrosoftExchange• DataAccess.MicrosoftOutlook• DataAccess.Microsoft_SQLServer• DataAccess.Microsoft_Access• DataAccess.Ingres• DataAccess.Greenplum• DataAccess.IBMDB2• DataAccess.Informix• DataAccess.ProgressOpenEdge• DataAccess.Oracle• DataAccess.Sybase• DataAccess.Teradata• DataAccess.SAPBW• DataAccess.SAP (security and data access for SAP BW and R/3 systems)• DataAccess.PersonalFiles• DataAccess.JavaBean• DataAccess.OpenConnectivity• DataAccess.HSQLDB• DataAccess.Derby

2011-10-1155

Installation

• DataAccess.Essbase• DataAccess.Peoplesoft (PeopleSoft Enterprise)• DataAccess.JDEdwards (JD Edwards EnterpriseOne)• DataAccess.Siebel (Siebel Enterprise Server)• DataAccess.OracleEBS (Oracle E-Business Suite)• DataAccess.Universe (SAP BusinessObjects Universe)• DataAccess.MyCube (OLAP Cube)• DataAccess.XML• DataAccess.ADO.NET• DataAccess.COMData• DataAccess.DataSet (Dataset Consumer)• DataAccess.SymantecACT• DataAccess.BDE (IDAPI Database DLL)• DataAccess.CDO (Crystal Data Objects)• DataAccess.FieldDefinitions• DataAccess.FileSystem• DataAccess.NTEventLog• DataAccess.WebActivityLog• DataAccess.Btrieve (Pervasive Database Driver)• DataAccess.dBase• DataAccess.UWSC (Universal Web Services Connector (UWSC))

• Samples: install sample reports and data sources

4.2.2.2 Response file example

The following example response file contains options for installing SAP BusinessObjects BusinessIntelligence platform.

Example:

In this example, the response file is named $HOME/response.ini.### Choose to Integrate Introscope Enterprise Manager: integrate or nointegratechooseintroscopeintegration=nointegrate

### Choose to Integrate Solution Manager Diagnostics (SMD) Agent: integrate or nointegratechoosesmdintegration=nointegrate

### CMS administrator passwordcmspassword=Password1

### #property.CMSPasswordConfirm.description#cmspasswordconfirm=Password1

### CMS connection portcmsport=6400

2011-10-1156

Installation

### CMS cluster keyClusterKey=Crypto1

### #property.ClusterKeyConfirm.description#ClusterKeyconfirm=Crypto1

### Choose to start servers after install: 0 or 1enableservers=1

### Installation directoryinstalldir=/opt/sap/sap_bobj/

### Choose install type: default, custom, webtierinstalltype=custom

### Introscope Enterprise Manager Hostnameintroscope_ent_host=$IntroscopeAgentEnterpriseManagerHost

### Introscope Enterprise Manager Port numberintroscope_ent_port=$IntroscopeAgentEnterpriseManagerPort

### LCM server namelcmname=LCM_repository

### LCM passwordlcmpassword=Password1

### #property.LCMPasswordConfirm.description#lcmpasswordconfirm=Password1

### LCM portlcmport=3690

### LCM user namelcmusername=LCM

### Choose install mode: new, expandneworexpandinstall=new

### Product keycodeproductkey=XXXXX-XXXXXXX-XXXXXXX-XXXXXXX-XX

### Registered Companyregisteredcompany=default_company

### Registered Userregistereduser=default_user

### Language Packs Selected to Installselectedlanguagepacks=en

### Setup UI languagesetupuilanguage=en

### SIA node namesianame=SIA1

### SIA connector portsiaport=6410

### SMD Agent Hostnamesmdagent_host=$SMDAgentHost

### SMD Agent Port Numbersmdagent_port=$SMDAgentPort

### #propertyDeclaration.SQLExpressAdminPassword.description#sqlexpressadminpassword=Password1

### #propertyDeclaration.SQLExpressBOEUserName.description#sqlexpressboeusername=boeuser

### #propertyDeclaration.SQLExpressBOEUserPassword.description#sqlexpressboeuserpassword=Password1

### #propertyDeclaration.TomcatConnectionPort.description#tomcatconnectionport=8080

2011-10-1157

Installation

### #propertyDeclaration.TomcatRedirectPort.description#tomcatredirectport=8443

### #propertyDeclaration.TomcatShutdownPort.description#tomcatshutdownport=8005

### #propertyDeclaration.WACSPort.description#wacsport=6405

### Available features### ------------------### root### WebTier### JavaWebApps1### tomcat60### Servers### PlatformServers### CMS### FRS### PlatformServers.IntegratedDB### DashboardAnalyticsServer### PlatformServers.EventServer### PlatformServers.SystemLandscapeSupplier### PlatformServers.WebAppContainerService### AdaptiveProcessingServer### AdaptiveJobServer### Subversion### ConnectionServices### ConnectionProcService### DataFederatorServices### DataFederatorQueryService### AdvancedAnalysisServices### MultidimensionalAnalysisServices### BExWebApplicationsService### CrystalReportsServers### CrystalReportsProcServices### CrystalReportSchedulingServices### CrystalReport2011ProcServices### CrystalReport2011SchedulingServices### ExportSupport### Export.MicrosoftMail### Export.LotusNotesMail### Export.LotusNotes### Export.ExchangeFolders### Export.Application### Export.HTML### Export.ODBC### Export.Record### Export.ReportDefinition### WebIServers### WebIProcServer### WebISchedulingServices### XcelsiusServers### MobileServers### IntegrationServers### SiebelSignOnServer### BWPublisherServer### AdministratorTools### UpgradeManager### DeveloperTools### BOE64bitNETSDK### DataAccess### DataAccess.DataFederator### DataAccess.HPNeoView### DataAccess.MySQL### DataAccess.GenericJDBC### DataAccess.GenericODBC### DataAccess.GenericOLEDB### DataAccess.OptionalDataDirectODBC### DataAccess.MaxDB### DataAccess.Salesforce### DataAccess.Netezza### DataAccess.Microsoft_AnalyticalServices### DataAccess.MicrosoftExchange### DataAccess.MicrosoftOutlook### DataAccess.Microsoft_SQLServer### DataAccess.Microsoft_Access### DataAccess.Ingres

2011-10-1158

Installation

### DataAccess.Greenplum### DataAccess.IBMDB2### DataAccess.Informix### DataAccess.ProgressOpenEdge### DataAccess.Oracle### DataAccess.Sybase### DataAccess.Teradata### DataAccess.SAPBW### DataAccess.SAP### DataAccess.PersonalFiles### DataAccess.JavaBean### DataAccess.OpenConnectivity### DataAccess.HSQLDB### DataAccess.Derby### DataAccess.Essbase### DataAccess.Peoplesoft### DataAccess.JDEdwards### DataAccess.Siebel### DataAccess.OracleEBS### DataAccess.Universe### DataAccess.MyCube### DataAccess.XML### DataAccess.ADO.NET### DataAccess.COMData### DataAccess.DataSet### DataAccess.SymantecACT### DataAccess.BDE### DataAccess.CDO### DataAccess.FieldDefinitions### DataAccess.FileSystem### DataAccess.NTEventLog### DataAccess.WebActivityLog### DataAccess.Btrieve### DataAccess.dBase### DataAccess.UWSC### Samples### Helpfeatures=JavaWebApps1,tomcat60,WebTier,CMS,FRS,PlatformServers.IntegratedDB,DashboardAnalyticsServer,PlatformServers.EventServer,PlatformServers.SystemLandscapeSupplier,PlatformServers.WebAppContainerService,AdaptiveProcessingServer,AdaptiveJobServer,Subversion,PlatformServers,ConnectionProcService,ConnectionServices,DataFederatorQueryService,DataFederatorServices,MultidimensionalAnalysisServices,BExWebApplicationsService,AdvancedAnalysisServices,CrystalReportsProcServices,CrystalReportSchedulingServices,CrystalReport2011ProcServices,CrystalReport2011SchedulingServices,Export.MicrosoftMail,Export.LotusNotesMail,Export.LotusNotes,Export.ExchangeFolders,Export.Application,Export.HTML,Export.ODBC,Export.Record,Export.ReportDefinition,ExportSupport,CrystalReportsServers,WebIProcServer,WebISchedulingServices,WebIServers,XcelsiusServers,MobileServers,SiebelSignOnServer,BWPublisherServer,IntegrationServers,Servers,UpgradeManager,AdministratorTools,BOE64bitNETSDK,DeveloperTools,DataAccess.DataFederator,DataAccess.HPNeoView,DataAccess.MySQL,DataAccess.GenericJDBC,DataAccess.GenericODBC,DataAccess.GenericOLEDB,DataAccess.MaxDB,DataAccess.Salesforce,DataAccess.Netezza,DataAccess.Microsoft_AnalyticalServices,DataAccess.MicrosoftExchange,DataAccess.MicrosoftOutlook,DataAccess.Microsoft_SQLServer,DataAccess.Microsoft_Access,DataAccess.Ingres,DataAccess.Greenplum,DataAccess.IBMDB2,DataAccess.Informix,DataAccess.ProgressOpenEdge,DataAccess.Oracle,DataAccess.Sybase,DataAccess.Teradata,DataAccess.SAPBW,DataAccess.SAP,DataAccess.PersonalFiles,DataAccess.JavaBean,DataAccess.OpenConnectivity,DataAccess.HSQLDB,DataAccess.Derby,DataAccess.Essbase,DataAccess.Peoplesoft,DataAccess.JDEdwards,DataAccess.Siebel,DataAccess.OracleEBS,DataAccess.Universe,DataAccess.MyCube,DataAccess.XML,DataAccess.ADO.NET,DataAccess.COMData,DataAccess.DataSet,DataAccess.SymantecACT,DataAccess.BDE,DataAccess.CDO,DataAccess.FieldDefinitions,DataAccess.FileSystem,DataAccess.NTEventLog,DataAccess.WebActivityLog,DataAccess.Btrieve,DataAccess.dBase,DataAccess.UWSC,Samples,Help

2011-10-1159

Installation

2011-10-1160

Installation

Post-Installation

This section describes the activities that should be performed after the installation program has finished,to test that the installation was successful.

5.1 Launching the CMC

Verify that the installation was successful by logging on to the Central Management Console (CMC).The CMC is used to administer servers, users and groups, rights, and security policies. For moreinformation on using the CMC, see the SAP BusinessObjects Business Intelligence Platform AdministratorGuide.

If you have installed a dedicated web application server, you can enter the web application server'sURL to access the CMC. Use the following URL:http://<WEB_APP_SERVER>:<PORT>/BOE/CMC

Substitute <WEB_APP_SERVER> for the hostname of the web application server and <PORT> for theweb application server's listening port. If you are using a custom web application server root context orBOE.war web application context, the URL will be different.

If you are using Internet Explorer, you may receive several “Internet Explorer Enhanced SecurityConfiguration” warnings because the new server is not yet added to the list of trusted sites. Click Addto add the local web server to the list of trusted web sites. If your server is not using SSL encryption,deselect Require server verification (https:) for all sites in this zone.

Log on as the Administrator user by typing Administrator into the "User Name" field and entering theadministrative password that you entered into the installation program.

5.2 Troubleshooting login issues

If you are unable to log on to the CMC, evaluate the following possible causes:1. Is a firewall blocking the CMS port number (default 6400) or the web application server port?2. Is the URL correct??

2011-10-1161

Post-Installation

The default URL to access the CMC is:http://<WEB_APP_SERVER>:<PORT>/BOE/CMC

Substitute <WEB_APP_SERVER> for the hostname of the web application server and <PORT> for theweb application server's listening port. If you are using a custom web application server root contextor BOE.war web application context, the URL will be different.

3. Is the correct method specified in the Authentication field?

The default authentication type is "Enterprise", referring to native SAP BusinessObjects BusinessIntelligence platform authentication system.

If you are using an LDAP single sign-on authentication system, select the system instead.

4. Did you provide the correct user credentials in the User Name and Password fields on the CMClogin screen?

The name of the administrative account is Administrator. The password configured when SAPBusinessObjects Business Intelligence platform was installed.

5. Is the Server Intelligence Agent (SIA) is running.

Start the CCM with the ccm.sh script.If the SIA is not running, start it.

6. Ensure that the database server(s) used for the CMS system and Auditing Data Store databasesare running, and that the network connection from the CMS to the database is working.

7. If you are attempting to connect to a CMS cluster using the @<clustername> format, and this is yourfirst attempt to connect to the cluster, the CMC will not know which CMS servers belong to thecluster.

In this case, you need to specify a list of CMS servers in the web.xml, found in the WEB-INF folderof the CMC web application WAR file. Follow the instructions in the cms.clusters section ofweb.xml for more details. It is also possible to specify CMS cluster information for the BI launchpad by modifying its corresponding web.xml file.

If none of these solutions work, consider repairing or reinstalling the software or contacting SAPBusinessObjects support at service.sap.com/bosap-support.

5.3 Creating additional Adaptive Processing Servers

The installation program installs one Adaptive Processing Server (APS) per host system. Dependingon the features that you've installed, this APS may host a large number of services, such as theMonitoring Service, Lifecycle Management Service, Multi-Dimensional Analysis Service (MDAS),Publishing Service, and others.

If you are installing a production environment, do not use the default APS. Instead, it is highlyrecommended that once the installation process is complete, you perform a system sizing to determine:• The type and number of APS services.• The distribution of services across multiple APS servers.

2011-10-1162

Post-Installation


• The optimal number of APS servers. Multiple APS servers provide redundancy, better performance,and higher reliability.

• The distribution of APS servers across multiple nodes.

Create new APS server instances as determined by the sizing process.

For example, if the outcome of your sizing happens to suggest the creation of one APS for each servicecategory, then may end up creating eight APS servers. One for each service category: AdvancedAnalysis Services, Connectivity Services, Core Services, Crystal Reports Services, Dashboard DesignServices, Data Federation Services, Lifecycle Management Services, and Interactive Analysis Services.

5.4 Deploying web applications

The installation only installs web applications to Tomcat 6. If the installation program did not automaticallydeploy web applications to your web application server, you must deploy the web applications manuallywith the WDeploy tool, or with the web application server administrative console.

The WDeploy tool automates the deployment of web applications to supported web application servers.For more information on using WDeploy, see the SAP BusinessObjects Business Intelligence PlatformWeb Application Deployment Guide.

5.5 SAP support

5.5.1 To configure System Landscape Directory (SLD) Data Supplier (DS) postinstallation

If you decided not to enable support for SAP System Landscape Directory (SLD) when installing SAPBusinessObjects Business Intelligence platform, you can enable it at any time later by installing SAPHost Agent. For more information, see To enable SAP System Landscape Directory (SLD) support.

Once SAP Host Agent is installed, open the Central Management Console (CMC), select the "Servers"tab, and restart the SIA nodes. SLD registration will automatically occur whenever a SIA is restartedor created.

To enable SLD support for web applications deployed to a web application server, see “SAP SystemLandscape Directory (SLD) registration” in the SAP BusinessObjects Business Intelligence PlatformWeb Application Deployment Guide.

2011-10-1163

Post-Installation

5.5.2 To configure SMD Agent post installation

If you did not configure SAP Solution Manager Diagnostics (SMD) during the installation process, youcan still give the SMD Agent hostname and port number in the Central Management Console (CMC).

Note:SMD Agent must be installed before configuring the SMD Agent hostname and port number in SAPBusinessObjects Business Intelligence platform.

1. Open the Central Management Console.2. Select the Servers tab.3. Expand the SIA Nodes folder in server list, and right-click the SIA to be updated.4. Select "Placeholders" from the context menu.5. Ensure that the placeholders related to SMD Agent are set correctly:

a. Update the %SMDAgentHost% placeholder with the SMD Agent hostname.b. Update the %SMDAgentPort% placeholder with the SMD Agent port number.

6. Save and close the "Placeholders" screen.7. Restart the SIA.8. When more than one SIA is present, repeat steps 3-7 for each SIA in the Nodes folder.

5.5.3 To configure CA Wily Introscope Agent post installation

If you did not configure CA Wily Introscope during the installation process, you can configure it later inthe Central Management Console (CMC).

Note:The Introscope Agent must be installed and running before configuring it in the CMC.

1. Open the Central Management Console.2. Select the Servers tab.3. Expand the SIA Nodes folder in server list, and right-click the SIA to be updated.4. Select "Placeholders" from the context menu.5. Ensure that the placeholders related to Introscope are set correctly:

a. Change the %IntroscopeAgentEnableInstrumentation% placeholder from false totrue.

b. Update the %IntroscopeAgentManagerHost% placeholder with the Introscope Agent hostname.c. Update the %IntroscopeAgenEnterpriseManagerPort% placeholder with the Introscope

Agent port number.

2011-10-1164

Post-Installation

d. Review %IntroscopeAgenEnterpriseManagerTransport% to ensure that the correctnetwork transport is selected (for example, TCP).

6. Save and close the "Placeholders" screen.7. Restart the SIA.8. When more than one SIA is present, repeat steps 3-7 for each SIA in the Nodes folder.

5.6 Third-party ERP integration

5.6.1 To enable Siebel Enterprise integration

To integrate SAP BusinessObjects Business Intelligence platform with Siebel Enterprise, you may needto take some additional steps. There are two methods you can use to report off Siebel data:• Reporting from a local Siebel client

To report from a local Siebel client, ensure that Siebel Enterprise is configured so that either SiebelDedicated Web Client or Mobile Web Client is enabled and accessible.

• Report directly off your Siebel Enterprise server

To enable Siebel Enterprise integration, the Siebel Java Data Bean JAR files must be copied to theSAP BusinessObjects Business Intelligence platform and web application server lib folders.

1. Locate the classes folder that was created when you installed Siebel Tools.

The Java data bean files are typically located in the <SIEBEL_HOME>/classes folder. For example,the Siebel classes folder may be /opt/siebel/7.8/classes.

2. Copy the SiebelJI.jar and SiebelJI_enu.jar Java data bean files to the SAP BusinessObjectsBusiness Intelligence platform Java lib directory.

For example, copy /opt/siebel/7.8/classes/SiebelJI.jar and/opt/siebel/7.8/classes/SiebelJI_enu.jar to <BOE_INSTALL_DIR>/sap_bobj/enterprise_xi40/java/lib/siebel.

3. Copy the SiebelJI.jar and SiebelJI_enu.jar Java data bean files to the lib directory ofyour web application server.

For example, copy /opt/siebel/7.8/classes/SiebelJI.jar and/opt/siebel/7.8/classes/SiebelJI_enu.jar to<WAS_INSTALL_DIR>/lib. If you installedthe Tomcat web application server bundled with SAP BusinessObjects Business Intelligence platform,the folder is <BOE_INSTALL_DIR>/Tomcat6/lib.

4. Restart the Central Management Server and web application server.

2011-10-1165

Post-Installation

For more information, see “Configuring for Siebel integration” in the SAP BusinessObjects BusinessIntelligence Platform Administrator Guide.

5.6.2 To enable JD Edwards EnterpriseOne integration

To enable JD Edwards EnterpriseOne integration, the JD Edwards Java Data Bean JAR files must becopied to the SAP BusinessObjects Business Intelligence platform Java lib folder.1. Locate the classes folder that was created when you installed JD Edwards EnterpriseOne.

The Java data bean files are typically located in the <JDE_HOME>/system/classes folder.

2. Locate the following Java data bean files:• kernel.jar• jdeutil.jar• log4j.jar• pseoneqryxml.jar• pseonexml.jar

3. Copy the .jar files above into the SAP BusinessObjects Business Intelligence platform JD Edwardslib folder:

<BOE_INSTALL_DIR>/sap_bobj/enterprise_xi40/java/lib/jdedwards/default/jdedwards.

4. Also copy the .jar into the web application server Java lib folder. For example, if you're using theweb application server bundled with SAP BusinessObjects Business Intelligence platform, the defaultweb application server lib directory is:

<BOE_INSTALL_DIR>/sap_bobj/enterprise_xi40/tomcat/lib.

5. Restart the Central Management Server and Web Application Server.

For more information, see “Configuring for JD Edwards integration” in the SAP BusinessObjects BusinessIntelligence Platform Administrator Guide.

5.6.3 To enable Oracle E-Business Suite (EBS) integration

To enable reporting from Oracle EBS data sources in SAP Crystal Reports, ensure that the 32-bit Oracleclient is installed on systems running SAP Crystal Reports.

To enable SAP BusinessObjects Business Intelligence platform integration with Oracle EBS, includingOracle EBS authentication and import roles, follow the steps below.1. Install and configure the 64-bit Oracle client on SAP BusinessObjects Business Intelligence platform

hosts.

2011-10-1166

Post-Installation

When installing the 64-bit Oracle client, ensure that the following components are installed:• Oracle JDBC driver• JDBC-OCI bridge

2. Verify that the Oracle client can connect by logging on to the Oracle EBS database on the client.3. Copy the following Oracle client binaries to the SAP BusinessObjects Business Intelligence platform

Oracle library.

Copy:• <ORA_HOME>/lib/ocijdbc11.so• <ORA_HOME>/lib/libclntsh.so.11.1• <ORA_HOME>/lib/libnnz11.so

To: <BOE_INSTALL_DIR>/sap_bobj/enterprise_xi40/java/lib/oracle/default.

4. Copy the following file to the web application server lib directory.

Copy:• <ORA_HOME>/jdbc/lib/ojdbc5.jar

Copy the file to the web application server lib directory. For example, if you're using the webapplication server bundled with SAP BusinessObjects Business Intelligence platform, the defaultweb application server lib directory is:

<BOE_INSTALL_DIR>/sap_bobj/enterprise_xi40/tomcat/lib.

5. Restart the CMS.6. Stop the web application server.7. Clean up the web application work folder.

For example, on the Tomcat 6.0 web application server supplied with SAP BusinessObjects BusinessIntelligence platform, remove all the files in the Tomcat work folder (<BOE_INSTALL_DIR>/Tomcat6/work/Catalina/localhost/BOE).

8. Restart the web application server.

After installing integration for Oracle E-Business Suite, ensure that the Oracle EBS security context isenforced. To do this, manually create the bobj_pkg package in any new Oracle EBS database beforeusing the integration solution for the first time. To generate the package, log on to the Oracle EBSdatabase and use the PL\SQL code given in the following file:

<BOE_INSTALL_DIR>/Samples/ebs/bobj_pkg.txt

5.7 Post-install diagnostic checks

You can run the Monitoring Tool at any time to run a diagnostics check and look for problems.

To access the Monitoring Tool in order to run diagnostic tests, log on to the Central ManagementConsole (CMC), select the "Monitoring" screen, and click the Probes tab.

2011-10-1167

Post-Installation

5.8 Making changes to SAP BusinessObjects Business Intelligence platform

5.8.1 To modify SAP BusinessObjects Business Intelligence platform

These instructions describe the process to modify your SAP BusinessObjects Business Intelligenceplatform installation by adding or removing installed features.

It is recommended that you back up the CMS system database before modifying SAP BusinessObjectsBusiness Intelligence platform.

Note:The CMS must be running in order to modify an SAP BusinessObjects Business Intelligence platforminstallation.

1. Change directory to the <BOE_INSTALL_DIR> folder.2. Run the command:

./modifyOrRemoveProducts.sh

Note:Log files, configuration files for web applications, and web applications will not be removed by theremoval program. Folders left after removing a corresponding feature can be removed manuallylater with the rm command.

3. Select the installation to be modified.4. Select the Modify option.5. Ensure that all features you want available are selected. Ensure that features you do not want

installed are deselected.Expand the highlighted feature in the selection tree by pressing the keyboard spacebar. Use thearrow keys to navigate up or down. Toggle feature selections with the X key.When you are satisfied with the selected features, press Enter.

6. If you are modifying a server with a CMS installed, press Enter to apply the changes. If you aremodifying a server that uses a remotely installed CMS, enter the hostname, port, and an administrativeaccount username and password.

7. When the changes have been made, press Enter to return to the command-line.

The installation has been updated.

2011-10-1168

Post-Installation

5.8.2 To repair SAP BusinessObjects Business Intelligence platform

These instructions describe the process to repair an SAP BusinessObjects Business Intelligence platforminstallation. This process restores the files and settings originally configured by the setup program.

It is recommended that you back up the CMS system database before repairing SAP BusinessObjectsBusiness Intelligence platform.

Note:The CMS must be running in order to modify an installation.

1. Change directory to the <BOE_INSTALL_DIR> folder.2. Run the command:

./modifyOrRemoveProducts.sh

Note:Log files, configuration files for web applications, and web applications will not be removed by theremoval program. Any remaining folders can be removed manually with the rm command.

3. Select the installation to be repaired.4. Select the Repair option.5. Enter the hostname, port, and an administrative account username and password.6. When the repair is finished, press Enter to return to the command-line.

The installation has been repaired, restoring your system to its original configuration.

5.8.3 To remove SAP BusinessObjects Business Intelligence platform

These instructions describe the process to permanently uninstall SAP BusinessObjects BusinessIntelligence platform from a system.

It is recommended that you back up the CMS database before removing SAP BusinessObjects BusinessIntelligence platform.

Note:

• Add-on products that with dependencies on other products should be removed before the producton which they depend. For example, for servers with SAP BusinessObjects Business Intelligenceplatform Explorer installed, SAP BusinessObjects Business Intelligence platform Explorer shouldbe removed first, as it will not function without SAP BusinessObjects Business Intelligence platform.

• Removing SAP BusinessObjects Business Intelligence platform removes the core product plus anyinstalled maintenance packages. To remove maintenance packages individually, see the installationguides for those maintenance packages.

2011-10-1169

Post-Installation

The following items will remain:• The repository database, as it may be shared with other programs• The file repository folder, as it may contain user data• Web applications deployed to a web application server will not be undeployed. Use the WDeploy

command or the web application server administrative console to undeploy web applications.• Web application files customized to an individual web application server• Configuration files

Note:These items can be manually removed later by an administrator, if required.

1. Stop all server processes.Change directory to the <BOE_INSTALL_DIR>/sap_bobj folder and run the command:./ccm.sh –stop all

Alternatively, run the command:./stopservers

2. If you are using the DB2 database bundled with SAP BusinessObjects Business Intelligence platform,stop DB2.For example, run the command:./db2shutdown.sh

3. If you are using the Tomcat web application server bundled with SAP BusinessObjects BusinessIntelligence platform, stop Tomcat.For example, run the command:./tomcatshutdown.sh

4. Change directory to the <BOE_INSTALL_DIR> folder.For example, run the following command:cd ..

5. Run the command:./modifyOrRemoveProducts.sh

Note:Log files, configuration files for web applications, and web applications will not be removed by theremoval program. Any remaining folders can be removed manually with the rm command.

6. Select the installation to remove.7. Select the Remove option.

The software has been removed from the system.

5.9 When the administrator account password is lost

2011-10-1170

Post-Installation

If the credentials for the SAP BusinessObjects Business Intelligence platform administrator accountare lost, consider the following potential resolutions:• If another administrative account is available, use it to change the password for the SAP

BusinessObjects Business Intelligence platform administrator account.• Reset the SAP BusinessObjects Business Intelligence platform administrator account password

with the steps shown in "To reset the SAP BusinessObjects Enterprise administrator accountpassword".

5.9.1 To reset the SAP BusinessObjects Business Intelligence platform administratoraccount password

Use the following instructions if you have lost access to the credentials for the SAP BusinessObjectsBusiness Intelligence platformadministrator account and cannot use another account to reset thepassword.

Note:

• Access to the machine hosting the Server Intelligence Agent (SIA) is required.• Ensure that SAP BusinessObjects Business Intelligence platform is running.

1. Go to the following folder:

<BOE_INSTALL_DIR>/sap_bobj/enterprise_xi40/dfo

The dfo folder contains a subfolder with a randomly generated name starting with dfo_.

2. Copy the file named BusinessObjects_Administrator_dfo.xml from inside the dfo_ folderto the following folder:

<BOE_INSTALL_DIR>/sap_bobj/enterprise_xi40/packages

3. Locate the CMS process.

Use the ps command to find a process named boe_cmsd. For example:ps aux | grep boe_cmsd

4. Copy the CMS command to the clipboard.

Copy everything after the start of the boe_cmsd command to the clipboard. For example, on Linuxplatforms, grep may shown the following output:16835 pts/0 Sl 0:19 /opt/sap_bobj/enterprise_xi40/linux_x64/boe_cmsd -loggingPath/opt/sap_bobj/logging/ -port 6400 -restart -dbinfo /opt/sap_bobj/enterprise_xi40/linux_x64/_boe_mysia1.dbinfo -noauditor -autoboot -fg -name mysia1.cms -pidfile /opt/sap_bobj/serverpids/mysia1_mysia1.CentralManagementServer.pid

Ensure that you include the full path to the boe_cmsd command. In the example above, the followinginformation should be copied:/opt/sap_bobj/enterprise_xi40/linux_x64/boe_cmsd -loggingPath /opt/sap_bobj/logging/ -port 6400 -restart-dbinfo /opt/sap_bobj/enterprise_xi40/linux_x64/_boe_mysia1.dbinfo -noauditor -autoboot -fg -namemysia1.cms -pidfile /opt/sap_bobj/serverpids/mysia1_mysia1.CentralManagementServer.pid

2011-10-1171

Post-Installation

5. Use the Central Configuration Manager (CCM) to stop the SIA.

Use the ccm.sh command in <BOE_INSTALL_DIR>/sap_bobj. For example:cd <BOE_INSTALL_DIR>/sap_bobj./ccm.sh -stop mysia1

Once you have confirmed that the SIA has stopped, proceed to the next step.

6. Paste the CMS command to a command-line. Do not press Enter.

Paste the result of step 4 onto the command-line.

7. Append the -serverconsole switch to the command and press Enter.For example, note that the following command has -serverconsole appended:/opt/sap_bobj/enterprise_xi40/linux_x64/boe_cmsd -loggingPath /opt/sap_bobj/logging/ -port 6400 -restart-dbinfo /opt/sap_bobj/enterprise_xi40/linux_x64/_boe_mysia1.dbinfo -noauditor -autoboot -fg -namemysia1.cms -pidfile /opt/sap_bobj/serverpids/mysia1_mysia1.CentralManagementServer.pid -serverconsole

The SIA is launched in serverconsole mode. You will be prompted when the SIA is ready toaccept commands.

8. Enter the following query:select si_id from ci_systemobjects where si_name='Administrator'

Four objects are returned. Record the SI_ID for each object.

Tip:One of the entries should have the SI_ID set to 12.

9. Delete the objects by typing the following command for each object:delete <ID_NUMBER>

10. Verify that the objects have been deleted by re-entering the command from step 8:select si_id from ci_systemobjects where si_name='Administrator'

No objects should be returned.

11. Enter the following query:select si_id from ci_systemobjects where si_name='BusinessObjects_Administrator_dfo.xml'

One object should be returned. Record the object's SI_ID number.

12. Delete the object by entering the following command:delete <SI_ID>

13. Type quit to exit.14. Use the CCM to start the SIA.

Use the ccm.sh command in <BOE_INSTALL_DIR>/sap_bobj. For example:cd <BOE_INSTALL_DIR>/sap_bobj./ccm.sh -start mysia1

You can now log on to the administrator account without having to provide password (leave the"Password" field blank).

2011-10-1172

Post-Installation

More Information

LocationInformation Resource

http://www.sap.comSAP BusinessObjects product infor-mation

Navigate to http://help.sap.com/businessobjects and on the "SAP Busi-nessObjects Overview" side panel click All Products.

You can access the most up-to-date documentation covering all SAPBusinessObjects products and their deployment at the SAP Help Portal.You can download PDF versions or installable HTML libraries.

Certain guides are stored on the SAP Service Marketplace and are notavailable from the SAP Help Portal. These guides are listed on the HelpPortal accompanied by a link to the SAP Service Marketplace. Customerswith a maintenance agreement have an authorized user ID to accessthis site. To obtain an ID, contact your customer support representative.

SAP Help Portal

http://service.sap.com/bosap-support > Documentation• Installation guides: https://service.sap.com/bosap-instguides• Release notes: http://service.sap.com/releasenotes

The SAP Service Marketplace stores certain installation guides, upgradeand migration guides, deployment guides, release notes and SupportedPlatforms documents. Customers with a maintenance agreement havean authorized user ID to access this site. Contact your customer supportrepresentative to obtain an ID. If you are redirected to the SAP ServiceMarketplace from the SAP Help Portal, use the menu in the navigationpane on the left to locate the category containing the documentation youwant to access.

SAP Service Marketplace

https://cw.sdn.sap.com/cw/community/docupedia

Docupedia provides additional documentation resources, a collaborativeauthoring environment, and an interactive feedback channel.

Docupedia

https://boc.sdn.sap.com/

https://www.sdn.sap.com/irj/sdn/businessobjects-sdklibraryDeveloper resources

2011-10-1173

More Information

http://www.sap.com

http://help.sap.com/businessobjects


https://service.sap.com/bosap-instguides

http://service.sap.com/releasenotes

https://cw.sdn.sap.com/cw/community/docupedia

https://boc.sdn.sap.com/

https://www.sdn.sap.com/irj/sdn/businessobjects-sdklibrary

LocationInformation Resource

https://www.sdn.sap.com/irj/boc/businessobjects-articles

These articles were formerly known as technical papers.SAP BusinessObjects articles onthe SAP Community Network

https://service.sap.com/notes

These notes were formerly known as Knowledge Base articles.Notes

https://www.sdn.sap.com/irj/scn/forumsForums on the SAP CommunityNetwork

http://www.sap.com/services/education

From traditional classroom learning to targeted e-learning seminars, wecan offer a training package to suit your learning needs and preferredlearning style.

Training


The SAP Support Portal contains information about Customer Supportprograms and services. It also has links to a wide range of technical in-formation and downloads. Customers with a maintenance agreementhave an authorized user ID to access this site. To obtain an ID, contactyour customer support representative.

Online customer support

http://www.sap.com/services/bysubject/businessobjectsconsulting

Consultants can accompany you from the initial analysis stage to thedelivery of your deployment project. Expertise is available in topics suchas relational and multidimensional databases, connectivity, databasedesign tools, and customized embedding technology.

Consulting

2011-10-1174

More Information

https://www.sdn.sap.com/irj/boc/businessobjects-articles

https://service.sap.com/notes

https://www.sdn.sap.com/irj/scn/forums

http://www.sap.com/services/education


http://www.sap.com/services/bysubject/businessobjectsconsulting

Index64-bit

platform 18

A

account permissions 18administrator password 71AIX 25Auditing Data Store

preparing for 21

B

BusinessObjects Enterpriseupgrade from 12

C

CA Wily Introscopepost-install configuration 64support 28

check-listinstallation 28

Client Tools 10CMC

launching 61troubleshooting 61

CMS system databasepreparing for 21

co-existence, product 13command-line

installation 45installation program parameters 46

components, new 10

D

databasechoosing 15

DB2extra requirements 23, 24

deploymentweb applications 63

diagnostic tests 67disaster mitigation

reset administrator password 71

E

Enterprise Resource Planning (ERP)11, 28

F

feature codesEnterprise 53

features, new 10

G

GNU products 19

I

installationaccount permissions 18check-list 28command-line 45, 46custom 37, 39Enterprise feature codes 53expand 37full 34JD Edwards EnterpriseOne 66methods 31Oracle EBS integration 66parameters 48planning 9post-install 61preparation for 17requirements 18response file 45, 46, 47response file example 56Siebel integration 65silent 48software removal 69type 33web tier 43

Introscopesee CA Wily Introscope 28

J

JD Edwards EnterpriseOne 11JD Edwards integration 66

L

LANG environment variable 19languages 10LC_ALL environment variable 19locale 19

M

Monitoring Tool 67

N

networkpermissions 20

O

object typesrequirements 12

Oracle E-Business Suite 11, 66

P

password reset 71PeopleSoft Enterprise 11permissions

for installation account 18network 20

planning installation 9post-installation 61

diagnostic tests 67

R

remove software 69requirements 18response file 46, 47

Enterprise feature codes 53example 56parameters 48

S

SAP ERP 11SAP Host Agent 17, 26SAP System Landscape Directory

(SLD) 26

2011-10-1175

Siebel Enterprise 11Siebel integration 65SMD Agent 27

post-install configuration 64SUSE 25Sybase

extra requirements 25System Landscape Directory (SLD)

Data Supplier (DS) 63

U

ulimit 25uninstallation 69upgrade support 12upgrades

requirementsobject types 12

W

web application server, choosing 14web applications 63web server, choosing 15

2011-10-1176

Index

XI4 Install Unix En

Documents

Transcript of XI4 Install Unix En