business intelligence platform installation guide 4.0

Business Intelligence Platform Installation Guide■ SAP BusinessObjects Business Intelligence platform 4.0 Feature Pack 3

2012-05-02

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

Copyright

herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and other countries.Business Objects and the Business Objects logo, BusinessObjects,Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects productsand services mentioned herein as well as their respective logos are trademarks or registeredtrademarks of Business Objects Software Ltd. Business Objects is an SAP company.Sybase andAdaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and servicesmentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase,Inc. Sybase is an SAP company. Crossgate, m@gic EDDY, B2B 360°, B2B 360° Services areregistered trademarks of Crossgate AG in Germany and other countries. Crossgate 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.

2012-05-02

Contents

Introduction.............................................................................................................................7Chapter 1

About this Document...............................................................................................................71.1Document History....................................................................................................................71.1.1Purpose...................................................................................................................................81.2Integration................................................................................................................................81.3Constraints..............................................................................................................................81.4Additional documentation.........................................................................................................91.5

Planning................................................................................................................................11Chapter 2

New features and components...............................................................................................112.1Enterprise Resource Planning (ERP) integration.....................................................................132.1.1Upgrade support....................................................................................................................132.2Database servers...................................................................................................................142.3

Preparation............................................................................................................................15Chapter 3

System requirements.............................................................................................................163.1Additional requirements for Solaris.........................................................................................163.1.1Account permissions..............................................................................................................163.1.2Network permissions.............................................................................................................173.1.3Preparing the CMS system or Auditing Data Store database.................................................183.2Extra requirements for IBM DB2............................................................................................193.2.1Extra requirements for Sybase...............................................................................................203.2.2Extra requirements for SAP HANA ........................................................................................203.2.3SAP support..........................................................................................................................203.3Support for SAP System Landscape Directory (SLD)............................................................203.3.1Support for SAP Solution Manager Diagnostics (SMD).........................................................223.3.2Support for CA Wily Introscope.............................................................................................233.3.3Final checklist.........................................................................................................................233.4

Installation.............................................................................................................................25Chapter 4

Overview................................................................................................................................254.1To download the installation program.....................................................................................254.2

2012-05-023

To run an interactive installation.............................................................................................264.3To select an install type..........................................................................................................274.3.1While the installation program runs.........................................................................................394.3.2When installation is complete.................................................................................................394.3.3To run a silent installation.......................................................................................................394.4Command-line switch parameters..........................................................................................404.4.1Installation option parameters.................................................................................................434.4.2

Post-Installation....................................................................................................................57Chapter 5

Launching the CMC...............................................................................................................575.1Troubleshooting login issues..................................................................................................575.2Creating additional Adaptive Processing Servers...................................................................585.3Deploying web applications....................................................................................................595.4SAP support..........................................................................................................................595.5To configure System Landscape Directory (SLD) Data Supplier (DS) post installation...........595.5.1To configure SMD Agent post installation..............................................................................605.5.2To configure CA Wily Introscope Agent post installation........................................................605.5.3Third-party ERP integration.....................................................................................................615.6To enable Siebel Enterprise integration..................................................................................615.6.1To enable JD Edwards EnterpriseOne integration...................................................................625.6.2To enable Oracle E-Business Suite (EBS) integration.............................................................625.6.3Post-install diagnostic checks.................................................................................................645.7Making changes to SAP BusinessObjects Business Intelligence platform..............................645.8To modify SAP BusinessObjects Business Intelligence platform............................................645.8.1To repair SAP BusinessObjects Business Intelligence platform..............................................655.8.2To remove SAP BusinessObjects Business Intelligence platform...........................................665.8.3When the administrator account password is lost..................................................................675.9

Installing SAP BusinessObjects Business Intelligence Platform Client Tools......................69Chapter 6

Desktop client applications.....................................................................................................706.1Web Intelligence Desktop......................................................................................................706.1.1Business View Manager.........................................................................................................706.1.2Report Conversion Tool.........................................................................................................716.1.3Universe design tool..............................................................................................................716.1.4Query as a Web Service........................................................................................................716.1.5Information design tool...........................................................................................................726.1.6Translation Management Tool................................................................................................726.1.7Data Federation Administration Tool.......................................................................................736.1.8Widgets for SAP BusinessObjects Business Intelligence platform.........................................736.1.9To run an interactive installation of Client Tools......................................................................746.2

2012-05-024

Contents

To run a silent installation of Client Tools...............................................................................766.3Command-line silent install of Client Tools.............................................................................776.3.1Installation option parameters for Client Tools........................................................................796.3.2Making changes to Client Tools.............................................................................................856.4To modify Client Tools...........................................................................................................856.4.1To repair a Client Tools installation.........................................................................................866.4.2To remove Client Tools..........................................................................................................876.4.3Upgrading Client Tools...........................................................................................................876.5

More Information...................................................................................................................89Appendix A

Index 91

2012-05-025

Contents

2012-05-026

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 Windows: for use with

Microsoft Windows operating systems (this document).

• SAP BusinessObjects Business Intelligence Platform Installation Guide for Unix: for use with Unixor Linux operating systems.

1.1.1 Document History

The following table provides an overview of important document changes.

2012-05-027

Introduction

DescriptionDateVersion

First release of this document.30, November2010

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, available at http://service.sap.com/~sapidb/011000358700001236432010E.

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.

2012-05-028

Introduction

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

http://service.sap.com/~sapidb/011000358700001236432010E


1.5 Additional documentation

Information is available at http://help.sap.com/bobip40. Documents listed in the following table arerelevant to deployment and installation.

Document TitleLink to DocumentDocument Description

SAP BusinessObjects BusinessIntelligence Suite Master Guide


Overview of SAP Busines-sObjects Business Intelli-gence platform documen-tation.

SAP BusinessObjects BusinessIntelligence Platform PlanningGuide


Overview of SAP Busines-sObjects Business Intelli-gence platform architec-ture, plus guidelines onintegrating into existinginfrastructure.

SAP BusinessObjects BusinessIntelligence Platform What'sNew Guide

http://help.sap.com/businessobject/product_guides/boexir4/en/xi4_whats_new_en.pdf

Overview of new featuresin SAP BusinessObjectsBusiness Intelligenceplatform.

SAP BusinessObjects BusinessIntelligence Platform UpgradeGuide


Instructions to upgradefrom a previous release.

SAP BusinessObjects BusinessIntelligence Platform Web Appli-cation Deployment Guide

http://service.sap.com/~sapidb/011000358700001237082010E/xi4_webappdeploy_win_en.pdf

Detailed instructions fordeploying web applica-tions to supported webapplication servers.

SAP BusinessObjects BusinessIntelligence Platform Administra-tor Guide

http://help.sap.com/businessobject/product_guides/boexir4/en/xi4_bip_admin_en.pdf

Administrative documen-tation for setting up andmaintaining an SAP Busi-nessObjects Business In-telligence platform server.

SAP BusinessObjects BI 4.0Product Availability Matrix(PAM)

http://service.sap.com/pam

Lists the supported plat-forms, databases, webapplication servers, webservers, and other sys-tems.

2012-05-029

Introduction

http://help.sap.com/bobip40


















2012-05-0210

Introduction

Planning

The SAP BusinessObjects Business Intelligence (BI) platform can be installed on Windows, Unix, orLinux platforms.

Before installing:• Ensure the operating system, application server, database server, and other components on which

you will install the BI platform are supported. See the SAP BusinessObjects BI 4.0 Product AvailabilityMatrix (PAM) at http://service.sap.com/pam.

• Decide whether to use the included Microsoft SQL Server database server for the CMS and auditingdatabase.

If you do not have a database server to use with the BI platform, the installation program can installand configure one for you. It is recommended that you evaluate your requirements against informationfrom your database server vendor to determine which supported database would best suit yourorganization's requirements.

Note:If you do not plan to use the default database that is included in the installation program, ensure thedatabase that you plan to use is configured before beginning the installation. The database musthave user accounts with the appropriate database privileges ready, and the appropriate drivers mustbe installed and verified as working. The installation program will connect to and initialize the database.

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

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

If you do not have a web application server system to host BI platform web applications, the installationprogram can install and configure one for you. It is recommended that you evaluate your requirementsagainst information from your web application server vendor to determine which supported databasewould best suit your organization's requirements. To use any other supported web application server,it must be installed, configured, enabled, and accessible before you install the BI platform.

The installation program will only install Tomcat on the local machine. It cannot install across anetwork.

2.1 New features and components

2012-05-0211

Planning


The following components are now integrated into the SAP BusinessObjects Business Intelligenceplatform 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.

• 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 Dashboards (formerly Xcelsius) server support

SAP BusinessObjects Dashboards 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.

2012-05-0212

Planning

• WDeploy command-line and GUI tools

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

The following components are no longer part of the SAP BusinessObjects Business Intelligence platforminstallation program:• Client Tools

