SAP BusinessObjects Enterprise Installation Guide SAP BusinessObjects Enterprise 4.

2011-01-10

Copyright

2011 SAP AG. All rights reserved.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.These materials are subject to change without notice. These materials are provided 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 or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. 2011-01-10

Contents

Chapter 1

Introduction.............................................................................................................................5 About this Document...............................................................................................................5 Purpose...................................................................................................................................5 Integration................................................................................................................................5 Constraints..............................................................................................................................6 Information Available in SAP Service Marketplace....................................................................6 Planning..................................................................................................................................7 New features and components.................................................................................................8 Enterprise Resource Planning (ERP) integration.......................................................................9 Upgrade support....................................................................................................................10 Object types and feature requirements..................................................................................10 Product co-existence.............................................................................................................11 Web application servers.........................................................................................................12 Web servers..........................................................................................................................13 Database servers...................................................................................................................13 Preparation............................................................................................................................15 System requirements.............................................................................................................15 Installing SAP BusinessObjects Enterprise on an HPUX 64-bit system...................................16 Account permissions..............................................................................................................16 Network permissions.............................................................................................................18 Preparing the CMS system or Auditing Data Store database.................................................19 Extra requirements for IBM DB2............................................................................................21 Extra requirements for Sybase...............................................................................................22 Set ulimit to unlimited.............................................................................................................23 SAP support..........................................................................................................................23 Support for SAP System Landscape Directory (SLD)............................................................23 Support for SAP Solution Manager Diagnostics (SMD).........................................................24 Support for CA Wily Introscope.............................................................................................25 Final checklist.........................................................................................................................26

1.1 1.2 1.3 1.4 1.5

Chapter 2

2.1 2.1.1 2.2 2.2.1 2.2.2 2.3 2.4 2.5

Chapter 3

3.1 3.1.1 3.1.2 3.1.3 3.2 3.2.1 3.2.2 3.3 3.4 3.4.1 3.4.2 3.4.3 3.5

2011-01-10

Contents

Chapter 4

Installation.............................................................................................................................27 To run an interactive installation.............................................................................................27 To select an install type..........................................................................................................29 While the installation program runs.........................................................................................40 When installation is complete.................................................................................................40 To run a silent installation.......................................................................................................40 Command-line switch parameters..........................................................................................41 Installation option parameters.................................................................................................44 Post-Installation....................................................................................................................57 Launching the CMC...............................................................................................................57 Troubleshooting login issues..................................................................................................57 Creating additional Adaptive Processing Servers...................................................................58 Deploying web applications....................................................................................................59 SAP support..........................................................................................................................59 To configure System Landscape Directory (SLD) Data Supplier (DS) post installation...........59 To configure SMD Agent post installation..............................................................................60 To configure CA Wily Introscope Agent post installation........................................................60 Third-party ERP integration.....................................................................................................61 To enable Siebel Enterprise integration..................................................................................61 To enable JD Edwards EnterpriseOne integration...................................................................62 To enable Oracle E-Business Suite (EBS) integration.............................................................62 Post-install diagnostic checks.................................................................................................63 Making changes to SAP BusinessObjects Enterprise.............................................................64 To modify SAP BusinessObjects Enterprise...........................................................................64 To repair SAP BusinessObjects Enterprise............................................................................65 To remove SAP BusinessObjects Enterprise..........................................................................65 When the administrator account password is lost..................................................................66 To reset the SAP BusinessObjects Enterprise administrator account password.....................67 More Information...................................................................................................................69 71

4.1 4.1.1 4.1.2 4.1.3 4.2 4.2.1 4.2.2

Chapter 5

5.1 5.2 5.3 5.4 5.5 5.5.1 5.5.2 5.5.3 5.6 5.6.1 5.6.2 5.6.3 5.7 5.8 5.8.1 5.8.2 5.8.3 5.9 5.9.1
Appendix A Index

2011-01-10

Introduction

Introduction

This document guides you through the installation of SAP BusinessObjects Enterprise.

1.1 About this Document

The following documentation provides administrators with information, procedures, and options for the installation, removal, and modification of an SAP BusinessObjects Enterprise server. Two versions of this guide exist: SAP BusinessObjects Enterprise Installation Guide for Unix: for use with Unix or Linux operating systems (this document).

SAP BusinessObjects Enterprise Installation Guide for Windows: for use with Microsoft Windows operating systems.

1.2 Purpose
This document is intended for system administrators installing SAP BusinessObjects Enterprise. For the latest information, patches, and other information, visit the SAP BusinessObjects support site: ser vice.sap.com/bosap-support.

1.3 Integration
SAP BusinessObjects Enterprise is a suite of enterprise-level business intelligence analysis and reporting systems. The suite will integrate into your existing network, database, authentication, security, and operating systems. For an overview of the technologies and architecture used in SAP BusinessObjects Enterprise, and how they can fit into your organization's existing infrastructure, read the SAP BusinessObjects Enterprise Planning Guide.

2011-01-10

Introduction

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

1.5 Information Available in SAP Service Marketplace

Information on the following areas is available in the SAP Service Marketplace. Documentation
Description Internet Address Title

Overview of SAP BusinessObjects En- service.sap.com/bosap-support SAP BusinessObterprise documentation. jects Enterprise Master Guide Overview of new features in SAP Busi- service.sap.com/bosap-support SAP BusinessObnessObjects Enterprise. jects Enterprise What's New Guide How to upgrade an existing installation service.sap.com/bosap-support SAP BusinessObto the most current version of SAP jects Enterprise UpBusinessObjects Enterprise. grade Guide Detailed instructions for deploying web service.sap.com/bosap-support SAP BusinessObapplications to supported web applicajects Enterprise Web tion servers. Application Deployment Guide Administrative documentation for setting service.sap.com/bosap-support SAP BusinessObup and maintaining an SAP BusinessObjects Enterprise Adjects Enterprise server. ministrator Guide For a detailed list of specific platform, database, web application server, web server, and other systems supported by SAP BusinessObjects Enterprise, consult the Supported Platforms Guide, available at http://service.sap.com/bosap-support.

2011-01-10

Planning

Planning

SAP BusinessObjects Enterprise can be installed on Windows, Unix, or Linux platforms, with a combination of supported web servers, web application servers, database servers, and web technologies. You decide how the components that make up SAP BusinessObjects Enterprise will be deployed. A small development deployment might use the setup program's default options to install SAP BusinessObjects Enterprise, a database, and a web application server on a single computer system. A larger scale deployment might install individual server components on dedicated systems to host individual server functions over a network. For example: a dedicated host for a web application server; a dedicated host for the SAP BusinessObjects Enterprise core system; and a dedicated host for the database. Before installing: Review your systems to ensure they meet the basic requirements. For a detailed list of supported environments and hardware requirements, consult the Supported Platforms Guide available on the SAP BusinessObjects Enterprise support site at ser vice.sap.com/bosap-support. This document includes specific version and patch-level requirements for web application servers, web browsers, databases, and operating systems. For more information on how to plan your installation, see the Architecture section of the SAP BusinessObjects Enterprise Planning Guide. For more information on the documentation available, see the SAP BusinessObjects Enterprise Master Guide. Both guides are available on the SAP BusinessObjects Enterprise support site at service.sap.com/bosap-support. When setting up a deployment comprised of two or more hosts, ensure that the hosts can communicate with each other across the network. Decide whether to use the included DB2 database server. If you do not have a database server in place for use with SAP BusinessObjects Enterprise, the installation program can install and configure one for you. It is recommended that you evaluate your requirements against information from your database server vendor to determine which supported database would best suit your organization's requirements. Note: An existing database must have database user accounts with the appropriate database privileges ready, and the appropriate drivers must be installed and verified as working. The setup program attempts to connect to, and initialize, the database as a part of the installation process. The installation program will only install a database on the local host. It cannot install across a network. Decide whether to use the included Tomcat web application server.

2011-01-10

Planning

If you do not have a web application server system to serve SAP BusinessObjects Enterprise web applications, the installation program can install and configure one for you. It is recommended that you evaluate your requirements against information from your web application server vendor to determine which supported database would best suit your organization's requirements. To use any other supported web application server, it must be installed, configured, enabled, and accessible before you install SAP BusinessObjects Enterprise. The installation program will only install Tomcat to the local machine. It cannot install to remote systems across a network. Decide which installation option to use. The installation program offers three installation options: 1. "Full": install all available components, including a bundled web application server and database server. 2. "Custom / Expand": select and install all or any of the available components. 3. "Web Tier": install web applications on a dedicated web application server. You can use an previously installed web application server, or the bundled Tomcat web application server. Determine the location of the components to be installed. This includes the specific subnet, machines, database, security, or cluster systems to be used.

2.1 New features and components