To install Client Tools, use the dedicated SAP BusinessObjects Business Intelligence platform ClientTools installation program.

• Mobile Configuration Tool

To configure the Mobile application, see the SAP BusinessObjects Mobile Installation and DeploymentGuide

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 a number of ERP systems.See the SAP BusinessObjects BI 4.0 Product Availability Matrix (PAM) , available at http://service.sap.com/pam.

SAP ERP and BW support is installed by default. Use the Custom / Expand installation option to deselectSAP integration support if you do not want support for SAP ERP or BW. Support for other ERP systemsis not installed by default. Use the "Custom / Expand" installation option to select and install integrationfor non-SAP ERP systems.

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 Feature Pack 3, you must firstinstall it, then migrate settings and content using the Upgrade management tool. See the SAPBusinessObjects Business Intelligence Platform Upgrade Guide for more information.

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.

2012-05-0213

Planning



2.3 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.

Microsoft SQL Server 2008 is the default database server. Any other database server must be runningand accessible when you run the installation program.

Note:If you intend to use Microsoft SQL Server, ensure that the account being used to install has theappropriate privileges. Microsoft SQL Server installation requires that the account being used is amember of the Windows Administrators group, and that the default privileges assigned to theAdministrators group have not been modified. For more information, see Microsoft SQL Server 2008knowledge base article number 2000257: SQL Server 2008 installation will fail if the setup accountdoes not have certain user rights.

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 SAPBusinessObjects BI 4.0Product Availability Matrix (PAM), available at http://service.sap.com/pam.

2012-05-0214

Planning


Preparation

This section details how to prepare for the installation of the SAP BusinessObjects Business Intelligence(BI) platform.

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 SAP Service Marketplace as described in To download the installation program.• To download SAPCAR, go to http://service.sap.com/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.com/bosap-support > SoftwareDownloads > Support Packages and Patches > Browse our Download Catalog > SAPTechnology Components > SAP HOST AGENT

Note:The path that you download the product to should not be too long.

3. If you plan to use SAP System Landscape Directory (SLD), ensure that the SAP Host Agent isinstalled before installing the BI platform. For more information on SLD, see “Registration of SAPBusinessObjects Business Intelligence platform in the System Landscape” in the SAPBusinessObjects Business Intelligence Platform Administrator Guide. For information on SAP HostAgent, 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 BI 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 the BI 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.

2012-05-0215

Preparation

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

3.1 System requirements

Use the following guidelines when you install SAP BusinessObjects Business Intelligence platform:• Ensure that the operating system is supported. Only 64-bit operating systems are supported.

Windows .NET Framework 3.5 Service Pack 1 and Windows installation program 4.5 are required.

• Before you run the installation program, ensure that the destination partition has enough room forthe deployment to expand (when updates and new features are added in the future).

• If you install the deployment on the operating system partition, ensure that there is enough room forthe 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 Additional requirements for Solaris

The SAP BusinessObjects Business Intelligence platform cannot be installed onto a Solaris machinethat is configured with soft partitions.

3.1.2 Account permissions

To install SAP BusinessObjects Business Intelligence platform on a Windows host, a user must havethe following permissions:

2012-05-0216

Preparation

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

Required accessCategory

Local administrative privileges.Operating system

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

• Access to shared file system directories for users of the deployment.• 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

Note:You cannot install the deployment on a domain controller, or on a Windows host where the default localAdministrator group security settings have been modified.

3.1.3 Network permissions

Ensure that the upgrade management tool can communicate with the source and destinationdeployments. For more information on network permissions, see the “Securing SAP BusinessObjectsBusiness Intelligence platform” chapter of the SAP BusinessObjects Business Intelligence platformAdministrator’s Guide.

3.1.3.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.

2012-05-0217

Preparation

3.2 Preparing the CMS system or Auditing Data Store database

To use a database server other than the default one, complete the following tasks before installing theSAP BusinessObjects Business Intelligence (BI)platform.• Create a database (or tablespace or schema, if applicable to your database), and account to store

CMS configuration and system information. A second tablespace or scheme is required to holdauditing information. Record the database, tablespace, and account information so you can enterthe details when prompted by the BI platform installation program.

Caution:If you have an existing BI platform installation, you must create a fresh database and migrate existingcontent after the install is complete.

• Ensure that your database server is configured to use Unicode character encoding (such as UTF-8).• Ensure that the database accounts have privileges to create, modify, and delete tables, and to create

stored procedures.• When using a database server on a network, the appropriate database client drivers must be installed

and verified as working before installing BI platform. Contact your database administrator to establishwhich 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

• ODBC DSN name (selected from the Windows System DSN list)• Account username• Account password• Database name• "Use trusted connection" checkbox• "Show system database" checkbox• "Reset existing database" checkbox (recommended setting)

MicrosoftSQL Serverusing ODBC

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

MySQL

2012-05-0218

Preparation

Information required by installation programDatabase

• 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

• 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.

• BI platform will connect to the default database for the user you specify. Thedefault is set by the database administrator.

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

Sybase

3.2.1 Extra requirements for IBM DB2

If you plan to install and use an IBM DB2 database server for use with the BI 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.

2012-05-0219

Preparation

• Create a user temporary table space before installing the BI platform. If you do not create a usertemporary table space, the BI platform installation program will not be able to configure the DB2database.

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.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.2.3 Extra requirements for SAP HANA

If you are using SAP HANA for the CMS database, you must select the default database duringinstallation then export the data to an SAP HANA database. See To select SAP HANA as a CMSdatabase in the SAP BusinessObjects Business Intelligence platform Administrator's Guide.

3.3 SAP support

3.3.1 Support for SAP System Landscape Directory (SLD)

SAP System Landscape Directory (SLD) is a directory service that maintains a list of installed SAP and(optionally) non-SAP software. SLD provides two main categories of information:

2012-05-0220

Preparation

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

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

• 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.3.1.1 To enable SAP System Landscape Directory (SLD) support

If you plan on using SAP System Landscape Directory (SLD) or SAP Solution Manager Diagnostics(SMD), ensure that the SAP Host Agent is installed and configured. The following steps walk you throughinstalling SAP Host Agent.

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

Note:If you have installed SAP GUI or SAP Solution Manager Diagnostics (SMD), skip to step 4 below.

Prior to installing support for SAP System Landscape Directory (SLD) there must be an sapadm userwith administrator 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

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

%Program Files%\SAP\hostctrl\exe

2012-05-0221

Preparation

http://service.sap.com/swdc

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 the BI platform, restart all SIA nodes in the Central Configuration Manager(CCM) to register with the SLD.

3.3.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 laterin the Central Management Console (CMC) "Placeholders" screen. For more information, seeToconfigure SMD Agent post installation.

SMD Agent is included in the COLLATERALS\DiagnosticsAgent7.3 folder of the installation directory.For information on installing SMD agent, see SAP Note 1448655.

2012-05-0222

Preparation

3.3.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, seeTo configure SMD Agent post installation.

3.4 Final checklist

Prior to installing the SAP BusinessObjects Business Intelligence (BI) platform, review the followingchecklist.• 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 are using your own database server:• Have you created a database, tablespace (if required), and accounts for the CMS system and

Auditing Data Store databases?• Have you made sure you can log onto the database from the BI platform host?• If you are using DB2 or Sybase, have you verified that your database was created with the correct

settings? (Some settings can't be modified after the database has been created.)• Has the database client software been properly configured?

• If you are using your own web application server:• Have you decided on which web application server to use?• Has the server already been installed and configured?• Have you ensured that your existing web application server has the required JDK installed?

2012-05-0223

Preparation

• If you plan to use SAP System Landscape Directory (SLD), ensure that SAP Host Agent beeninstalled and configured. For more information, seeSupport for SAP System Landscape Directory(SLD).

• If you plan to use SAP Solution Manager Diagnostics (SMD), SMD Agent may have been installedand configured before or after the BI platform. For more information, see Support for SAP SolutionManager Diagnostics (SMD).

Installation on Microsoft Windows requires a minimum screen solution of 1024 × 768.

Note:The BI platform installation program no longer installs Client Tools. Client Tools can only be installedwith the dedicated Client Tools installation program.

2012-05-0224

Preparation

Installation

This chapter guides you through the installation of SAP BusinessObjects Business Intelligence

platform.

4.1 Overview

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 or in a text file. This option is useful if you wantto install the same configuration on multiple machines.

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.

When the installation program detects an identical previously-installed version, it will enter maintenancemode, allowing you to remove, repair, or modify the software.

Note:The installation program does not provide visual feedback during the installation. It may take more thanone hour to complete.

4.2 To download the installation program

1. Go to https://service.sap.com/bosap-support > Software Downloads.2. On the "Find your software" tab, under the "A–Z Index", select Installations and Upgrades.3. Select B > SBOP BI platform (former SBOP Enterprise) > SBOP BI Platform 4.0.

2012-05-0225

Installation


4. Select Installation and Upgrade and then select your platform.5. Select all of the objects titled "SBOP BI PLATFORM <version> SERVER" plus any additional add-on

products you require, then follow the instructions on the website to download and extract the objects.

Note:The software may take a long time to download, and you may need to contact the system administratorto ensure your company's firewall will not terminate the download process.

Support Packages and Patches are installation programs that contain updates to BI platform software.You can download them from https://service.sap.com/bosap-support > Software Downloads. On the"Find your software" tab, under the "A–Z Index", click Support Packages and Patches. For moreinformation on installing Support Packages and Patches, see the SAP BusinessObjects BusinessIntelligence Platform Upgrade Master Guide.

4.3 To run an interactive installation

Before installing, ensure that the account being used has Administrator privileges. The installationrequires that the account being used is a member of the Windows Administrators group, and that thedefault privileges assigned to the Administrators group have not been modified.

When the installation program starts, a series of prerequisite checks are performed. The result of thistest is displayed for your information. If your system does not meet the minimum requirements, theinstallation program will not install the SAP BusinessObjects Business Intelligence (BI) platform. MicrosoftC++ redistributable components will be installed automatically if they are not found.

Note:The prerequisite checks may take a long time to complete and do not provide visual indication ofprogress. It is not recommended to restart the installation program during this operation.

1. Log in at the console or use Microsoft Remote Desktop connection with a minimum screen resolutionof 1024 × 768.

2. Locate the installation program. If you are installing from a physical media, look for setup.exe inthe top-level folder. If you are installing from a compressed download, extract it and locate setup.exe.

3. Run setup.exe by double-clicking it in Windows Explorer or calling it from the command-line.4. Choose a language for the setup program to use during the installation process. The language

setting 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 Windows componentsconfigured by the installation program, such as Windows service names and Start menu shortcuts.These names cannot be changed later and are not affected by language settings once the installationis complete.

2012-05-0226

Installation


5. The installation program checks for required components. Review the results and decide whetherto 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 a missing or unsupported component is optional, you have the option to either continuewith the installation or stop and correct the condition. The installation program will provide informationon how to correct the condition.

6. Review the recommendations made by the installation program welcome screen.7. Review the agreement and select I accept the License Agreement.8. Enter the name, company, and the product keycode you purchased. Keep the keycode safe in case

you need to re-install the product.9. To install support for a language, select it from the list.

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 the BI platform.

The language currently being used by the operating system is selected automatically. Englishlanguage support cannot be deselected because it is used if a problem is detected with an individuallanguage.

The "Choose Install Type" screen appears.

4.3.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 a Microsoft SQL Server database. If you do not have an existing web applicationserver, the installation 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

2012-05-0227

Installation

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 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.

Review the "Destination Folder" shown. This is the folder into which the installation program willinstall SAP 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 set to the same folder in which the installation program

has been extracted.

• If you have already installed SAP BusinessObjects products, the Destination Folder field is noteditable, and the path to the existing folder is displayed.

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.3.1.1 Full installation

The following steps are performed for Full installations of the SAP BusinessObjects Business Intelligence(BI)platform.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 the BI platform, the installation programcan install and configure one for you. It is recommended that you evaluate your requirements againstinformation from your database server vendor to determine which supported database would bestsuit your organization's needs.To install the bundled database server, select Install and use the default database.

Microsoft SQL Server 2008 will be installed and configured to store Central Management Server(CMS) and auditing data.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.

2012-05-0228

Installation

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 the BI platform web applications.

If you do not have a web application server in place for use with the BI platform, the installationprogram can install and configure a Tomcat web application server for you. It is recommended thatyou evaluate your requirements against information from your web application server vendor todetermine which supported web application server would best suit your organization's needs.

Note:When configuring a production environment, it is recommended that the web application server ishosted on a separate system. Running the BI platform and a web application server on the samehost in a production environment may decrease performance.

Note:This release of the BI platform does not support the automatic deployment of web applications toany web application server other than the bundled Tomcat web application server. To deploy webapplications to a different supported web application server, use the WDeploy tool. For moreinformation, see the SAP BusinessObjects Business Intelligence Platform Web ApplicationDeployment 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.

2012-05-0229

Installation

Port 6410 is a standard TCP/IP port number reserved for use with a BI 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 the BI platform CMS.

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

Note:The CMS Administrator is a super-user account in the BI platform authentication system, used onlyto administer your SAP BusinessObjects server configuration. It is not part of any operating systemor 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 and confirm the datase administrator account password, and an Enterprise user accountpassword. The Enterprise user name may be changed if you do not want to use the default.

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.

If you're using an ODBC database driver, you must configure an ODBC data source. On olderWindows operating system, such as Windows 2003 Server, a system ODBC DSN connectioncan be configured from: Start > Settings > Control Panel > Administrative Tools > DataSources (ODBC). If you're using a newer Windows operating system, such as Windows 2008Server or Windows 7, a system ODBC DSN can be configured from: Start > Control Panel >Administrative Tools > Data Sources (ODBC).

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.

If you selected Web Application Container Server (WACS) in the feature list, review the "HTTPListening Port" number for the Web Application Container Server to listen for incoming connectionsfrom web clients.

2012-05-0230

Installation

The web application server and WACS must be able to receive incoming connections on the givenport numbers, so ensure that your firewall is configured appropriately.

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 the BI platform to use when accessingthe Subversion repository.

12. The BI platform can integrate with your organization's deployment of SAP Solution ManagerDiagnostics (SMD). If your organization uses SAP SMD, select Configure connectivity to SAPSMD Agent. You will be prompted for information. If you chose not to configure SMD at this time,you can configure SMD Agent in the Central Management Console (CMC) "Placeholders" screenlater.

Note:To use SAP Solution Manager Diagnostics (SMD), SAP Host Agent and SMD Agent must be installed:• For information on installing the SAP Host Agent before installing the BI platform, see To enable

SAP System Landscape Directory (SLD) support.• For information on installing the SAP Host Agent after installing the BI platform, see To configure

System Landscape Directory (SLD) Data Supplier (DS) post installation.• For information on installing SMD Agent before installing the BI platform, see Support for SAP

Solution Manager Diagnostics (SMD).• For information on installing SMD Agent after installing the BI 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. The BI platform can integrate with your organization's deployment of CA Wily Introscope EnterpriseManager. If your organization uses Introscope Enterprise Manager, select Integrate connectivityto Introscope Enterprise Manager. You will be prompted for information.

Note:To use CA Wily Introscope Enterprise Manager, SMD Agent must be installed.

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.3.1.2 Custom / Expand installation

The following steps are performed for Custom / Expand installations of the SAP BusinessObjectsBusiness Intelligence (BI) 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:

2012-05-0231

Installation

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 the BI platform, the installationprogram can install and configure a Tomcat web application server for you. It is recommendedthat you evaluate your requirements against information from your web application server vendorto determine which supported web application server would best suit your organization's needs.


• Servers

Server features include the Business Intelligence platform servers (such as processing andscheduling servers), major system components (such as the CMS, Event Server, bundleddatabase, and a version control system), and servers that integrate the BI platform into yourorganization's existing network infrastructure, such as SAP BW or other Enterprise ResourcePlanning (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.

• Developer Tools

If you plan to develop your own applications with a BI platform Software Development Kit (SDK),install the Developer Tools feature.

• Database Access

To access, analyze, and report on the data in your organization's existing databases, select 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.

2012-05-0232

Installation

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.

4.3.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 a the BI 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 the BI platform CMS.

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 the BI platform authentication system, usedonly to administer your server. It is not part of any operating system or single sign-on authenticationsystem.

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

5. Configure the CMS system database.

2012-05-0233

Installation

a. If you chose to install the bundled database, the installation program uses your choices to installand configure the database for use with the BI platform.

Enter and confirm the datase administrator account password, and an Enterprise user accountpassword. The Enterprise user name may be changed if you do not want to use the default.

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.

If you're using an ODBC database driver, you must configure an ODBC data source. On olderWindows operating system, such as Windows 2003 Server, a system ODBC DSN connectioncan be configured from: Start > Settings > Control Panel > Administrative Tools > DataSources (ODBC). If you're using a newer Windows operating system, such as Windows 2008Server or Windows 7, a system ODBC DSN can be configured from: Start > Control Panel >Administrative Tools > Data Sources (ODBC).

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


If you selected Web Application Container Server (WACS) in the feature list, review the "HTTPListening Port" number for the Web Application Container Server to listen for incoming connectionsfrom web clients.



9. The BI platform can integrate with your organization's deployment of SAP Solution ManagerDiagnostics (SMD). If your organization uses SAP SMD, select Configure connectivity to SAPSMD Agent. You are prompted for information. If you chose not to configure SMD at this time,you can configure SMD Agent in the Central Management Console (CMC) "Placeholders" screenlater.

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 the BI platform, see To enable SAP

System Landscape Directory (SLD) support.

2012-05-0234

Installation

• For information on installing the SAP Host Agent after the BI platform, see To enable SAP SystemLandscape Directory (SLD) support.

• For information on installing SMD Agent before the BI platform, see To configure SystemLandscape Directory (SLD) Data Supplier (DS) post installation.

• For information on installing SMD Agent after the BI platform, see Support for SAP SolutionManager Diagnostics (SMD).

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

10. The BI platform can integrate with your organization's deployment of CA Wily Introscope EnterpriseManager. If your organization uses Introscope Enterprise Manager, select Integrate connectivityto Introscope Enterprise Manager. You are prompted for information.

Note:To use CA Wily Introscope Enterprise Manager, SMD Agent must be installed:




4.3.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 database drivers must be installed and verified as working on the expand host.

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 a BI platform SIA.

3. Enter connection information for the existing CMS.This includes the hostname and port number of the primary CMS, as well as the Administratoraccount password. Fully qualified domain names are supported.

4. Enter the CMS cluster key for the existing CMS host.

2012-05-0235

Installation

Communication between some CMS components is encrypted to provide a higher level of security.The cluster key must match the key entered on the existing CMS host, to which you are attemptingto connect.

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 other CMS nodes (if applicable)and servers. The CMS must be able to receive incoming connections on this port, so ensure thatyour firewall is configured appropriately.Port 6400 is a standard TCP/IP port number reserved for use with the BI platform CMS.

6. Enter connection details for the CMS system database.If you are using the Microsoft SQL Server 2008 database bundled with the BI platform on the existingCMS, to which you are attempting to connect, you must configure a system ODBC DSN connectionfor the existing CMS system database. If you are using a different previously installed database,enter connection credentials for the CMS to connect to the database.


8. Configure the web application server.a. If you chose Install Tomcat application server and automatically deploy web applications

and services to it above, review the default values for the web application server connectionport 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


b. If you chose Install Web Application Container Server and automatically deploy webapplications and services to it above, review the "HTTP Listening Port" number for the WebApplication Container Server to listen for incoming connections from web clients.



10. The BI platform can integrate with your organization's deployment of SAP Solution ManagerDiagnostics (SMD). If your organization uses SAP SMD, select Configure connectivity to SAPSMD Agent. You are prompted for information. If you chose not to configure SMD at this time,you can configure SMD Agent in the Central Management Console (CMC) "Placeholders" screenlater.

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 the BI platform, see To enable SAP

System Landscape Directory (SLD) support.• For information on installing the SAP Host Agent after the BI platform, see To configure System

Landscape Directory (SLD) Data Supplier (DS) post installation.

2012-05-0236

Installation

• For information on installing SMD Agent before the BI platform, see Support for SAP SolutionManager Diagnostics (SMD).

• For information on installing SMD Agent after the BI platform, see To configure SMD Agent postinstallation.

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

11. The BI platform can integrate with your organization's deployment of CA Wily Introscope EnterpriseManager. If your organization does not use Introscope Enterprise Manager, select Do not integrateconnectivity to Introscope Enterprise Manager.

Note:To use CA Wily Introscope Enterprise Manager, SMD Agent must be installed




4.3.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. For

2012-05-0237

Installation

more 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• 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.

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.




2012-05-0238

Installation

4.3.2 While the installation program runs

The progress bar illustrates the progress of the installation as a whole.

Note:When performing an Expand installation, the existing CMS may be restarted automatically as a part ofthe installation process.

4.3.3 When installation is complete

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.3.3.1 Reboot suppression

If a file is locked during the installation, you may be prompted to restart the server after the installation.You can choose to reboot immediately, or later. However, if you choose to suppress the reboot, thesystem may be in an unsupported state until the system is rebooted. The installation log will recordwhether the system is rebooted at the end of the installation process.

4.4 To run a silent installation

Every option in the installation wizard can be given from the command-line or read from a responsefile. This type of installation is called a silent install.

• 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.

2012-05-0239

Installation

In the following example of giving the CMSPort parameter on the command-line, ellipses ([...])are shown to indicate where other installation options would normally be present:

setup.exe [...] CMSPort=6401 [...]

• Giving installation options in a response file

Installation options can be stored in a response file, which is a text file containing installation 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.exe [...] -r C:\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[...]

Note:The installation program returns the cursor to the command-line prompt when it starts. To run theinstallation program from a script, or to force the installation program to wait to complete before returningto the command-line, use the Windows Command Interpreter start /wait command to invokesetup.exe.

For example:start /wait setup.exe [<COMMAND_LINE_OPTIONS>]

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

4.4.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.

2012-05-0240

Installation

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

ExampleDescriptionSwitch parameter

setup.exe -w "C:\response.ini"

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

-w <FILENAME>

setup.exe -r "C:\response.ini"

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

-r <FILENAME>

setup.exe -q -r "C:\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.4.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 C:\response.ini:setup.exe -r C:\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.

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.

2012-05-0241

Installation

4.4.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 C:\response.ini:setup.exe -w C:\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.4.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 C:\response.ini, but overrides the response file's setting for the installation destination folder:setup.exe -r C:\response.ini InstallDir="C:\SAP\BusinessObjects BI platform"

4.4.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.

2012-05-0242

Installation

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 C:\SAP\BusinessObjects BI platform instead of the defaultfolder).setup.exe -q InstallDir="C:\SAP\BusinessObjects BI platform"



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.4.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 Windows for parameters specific to Windowsoperating systems.