The following components are now integrated into the SAP BusinessObjects Enterprise XI 4.0 installation program, and no longer require a separate installation: Enterprise Resource Planning The installation program now includes support for ERP integration (SAP Business Warehouse (BW), Siebel Enterprise, PeopleSoft Enterprise, JD Edwards EnterpriseOne) and portals (Microsoft SharePoint, 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 Enterprise and enables you to move Business Intelligence (BI) resources from one system to another without affecting resource dependencies. It also enables you to manage different versions of BI resources, manage dependencies of BI resources, and roll back a promoted resource to restore the destination system to an earlier state. The installation program can install and configure the Subversion version control system, or use an existing installation of Subversion or ClearCase. Lifecycle management console replaces Upgrade Management Tool for promotion workflows. SAP Solution Manager support

2011-01-10

Planning

The installation program can now integrate SAP BusinessObjects Enterprise into the SAP Solution Manager infrastructure. This allows system inventory and performance instrumentation tools like SAP System Landscape Directory (SLD), SAP Solution Manager Diagnostics (SMD), and CA Wily Introscope, and IBM Tivoli. Data Federation Data federation enables multi-source universes by distributing queries across disparate data sources, and lets you federate data through a single data foundation. Mobile server support Mobile server support allows your users to remotely access business intelligence (BI) reports, metrics, and real-time data from a wireless device. SAP BusinessObjects Dashboard Design (formerly Xcelsius) server support SAP BusinessObjects Dashboard Design is a tool for data visualization and the creation of dynamic, interactive dashboards. Language support Supported languages are now only installed by the installation program. Note: Carefully consider which languages need to be installed for your organization before installing them. To add or remove language support later requires that you remove and re-install SAP BusinessObjects Enterprise. SAP BW publishing servers The ability to publish reports to SAP BW no longer requires a separate installation. WDeploy command-line and GUI tools The WDeploy tool is now installed with both command-line and graphical user interface (GUI) support. Note: The SAP BusinessObjects Enterprise installation program no longer includes Client Tool components. To install Client Tools, use the dedicated SAP BusinessObjects Enterprise Client Tools installation program.

2.1.1 Enterprise Resource Planning (ERP) integration

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

2011-01-10

Planning

Note: SAP GUI must be installed before using OLAP Data Access (ODA), SAP BusinessObjects Analysis (formerly Voyager), or BW connections. Siebel Enterprise Oracle E-Business Suite JD Edwards EnterpriseOne PeopleSoft Enterprise

Note: SAP ERP and BW support is installed by default. Use the Custom / Expand installation option to deselect SAP integration support if you do not want support for SAP ERP or BW. Support for Siebel Enterprise, Oracle E-Business Suite, JD Edwards EnterpriseOne, or PeopleSoft is not installed by default. Use the "Custom / Expand" installation option to select and install integration for non-SAP ERP systems.

For detailed information on the specific versions supported by SAP BusinessObjects Enterprise, consult the Supported Platforms Guide, available at service.sap.com/bosap-support. To configure ERP integration, see the SAP BusinessObjects Enterprise Administrator Guide.

2.2 Upgrade support

To upgrade to SAP BusinessObjects Enterprise XI 4.0, you must install SAP BusinessObjects Enterprise XI 4.0, then migrate settings and content using the Upgrade management tool. For information on how to upgrade from a previous version, see the SAP BusinessObjects Enterprise Upgrade Guide. When the installation program detects a previously installed version of SAP BusinessObjects Enterprise, it presents the option to perform a side-by-side installation, which installs the new version, leaving the previously installed version intact. A system can host more than one version of SAP BusinessObjects Enterprise, although system performance may be degraded if both are running at once.

2.2.1 Object types and feature requirements

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

10

2011-01-10

Planning

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

BI workspaces (Dashboards) Crystal reports Dashboard Design and Presentation Design (Xcelsius) data Explorer Interactive Analysis (Web Intelligence) documents and publications Lifecycle management console (LifeCycle Manager) data Mobile Universes, connections Analysis, edition for OLAP workspaces Web service query tool (QaaWS)

BI workspace Services none none none Connectivity Processing Services Platform Processing Services or Platform Scheduling Services CMS plugin for Mobile Connectivity Processing Services none Connectivity Processing Services

2.2.2 Product co-existence

Several SAP BusinessObjects Enterprise products can exist on the same host. Note: All SAP BusinessObjects Enterprise products installed at your organization must have the same patch level. For example, if your organization upgrades SAP BusinessObjects Enterprise server products to a service pack or fix pack, all add-ons, Client Tools, and stand-alone products must also be upgraded. Similarly, if one product is downgraded, all other products should also be downgraded. To install add-on products, ensure that any required server components are present. A dependency check that identifies missing or outdated components is run by SAP BusinessObjects installation programs. If a dependency requirement is not met, the installation program identifies and suggests ways to meet the requirement. An add-on product which requires server components will not install until the appropriate server components are available. Mid-market server products, such as SAP Crystal Reports Server OEM Edition, cannot be installed on the same host as SAP BusinessObjects Enterprise XI 4.0.

11

2011-01-10

Planning

When installing SAP BusinessObjects Enterprise products, the user has the option to select a custom destination parent folder, into which the software is installed. Subsequent installations of other SAP BusinessObjects Enterprise products uses the same folder given for the original installation, and cannot be changed. If an SAP BusinessObjects Enterprise product is removed from a host, any remaining SAP BusinessObjects Enterprise product installation will be unaffected. Any component shared by the both installations will remain, and will only be removed when the last product that requires the shared component is removed. Add-on products with dependencies on other products should be removed before the product on which they depend.

2.3 Web application servers

You can integrate SAP BusinessObjects Enterprise with a Java web application server. If you do not have a web application server in place for use with SAP BusinessObjects Enterprise, the installation program can install and configure a Tomcat 6.0 web application server for you. It is recommended that you evaluate your requirements against information from your web application server vendor to determine which supported web application server would best suit your organization's requirements. Note: When configuring a production environment, it is recommended that the web application server is hosted on a separate system. Running SAP BusinessObjects Enterprise and a web application server on the same host in a production environment may decrease performance. If Tomcat 6.0 does not meet your organization's requirements, the following web application servers are supported: Tomcat (5.5) JBoss Oracle Application Server SAP NetWeaver Application Server Sun Java System Application Server WebLogic WebSphere

For a detailed list of supported web application servers, versions, and patch levels, consult the Supported Platforms Guide available at http://service.sap.com/bosap-support. Note: To use a supported web application server other than the bundled version of Tomcat 6.0, it must be running and accessible before you attempt to install.

12

2011-01-10

Planning

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

2.4 Web servers

You can use a dedicated web server to host static web content, such as images, HTML, or multimedia files. This is known as a split deployment. Split deployments increase the performance of the web application server as it no longer needs to serve static content, and returns dynamic content only when required. The WDeploy tool is able to separate static dynamic content for deployment to separate web and web application servers. For more information on split deployments, see the SAP BusinessObjects Enterprise Web Application Deployment Guide. The web and web application servers can run on the same machine, or on separate machines across a network. SAP BusinessObjects Enterprise supports the following combinations of web servers and web application servers: Apache web server with Tomcat Apache web server with WebLogic IBM IHS web server with WebSphere Sun Java System Web server with Sun Java System Application Server

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

2.5 Database servers

If you do not have a database server in place for use with SAP BusinessObjects Enterprise, the installation program can install and configure one for you. It is recommended that you evaluate your requirements against information from your database server vendor to determine which supported database would best suit your organization's requirements. IBM DB2 is the default database server. Any other database server must be running and accessible when you run the installation program. SAP BusinessObjects Enterprise also supports the following database servers: MySQL Oracle MaxDB Sybase

13

2011-01-10

Planning

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

14

2011-01-10

Preparation

Preparation

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

3.1 System requirements

15

2011-01-10

Preparation

Use the following guidelines when you install SAP BusinessObjects Enterprise: Ensure that the operating system is supported. Only 64-bit operating systems are supported. Before you run the installation program, ensure that the destination partition has enough room for the deployment to expand (when updates and new features are added in the future). If you install the deployment on the operating system partition, ensure that there is enough room for the deployment and the operating system. It is recommended that you have at least 2 gigabytes available for temporary files and web applications. If you have previously installed any SAP BusinessObjects products, the installation program uses the existing directory. For a detailed list of supported operating systems and hardware requirements, consult the Supported Platforms documentation available at http://service.sap.com/bosap-support.

3.1.1 Installing SAP BusinessObjects Enterprise on an HPUX 64-bit system

The SAP BusinessObjects Enterprise Java components require the HP 64-bit release of the JDK or JRE. To run the Java Virtual Machine in 64-bit mode, use the -d64 option. For more information, see http://docs.hp.com/en/JAVAPROGUIDE/hotspot.html#-d64 Note: The following SAP BusinessObjects products and components will not run on an HPUX Itanium 64-bit system platform: Business View Manager Enterprise Explorer Predictive Analysis Multi-Dimensional Analysis Services

3.1.2 Account permissions

To install SAP BusinessObjects Enterprise on a Unix or Linux host, a user must have the following permissions:

16

2011-01-10

Preparation

Category

Required access

Operating system

Permission to read, write, and execute scripts in the destination directory. For a system install, root access is required (the installation program creates start-up run control scripts in /etc/rc that start or stop the servers when the host machine is started or stopped). Network connectivity through appropriate ports to all machines in the deployment. Access to shared file system directories. Appropriate network authentication privileges. Permission for the SAP BusinessObjects user account to create, edit, and drop tables. Permission for the SAP BusinessObjects user account to create stored procedures (required by the Central Management Server (CMS) system database).

Network

Database

3.1.2.1 Additional Unix and Linux requirements

User account Create a user account and group under which the software's background processes can run. Use this account to perform the installation and run the software. The account does not require root privileges. Locale Before you install, set the installing account's environment to use a supported UTF-8 locale and ensure that your console software supports UTF-8 character sets. To ensure that your operating system uses the correct locale, set the LC_ALL and LANG environment variables to your preferred locale in your login environment. For example, the following bash shell commands set the locale to the United States English UTF-8 locale:
export LANG=en_US.utf8 export LC_ALL=en_US.utf8

Tip: Type locale to check that all of the related locale environment variables (such as LC_MONETARY, LC_NUMERIC) were properly set by LC_ALL. For a detailed list of supported Unix and Linux environments, see the Supported Platforms guide available on the SAP BusinessObjects Enterprise support site service.sap.com/bosap-support. See the section on International Deployments in the Administrator Guide for information on deploying to a multilingual audience.

17

2011-01-10

Preparation

Commands In order for the installation program to run correctly, the following utilities must be installed on your system and available on the path: /bin/sh uname awk tar stty pwd expr chown id ulimit read hostname grep dirname which touch sed tail gzip

If one of them is not available on your system, install a version from your operating system vendor rather than a third-party vendor (such as the GNU project). Note: The output from a GNU version of a utility can differ significantly from the version provided by your operating system vendor. To prevent the installation program from encountering output in an unexpected format, ensure that no GNU utilities are used in the installing user account's environment. Installations A new installation can be one of two different types. User installation The installed software is owned by the account that was used to run the installation program. This account must be used to start and stop the servers. Access to the root user account is not required to perform a user installation, and installation program will exit if it detects that it is being run as root. System installation A system installation is a finished user installation with system startup and shutdown run control scripts added. These scripts automatically start and stop SAP BusinessObjects Enterprise server functions as the operating system starts up or shuts down. The script to install the run control scripts must be run with root privileges after a user installation has completed.

3.1.3 Network permissions

When you install SAP BusinessObjects Enterprise across multiple machines, use the following guidelines to ensure your network functions properly: Servers running on all hosts must be able to communicate with each other. Each machine must be able to communicate with the web application server, the Central Management Server (CMS) host, all SIA hosts, and clients.

18

2011-01-10

Preparation

On any host with more than one network interface card (NIC), ensure that the primary NIC is routable before running the installation program. If the primary NIC is not routable, you will have to re-configure the networking settings after the installation. For information on how to bind to routable NICs, see the Managing and Configuring Servers chapter of the SAP BusinessObjects Enterprise AdministratorGuide. Each machine must use a fixed hostname. Fully-qualified hostnames are supported. Note: Ensure that deployment hostnames do not include any of the following characters: underscore (_), period (.), backslash (\), or forward-slash (/).

If you run the installation program behind a firewall, see the Securing SAP BusinessObjects Enterprise chapter of the SAP BusinessObjects Enterprise Administrators Guide.

3.1.3.1 Choosing a server location

When planning a distributed installation, consider the latency between servers. To maintain high CMS performance, place your CMS on the same subnet as the CMS system and Auditing Data Store database servers. The CMS can also be clustered, so that CMS server processes run on different host systems in the cluster. When creating a CMS cluster, ensure that each machine experiences the same network latency to the CMS system or Auditing Data Store. Consult the Managing and Configuring Servers section of the SAP BusinessObjects Enterprise Administrator Guide for more information on clustering CMS server processes.

3.2 Preparing the CMS system or Auditing Data Store database

To use a database server other than the database bundled with SAP BusinessObjects Enterprise, the following tasks must be completed before installing SAP BusinessObjects Enterprise. Create a database (or tablespace or schema, if applicable to your database), and account to store CMS configuration and system information. A second tablespace or scheme is required to hold auditing information. Record the database, tablespace, and account information so you can enter the details when prompted by the SAP BusinessObjects Enterprise installation program. Caution: If you have an existing SAP BusinessObjects Enterprise installation, you must create a fresh database and migrate existing content after the install is complete. Ensure that your database server is configured to use Unicode character encoding (such as UTF-8). Ensure that the database accounts have privileges to create, modify, and delete tables, and to create stored procedures.

19

2011-01-10

Preparation

When using a database server on a network, the appropriate database client drivers must be installed and verified as working before installing SAP BusinessObjects Enterprise. Contact your database administrator to establish which drivers are required for your database.

During your installation, you will be prompted for the connection and authentication credentials so that the installation program can initialize the database. The table below shows which information is required for supported databases:
Database Information required by installation program

MySQL

MySQL database name Server hostname Port number (default is 3306) Account username Account password "Reset existing database" checkbox (recommended setting) DB2 Alias name Account username Account password "Reset existing database" checkbox (recommended setting) Oracle TNSNAME connection identifier Account username Account password "Reset existing database" checkbox (recommended setting) Database name Server hostname Port number (default is 7210) Account username Account password "Reset existing database" checkbox (recommended setting) Service name Note: The Sybase service name is a combination of the hostname and the port number, set by your database administrator in the sql.ini and interfaces files. SAP BusinessObjects Enterprise will connect to the default database for the user you specify. The default is set by the database administrator.

IBM DB2

Oracle

MaxDB

Sybase

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

20

2011-01-10

Preparation

3.2.1 Extra requirements for IBM DB2

IBM DB2 has requirements that must be met before installing either SAP BusinessObjects Enterprise with the integrated IBM DB2 database, or your own IBM DB2 database. If you plan to use the integrated IBM DB2 database bundled with SAP BusinessObjects Enterprise, or you plan to install and use your own IBM DB2 database server for use with SAP BusinessObjects Enterprise: Ensure that the ID of the user account used to host the DB2 database meets the following requirements from IBM. For more information an IBM's requirements for Unix or Linux systems hosting DB2, see DB2 users and groups (Linux and UNIX) in the Database Fundamentals section of the DB2 Solution Information Center at http://www.ibm.com/support. Must have a primary group other than guests, admins, users, or local Can include only lowercase letters (a-z), numbers (0-9), or the underscore character (_) Cannot be longer than eight characters Cannot begin with IBM, SYS, SQL, or a number Cannot be a DB2 reserved word (USERS, ADMINS, GUESTS, PUBLIC, or LOCAL), or an SQL reserved word Cannot use any user IDs with root privilege for the DB2 instance ID, DAS ID, or fenced ID. Cannot include accented characters If existing user IDs are specified instead of creating new user IDs, ensure that the user IDs: Are not locked Do not have expired passwords

The primary group of the user must meet the following requirements: Cannot be one of guests, admins, users, or local Cannot start with sql or ibm Cannot start with a number Must contain only lowercase letters (a-z), numbers (0-9), or the underscore character (_)

If you plan to install and use an IBM DB2 database server for use with SAP BusinessObjects Enterprise: 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 for more information. If your DB2 database does not have the Collating Sequence = "Identity" setting, the user and user group objects may not sort as expected in the CMC.

21

2011-01-10

Preparation

Create a user temporary table space before installing SAP BusinessObjects Enterprise. If you do not create a user temporary table space, the SAP BusinessObjects Enterprise installation program will not be able to configure the DB2 database. For more information on user temporary table spaces in IBM DB2, see DB2 Basics: Table spaces and buffer pools in the IBM technical library: http://www.ibm.com/developerworks/data/library/techar ticle/0212wieser/0212wieser.html.

When using IBM DB2 to host an Auditing Data Store database, ensure that the page size for the auditing table space is set to a minimum of 8192 (8 KB). Ensure that the CMS system database is not partitioned. The Auditing Data Store database may be partitioned.

3.2.1.1 Interprocess Communications (IPC) settings when using the bundled DB2 9.7 FP1 database
The database bundled with SAP Businessobjects Enterprise is IBM DB2 9.7 FP1. If using the bundled database, prior to installation, ensure the following IPC parameters have been set with a value equal to or greater than the following minimum values:
IPC kernel parameter Enforce minimum setting

kernel.shmmax (SHMMAX) kernel.sem (SEMMNI) kernel.msgmni (MSGMNI) kernel.msgmax (MSGMAX) kernel.msgmnb

1 073 741 824 (64-bit kernel) 1 024 1 024 65 536 65 536

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 the database creation and cannot be changed after the database is created. Use a Unicode character set, such as UTF-8.

22

2011-01-10

Preparation

3.3 Set ulimit to unlimited

To successfully build and deploy SAP BusinessObjects Enterprise web applications, the host operating system or user account ulimit setting must be configured as unlimited. Set the ulimit configuration with the ulimit command, or modify the system configuration file /etc/security/limits.conf. For more information about the ulimit setting, see the documentation included with your operating system.

3.4 SAP support

3.4.1 Support for SAP System Landscape Directory (SLD)

SAP System Landscape Directory (SLD) is a directory service that maintains a list of installed SAP and (optionally) non-SAP software. SLD provides two main categories of information: Software already installed Software that could be installed at a later time SAP systems come with a data supplier (DS) component that automatically updates the landscape directory. Non-SAP software that supports SLD registers through an open API. The information gathered on installed software includes: Version Host information Connection information To use SLD support, ensure that SAP Host Agent is installed and working on the system(s) that host SAP BusinessObjects Enterprise. SAP Host Agent may be installed and configured before or after installing SAP BusinessObjects Enterprise.

3.4.1.1 To enable SAP System Landscape Directory (SLD) support

23

2011-01-10

Preparation

If you plan on using SAP System Landscape Directory (SLD) or SAP Solution Manager Diagnostics (SMD), ensure that the SAP Host Agent is installed and configured. The following steps walk you through installing SAP Host Agent. SAP Host Agent may be installed and configured before or after installing SAP BusinessObjects Enterprise. For more information on SAP Host Agent, see Registration of SAP BusinessObjects Enterprise in the System Landscape in the SAP BusinessObjects Enterprise Administrator Guide. Note: If you have installed SAP GUI, skip to step 4 below. Prior to installing support for SAP System Landscape Directory (SLD) there must be an sapadm user with root privileges. The SAP_LocalAdmin group must also exist, and the sapadm user must be a member. The sapadm user password is required during the SAPHOSTCONTROL installation. 1. Download SAP Host Agent (SAPHOSTAGENT.SAR) from the SAP Software Distribution Center of the SAP Service Marketplace ( http://service.sap.com/swdc). Log on with your SAP Service Marketplace ID and locate the version of SAPHOSTAGENT.SAR appropriate for your system. 2. Extract SAPHOSTAGENT.SAR by entering the following command: sapcar -xvf SAPHOSTAGENT.SAR 3. Install SAPHOSTCONTROL by entering the following command: saphostexec -install 4. Locate the sldreg tool, which is usually located in the following folder: /usr/sap/hostctrl/exe 5. Create an SLD key with the following command: sldreg configure connect.key You will be prompted to supply a username, password, host, port, and protocol for connecting to the SLD server. 6. Enter the information requested. The sldreg tool creates a connect.key file that will automatically be used by sld-ds to push information to SLD server. If you have already installed SAP BusinessObjects Enterprise, restart all SIA nodes in the Central Configuration Manager (CCM) to register with the SLD.

3.4.2 Support for SAP Solution Manager Diagnostics (SMD)

24

2011-01-10

Preparation

SAP Solution Manager Diagnostics (SMD) monitors the performance of systems in the SAP System Landscape Directory (SLD). Problems can be identified, analyzed, and resolved with the information gathered by SMD, which includes: Performance monitoring Configuration management Log management Load testing Alerting Resource monitoring Tools integrated into SMD include: CA Wily Introscope For full instrumentation, both SMD and CA Wily Introscope should be used. SAP LoadRunner by HP

Non-SAP software with an SAP-certified integration is entered into a central repository and transferred automatically to your SAP System Landscape Directories (SLD). SAP customers can then easily identify which version of third-party product integration has been certified by SAP within their SAP system environment. This service provides additional awareness for third-party products besides our online catalogs for third-party products. To use SMD, the SMD Agent must be installed. SMD Agent may be installed and configured before or after installing SAP BusinessObjects Enterprise. During installation, the installation program prompts for the hostname and port number of the SMD Agent. If you do not want to use SMD, or you will install SMD later, you can choose not to use SMD. The SMD Agent can be configured later in the Central Management Console (CMC) "Placeholders" screen. For more information, see To configure SMD Agent post installation. For more information on SMD, or to download SMD, visit the SAP Service Marketplace at: ser vice.sap.com/swdc.

3.4.3 Support for CA Wily Introscope

CA Wily Introscope is included as a part of SAP Solution Manager Diagnostics (SMD). For full instrumentation, both SMD and CA Wily Introscope should be used. To use CA Wily Introscope and SMD, the SMD Agent must be installed. SMD Agent may be installed and configured before or after installing SAP BusinessObjects Enterprise. During installation, the installation program prompts for the hostname and port number of the Introscope Agent. If you do not want to use Introscope, or you will install it later, you can choose not use Introscope. Introscope can be configured later in the Central Management Console (CMC) "Placeholders" screen. For more information, see To configure SMD Agent post installation.

25

2011-01-10

Preparation

3.5 Final checklist

Prior to installing SAP BusinessObjects Enterprise, review the following checklist. Have you decided on the installation destination folder? Note: The use of Unicode characters in the destination folder is not supported. Ensure that the installation destination folder is not the same folder in which the installation program has been extracted (do not install to the current working directory when running the installation program from the current working directory).

Have you verified appropriate network connectivity between all machines that will be part of your deployment? If you plan to use SAP Enterprise Resource Planning (ERP) integration for OLAP Data Access (ODA), SAP BusinessObjects Analysis (formerly Voyager), or SAP Business Warehouse (BW), ensure that SAP GUI is installed and configured before SAP BusinessObjects Enterprise. If you are using your own database server: Have you created a database, tablespace (if required), and accounts for the CMS system and Auditing Data Store databases? Have you made sure you can log onto the database from the SAP BusinessObjects Enterprise 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? If you plan to use SAP System Landscape Directory (SLD), ensure that SAP Host Agent been installed and configured. For more information, see Support for SAP System Landscape Directory (SLD). If you plan to use SAP Solution Manager Diagnostics (SMD), SMD Agent may been installed and configured before or after SAP BusinessObjects Enterprise. For more information, see Support for SAP Solution Manager Diagnostics (SMD).

26

2011-01-10

Installation

Installation

There are two different methods of running the installation program for SAP BusinessObjects Enterprise: Interactive installation An interactive wizard prompts for all information related to the installation. Use this option to select individual installation options from a series of screens. This is the default installation method. Silent installation Installation options are given on the command-line, which override the installation program's default values. The command-line can be used to give some or all installation options. When an installation option is not given on the command-line, the installation program uses a default value. Installation options can be given in a response file rather than directly on the command-line. This type of silent installation uses the -r command-line parameter to read installation options from the response file. Use this option if you want to install multiple machines with the same configuration. Installation options stored in a response file can be overridden by giving them on the command-line. When the -q (quiet mode) switch is used, the installation program does not prompt for any user input during the installation. If the installation program encounters an unexpected condition, and is unable to continue, it will undo any work completed up to that point, and return the system to the state that it was in before the installation started.

4.1 To run an interactive installation

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

The installation log file will be saved to <BOE_INSTALL_DIR>/InstallData/logs/<DATE>/In stallDU<COMPONENT>.log. 1. Change directory to the folder containing the setup.sh installation program. Use the InstallDir=<DESTINATION_DIR> parameter to set the destination folder from the command line. For example, to install SAP BusinessObjects Enterprise into the folder /opt/sap, use the command ./setup.sh InstallDir=/opt/sap.

27

2011-01-10

Installation

2. 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 your choice. If you select a non-English language, the corresponding language pack is automatically installed on the server. Note: The installation program will automatically run in the same language as your operating system. The language used by the installation program will determine the names used for components configured by the installation program. These names cannot be changed later and are not affected by language settings once the installation is complete. 3. Review the destination folder shown. This is the folder into which the installation program will install SAP BusinessObjects Enterprise. If the folder does not exist, the installation program creates it. Note: The use of Unicode characters in the destination folder is not supported. Ensure that the destination folder is not the same folder in which the installation program has been extracted (do not install to the current working directory when running the installation program from the current working directory).

4. The installation program checks for required components and conditions. Review the results and decide whether to continue with the installation, or abort and correct any unmet requirements. If a dependency prerequisite condition is critical, the installation program will not allow the installation to proceed. If the missing or unsupported component is optional, you have the option to either continue with the installation or stop and correct the condition. 5. Review the installation welcome screen. 6. Review and accept the license agreement. 7. Enter the product keycode. The product keycode was given to you when you purchased SAP BusinessObjects Enterprise. Store the keycode and registration information in a safe place in case you need to re-install. 8. To install support for a language, select it from the list. Note: Carefully consider which languages need to be installed for your organization. To add or remove language support later requires that you remove and re-install SAP BusinessObjects Enterprise. The language currently being used by the operating system is selected automatically. English language support cannot be deselected because SAP BusinessObjects Enterprise falls back to using English if a problem is detected with an individual language. 9. Select one of the following install type options: User install A user installation causes the installation program to install the software as a self-contained package within a directory, where the software must be started and stopped manually from the command-line. System install

28

2011-01-10

Installation

A system installation causes the installation program to install start-up and shutdown scripts in the run control (rc) folder of the operating system (/etc/rc or similar) so that the software will start and stop automatically with the operating system. Note: A system installation requires root user privileges. The "Choose Install Type" screen appears.

4.1.1 To select an install type

SAP BusinessObjects Enterprise requires a database server and web application server to function. If you do not have an existing database, the installation program can automatically install and configure an IBM DB2 database. If you do not have an existing web application server, 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 a single-host deployment, such as a pre-production development or test environment. Custom / Expand Install Allows experienced users to select individual components. Use this option: When distributing server components between more than one host, such as creating a CMS cluster. When you want full control over which components are deployed to a host. Web Tier The web tier hosts web applications and serves content to users over the web. Use the Web Tier installation option to install Java web applications onto a dedicated Java web application server. If you do not have a web application server in place for use with SAP BusinessObjects Enterprise, the installation program can install and configure a Tomcat web application server for you. It is recommended that you evaluate your requirements against information from your web application server vendor to determine which supported web application server would best suit your organization's needs. If you already have a supported web application server installed, you can deselect the option to install Tomcat, and only install the Java web applications 2. Proceed to the next screen to start configuring the selected installation. You may return to the install type options screen at any time later.

29

2011-01-10

Installation

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

4.1.1.1 Full installation

The following steps are performed for Full installations of SAP BusinessObjects Enterprise. 1. A database is required to store Central Management Server (CMS) configuration and run-time information. A second database is required for Auditing Data Store (ADS) information. If you do not have a database server in place for use with SAP BusinessObjects Enterprise, the installation program can install and configure one for you. It is recommended that you evaluate your requirements against information from your database server vendor to determine which supported database would best suit your organization's needs. To install the bundled database server, select Install and use the default database. IBM DB2 will be installed and configured to store Central Management Server (CMS) and auditing data. To use an existing supported database server, select Use an existing database server. The installation program prompts for information on the database type and connection credentials for both the CMS system and Auditing Data Store databases. Note: An existing database must have user accounts with the appropriate privileges ready, and the appropriate drivers must be installed and verified as working. The installation program attempts to connect to, and initialize, the database as a part of the installation process. 2. If you selected Use an existing database server: a. Select the database type to use for the CMS database. b. Select the database type to use for the Auditing database (Auditing Data Store). If you do not want to use the auditing feature, select No Auditing Database. 3. A Java web application server is required to host SAP BusinessObjects Enterprise web applications. If you do not have a web application server in place for use with SAP BusinessObjects Enterprise, the installation program can install and configure a Tomcat web application server for you. It is recommended that you evaluate your requirements against information from your web application server vendor to determine which supported web application server would best suit your organization's needs. Note: When configuring a production environment, it is recommended that the web application server is hosted on a separate system. Running SAP BusinessObjects Enterprise and a web application server on the same host in a production environment may decrease performance.

30

2011-01-10

Installation

Note: This release of SAP BusinessObjects Enterprise does not support the automatic deployment of web applications to any web application server other than the bundled Tomcat web application server. To deploy web applications to a different supported web application server, use the WDeploy tool. For more information, see the SAP BusinessObjects Enterprise Web Application Deployment Guide. To use the bundled Tomcat Java web application server, select Install Tomcat application server and 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 Central Management Server (CMS) or BI launch pad applications, select Install Web Application Container Server 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 configuration versions with the SAP Lifecycle Manager. To use an existing version control system, you must manually configure the Lifecycle Manager after the installation is complete. Lifecycle Manager stores each configuration change in a version control system, making it easier to revert to a previous configuration when needed. 5. Enter a name and port number for the System Intelligence Agent (SIA) node. The name must consist of 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 servers can 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 able to receive incoming connections on this port, so ensure that your firewall is configured appropriately. Port 6410 is a standard TCP/IP port number reserved for use with an SAP BusinessObjects Enterprise SIA. 6. Review the default value for the Central Management Server (CMS) port number. This is the port on which the CMS listens for incoming connections from the web application server, web server (if applicable), other CMS nodes (if applicable) and servers. The CMS must be able to receive incoming connections on this port, so ensure that your firewall is configured appropriately. Port 6400 is a standard TCP/IP port number reserved for use with SAP BusinessObjects Enterprise CMS systems. 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 SAP BusinessObjects Enterprise authentication system, used only to administer your SAP BusinessObjects server configuration. It is not part of any operating system or single sign-on authentication system. Communication between some CMS components is encrypted to provide a higher level of security when using clusters. 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 Enterprise.

31

2011-01-10

Installation

Enter the port number for DB2 to listen for incoming database queries. The DB2 database must be able to receive incoming connections on this port, so ensure that your firewall is configured appropriately. b. If you deselected the Integrated Database option in the feature list, enter the connection information for an existing database to use for the CMS system database. c. If you deselected the Integrated Database option in the feature list, and you plan to use auditing, enter the connection information for the Auditing Data Store (ADS) database. 9. Decide whether to start the servers as soon as the installation is complete. If you do not start the servers after the installation process is complete, the servers must be started manually with the Central 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 server connection port number, the shutdown port number, and the redirect port number. The Connection port is the port on which the web application server listens for incoming connections from web clients. The Shutdown port allows the web application to be shut down remotely. The Redirect port enables redirects to secure web connections. 11. If you chose to install the bundled Subversion version control system for use with Lifecycle Manager, confirm the port number and enter and confirm a password for SAP BusinessObjects Enterprise to use when accessing the Subversion repository. 12. SAP BusinessObjects Enterprise can integrate with your organization's deployment of SAP Solution Manager Diagnostics (SMD). If your organization uses SAP SMD, select Configure connectivity to SAP SMD 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" screen later. Note: To use SAP Solution Manager Diagnostics (SMD), SAP Host Agent and SMD Agent must be installed: For information on installing the SAP Host Agent before SAP BusinessObjects Enterprise, see To enable SAP System Landscape Directory (SLD) support. For information on installing the SAP Host Agent after SAP BusinessObjects Enterprise, see To configure System Landscape Directory (SLD) Data Supplier (DS) post installation. For information on installing SMD Agent before SAP BusinessObjects Enterprise, see Support for SAP Solution Manager Diagnostics (SMD). For information on installing SMD Agent after SAP BusinessObjects Enterprise, see To configure SMD Agent post installation. a. If you chose to integrate with SMD, enter the SMD Agent hostname and port number. 13. SAP BusinessObjects Enterprise can integrate with your organization's deployment of CA Wily Introscope Enterprise Manager. If your organization uses Introscope Enterprise Manager, select Integrate connectivity to Introscope Enterprise Manager. You will be prompted for information. Note: To use CA Wily Introscope Enterprise Manager, SMD Agent must be installed: For information on installing SMD Agent before SAP BusinessObjects Enterprise, see Support for SAP Solution Manager Diagnostics (SMD).

32

2011-01-10

Installation

For information on installing SMD Agent after SAP BusinessObjects Enterprise, see To configure SMD Agent post installation.

a. If you chose to integrate with Introscope Enterprise Manager, enter the hostname and port number for the Introscope Enterprise Manager server. The "Start Installation" screen appears. Click "Next" to install. Proceed to While the installation program runs.

4.1.1.2 Custom / Expand installation

The following steps are performed for Custom / Expand installations of SAP BusinessObjects Enterprise. The "Select Features" screen displays selectable components that can be installed. 1. Review the list of features to install. Only features with a selected checkbox are installed. Features are grouped under the following headings: Web Tier The web tier components serve content to web browsers. If you do not have a web application server in place for use with SAP BusinessObjects Enterprise, the installation program can install and configure a Tomcat web application server for you. It is recommended that you evaluate your requirements against information from your web application server vendor to determine which supported web application server would best suit your organization's needs. If you already have a supported web application server installed, you can deselect the option to install Tomcat, and only install the Java web applications Servers Server features include the Business Intelligence platform servers (such as processing and scheduling servers), major system components (such as the CMS, Event Server, bundled database, and a version control system), and servers that integrate SAP BusinessObjects Enterprise into your organization's existing network infrastructure, such as SAP BW or other Enterprise Resource Planning (ERP) systems. Note: If you plan to use SAP BW authentication, ensure that the BW Publisher Server feature is selected in the Integration Servers feature list. Administrator Tools The Administrator Tools features help administrators maintain an installation. Note: If you plan to use the upgrade management tool to upgrade objects from an older version of SAP BusinessObjects Enterprise, see Object types and feature requirements.

33

2011-01-10

Installation

Database Access To access, analyze, and report on the data in your organization's existing databases, select the appropriate Database Access features. If your organization does not use a particular database, you can deselect it. Note: Integration for PeopleSoft Enterprise, JD Edwards EnterpriseOne, Siebel, or Oracle EBS Enterprise Resource Planning (ERP) systems is not selected by default. If you plan to use an ERP single sign-on authentication, or other ERP features, ensure that the appropriate ERP feature is selected in the Data Access feature list. If you plan to use integration for SAP, SAP BW, or SAP R3 systems, ensure that the SAPBW and SAP features are selected in the Data Access feature list.

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

2. Select the type of installation being performed. If you are installing a stand-alone server, or the first server in a cluster, select Start a new SAP BusinessObjects Enterprise deployment. If you already have a CMS and want to create a new server as part of a cluster, select Expand an existing SAP BusinessObjects Enterprise deployment. If you selected Start a new SAP BusinessObjects Enterprise deployment on the last screen, proceed to Custom (New) installation. If you selected Expand an existing SAP BusinessObjects Enterprise deployment on the last screen, proceed to Custom (Expand) installation.

4.1.1.2.1 Custom (New) installation

If you chose the Start a new SAP BusinessObjects Enterprise deployment option for a "Custom / Expand" installation: 1. If you deselected the Integrated Database option in the feature selection screen: a. Select the type of database to use for the CMS system database. b. Select the type of database to use for the Auditing Data Store (ADS) database. If you do not want to use auditing, select No Auditing Database. Note: An existing database must have database user accounts with the appropriate database privileges ready, and the appropriate drivers must be installed and verified as working. The installation program attempts 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 consist of 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 servers can be managed by a single SIA.

34

2011-01-10

Installation

The port is used for the SIA to listen for incoming connections from the CMS. The SIA must be able to receive incoming connections on this port, so ensure that your firewall is configured appropriately. Port 6410 is a standard TCP/IP port number reserved for use with an SAP BusinessObjects Enterprise SIA. 3. Review the default value for the Central Management Server (CMS) port number. This is the port on which the CMS listens for incoming connections from the web application server, web server (if applicable), other CMS nodes (if applicable) and servers. The CMS must be able to receive incoming connections on this port, so ensure that your firewall is configured appropriately. Port 6400 is a standard TCP/IP port number reserved for use with SAP BusinessObjects Enterprise CMS systems. 4. Enter and confirm the CMS Administrator account password and the CMS cluster key. Note: The CMS Administrator is a super-user account in the SAP BusinessObjects Enterprise authentication system, used only to administer your server. It is not part of any operating system or single sign-on authentication system. Communication between some CMS components is encrypted, to provide a higher level of security when using clusters. 5. Configure the CMS system database. a. If you chose to install the bundled database, the installation program uses your choices to install and configure the database for use with SAP BusinessObjects Enterprise. Enter the port number for DB2 to listen for incoming database queries. The DB2 database must be able to receive incoming connections on this port, so ensure that your firewall is configured appropriately. b. If you deselected the Integrated Database option in the feature list, enter the connection information for an existing database to use for the CMS system database. c. If you deselected the Integrated Database option in the feature list, and you plan to use auditing, enter the connection information for the Auditing Data Store (ADS) database. 6. Decide whether to start the servers as soon as the installation is complete. If you do not start the servers after the installation process is complete, the servers must be started manually with the Central Configuration Manager (CCM). 7. Configure the web application server. If you selected Tomcat 6.0 in the feature list, review the default values for the web application server connection 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. 8. If you chose to install the bundled Subversion version control system for use with Lifecycle Manager, confirm the port number and enter and confirm a password for SAP BusinessObjects Enterprise to use when accessing the Subversion repository. 9. SAP BusinessObjects Enterprise can integrate with your organization's deployment of SAP Solution Manager Diagnostics (SMD). If your organization uses SAP SMD, select Configure connectivity

35

2011-01-10

Installation

to SAP SMD 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" screen later. Note: To use SAP Solution Manager Diagnostics (SMD), SAP Host Agent and SMD Agent must be installed: For information on installing the SAP Host Agent before SAP BusinessObjects Enterprise, see To enable SAP System Landscape Directory (SLD) support. For information on installing the SAP Host Agent after SAP BusinessObjects Enterprise, see To configure System Landscape Directory (SLD) Data Supplier (DS) post installation. For information on installing SMD Agent before SAP BusinessObjects Enterprise, see Support for SAP Solution Manager Diagnostics (SMD). For information on installing SMD Agent after SAP BusinessObjects Enterprise, see To configure SMD Agent post installation. a. If you chose to integrate with SAP Solution Manager Diagnostics (SMD), enter the SMD Agent hostname and port number. 10. SAP BusinessObjects Enterprise can integrate with your organization's deployment of CA Wily Introscope Enterprise Manager. If your organization uses Introscope Enterprise Manager, select Integrate connectivity to Introscope Enterprise Manager. You are prompted for information. Note: To use CA Wily Introscope Enterprise Manager, SMD Agent must be installed: For information on installing SMD Agent before SAP BusinessObjects Enterprise, see Support for SAP Solution Manager Diagnostics (SMD). For information on installing SMD Agent after SAP BusinessObjects Enterprise, see To configure SMD Agent post installation. a. If you chose to integrate with Introscope Enterprise Manager, enter the hostname and port number for the Introscope Enterprise Manager server. The "Start Installation" screen appears. Click "Next" to install. Proceed to While the installation program runs.

4.1.1.2.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 connection credentials. Note: The appropriate drivers must be installed and verified as working on the expand host. 2. Enter a name and review the port number for the System Intelligence Agent (SIA) node. The name must consist of English alphanumeric characters (A-Z, a-z, and 0-9) and contain no spaces or punctuation. The SIA name cannot start with a number.

36

2011-01-10

Installation

This is the name that you will see in the Central Configuration Manager (CCM). Many CMS servers can be managed by a single SIA. The port is used for the SIA to listen for incoming connections from the CMS. The SIA must be able to receive incoming connections on this port, so ensure that your firewall is configured appropriately. Port 6410 is a standard TCP/IP port number reserved for use with a SAP BusinessObjects Enterprise SIA. 3. Enter connection information for the existing CMS. This includes the hostname and port number of the primary CMS. Fully qualified domain names are supported. 4. Enter and confirm a value for the CMS cluster key. Communication between some CMS components is encrypted to provide a higher level of security. 5. Review the default value for the new Central Management Server (CMS) port number. This is the port on which the new CMS listens for incoming connections from the web application server, web server (if applicable), other CMS nodes (if applicable) and servers. The CMS must be able to receive incoming connections on this port, so ensure that your firewall is configured appropriately. Port 6400 is a standard TCP/IP port number reserved for use with SAP BusinessObjects Enterprise CMS systems. 6. If you are installing the bundled database, enter a database administrator account password and an Enterprise user account name and password. If you are using a previously installed database, enter connection credentials for the CMS to connect to the database. The installation program uses your choices to install, configure the database for use with SAP BusinessObjects Enterprise. 7. Decide whether to start the servers as soon as the installation is complete. If you do not start the servers after the installation process is complete, the servers must be started manually with the Central Configuration Manager (CCM). 8. Review the default values for the web application 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 ensure that your firewall is configured appropriately. 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. 9. Review the port number and provide a password for SAP BusinessObjects Enterprise to use when accessing the Subversion repository. 10. SAP BusinessObjects Enterprise can integrate with your organization's deployment of SAP Solution Manager Diagnostics (SMD). If your organization uses SAP SMD, select Configure connectivity to SAP SMD 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" screen later. Note: To use SAP Solution Manager Diagnostics (SMD), SAP Host Agent and SMD Agent must be installed: For information on installing the SAP Host Agent before SAP BusinessObjects Enterprise, see To enable SAP System Landscape Directory (SLD) support.

37

2011-01-10

Installation

For information on installing the SAP Host Agent after SAP BusinessObjects Enterprise, see To configure System Landscape Directory (SLD) Data Supplier (DS) post installation. For information on installing SMD Agent before SAP BusinessObjects Enterprise, see Support for SAP Solution Manager Diagnostics (SMD). For information on installing SMD Agent after SAP BusinessObjects Enterprise, see To configure SMD Agent post installation.

a. If you chose to integrate with SAP Solution Manager Diagnostics (SMD), enter the SMD Agent hostname and port number. 11. SAP BusinessObjects Enterprise can integrate with your organization's deployment of CA Wily Introscope Enterprise Manager. If your organization does not use Introscope Enterprise Manager, select Do not integrate connectivity to Introscope Enterprise Manager. Note: To use CA Wily Introscope Enterprise Manager, SMD Agent must be installed: For information on installing SMD Agent before SAP BusinessObjects Enterprise, see Support for SAP Solution Manager Diagnostics (SMD). For information on installing SMD Agent after SAP BusinessObjects Enterprise, see To configure SMD Agent post installation.

a. If you chose to integrate with Introscope Enterprise Manager, enter the hostname and port number for the Introscope Enterprise Manager server. The "Start Installation" screen appears. Select "Next" to install. Proceed to While the installation program runs.

4.1.1.3 Web Tier installation

The web tier hosts web applications and serves content to users over the web. Use the "Web Tier" installation option to install Java web applications onto a dedicated Java web application server. Note: If you plan to use a web tier with third-party authentication, or integration for Enterprise Resource Planning (ERP) systems such as SAP BW, Siebel Enterprise, JD Edwards EnterpriseOne, or Oracle E-Business Suite, you must perform a "Custom / Expand" installation and select the components you need. For example, to perform a web tier installation with 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 > SAP To perfom a Web Tier installation with support for a different ERP system, select:

38

2011-01-10

Installation

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 deploy web applications to a web application server after a web tier installation, use the WDeploy tool. For more information on using the WDeploy tool, see the SAP BusinessObjects Enterprise Web Application Deployment Guide.

If you do not have a web application server in place for use with SAP BusinessObjects Enterprise, the installation program can install and configure a Tomcat web application server for you. It is recommended that you evaluate your requirements against information from your web application server vendor to determine which supported web application server would best suit your organization's needs. If you already have a supported web application server installed, you can deselect the option to install Tomcat, and only install the Java web applications The following steps are performed for Web Tier installations of SAP BusinessObjects Enterprise. 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 web application 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 ensure that your firewall is configured appropriately. 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. 3. SAP BusinessObjects Enterprise can integrate with your organization's deployment of CA Wily Introscope Enterprise Manager. If your organization uses Introscope Enterprise Manager, select Integrate connectivity to Introscope Enterprise Manager. You will be prompted for information. Note: To use CA Wily Introscope Enterprise Manager, SMD Agent must be installed: For information on installing SMD Agent before SAP BusinessObjects Enterprise, see Support for SAP Solution Manager Diagnostics (SMD). For information on installing SMD Agent after SAP BusinessObjects Enterprise, see To configure SMD Agent post installation. a. If you chose to integrate with Introscope Enterprise Manager, enter the hostname and port number for the Introscope Enterprise Manager server. The "Start Installation" screen appears. Click "Next" to install. Proceed to While the installation program runs.

39

2011-01-10

Installation

4.1.2 While the installation program runs

The progress bar illustrates the progress of the installation as a whole. Note: When performing an Expand installation, the existing CMS may be restarted automatically as a part of the installation process. The installation program installs SAP activity and resource monitoring tools. These tools enable you to provide detailed technical information about your installation in the event of a problem.

4.1.3 When installation is complete

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

4.2 To run a silent installation

Every option in the installation wizard can be given from the command-line. This type of installation is known as a silent install. Installation options can be given directly on the command-line as a parameter, or can be stored in a response file. Giving installation options on the command-line Installation options can be passed directly to the setup program from the command-line as a parameter. For example, the installation option CMSPort=6401 can be given on the command-line as a parameter when running the installation program to set the CMS port number to 6401, instead of the default value of 6400. In the following example of giving the CMSPort parameter on the command-line, ellipses ([...]) are shown to indicate where other installation options would normally be present: ./setup.sh [...] CMSPort=6401 [...] Giving installation options in a response file

40

2011-01-10

Installation

Installation options can be stored in a response file, which is a text file containing installation option parameters in key-value format. When using a response file to give installation options, the installation program is run from the command-line with the -r <RESPONSE_FILE> parameter, where <RE SPONSE_FILE> is the name of the response file. The response file contains multiple installation options, with one installation option per line. In the following example, the response file is given as a parameter: ./setup.sh [...] -r $HOME/response.ini [...] For example, the installation option CMSPort=6401 can be given on a line in the response file to set the CMS port number to 6401, instead of the default value of 6400. In the following example of giving the CMSPort parameter in a response file, ellipses ([...]) are shown to indicate where other installation options would normally be present:
[...] CMSPort=6401 [...]

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

4.2.1 Command-line switch parameters

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

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

Switch parameter Description Example

-w <FILENAME>

Writes a response file to <FILE NAME>, containing the options selected from the installation wizard. Reads installation options from a response file named <FILENAME>.

./setup.sh -w "$HOME/re sponse.ini"

-r <FILENAME>

./setup.sh -r "$HOME/re sponse.ini"

41

2011-01-10

Installation

Switch parameter

Description

Example

-q

When performing a silent installation, this switch causes the installation program to install with no console output or prompting. If a problem is encountered, the installation program will write a message to the installation log file and exit. This switch must always be used in combination with the -r <FILENAME> switch parameter.

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

4.2.1.1 To use a response file

To use a response file, run the installation program with the -r <RESPONSE_FILE> parameter. The installation program reads all installation options from the response file, and no further input is required. For example, the following command reads installation options from the response file $HOME/re sponse.ini:
./setup.sh -r $HOME/response.ini

To override an installation option in a response file, give that option on the command-line. Installation options given on the command-line take precedence over the options in the response file. For a complete list of installation options, see Installation option parameters below. If an unexpected condition is encountered, an error message is written to the installation log file and the installation program exits. Installation activity, warnings, and errors are written to the installation log file in the folder: <BOE_INSTALL_DIR>/InstallData/logs/<DATE>/InstallDU<COMPONENT>.log If the <BOE_INSTALL_DIR> folder has not been created by the time the installation program exits, look for install.log in the temporary folder specified by the system TEMP environment variable.

4.2.1.1.1 To write a response file

To create a response file, run the installation program with the -w <RESPONSE_FILE> parameter and select the desired installation options with the installation wizard. When the wizard completes, the installation program exits and the response file is created. The response file can then be used for future installations. For example, the following command creates the response file $HOME/response.ini:
./setup.sh -w $HOME/response.ini

42

2011-01-10

Installation

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 will be written to the response file in plain text format.

4.2.1.1.2 To read a response file

A response file installation is started on the command-line, but installation options are read from a ASCII text file with the options stored in key-value format. This is useful when setting up a cluster, or for creating 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 options take precedence over the response file options. This allows an administrator to override an option in a response file when required. This provides three levels precedence for installation options: 1. Installation options given on the command-line take highest precedence, and will always override response file and default values. 2. Installation options given in a response file are used when not given on the command-line, and override default values. 3. Installation option default values are used when not given on the command-line or in a response file. For example, the following command reads installation options from the response file $HOME/re sponse.ini, but overrides the response file's setting for the installation destination folder:
./setup.sh -r $HOME/response.ini InstallDir=/opt/sap/sap_bobj/

4.2.1.2 Quiet mode installations

A quiet mode installation is a command-line installation that does not prompt for installation options. Installation options must be provided on the command-line or in a response file. Any installation options not 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 be performed with no human input and no console output. For example, the following command uses the default values for all installation options, except for the installation destination folder (set to /opt/sap/sap_bobj instead of the current working folder).
setup.exe -q InstallDir=/opt/sap/sap_bobj/

If an unexpected condition is encountered, an error message is written to the installation log file and the installation program exits. Installation activity, warnings, and errors are written to the installation log file in the folder: <BOE_INSTALL_DIR>/InstallData/logs/<DATE>/InstallDU<COMPONENT>.log

43

2011-01-10

Installation

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 the system TEMP environment variable.

4.2.2 Installation option parameters

The following table lists the parameters that can be used to select installation options on both the command-line and in response files. See the table Installation option parameters specific to Unix or Linux for parameters specific to Unix or Linux operating systems.

Table 4-2: Installation option parameters

Parameter Description

SetupUILanguage=<CODE>

Determines which language for the installation program to use during the 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

44

2011-01-10

Installation

Parameter

Description

InstallDir=<PATH>

Destination folder into which the setup program will install. Note: The use of Unicode characters in the destination folder is not supported. The use of Unicode characters in the destination folder is not supported. Ensure that the destination folder is not the same folder in which the installation program has been extracted (do not install to the current working directory when running the installation program from the current working directory).

45

2011-01-10

Installation

Parameter

Description

SelectedLanguagePacks=<CODE>

Installs language support for users and administrators to interact with SAP BusinessObjects Enterprise in a supported language. If more than one language pack is to be installed, use a semi-colon delimited 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 ChooseIntroscopeIntegra tion=<VALUE> Determines whether Introscope support will be enabled or not. To enable Introscope integration, set <VALUE> to integrate. To disable Introscope integration, set <VALUE> to nointegrate. Password to use for the CMS Administrator account. Substitute <PASSWORD> with the password. Password confirmation for the CMS Administrator account. Substitute <PASSWORD> with the password. Hostname of the Introscope server. Substitute <HOSTNAME> with the Introscope server hostname.

CMSPassword=<PASSWORD>

CMSPasswordConfirm=<PASSWORD>

Introscope_ent_host=<HOSTNAME>

46

2011-01-10

Installation

Parameter

Description

Introscope_ent_port=<PORT>

Network TCP listening port number used by the Introscope server. Substitute <PORT> with the Introscope server port number. 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. Hostname of the SMD Agent. Substitute <HOSTNAME> with the agent hostname. Network TCP listening port number used by the SMD Agent. Substitute <PORT> with the agent port number. Name of the user to whom the software is registered. Substitute <NAME> with the name. Name of the company to whom the software is registered. Substitute <NAME> with the name. Product license key issued when you purchased the software. Substitute <KEY> with the product key in the format XXXXXXXXXXX-XXXXXX-XXXX. Network TCP listening port number used by the CMS for incoming connections. Substitute <PORT> with the port number. The default value is 6400. Cryptographic key used to encrypt secure CMS cluster communications. Substitute <KEY> with the key string. Cryptographic key conformation. Substitute <KEY> with the key string. Determines whether or not the CMS servers will be started automatically after the installation is complete. To enable servers automatically after the installation, set <SWITCH> to 1. To not enable the servers, so that they must be started manually at a later time, set <SWITCH> to 0. Hostname of the SAP Lifecycle management server. Note: Do not change this value.

ChooseSMDIntegration=<VALUE>

SMDAgent_host=<HOSTNAME>

SMDAgent_port=<PORT>

RegisteredUser=<NAME>

RegisteredCompany=<NAME>

ProductKey=<KEY>

CMSPort=<PORT>

ClusterKey=<KEY>

ClusterKeyConfirm=<KEY>

EnableServers=<SWITCH>

LCMName=LCM_Repository

LCMPort=<PORT>

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

47

2011-01-10

Installation

Parameter

Description

LCMUsername=LCM

Username to access SAP Lifecycle management server. Note: Do not change this value.

LCMPassword=<PASSWORD>

User password to access SAP Lifecycle management server. Substitute <PASSWORD> with the password. User password confirmation. Substitute <PASSWORD> with the password. Determines whether or not the installation is a new LCM on a fresh server, or an expand installation used to create a CMS cluster. To perform a new installation, set <VALUE> to new. To perform an expand installation, set <VALUE> to expand. Determines whether or not the bundled database will be installed. To install the bundled database, set <VALUE> to 1. The bundled database is IBM DB2.

LCMPasswordConfirm=<PASSWORD>

NewOrExpandLCM=<VALUE>

SelectIntegratedDatabase=<VAL UE>

SIAName=<NAME>

Name of the Server Intelligence Agent (SIA) node create for this installation. The name must be alphanumeric and cannot start with a number. Substitute <NAME> with the SIA name. Network TCP listening port number used by the SIA. Substitute <PORT> with the port number. Network TCP listening port number used by the Tomcat web application server for inbound connections. Substitute <PORT> with the port number. Network TCP listening port number used by the Tomcat web application server to trigger a server shutdown. Substitute <PORT> with the port number. Network TCP listening port number used by the Tomcat web application server for server request redirection. Substitute <PORT> with the port number. Determines whether or not the installation program should select installable components based upon the default settings, custom settings (allows you to select components), or settings used for installing web tier components (when installing to a web application server). To install the default components, set <VALUE> to default. To install a custom selection of components, set <VALUE> to cus tom. To install a web tier components, set <VALUE> to webtier.

SIAPort=<PORT>

TomcatConnectionPort=<PORT>

TomcatShutdownPort=<PORT>

TomcatRedirectPort=<PORT>

InstallType=<VALUE>

48

2011-01-10

Installation

Parameter

Description

WebAppServerType=<VALUE>

Sets the web application server to use for web application deployment. The default value is tomcat. Before deploying web applications with the WDeploy tool, you must still manually update the WDeploy configuration files. For more information, see the SAP BusinessObjects Enterprise Web Application Deployment Guide. List of components to install. Used in combination with the Install Type=custom or InstallType=webtier parameter. This parameter should not be modified manually. Features must be selected through the installation program user interface when creating a response file. For a complete list of feature codes, see Feature codes.

Features=<CODE>

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

Parameter Description

DB2PortNumber=<PORT>

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

4.2.2.1 Feature codes

The following feature codes to select features for installation. Multiple features are separated with commas. 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 Resource Planning (ERP) systems such as SAP BW, Siebel Enterprise, JD Edwards EnterpriseOne, or Oracle E-Business Suite, you must perform a "Custom / Expand" installation and select the components you need. For example, to perform a web tier installation with 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)

49

2011-01-10

Installation

Instances > Database Access > SAPBW Instances > Database Access > SAP

To 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 PlatformServers: install all platform servers CMS (Central Management Server) FRS (File Repository Servers) PlatformServers.IntegratedDB.DB2 (installs bundled IBM DB2 server) DashboardAnalyticsServer (BI Workspace) PlatformServers.EventServer PlatformServers.SystemLandscapeSupplier (SLD) PlatformServers.WebAppContainerService (WACS) AdaptiveProcessingServer (platform processing) AdaptiveJobServer (scheduling) Subversion (Subversion version control system) ConnectionProcService DataFederatorQueryService MultidimensionalAnalysisServices (MDAS) BExWebApplicationsService CrystalReportsProcServices (SAP Crystal Reports Processing) CrystalReportSchedulingServices CrystalReport2011ProcServices (SAP Crystal Reports 2011 Processing) CrystalReport2011SchedulingServices (SAP Crystal Reports 2011 Scheduling) WebIProcServer (Web Intelligence Processing) WebISchedulingServices (Web Intelligence Scheduling)

Servers: install all server components

ConnectionServices: install connectivity components DataFederatorServices: install all data federation components AdvancedAnalysisServices: install all Analysis components

CrystalReportsServers: install all SAP Crystal Reports components

WebIServers: install all Web Intelligence components

XcelsiusServers (Dashboard Design) MobileServices MobileServers MobileAddon (CMS plugin for Mobile)

50

2011-01-10

Installation

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

AdministratorTools: install all administrator tools UpgradeManager (Upgrade management tool) Note: If you plan to use the upgrade management tool to upgrade objects from an older version of SAP BusinessObjects Enterprise, see Object types and feature requirements.

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

51

2011-01-10

Installation

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

Samples: install sample reports and data sources

4.2.2.2 Response file example

The following example response file contains options for installing SAP BusinessObjects Enterprise. Example: In this example, the response file is named $HOME/response.ini.
### Choose to Integrate Introscope Enterprise Manager: integrate or nointegrate chooseintroscopeintegration=nointegrate ### Choose to Integrate Solution Manager Diagnostics (SMD) Agent: integrate or nointegrate choosesmdintegration=nointegrate ### CMS administrator password cmspassword=Password1 ### #property.CMSPasswordConfirm.description# cmspasswordconfirm=Password1 ### CMS connection port cmsport=6400 ### CMS cluster key ClusterKey=Crypto1 ### #property.ClusterKeyConfirm.description# ClusterKeyconfirm=Crypto1

52

2011-01-10

Installation

### Choose to start servers after install: 0 or 1 enableservers=1 ### Installation directory installdir=/opt/sap/sap_bobj/ ### Choose install type: default, custom, webtier installtype=custom ### Introscope Enterprise Manager Hostname introscope_ent_host=$IntroscopeAgentEnterpriseManagerHost ### Introscope Enterprise Manager Port number introscope_ent_port=$IntroscopeAgentEnterpriseManagerPort ### LCM server name lcmname=LCM_repository ### LCM password lcmpassword=Password1 ### #property.LCMPasswordConfirm.description# lcmpasswordconfirm=Password1 ### LCM port lcmport=3690 ### LCM user name lcmusername=LCM ### Choose install mode: new, expand neworexpandinstall=new ### Product keycode productkey=XXXXX-XXXXXXX-XXXXXXX-XXXXXXX-XX ### Registered Company registeredcompany=default_company ### Registered User registereduser=default_user ### Language Packs Selected to Install selectedlanguagepacks=en ### Setup UI language setupuilanguage=en ### SIA node name sianame=SIA1 ### SIA connector port siaport=6410 ### SMD Agent Hostname smdagent_host=$SMDAgentHost ### SMD Agent Port Number smdagent_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

53

2011-01-10

Installation

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

54

2011-01-10

Installation

### 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 features=JavaWebApps1,tomcat60,WebTier,CMS,FRS,PlatformServers.IntegratedDB,DashboardAnalyticsServer,Plat formServers.EventServer,PlatformServers.SystemLandscapeSupplier,PlatformServers.WebAppContainerService,Adap tiveProcessingServer,AdaptiveJobServer,Subversion,PlatformServers,ConnectionProcService,ConnectionSer vices,DataFederatorQueryService,DataFederatorServices,MultidimensionalAnalysisServices,BExWebApplication sService,AdvancedAnalysisServices,CrystalReportsProcServices,CrystalReportSchedulingServices,CrystalRe port2011ProcServices,CrystalReport2011SchedulingServices,Export.MicrosoftMail,Export.LotusNotesMail,Ex port.LotusNotes,Export.ExchangeFolders,Export.Application,Export.HTML,Export.ODBC,Export.Record,Export.Re portDefinition,ExportSupport,CrystalReportsServers,WebIProcServer,WebISchedulingServices,WebIServers,Xcel siusServers,MobileServers,SiebelSignOnServer,BWPublisherServer,IntegrationServers,Servers,UpgradeManager,Ad ministratorTools,BOE64bitNETSDK,DeveloperTools,DataAccess.DataFederator,DataAccess.HPNeoView,DataAc cess.MySQL,DataAccess.GenericJDBC,DataAccess.GenericODBC,DataAccess.GenericOLEDB,DataAccess.MaxDB,DataAc cess.Salesforce,DataAccess.Netezza,DataAccess.Microsoft_AnalyticalServices,DataAccess.MicrosoftExchange,DataAc cess.MicrosoftOutlook,DataAccess.Microsoft_SQLServer,DataAccess.Microsoft_Access,DataAccess.Ingres,DataAc cess.Greenplum,DataAccess.IBMDB2,DataAccess.Informix,DataAccess.ProgressOpenEdge,DataAccess.Oracle,DataAc cess.Sybase,DataAccess.Teradata,DataAccess.SAPBW,DataAccess.SAP,DataAccess.PersonalFiles,DataAccess.Jav aBean,DataAccess.OpenConnectivity,DataAccess.HSQLDB,DataAccess.Derby,DataAccess.Essbase,DataAccess.People soft,DataAccess.JDEdwards,DataAccess.Siebel,DataAccess.OracleEBS,DataAccess.Universe,DataAccess.MyCube,DataAc cess.XML,DataAccess.ADO.NET,DataAccess.COMData,DataAccess.DataSet,DataAccess.SymantecACT,DataAccess.BDE,DataAc cess.CDO,DataAccess.FieldDefinitions,DataAccess.FileSystem,DataAccess.NTEventLog,DataAccess.WebActivity Log,DataAccess.Btrieve,DataAccess.dBase,DataAccess.UWSC,Samples,Help

55

2011-01-10

Installation

56

2011-01-10

Post-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 more information on using the CMC, see the SAP BusinessObjects Enterprise Administrator Guide. If you have installed a dedicated web application server, you can enter the web application server's URL 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 the web application server's listening port. If you are using a custom web application server root context or BOE.war web application context, the URL will be different. If you are using Internet Explorer, you may receive several Internet Explorer Enhanced Security Configuration warnings because the new server is not yet added to the list of trusted sites. Click Add to 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 the administrative password that you entered into the installation program.

5.2 Troubleshooting login issues

If you are unable to log on to the CMC, evaluate the following possible causes: 1. Is a firewall blocking the CMS port number (default 6400) or the web application server port? 2. Is the URL correct?? The default URL to access the CMC is:
http://<WEB_APP_SERVER>:<PORT>/BOE/CMC

57

2011-01-10

Post-Installation

Substitute <WEB_APP_SERVER> for the hostname of the web application server and <PORT> for the web application server's listening port. If you are using a custom web application server root context or 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 BusinessObjects Enterprise authentication system. If you are using an LDAP single sign-on authentication system, select the system instead. 4. Did you provide the correct user credentials in the User Name and Password fields on the CMC login screen? The name of the administrative account is Administrator. The password configured when SAP BusinessObjects Enterprise was installed. 5. Is the Server Intelligence Agent (SIA) is running. Start the CCM with the ccm.sh script. If the SIA is not running, start it. 6. Ensure that the database server(s) used for the CMS system and Auditing Data Store databases are 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 your first attempt to connect to the cluster, the CMC will not know which CMS servers belong to the cluster. In this case, you need to specify a list of CMS servers in the web.xml, found in the WEB-INF folder of the CMC web application WAR file. Follow the instructions in the cms.clusters section of web.xml for more details. It is also possible to specify CMS cluster information for the BI launch pad by modifying its corresponding web.xml file. If none of these solutions work, consider repairing or reinstalling the software or contacting SAP BusinessObjects support at service.sap.com/bosap-support.

5.3 Creating additional Adaptive Processing Servers

The installation program installs one Adaptive Processing Server (APS) per host system. Depending on the features that you've installed, this APS may host a large number of services, such as the 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 highly recommended 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.

58

2011-01-10

Post-Installation

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 service category, then may end up creating eight APS servers. One for each service category: Advanced Analysis Services, Connectivity Services, Core Services, Crystal Reports Services, Dashboard Design Services, 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 automatically deploy web applications to your web application server, you must deploy the web applications manually with 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 Enterprise Web Application Deployment Guide.

5.5 SAP support

5.5.1 To configure System Landscape Directory (SLD) Data Supplier (DS) post installation
If you decided not to enable support for SAP System Landscape Directory (SLD) when installing SAP BusinessObjects Enterprise, you can enable it at any time later by installing SAP Host Agent. For more information, see To enable SAP System Landscape Directory (SLD) support. Once SAP Host Agent is installed, open the Central Management Console (CMC), select the "Servers" tab, and restart the SIA nodes. SLD registration will automatically occur whenever a SIA is restarted or created. To enable SLD support for web applications deployed to a web application server, see SAP System Landscape Directory (SLD) registration in the SAP BusinessObjects Enterprise Web Application Deployment Guide.

59

2011-01-10

Post-Installation

5.5.2 To configure SMD Agent post installation

If you did not configure SAP Solution Manager Diagnostics (SMD) during the installation process, you can 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 SAP BusinessObjects Enterprise. 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 in the Central Management Console (CMC). Note: The Introscope Agent must be installed and running before configuring it in the CMC. 1. Open the Central Management Console. 2. Select the Servers tab. 3. Expand the SIA Nodes folder in server list, and right-click the SIA to be updated. 4. Select "Placeholders" from the context menu. 5. Ensure that the placeholders related to Introscope are set correctly: a. Change the %IntroscopeAgentEnableInstrumentation% placeholder from false to true. b. Update the %IntroscopeAgentManagerHost% placeholder with the Introscope Agent hostname. c. Update the %IntroscopeAgenEnterpriseManagerPort% placeholder with the Introscope Agent port number.

60

2011-01-10

Post-Installation

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 Enterprise with Siebel Enterprise, you may need to 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 Siebel Dedicated 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 the SAP BusinessObjects Enterprise and web application server lib folders. 1. Locate the classes folder that was created when you installed Siebel Tools. The Java data bean files are typically located in the <SIEBEL_HOME>/classes folder. For example, the Siebel classes folder may be /opt/siebel/7.8/classes. 2. Copy the SiebelJI.jar and SiebelJI_enu.jar Java data bean files to the SAP BusinessObjects Enterprise Java lib directory. For example, copy /opt/siebel/7.8/classes/SiebelJI.jar and /opt/siebel/7.8/classes/SiebelJI_enu.jar to <BOE_INSTALL_DIR>/sap_bobj/en terprise_xi40/java/lib/siebel. 3. Copy the SiebelJI.jar and SiebelJI_enu.jar Java data bean files to the lib directory of your web application server. For example, copy /opt/siebel/7.8/classes/SiebelJI.jar and /opt/siebel/7.8/classes/SiebelJI_enu.jar to <WAS_INSTALL_DIR>/lib. If you installed the Tomcat web application server bundled with SAP BusinessObjects Enterprise, the folder is <BOE_INSTALL_DIR>/Tomcat6/lib. 4. Restart the Central Management Server and web application server.

61

2011-01-10

Post-Installation

For more information, see Configuring for Siebel integration in the SAP BusinessObjects Enterprise 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 be copied to the SAP BusinessObjects Enterprise 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 Enterprise JD Edwards lib folder: <BOE_INSTALL_DIR>/sap_bobj/enterprise_xi40/java/lib/jdedwards/default/jd edwards. 4. Also copy the .jar into the web application server Java lib folder. For example, if you're using the web application server bundled with SAP BusinessObjects Enterprise, the default web application server lib directory is: <BOE_INSTALL_DIR>/sap_bobj/enterprise_xi40/tomcat/lib. 5. Restart the Central Management Server and Web Application Server. For more information, see Configuring for JD Edwards integration in the SAP BusinessObjects Enterprise Administrator Guide.

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

To enable reporting from Oracle EBS data sources in SAP Crystal Reports, ensure that the 32-bit Oracle client is installed on systems running SAP Crystal Reports. To enable SAP BusinessObjects Enterprise integration with Oracle EBS, including Oracle EBS authentication and import roles, follow the steps below. 1. Install and configure the 64-bit Oracle client on SAP BusinessObjects Enterprise hosts. When installing the 64-bit Oracle client, ensure that the following components are installed: Oracle JDBC driver

62

2011-01-10

Post-Installation

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 Enterprise Oracle library. Copy: <ORA_HOME>/lib/ocijdbc11.so (on HP-IA: libocijdbc11.sl) <ORA_HOME>/lib/libclntsh.so.11.1 (on HP-IA: libclntsh.sl.11.1) <ORA_HOME>/lib/libnnz11.so (on HP-IA: libnnz11.sl) To: <BOE_INSTALL_DIR>/sap_bobj/enterprise_xi40/java/lib/oracle/default. 4. Copy the following file to the web application server lib directory. Copy: <ORA_HOME>/jdbc/lib/ojdbc5.jar Copy the file to the web application server lib directory. For example, if you're using the web application server bundled with SAP BusinessObjects Enterprise, the default web application server lib directory is: <BOE_INSTALL_DIR>/sap_bobj/enterprise_xi40/tomcat/lib. 5. Restart the CMS. 6. Stop the web application server. 7. Clean up the web application work folder. For example, on the Tomcat 6.0 web application server supplied with SAP BusinessObjects Enterprise, remove all the files in the Tomcat work folder (<BOE_INSTALL_DIR>/Tom cat6/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 is enforced. To do this, manually create the bobj_pkg package in any new Oracle EBS database before using the integration solution for the first time. To generate the package, log on to the Oracle EBS database and use the PL\SQL code given in the following file: <BOE_INSTALL_DIR>/Samples/ebs/bobj_pkg.txt

5.7 Post-install diagnostic checks

You can run the Monitoring Tool at any time to run a diagnostics check and look for problems. To access the Monitoring Tool in order to run diagnostic tests, log on to the Central Management Console (CMC), select the "Monitoring" screen, and click the Probes tab.

63

2011-01-10

Post-Installation

5.8 Making changes to SAP BusinessObjects Enterprise

5.8.1 To modify SAP BusinessObjects Enterprise

These instructions describe the process to modify your SAP BusinessObjects Enterprise installation by adding or removing installed features. It is recommended that you back up the CMS system database before modifying SAP BusinessObjects Enterprise. Note: The CMS must be running in order to modify an SAP BusinessObjects Enterprise installation. 1. Change directory to the <BOE_INSTALL_DIR> folder. 2. Run the command:
./modifyOrRemoveProducts.sh

Note: Log files, configuration files for web applications, and web applications will not be removed by the removal program. Folders left after removing a corresponding feature can be removed manually later with the rm command. 3. Select the installation to be modified. 4. Select the Modify option. 5. Ensure that all features you want available are selected. Ensure that features you do not want installed are deselected. Expand the highlighted feature in the selection tree by pressing the keyboard spacebar. Use the arrow keys to navigate up or down. Toggle feature selections with the X key. When you are satisfied with the selected features, press Enter. 6. If you are modifying a server with a CMS installed, press Enter to apply the changes. If you are modifying a server that uses a remotely installed CMS, enter the hostname, port, and an administrative account username and password. 7. When the changes have been made, press Enter to return to the command-line. The installation has been updated.

64

2011-01-10

Post-Installation

5.8.2 To repair SAP BusinessObjects Enterprise

These instructions describe the process to repair an SAP BusinessObjects Enterprise installation. This process restores the files and settings originally configured by the setup program. It is recommended that you back up the CMS system database before repairing SAP BusinessObjects Enterprise. Note: The CMS must be running in order to modify an installation. 1. Change directory to the <BOE_INSTALL_DIR> folder. 2. Run the command:
./modifyOrRemoveProducts.sh

Note: Log files, configuration files for web applications, and web applications will not be removed by the removal program. Any remaining folders can be removed manually with the rm command. 3. Select the installation to be repaired. 4. Select the Repair option. 5. Enter the hostname, port, and an administrative account username and password. 6. When the repair is finished, press Enter to return to the command-line. The installation has been repaired, restoring your system to its original configuration.

5.8.3 To remove SAP BusinessObjects Enterprise

These instructions describe the process to permanently uninstall SAP BusinessObjects Enterprise from a system. It is recommended that you back up the CMS database before removing SAP BusinessObjects Enterprise. Note: Add-on products that with dependencies on other products should be removed before the product on which they depend. For example, for servers with SAP BusinessObjects Enterprise Explorer installed, SAP BusinessObjects Enterprise Explorer should be removed first, as it will not function without SAP BusinessObjects Enterprise. Removing SAP BusinessObjects Enterprise removes the core product plus any installed maintenance packages. To remove maintenance packages individually, see the installation guides for those maintenance packages.

65

2011-01-10

Post-Installation

The following items will remain: The repository database, as it may be shared with other programs The file repository folder, as it may contain user data Web applications deployed to a web application server will not be undeployed. Use the WDeploy command or the web application server administrative console to undeploy web applications. Web application files customized to an individual web application server Configuration files Note: These items can be manually removed later by an administrator, if required. 1. Stop all server processes. Change directory to the <BOE_INSTALL_DIR>/sap_bobj folder and run the command:
./ccm.sh stop all

Alternatively, run the command:

./stopservers

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

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

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

5. Run the command:

./modifyOrRemoveProducts.sh

Note: Log files, configuration files for web applications, and web applications will not be removed by the removal program. Any remaining folders can be removed manually with the rm command. 6. Select the installation to remove. 7. Select the Remove option. The software has been removed from the system.

5.9 When the administrator account password is lost

66

2011-01-10

Post-Installation

If the credentials for the SAP BusinessObjects Enterpriseadministrator account are lost, consider the following potential resolutions: If another administrative account is available, use it to change the password for the SAP BusinessObjects Enterpriseadministrator account. Reset the SAP BusinessObjects Enterpriseadministrator account password with the steps shown in "To reset the SAP BusinessObjects Enterprise administrator account password".

5.9.1 To reset the SAP BusinessObjects Enterprise administrator account password

Use the following instructions if you have lost access to the credentials for the SAP BusinessObjects Enterpriseadministrator account and cannot use another account to reset the password. Note: Access to the machine hosting the Server Intelligence Agent (SIA) is required. Ensure that SAP BusinessObjects Enterprise is running.

1. Go to the following folder: <BOE_INSTALL_DIR>/sap_bobj/enterprise_xi40/dfo The dfo folder contains a subfolder with a randomly generated name starting with dfo_. 2. Copy the file named BusinessObjects_Administrator_dfo.xml from inside the dfo_ folder to the following folder: <BOE_INSTALL_DIR>/sap_bobj/enterprise_xi40/packages 3. Locate the CMS process. Use the ps command to find a process named boe_cmsd. For example:
ps aux | grep boe_cmsd

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

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

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

67

2011-01-10

Post-Installation

Use the ccm.sh command in <BOE_INSTALL_DIR>/sap_bobj. For example:

cd <BOE_INSTALL_DIR>/sap_bobj ./ccm.sh -stop mysia1

Once you have confirmed that the SIA has stopped, proceed to the next step. 6. Paste the CMS command to a command-line. Do not press Enter. Paste the result of step 4 onto the command-line. 7. Append the -serverconsole switch to the command and press Enter. For example, note that the following command has -serverconsole appended:
/opt/sap_bobj/enterprise_xi40/linux_x64/boe_cmsd -loggingPath /opt/sap_bobj/logging/ -port 6400 -restart -dbinfo /opt/sap_bobj/enterprise_xi40/linux_x64/_boe_mysia1.dbinfo -noauditor -autoboot -fg -name mysia1.cms -pidfile /opt/sap_bobj/serverpids/mysia1_mysia1.CentralManagementServer.pid -serverconsole

The SIA is launched in serverconsole mode. You will be prompted when the SIA is ready to accept commands. 8. Enter the following query:
select si_id from ci_systemobjects where si_name='Administrator'

Four objects are returned. Record the SI_ID for each object. Tip: One of the entries should have the SI_ID set to 12. 9. Delete the objects by typing the following command for each object:
delete <ID_NUMBER>

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

No objects should be returned. 11. Enter the following query:

select si_id from ci_systemobjects where si_name='BusinessObjects_Administrator_dfo.xml'

One object should be returned. Record the object's SI_ID number. 12. Delete the object by entering the following command:
delete <SI_ID>

13. Type quit to exit. 14. Use the CCM to start the SIA. Use the ccm.sh command in <BOE_INSTALL_DIR>/sap_bobj. For example:
cd <BOE_INSTALL_DIR>/sap_bobj ./ccm.sh -start mysia1

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

68

2011-01-10

More Information

More Information

Information Resource

Location

SAP BusinessObjects product information

http://www.sap.com Navigate to http://help.sap.com/businessobjects and on the "SAP BusinessObjects Overview" side panel click All Products. You can access the most up-to-date documentation covering all SAP BusinessObjects products and their deployment at the SAP Help Portal. You can download PDF versions or installable HTML libraries. Certain guides are stored on the SAP Service Marketplace and are not available from the SAP Help Portal. These guides are listed on the Help Portal accompanied by a link to the SAP Service Marketplace. Customers with a maintenance agreement have an authorized user ID to access this site. To obtain an ID, contact your customer support representative. http://service.sap.com/bosap-support > Documentation Installation guides: https://service.sap.com/bosap-instguides Release notes: http://service.sap.com/releasenotes

SAP Help Portal

SAP Service Marketplace

The SAP Service Marketplace stores certain installation guides, upgrade and migration guides, deployment guides, release notes and Supported Platforms documents. Customers with a maintenance agreement have an authorized user ID to access this site. Contact your customer support representative to obtain an ID. If you are redirected to the SAP Service Marketplace from the SAP Help Portal, use the menu in the navigation pane on the left to locate the category containing the documentation you want to access. https://cw.sdn.sap.com/cw/community/docupedia

Docupedia

Docupedia provides additional documentation resources, a collaborative authoring environment, and an interactive feedback channel. https://boc.sdn.sap.com/

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

69

2011-01-10

More Information

Information Resource

Location

SAP BusinessObjects articles on the SAP Community Network

https://www.sdn.sap.com/irj/boc/businessobjects-articles These articles were formerly known as technical papers. https://service.sap.com/notes

Notes These notes were formerly known as Knowledge Base articles. Forums on the SAP Community Network https://www.sdn.sap.com/irj/scn/forums http://www.sap.com/services/education Training From traditional classroom learning to targeted e-learning seminars, we can offer a training package to suit your learning needs and preferred learning style. http://service.sap.com/bosap-support Online customer support The SAP Support Portal contains information about Customer Support programs and services. It also has links to a wide range of technical information and downloads. Customers with a maintenance agreement have an authorized user ID to access this site. To obtain an ID, contact your customer support representative. http://www.sap.com/services/bysubject/businessobjectsconsulting Consulting Consultants can accompany you from the initial analysis stage to the delivery of your deployment project. Expertise is available in topics such as relational and multidimensional databases, connectivity, database design tools, and customized embedding technology.

70

2011-01-10

Index
64-bit HPUX installation 16 platform 16

E
Enterprise Resource Planning (ERP) 9, 26

J
JD Edwards EnterpriseOne 9 JD Edwards integration 62

A
account permissions 16 administrator password 67 AIX 23 Auditing Data Store preparing for 19

F
feature codes Enterprise 49 features, new 8

L
LANG environment variable 17 languages 8 LC_ALL environment variable 17 locale 17

B
BusinessObjects Enterprise upgrade from 10

G
GNU products 17

M
Monitoring Tool 63

H
HPUX installation 16

C
CA Wily Introscope post-install configuration 60 support 25 check-list installation 26 Client Tools 8 CMC launching 57 troubleshooting 57 CMS system database preparing for 19 co-existence, product 11 command-line installation 40 installation program parameters 41 components, new 8

N
network permissions 18

I
installation account permissions 16 check-list 26 command-line 40, 41 custom 33, 34 Enterprise feature codes 49 expand 33 full 30 JD Edwards EnterpriseOne 62 methods 27 Oracle EBS integration 62 parameters 44 planning 7 post-install 57 preparation for 15 requirements 16 response file 40, 42, 43 response file example 52 Siebel integration 61 silent 43 software removal 65 type 29 web tier 38 Introscope see CA Wily Introscope 25

O
object types requirements 10 Oracle E-Business Suite 9, 62

P
password reset 67 PeopleSoft Enterprise 9 permissions for installation account 16 network 18 planning installation 7 post-installation 57 diagnostic tests 63

D
database choosing 13 DB2 extra requirements 21, 22 deployment web applications 59 diagnostic tests 63 disaster mitigation reset administrator password 67

R
remove software 65 requirements 16 response file 42, 43 Enterprise feature codes 49 example 52 parameters 44

71

2011-01-10

Index

S
SAP ERP 9 SAP Host Agent 15, 23 SAP System Landscape Directory (SLD) 23 Siebel Enterprise 9 Siebel integration 61 SMD Agent 24 post-install configuration 60

SUSE 23 Sybase extra requirements 22 System Landscape Directory (SLD) Data Supplier (DS) 59

upgrade support 10 upgrades requirements object types 10

U
ulimit 23 uninstallation 65

W
web application server, choosing 12 web applications 59 web server, choosing 13

72

2011-01-10