2012-05-0243

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>

2012-05-0244

Installation


Destination folder into which the setup program will install.

When installing to a host that already has an installation of SAPBusinessObjects Business Intelligence platform, the value of InstallDirwill be automatically set to the same path as the existinginstallation.

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>

2012-05-0245

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>

2012-05-0246

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>

2012-05-0247

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 Microsoft SQL Server 2008 Express.

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>

2012-05-0248

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 Windows


Admin password to assign to the Microsoft SQL Server sa adminis-trative user account. Substitute <PASSWORD> with the password.

SQLExpressAdminPassword=<PASSWORD>

Username to assign to the Microsoft SQL Server user account usedby the CMS. Substitute <USERNAME> with the username.

SQLExpressBOEUserName=<USERNAME>

Admin password to assign to the Microsoft SQL Server user accountused by the CMS. Substitute <PASSWORD> with the password.

SQLExpressBOEUserPassword=<PASSWORD>

4.4.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, or

2012-05-0249

Installation

Oracle 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• 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 (installs bundled Microsoft SQL Server 2008 Express)

• PlatformServers.EventServer• PlatformServers.SystemLandscapeSupplier (SLD)• PlatformServers.WebAppContainerService (WACS)• AdaptiveProcessingServer (platform processing)• AdaptiveJobServer (scheduling)• Platform.RestWebService• Platform.Action.Framework.backend: Insight to Action Framework• 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)

2012-05-0250

Installation

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

• XcelsiusServers (Dashboards)• MobileServices

• MobileServers• MobileAddon (CMS plugin for Mobile)

• IntegrationServers: install all integration components• BWPublisherServer (SAP BW authentication and SAP BW Publisher support)

• MultitenancyManager• AdministratorTools: install all administrator tools

• UpgradeManager (Upgrade management tool)

• DeveloperTools: install all developer tool components• BOE64bitNETSDK (64-bit SAP BusinessObjects Business Intelligence platform .NET SDK)

• DataAccess install all database access components• DataAccess.DataFederator• DataAccess.MySQL• DataAccess.GenericJDBC• DataAccess.GenericODBC• DataAccess.GenericOLEDB• DataAccess.OptionalDataDirectODBC• DataAccess.MaxDB• DataAccess.SAPHANA• 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

2012-05-0251

Installation

• DataAccess.SAPBW• DataAccess.SAPERP• DataAccess.OData• DataAccess.Excel• DataAccess.XMLWebServices• DataAccess.SAP (security and data access for SAP BW and R/3 systems)• DataAccess.PersonalFiles• DataAccess.JavaBean• DataAccess.OpenConnectivity• DataAccess.HSQLDB• DataAccess.Derby• DataAccess.HadoopHive• 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.4.2.2 Response file example

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

2012-05-0252

Installation

Example:

In this example, the response file is named C:\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

### CMS cluster keyClusterKey=Crypto1

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

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

### Installation directoryinstalldir=C:\Program Files (x86)\SAP BusinessObjects\

### 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 port

2012-05-0253

Installation

siaport=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

### #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### 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

2012-05-0254

Installation

### 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### 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,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

2012-05-0255

Installation

2012-05-0256

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.

Launch the CMC by going to: Start > Programs > SAP BusinessObjects BI platform 4 > SAPBusinessObjects BI platform > SAP BusinessObjects BI platform Central Management Console.

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?

2012-05-0257

Post-Installation

Check the Windows Firewall settings by going to: Start > Settings > Control Panel > WindowsFirewall.

2. Is the URL correct??

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 or Windows AD single sign-on authentication system, select the systeminstead.

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.

Go to Start > Programs > SAP BusinessObjects BI platform 4 > SAP BusinessObjects BIplatform > SAP BusinessObjects BI platform Central Management Console.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 athttps://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 the

2012-05-0258

Post-Installation


Monitoring 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.• 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, seeTo enable SAP System Landscape Directory (SLD) support.

2012-05-0259

Post-Installation

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.

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.

2012-05-0260

Post-Installation

5. Ensure that the placeholders related to Introscope are set correctly:a. Change the %IntroscopeAgentEnableInstrumentation% placeholder from false to

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

Agent port number.d. Review %IntroscopeAgenEnterpriseManagerTransport% to ensure that the correct

network 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 C:\Program Files (x86)\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 C:\Program Files (x86)\Siebel\7.8\classes\SiebelJI.jar andC:\Program Files (x86)\Siebel\7.8\classes\SiebelJI_enu.jar to <BOE_INSTALL_DIR>\SAP BusinessObjects Enterprise XI 4.0\java\lib\siebel.

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

2012-05-0261

Post-Installation

For example, copy C:\Program Files (x86)\Siebel\7.8\classes\SiebelJI.jar andC:\Program Files (x86)\Siebel\7.8\classes\SiebelJI_enu.jar to <WAS_INSTALL_DIR>\lib\. If you installed the Tomcat web application server bundled with SAPBusinessObjects Business Intelligence platform, the folder is <BOE_INSTALL_DIR>\Tomcat6\lib.

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

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 BusinessObjects Enterprise XI4.0\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 BusinessObjects Enterprise XI 4.0\tomcat6\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

2012-05-0262

Post-Installation

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.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>\bin\ocijdbc11.dll

To: <BOE_INSTALL_DIR>\SAP BusinessObjects Enterprise XI 4.0\win64_x64.

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 BusinessObjects Enterprise XI 4.0\tomcat6\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

2012-05-0263

Post-Installation

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.

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 Intelligence(BI) platform installation by adding or removing installed components though the Windows ControlPanel.

It is recommended that you back up the CMS system database before modifying the BI platform.1. Run the Central Configuration Manager (CCM) by selecting Start > Programs > SAP

BusinessObjects Enterprise >BusinessObjects Enterprise >Central ConfigurationManager.The CCM screen appears.

2. Select all listed servers and click the Stop button.3. When all of the servers are stopped, close the CCM console.4. If you're using a newer Windows operating system, such as Windows Server 2008, go to: Start >

Control Panel > Programs and Features. If you're using an older Windows operating system, suchas Windows Server 2003, go to: Start > Control Panel > Add or Remove Programs.

5. Select SAP BusinessObjects Business Intelligence platform 4.0 Feature Pack 3 and click theChange/Remove button.The "Application Maintenance" screen appears.

6. Select any features you want to install; unselect any features you want to remove.

Features are grouped under the following headings:• "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.

2012-05-0264

Post-Installation

If you do not have a web application server in place for use with the BI platform, the installationprogram can install and configure a Tomcat web application server for you. It is recommendedthat you evaluate your requirements against information from your web application server vendorto determine which supported web application server would best suit your organization's needs.


• Servers

Server features include the Business Intelligence platform servers (such as processing andscheduling servers), major system components (such as the CMS, Event Server, bundleddatabase, version control system), and servers that integrate the BI platform into yourorganization's existing network infrastructure (such as PeopleSoft, Siebel, and SAP BW). Installservers if you plan to use the installed system for BI processing, such as a stand-alone CentralManagement Server (CMS) or as part of a CMS cluster.

• Administrator Tools

The Administrator Tools features help administrators maintain an installation.

• Developer Tools

If you plan to develop your own applications with a BI platform Software Development Kit (SDK),install the Developer Tools feature.

• Database Access

To access, analyze, and report on the data in your organization's existing databases, select theappropriate Database Access features. If your organization does not use a particular database,you can deselect the option to install it.

• Samples

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

• Help

To install help files, select this feature. If you do not need help files installed on your system, youcan deselect it.

7. Select Next to apply your changes.The setup program applies your changes and returns to the Control Panel applet.

The installation has been updated.

5.8.2 To repair SAP BusinessObjects Business Intelligence platform

2012-05-0265

Post-Installation

These instructions describe the process to repair an SAP BusinessObjects Business Intelligence platforminstallation from the Microsoft Windows Add or Remove Control Panel applet. This process restoresthe 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.1. Run the Central Configuration Manager (CCM) by selecting Start > Programs > SAP

BusinessObjects Enterprise >BusinessObjects Enterprise >Central ConfigurationManager.The CCM screen appears.

2. Select all listed servers and click the Stop button.3. When all of the servers are stopped, close the CCM console.4. If you're using a newer Windows operating system, such as Windows Server 2008, go to: Start >


5. Select SAP BusinessObjects Business Intelligence platform 4.0 Feature Pack 3 and click theChange/Remove button.The "Application Maintenance" screen appears.

6. Select Repair.The "Application Maintenance" screen disappears and the software is restored to its originalconfiguration. This may take a long time. When complete, the Control Panel appears.

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 product onwhich they depend. For example, for servers with SAP BusinessObjects Business Intelligence platformExplorer installed, SAP BusinessObjects Business Intelligence platform Explorer should be removedfirst, as it will not function without SAP BusinessObjects Business Intelligence platform.

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.

2012-05-0266

Post-Installation

• Configuration files

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

1. Go to: Start > All Programs > SAP BusinessObjects BI platform 4 > SAP BusinessObjects BIplatform > Central Configuration Manager.

2. Change the status of all servers to stopped.3. When all of the servers are stopped, close the CCM.4. If you're using a newer Windows operating system, such as Windows Server 2008, go to: Start >


5. Select SAP BusinessObjects Business Intelligence platform 4.0 Feature Pack 3.6. On newer Windows operating systems, select Uninstall. On older Windows operating systems,

select Change/Remove.7. Click through to confirm the removal.8. Select Finish to close the "System Setup" screen.

The software has been removed from the system.

5.9 When the administrator account password is lost

If the credentials for the SAP BusinessObjects Business Intelligence platform administrator accountare lost, consider whether another administrative account is available, and use it to change the passwordfor the SAP BusinessObjects Business Intelligence platform administrator account.

If this is not possible, refer to SAP Knowledge Base Article 1679970 - How to reset the Administratorpassword in Business Intelligence Platform 4.0.

2012-05-0267

Post-Installation

2012-05-0268

Post-Installation

Installing SAP BusinessObjects Business IntelligencePlatform Client Tools

The SAP BusinessObjects Business Intelligence (BI) Platform Client Tools can only be installed by adedicated installation program, and are no longer bundled with the installation of the BI platform servers.

The BI platform Client Tools installation program installs a suite of desktop clients on supported Windowsoperating systems only. Client Tools are not available for Unix or Linux operating systems.

Note:

• Although the Client Tools are supported on 64-bit operating systems, the Client Tools themselvesare only available as 32-bit applications.

• When installing a database driver for Client Tools on 64-bit operating systems, ensure that you installthe 32-bit version. A 32-bit application cannot use a 64-bit driver.

• If you install both the Client Tools and BI platform servers on the same 64-bit Windows operatingsystem, you must install both 32-bit and 64-bit database drivers on the machine. You must alsoensure that both 32-bit and 64-bit database connector middleware is installed and that their datasource configurations are identical, because Client Tools requests in this scenario may be handledby either of the two 32-bit or 64-bit Native Connectivity Services.

Some of the client applications that make up the Client Tools suite are also available with their ownstand-alone installation program. This allows you to install the client application by itself, without havingto install the Client Tools suite's "Custom" installation option.

Client Tools can co-exist on a system that also runs BI platform server software. When installing bothBI platform servers and Client Tools on the same system, it is recommended that the server components(including add-ons and language packs) are installed before Client Tools. This allows the Client Toolsto use same the same components as the server.

No keycode is required to install Client Tools, but you require administrative privileges for the accountbeing used to run the installation program.

If a file is in use during the installation, the installation program recommends a system reboot when theinstall is complete. Although the reboot can be postponed, and you can continue to use the systemafter the installation, the system may be in an unsupported state until it is rebooted. It is recommendedthat you restart the system at the end of an installation if a reboot is recommended.

The installation program requires a minimum screen resolution of 1,024 × 768 pixels. Using MicrosoftRemote Desktop Connection to run the installation program is supported, as long as a minimum screenresolution of 1,024 × 768 pixels is used.

2012-05-0269

Installing SAP BusinessObjects Business Intelligence Platform Client Tools

6.1 Desktop client applications

The following desktop client applications are installed by the SAP BusinessObjects Business IntelligencePlatform Client Tools installation program:• Web Intelligence Desktop• Business View Manager• Report Conversion Tool• Universe design tool• Web service query tool• Information design tool• Translation Management Tool• Data Federation Administration Tool• Widgets for SAP BusinessObjects Business Intelligence platform• Developer Components

For integrating BusinessObjects functionality into interactive web applications. Includes the BIplatform Java SDK, Web Services SDK, and .NET SDK.

• Data Access and Security

6.1.1 Web Intelligence Desktop

Web Intelligence Desktop is an ad-hoc analysis and reporting tool for business users with or withoutaccess to the SAP BusinessObjects Business Intelligence platform.

It allows business users to access and combine data from relational, online analytical processing (OLAP),spreadsheet, or text file sources, using familiar business terms in a drag-and-drop interface. Workflowsallow very broad or very narrow questions to be analyzed, and for further questions to be asked at anypoint in the analysis workflow.

Web Intelligence Desktop users can continue to working with Web Intelligence document files (.wid)even when unable to connect to a Central Management Server (CMS).

6.1.2 Business View Manager

Business View Manager allows users to build semantic layer objects that simplify underlying databasecomplexity.

2012-05-0270


Business View Manager can create data connections, dynamic data connections, data foundations,business elements, business views, and relational views. It also allows detailed column and row-levelsecurity to be set for the objects in a report.

Designers can build connections to multiple data sources, join tables, alias field names, create calculatedfields, and then use the simplified structure as a Business View. Report designers and users can thenuse the business view as the basis for their reports, rather than and building their own queries from thedata directly.

6.1.3 Report Conversion Tool

The Report Conversion Tool converts reports to Web Intelligence format and publishes them to a CentralManagement Server (CMS).

Reports can be retrieved from the CMS folders Public, Favorites, or Inbox. Once converted,reports publish to the same folder as the original Web Intelligence report, or to a different folder. Thetool does not convert all Web Intelligence features and reports. The level of conversion depends on thefeatures in the original report. Some features prevent the report from being converted. Other featuresare modified, reimplemented, or removed by the tool during conversion.

The Report Conversion Tool also lets you audit your converted reports. This helps identify reports thatcannot be fully converted by the Report Conversion Tool and explains why.

6.1.4 Universe design tool

Universe design tool (formerly Universe Designer) allows data designers to combine data from multiplesources in a semantic layer that hides database complexity from end users. It abstracts the complexityof data by using business rather than technical language to access, manipulate, and organize data.

Universe design tool provides a graphical interface to select and view tables in a database. The databasetables are represented as table symbols in a schema diagram. Designers can use this interface tomanipulate tables, create joins between tables, create alias tables, create contexts, and solve loops ina schema.

You can also create universes from metadata sources. Universe design tool is used for the universegeneration at the end of the creation process.

6.1.5 Query as a Web Service

2012-05-0271


Query as a Web Service is a wizard-based application that allows queries to be made into a web serviceand integrated with web-ready applications. Queries can be saved to create a catalog of standardqueries that application builders can select as required.

Business Intelligence (BI) content is usually bound to a specific user interface of BI tools. Query as aWeb Service changes this by allowing BI content to be delivered to any user interface that can processweb services.

Query as a Web Service is designed to work on top of any Microsoft Windows application the sameway as other web services. Query as a Web Service is based on the W3C web service specificationsSOAP, SDL, and XML. It has two main components:• Server component

The server component (included in Business Intelligence platform) stores the Query as a WebService catalog and hosts the published web services.

• Client tool

This is how business users create and publish their queries as a web service on the server. Youcan install the client tool on several machines that can access and share the same catalog storedon the server. The client tool communicates with the server components via web services.

Query as a Web Service allows web queries to be used as part of a range of client-side solutions,including:• Microsoft Office, Excel, and InfoPath• SAP NetWeaver• OpenOffice• Business rules and process management applications• Enterprise Service Bus platforms

6.1.6 Information design tool

Information design tool (formerly Information Designer) is an SAP BusinessObjects metadata designenvironment that enables a designer to extract, define, and manipulate metadata from relational andOLAP sources to create and deploy SAP BusinessObjects universes.

6.1.7 Translation Management Tool

SAP BusinessObjects Business Intelligence platform provides support for multilingual documents anduniverses. A multilingual document contains localized versions of universe metadata and documentprompts. A user can create reports, for example, from the same universe in their chosen languages.

2012-05-0272


Translation Management Tool (formerly Translation Manager) defines the multilingual universes andmanages translation of universes and other report and analytic resources in the CMS repository.

Translation Management Tool:• Translates universe or documents for a multilingual audience.• Defines the metadata language parts of a document, and the appropriate translation. It generates

external XLIFF format and imports XLIFF files to get translated information.• Lists the universe or document structure to be translated.• Lets you translate the metadata through the user interface, or though an external translation tool by

importing and exporting XLIFF files.• Creates multilingual documents.

6.1.8 Data Federation Administration Tool

The Data Federation Administration Tool (formerly Data Federator) is a rich client application that offerseasy-to-use features to manage your data federation service.

Tightly integrated in the SAP BusinessObjects Business Intelligence platform, the data federation serviceenables multi-source universes by distributing queries across disparate data sources, and lets youfederate data through a single data foundation.

The data federation administration tool lets you optimize data federation queries and fine-tune the datafederation query engine for the best possible performance.

You use the data federation administration tool to do the following:• Test SQL queries.

• Visualize optimization plans which detail how federated queries are distributed to each source.

• Compute “statistics” and set system parameters to fine-tune the data federation services and getthe best possible performance.

• Manage properties to control how queries are executed in each data source at the connector level.

• Monitor running SQL queries.

• Browse the history of executed queries.

6.1.9 Widgets for SAP BusinessObjects Business Intelligence platform

Widgets are mini-applications that allow easy and fast access to frequently used functions and providevisual information from your desktop. Widgets for SAP BusinessObjects Business Intelligence platform(formerly BI Widgets) allows your organization to provide access to existing Business Intelligence (BI)

2012-05-0273


content on SAP BusinessObjects Business Intelligence platform, or you can add Web Dynpro applicationsthat are registered as XBCML (Extensible Business Client Markup Language) widgets on the SAPNetWeaver Application Servers as desktop widgets.

To render XBCML widgets on the user's desktop, SAP Web Dynpro Flex Client is used. The SAP WebDynpro Flex Client is a rendering engine based on Adobe Flex which is used for rendering widgets. Fordetails about how to configure Web Dynpro applications, see the To enable widgets on the SAPNetWeaver Application Server topic in the Widgets for SAP BusinessObjects User Guide.

Note:The SAP Web Dynpro Flex Client support for XBCML Widgets begins in release 7.0 EhP2 SP3. FlexClient queue support is confined only to Flex Client issues found in XBCML widgets in these specifiedreleases.

With widgets for SAP BusinessObjects Business Intelligence platform, you search or browse for existingcontent, such as Web Intelligence documents, Dashboards models, and Web Dynpro applications, thenpaste the information onto your desktop so it is available when needed.

As a widget, the content gains the following features from the widget framework:• User-controlled size and positioning• Automatic refresh• Optional setting as the top application window• Full SAP BusinessObjects Business Intelligence platform security (Web Intelligence report parts

and Dashboards models only)• Saved display• Saved data context state (Web Intelligence report parts only)• Web Intelligence OpenDocument links to detailed reports (Web Intelligence documents only)• Tabbed views (Dashboards models only)

6.2 To run an interactive installation of Client Tools

When the installation program starts, a series of prerequisite checks are performed. The result of thistest is displayed for your information. If your system does not meet the minimum requirements, theinstallation program will not install. If the installation program detects a previously installed version, amessage is displayed to inform you of the options available for side-by-side installations.

The installation program creates a human-readable log file. To read detailed information about theinstallation program's activities, see the installation log file after the installation is complete.1. Log in at the console or use Microsoft Remote Desktop connection with a minimum screen resolution

of 1024 × 768.2. Locate the installation program. If you are installing from a physical media, look for setup.exe in

the top-level folder. If you are installing from a compressed download, extract it and locate setup.exe.

3. Run setup.exe by double-clicking it in Windows Explorer or calling it from the command-line.

2012-05-0274


A log file containing information on the installation process is saved to <CLIENT_INSTALL_DIR>\InstallData\logs\<DATE>\InstallDU<COMPONENT>.log.

4. Select a language for the installation 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 support is automaticallyinstalled on your system.

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 Windows componentsconfigured by the installation program, such as Start menu shortcuts. These named cannot bechanged later and are not affected by language settings once the installation is complete.

5. The installation program checks for required components. Review the results and decide whetherto 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 a missing or unsupported component is optional, you have the option to either continuewith the installation or stop and correct the condition. The installation program will provide informationon how to correct the condition.During a silent installation, the installation program does not display the results of dependencyprerequisites. If a critical component is not found, the installation program writes an error to theinstallation log file and aborts. If an optional component is not found, the missing or unsupportedcomponent is noted in the installation log file.

6. Review the recommendations made by the installation program welcome screen.7. Review the agreement and select I accept the License Agreement.8. Select any language for which you want language support to be installed. A language pack allows

BI platform Client Tools to interact with users in a specific language.Users can select their preferred language in the preference settings for each language tool.

9. Review and confirm the destination folder setting.

If you have already installed SAP BusinessObjects products, the Destination Folder field is noteditable, and the path to the existing folder is displayed.

Note:

• The use of Unicode characters in the destination folder path is not supported.• Ensure that the destination folder is not set to the same folder in which the installation program

has been extracted.

10. Review the list of features to install. Only features with a selected checkbox is installed.The following components can be selected:• Client components

Desktop client applications:• Web Intelligence Desktop• Business View Manager• Report Conversion Tool• Universe design tool

2012-05-0275


• Web service query tool• Information design tool• Translation Management Tool• Data Federation Administration Tool• Widgets for the BI platform

• Developer components

Software Development Kits (SDK) for developing your own applications that integrate into SAPBusinessObjects Business Intelligence platform:• BI platform Java SDK• BI platform Web Services SDK• BI platform .NET SDK• SAP Crystal Reports Java SDK

• Data Access and Security

Drivers that allow client tools to access supported reporting systems, or third-party authenticationfor Enterprise Resource Planning (ERP) systems.

11. Review the confirmation screen and start the installation when ready.


6.3 To run a silent installation of Client Tools

Every option in the installation wizard can be given from the command-line. This type of installation 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.exe [...] CMSPort=6401 [...]

• Giving installation options in a response file

Installation options can be stored in a response file, which is a text file containing installation 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.

2012-05-0276


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.exe [...] -r C:\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[...]

Note:The installation program returns the cursor to the command-line prompt when it starts. To run theinstallation program from a script, or to force the installation program to wait to complete before returningto the command-line, use the Windows Command Interpreter start /wait command to invokesetup.exe.

For example:start /wait setup.exe [<COMMAND_LINE_OPTIONS>]

For a complete list of installation options, seeInstallation option parameters for Client Tools. For anexample of a response file, see Response file example.

6.3.1 Command-line silent install of Client Tools

You can install Client Tools with one command by giving parameters on the command-line. This isreferred to as a “silent” installation. When parameters are supplied on the command-line, the installationwill not prompt for information.

6.3.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 C:\response.ini:setup.exe -r C:\response.ini

2012-05-0277


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.



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.

6.3.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 C:\response.ini:setup.exe -w C:\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.

6.3.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 C:\response.ini, but overrides the response file's setting for the installation destination folder:setup.exe -r C:\response.ini InstallDir="C:\SAP\BusinessObjects BI platform"

2012-05-0278


6.3.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 C:\SAP\BusinessObjects BI platform instead of the defaultfolder).setup.exe -q InstallDir="C:\SAP\BusinessObjects BI platform"



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.

6.3.2 Installation option parameters for Client Tools

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

2012-05-0279


Table 6-1: Installation option parameters


Destination folder into which the setup program will install.

When installing to a host that already has an installation of SAPBusinessObjects Business Intelligence platform, the value of InstallDirwill be automatically set to the same path as the existinginstallation.

Note:

• The use of Unicode characters in the destination folder path isnot supported.

• Ensure that the destination folder is not set to the same folderin which the installation program has been extracted.

InstallDir=<PATH>

2012-05-0280



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-colondelimited list without spaces, within quotes, to separate each code.In the following example, language support for English, 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>

2012-05-0281



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>

List of components to install. To select multiple features, use acomma-delimited list without spaces to give each code. In the following example, Web Intelligence Desktop, Business View Manager,and Report Conversion Tool are selected for install:Features=WebI_Rich_Client,Business_View_Manager,Report_Conversion,[...]

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

Features=<CODE>

6.3.2.1 Feature codes for Client Tools

2012-05-0282


Use the following feature codes to select features for installation. To select multiple features, separateeach feature code with a comma, without spaces. For example, the following feature list selects WebIntelligence Desktop, Business View Manager, and Report Conversion Tool clients for installation:features=WebI_Rich_Client,Business_View_Manager,Report_Conversion,[...]

• root: install all features• ClientComponents: install all client components

• WebI_Rich_Client (Web Intelligence Desktop)• Business_View_Manager• Report_Conversion (Report Conversion Tool)• Universe_Designer (Universe design tool)• QAAWS (Web service query tool)• InformationDesignTool• Translation_Manager (Translation management tool)• DataFederationAdministrationTool• biwidgets (Widgets for SAP BusinessObjects Business Intelligence platform)

• DevComponents: install all developer tool components• JavaSDK (SAP BusinessObjects Business Intelligence platform Java SDK)• WebSDK (SAP BusinessObjects Business Intelligence platform Java Web Services SDK)• DotNetSDK (SAP BusinessObjects Business Intelligence platform .NET SDK)• CRJavaSDK (SAP Crystal Reports Java SDK)

• DataAccess install all database access components• DataFed_DataAccess (Data Federator)• HPNeoView_DataAccess• MySQL_DataAccess• GenericODBC_DataAccess• GenericOLEDB_DataAccess• GenericJDBC_DataAccess• MaxDB_DataAccess• SalesForce_DataAccess (Salesforce.com)• Netezza_DataAccess• Microsoft_DataAccess• Ingres_DataAccess• Greenplum_DataAccess• IBMDB2• Informix_DataAccess• Progress_Open_Edge_DataAccess• Oracle_DataAccess• Sybase_DataAccess• TeraData_DataAccess• SAPBW_DataAccess• SAP_DataAccess

2012-05-0283


• PersonalFiles_DataAccess• JavaBean_DataAccess• OpenConnectivity_DataAccess• HSQLDB_DataAccess• Derby_DataAccess• Essbase_DataAccess• PSFT_DataAccess (PeopleSoft Enterprise)• JDE_DataAccess (JD Edwards EnterpriseOne)• Siebel_DataAccess (Siebel Sign-on Server)• EBS_DataAccess (Oracle E-Business Suite)

6.3.2.2 Response file example for Client Tools

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

Example:

In this example, the response file is named C:\response.ini.### Installation directoryinstalldir=C:\Program Files (x86)\SAP BusinessObjects\

### #property.SelectedLanguagePack.description#selectedlanguagepacks=cs;da;nl;en;fi;fr;de;hu;it;ja;ko;nb;pl;pt;ru;zh_cn;sk;es;sv;th;zh_tw;tr

### Setup UI languagesetupuilanguage=en

### Available features### ------------------### root### ClientComponents### WebI_Rich_Client### Business_View_Manager### Report_Conversion### Universe_Designer### QAAWS### InformationDesignTool### Translation_Manager### DataFederationAdministrationTool### biwidgets### DevComponents### JavaSDK### WebSDK### DotNetSDK### CRJavaSDK### DataAccess### DataFed_DataAccess### HPNeoView_DataAccess### MySQL_DataAccess### GenericODBC_DataAccess### GenericOLEDB_DataAccess### GenericJDBC_DataAccess### MaxDB_DataAccess### SalesForce_DataAccess### Netezza_DataAccess

2012-05-0284


### Microsoft_DataAccess### Ingres_DataAccess### Greenplum_DataAccess### IBMDB2### Informix_DataAccess### Progress_Open_Edge_DataAccess### Oracle_DataAccess### Sybase_DataAccess### TeraData_DataAccess### SAPBW_DataAccess### SAP_DataAccess### PersonalFiles_DataAccess### JavaBean_DataAccess### OpenConnectivity_DataAccess### HSQLDB_DataAccess### Derby_DataAccess### Essbase_DataAccess### PSFT_DataAccess### JDE_DataAccess### Siebel_DataAccess### EBS_DataAccessfeatures=WebI_Rich_Client,Business_View_Manager,Report_Conversion,Universe_Designer,QAAWS,InformationDesignTool,Translation_Manager,DataFederationAdministrationTool,biwidgets,ClientComponents,JavaSDK,WebSDK,DotNetSDK,CRJavaSDK,DevComponents,DataFed_DataAccess,HPNeoView_DataAccess,MySQL_DataAccess,GenericODBC_DataAccess,GenericOLEDB_DataAccess,GenericJDBC_DataAccess,MaxDB_DataAccess,SalesForce_DataAccess,Netezza_DataAccess,Microsoft_DataAccess,Ingres_DataAccess,Greenplum_DataAccess,IBMDB2,Informix_DataAccess,Progress_Open_Edge_DataAccess,Oracle_DataAccess,Sybase_DataAccess,TeraData_DataAccess,SAPBW_DataAccess,SAP_DataAccess,PersonalFiles_DataAccess,JavaBean_DataAccess,OpenConnectivity_DataAccess,HSQLDB_DataAccess,Derby_DataAccess,Essbase_DataAccess,PSFT_DataAccess,JDE_DataAccess,Siebel_DataAccess,EBS_DataAccess,DataAccess,root

6.4 Making changes to Client Tools

6.4.1 To modify Client Tools

These instructions describe the process to modify your Client Tools installation by adding or removinginstalled components though the Windows Control Panel.1. If you're using a newer Windows operating system, such as Windows Server 2008, Vista, or Windows

7, go to: Start > Control Panel > Programs and Features. If you're using an older Windowsoperating system, such as Windows Server 2003 or Windows XP, go to: Start > Control Panel >Add or Remove Programs.

2. Select SAP BusinessObjects Business Intelligence platform Client Tools and click the Changebutton.The "Application Maintenance" screen appears.

3. Select any features you want to install; unselect any features you want to remove.The following components can be selected:• Client components

Desktop client applications:

2012-05-0285


Web Intelligence Desktop•• Business View Manager• Report Conversion Tool• Universe design tool• Web service query tool• Information design tool• Translation Management Tool• Data Federation Administration Tool• Widgets for SAP BusinessObjects Business Intelligence platform

• Developer components

Software Development Kits (SDK) for developing your own applications that integrate into SAPBusinessObjects Business Intelligence platform:• SAP BusinessObjects Business Intelligence platform Java SDK• SAP BusinessObjects Business Intelligence platform Web Services SDK• SAP BusinessObjects Business Intelligence platform .NET SDK• SAP Crystal Reports Java SDK

• Data access

Drivers that allow client tools to access supported databases.

4. Select Next to apply your changes.The setup program applies your changes and returns to the Control Panel applet.

The installation has been updated.

6.4.2 To repair a Client Tools installation

These instructions describe the process to repair a Client Tools installation from the Microsoft WindowsAdd or Remove Control Panel applet. This process restores the files originally installed by the setupprogram.

It is recommended that you back up your system before running a repair.1. If you're using a newer Windows operating system, such as Windows Server 2008, Vista, or Windows

7, go to: Start > Control Panel > Programs and Features. If you're using an older Windowsoperating system, such as Windows Server 2003 or Windows XP, go to: Start > Control Panel >Add or Remove Programs.

2. Select "SAP BusinessObjects BI platform 4.0 FP3" and click the Change button.The "Application Maintenance" screen appears.

3. Select Repair.The "Application Maintenance" screen disappears and the software is restored to its originalconfiguration. This may take a long time. When complete, the Control Panel appears.

2012-05-0286


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

6.4.3 To remove Client Tools

The following steps remove SAP BusinessObjects Business Intelligence platform Client Tools from asystem.

Note:Add-on products that with dependencies on other products should be removed before the product onwhich they depend. For example, for SAP BusinessObjects Business Intelligence platform servers withSAP BusinessObjects Business Intelligence platform Explorer installed, SAP BusinessObjects BusinessIntelligence platform Explorer should be removed first, as it will not function without SAP BusinessObjectsBusiness Intelligence platform.

1. If you're using a newer Windows operating system, such as Windows Server 2008, Vista, or Windows7 go to: Start >Control Panel > Programs and Features. If you're using an older Windows operatingsystem, such as Windows Server 2003 or Windows XP, go to: Start > Control Panel > Add orRemove Programs.

2. Select the SAP BusinessObjects BI platform Client Tools XI 4.0 to remove and click Remove.

Note:If you have installed a Client Tools component more than once, each instance will appear in theseparately.

For example, if Web Intelligence Desktop was installed once by the Client Tools installation program,and then again with a stand-alone installation program, there is an entry in the "Add or RemovePrograms" list for both Web Intelligence Desktop and Client Tools (containing a separate installationof Web Intelligence Desktop). Either can be removed without affecting the other. To remove the toolentirely, remove both Web Intelligence Desktop and Client Tools.

3. Confirm that you want to remove the selected components.The appropriate files are removed and the necessary configuration is completed.

4. Click Finish.

The Client Tools have been uninstalled and you are returned to the Control Panel.

The SAP BusinessObjects Business Intelligence platform Client Tools have now been removed fromthe system. Files that were not installed by the installation program, such as those created or modifiedpost-install, will not be removed.

6.5 Upgrading Client Tools

2012-05-0287


The Client Tools installation program will not modify existing previous versions of SAP BusinessObjectsBusiness Intelligence (BI) platform Client Tools. BI platform Client Tools are supported when installedon systems that also contain the following previous Client Tool versions:• SAP BusinessObjects Business Intelligence platform XI 3.1 (any version)• BusinessObjects Enterprise XI 3.0• BusinessObjects Enterprise XI R 2.0The installation of BI platform Client Tools with Client Tools form BusinessObjects Enterprise 10 orBusinessObjects Enterprise XI is not supported and you may encounter compatibility issues.

2012-05-0288


More Information

LocationInformation Resource

http://www.sap.comSAP product information

http://help.sap.com/businessobjects

Access the most up-to-date English documentation covering all SAPBusinessObjects products at the SAP Help Portal:• http://help.sap.com/bobi (Business Intelligence)• http://help.sap.com/boepm (Enterprise Performance Management)• http://help.sap.com/boeim (Enterprise Information Management)

Certain guides linked to from the SAP Help Portal are stored on the SAPService Marketplace. Customers with a maintenance agreement havean authorized user ID to access this site. To obtain an ID, contact yourcustomer support representative.

To find a comprehensive list of product documentation in all supportedlanguages, visit:http://help.sap.com/boall.

SAP Help Portal

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

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.

SAP Support Portal

http://www.sdn.sap.com/irj/sdn/bi-sdk-dev

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

http://www.sdn.sap.com/irj/boc/articles

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

2012-05-0289

More Information

http://www.sap.com

http://help.sap.com/businessobjects

http://help.sap.com/bobi

http://help.sap.com/boepm

http://help.sap.com/boeim

http://help.sap.com/boall

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

http://www.sdn.sap.com/irj/sdn/bi-sdk-dev

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

http://www.sdn.sap.com/irj/boc/articles

LocationInformation Resource

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

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

2012-05-0290

More Information

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

client tools 69platform 16

A

account permissions 16administrator password 67Auditing Data Store

preparing for 18

B

BI Widgetssee Widgets for SAP

BusinessObjects BusinessIntelligence platform 73

Business View Manager 70

C

CA Wily Introscopepost-install configuration 60support 23

check-listinstallation 23

Client Tools 11, 7064-bit vs. 32-bit 69installation 69, 74languages 69repair 86response file 84silent install 77uninstallation 87upgrade from previous versions 87

clientsBusiness View Manager 70Data Federation Administration

Tool 73Data Federator. See Data

Federation Administration Tool73

Information design tool 72Information Designer. See

Information design tool 72Query as a Web Service 72Report Conversion Tool 71Translation Management Tool 72Universe design tool 71Web Intelligence Desktop 70

clients (continued)Widgets for SAP BusinessObjects

Business Intelligence platform73

CMClaunching 57troubleshooting 57

CMS system databasepreparing for 18

command-lineinstallation 39installation program parameters 40

components, new 11

D

Data Federation Administration Tool73

databasechoosing 14

DB2extra requirements 19

deploymentweb applications 59

diagnostic tests 64disaster mitigation

reset administrator password 67

E

Enterprise Resource Planning (ERP)23

F

feature codesclient 82Enterprise 49

features, new 11

I

Information design tool 72installation

account permissions 16check-list 23client tools 69Client Tools 74Client Tools feature codes 82Client Tools silent install 77

installation (continued)command-line 39, 40custom 31, 33Enterprise feature codes 49expand 31full 28installation program 26JD Edwards EnterpriseOne 62methods 25Oracle EBS integration 62parameters 43planning 11post-install 57preparation for 15requirements 16response file 39, 41, 42, 77, 78response file example 52screen resolution 69Siebel integration 61silent 42, 79software removal 66type 27web tier 37

installation programto run 26

Introscopesee CA Wily Introscope 23

J

JD Edwards integration 62

L

languages 11

M

Monitoring Tool 64

N

networkpermissions 17

O

Oracle E-Business Suite 62

2012-05-0291

P

password reset 67permissions

for installation account 16network 17

planning installation 11post-installation 57

diagnostic tests 64modification 64, 85repair 65

Q

Query as a Web Service 72

R

reboot suppression 39remove software 66

Client Tools 87repair 65, 86Report Conversion Tool 71

requirements 16response file 41, 42, 77, 78

Client Tools feature codes 82Enterprise feature codes 49example 52example for Client Tools 84parameters 43

S

SAP Host Agent 15, 20, 21SAP System Landscape Directory

(SLD) 20, 21screen resolution

installation 69Siebel integration 61silent installation 76

parameters 79SMD Agent 22

post-install configuration 60Sybase

extra requirements 20

System Landscape Directory (SLD)Data Supplier (DS) 59

T

Translation Management Tool 72

U

uninstallation 66Client Tools 87

Universe design tool 71Universe Designer

see Universe design tool 71upgrade

Client Tools 87

W

web applications 59Web Intelligence Desktop 70Widgets for SAP BusinessObjects

Business Intelligence platform 73

2012-05-0292

Index