BusinessObjects XI 3.1 FixPack 2.

1 and above Installation and Deployment Guide

BusinessObjects Enterprise XI 3.1

Copyright

© 2009 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. 2009-10-12

Contents
Chapter 1 Introduction 5 About this Document...................................................................................6 Purpose..................................................................................................6 Constraints.............................................................................................6 What's new.............................................................................................7 Chapter 2 Planning 9

BusinessObjects FixPacks........................................................................10 FixPack platform support...........................................................................13 FixPack language support.........................................................................14 FixPack installation limitations and restrictions.........................................15 Planning your FixPack installation.............................................................17 Downloading FixPacks..............................................................................18 Chapter 3 Installation scenarios 19

FixPack installation scenarios....................................................................20 Updating a distributed BusinessObjects Enterprise deployment...............21 Updating web application components......................................................21 Saving web.xml file modifications..............................................................22 Chapter 4 FixPack installation on Windows 23

To install BusinessObjects FixPacks for server components on Windows.24 To install BusinessObjects FixPacks for client components on Windows..26 Silent installation on Windows...................................................................27 To run a silent installation using a response file on Windows..............27

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

3

Contents

Silent installation parameters on Windows..........................................28 Uninstalling BusinessObjects FixPacks on Windows................................33 To uninstall BusinessObjects FixPacks on Windows...........................34 Chapter 5 FixPack installation on UNIX 35

To install the BusinessObjects Enterprise FixPack on UNIX.....................36 Silent installation on UNIX.........................................................................38 To run a silent installation using a response file on UNIX....................38 Response file installation parameters for UNIX...................................39 To uninstall BusinessObjects FixPacks on UNIX.......................................44 Chapter 6 Uninstalling web application components 45

4

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

Introduction

1

1

Introduction About this Document

About this Document
This guide is intended for the system administrator or IT professional who is responsible for the installation, deployment, and maintenance of BusinessObjects Enterprise products. Topics covered in this guide include: • FixPack installation on Windows • FixPack installation on UNIX • Silent FixPack installation • Uninstalling FixPacks It is recommended that this guide be used in conjunction with the following FixPack documentation: • The FixPack Release Notes document which contains information about important issues, limitations, and work-arounds for the FixPack release. • The FixPack Fixed Issues document which provides information about the defects addressed by the FixPack. General product documentation, including installation, administration, and reference guides, is available at: http://help.sap.com/.

Purpose
This document is intended as a reference for use by system administrators when updating BusinessObjects Enterprise with the most recent FixPack. For the latest information, updates, and other information, visit the BusinessObjects support site at service.sap.com/bosap-support.

Constraints
This guide does not describe how to set up a host operating system, supported database, web application server, or web server. If you are planning to use a dedicated database, web application server, or web server, it must be installed and functioning before BusinessObjects Enterprise can be installed. Refer to the vendor documentation for more information on installing or upgrading these components.

6

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

Introduction About this Document

1

What's new
BusinessObjects XI 3.1 FixPack 2.1 introduces a new update framework for installing FixPacks on Windows platforms. This has been provided to reduce the time it takes to install updates on Windows. The new framework introduces some changes to the way that FixPacks from version 2.1 and above are uninstalled from Windows machines. • In the "Add or Remove Programs" dialog on Windows machines, FixPacks from version 2.1 and above appear as separate entries, and not as sub-entries of a core product. • FixPacks must be uninstalled across multiple products in reverse order. • Uninstalling a core product does not automatically remove related FixPack updates.
Related Topics

• Uninstalling BusinessObjects FixPacks on Windows

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

7

1

Introduction About this Document

8

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

Planning

2

2

Planning BusinessObjects FixPacks

BusinessObjects FixPacks
A separate FixPack is available for each BusinessObjects product, as outlined in the table below.
Note:

The BusinessObjects Enterprise XI 3.1 FixPack contains client tools updates but will only update client tools that were installed as part of a BusinessObjects Enterprise installation. If you installed client tools separately, using the BusinessObjects Enterprise Client Tools installer, you must use the BusinessObjects Enterprise XI 3.1 Client Tools FixPack to perform your update.

10

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

Planning BusinessObjects FixPacks

2

FixPack BusinessObjects Enterprise XI 3.1 FixPack

Description

Use this FixPack to update BusinessObjects Enterprise XI 3.1 installations. Unlike FixPacks for BusinessObjects XI Release 2, this FixPack is not a suite-wide FixPack for all BusinessObjects products Use this FixPack to update BusinessObjects Enterprise XI 3.1 Client Tools installations. Client tools include: • Desktop Intelligence • Web Intelligence Rich Client • Data Source Migration Wizard • Business View Manager • Report Conversion Tool • Import Wizard • Publishing Wizard • Query as a Web Service • Universe Designer • Universe Builder • Developer Components • BusinessObjects Enterprise .NET SDK • BusinessObjects Enterprise Java SDK • BusinessObjects Enterprise Web Services SDK • • • Translation Manager Software Inventory Tool Diagnostic Tool

BusinessObjects Enterprise XI 3.1 Client Tools FixPack

Note:

The BusinessObjects Client Tools FixPack is only available for Windows.

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

11

2

Planning BusinessObjects FixPacks

FixPack

Description

Crystal Reports 2008 Service Pack 1 Use this FixPack to update Crystal ReFixPack ports 2008 Service Pack 1 installations. Note: If you are running Crystal Reports 2008, see FixPack installation limitations and restrictions. BusinessObjects Live Office XI 3.1 FixPack BusinessObjects XI 3.1 LifeCycle Manager FixPack Use this FixPack to update BusinessObjects Live Office XI 3.1 installations. Use this FixPack to update BusinessObjects XI 3.1 LifeCycle Manager.

BusinessObjects Enterprise XI 3.1 In- Use this FixPack to update Integration tegration for SAP Solutions FixPack for SAP solutions. BusinessObjects Enterprise XI 3.1 In- Use this FixPack to update Integration tegration for PeopleSoft Enterprise for PeopleSoft Enterprise. FixPack BusinessObjects XI 3.1 Integration for Use this FixPack to update Integration Siebel FixPack for Siebel. BusinessObjects XI 3.1 Integration for Use this FixPack to update Integration JD Edwards EnterpriseOne FixPack for JD Edwards EnterpriseOne. BusinessObjects XI 3.1 Integration for Use this FixPack to update Integration Oracle E-Business Suite FixPack for Oracle E-Business Suite. Integration option for Microsoft SharePoint software XI 3.1 FixPack BusinessObjects Mobile XI 3.1 FixPack BusinessObjects BI Widgets XI 3.1 FixPack Note: Use this FixPack to update Integration option for Microsoft SharePoint software XI 3.1. Use this FixPack to update Mobile XI. Use this FixPack to update BI Widgets XI.

FixPacks for other BusinessObjects products may become available at a later date. Refer to the SAP Support Portal for an up-to-date list of available BusinessObjects FixPacks: http://service.sap.com/patches.

12

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

Planning FixPack platform support

2

FixPack platform support
The following table shows the platform support for each BusinessObjects FixPack.
FixPack Windows Solaris AIX Linux HPUX PARISC HP-UX IA64

BusinessObjects Enterprise XI 3.1 FixPack BusinessObjects Enterprise XI 3.1 Client Tools FixPack Crystal Reports 2008 Service Pack 1 FixPack BusinessObjects Live Office XI 3.1 FixPack BusinessObjects XI 3.1 LifeCycle Manager FixPack BusinessObjects Enterprise XI 3.1 Integration for SAP Solutions FixPack BusinessObjects Enterprise XI 3.1 Integration for PeopleSoft Enterprise FixPack BusinessObjects XI 3.1 Integration for Siebel FixPack BusinessObjects XI 3.1 Integration for JD Edwards EnterpriseOne FixPack BusinessObjects XI 3.1 Integration for Oracle E-Business Suite FixPack

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

13

2

Planning FixPack language support

FixPack

Windows

Solaris

AIX

Linux HPUX PARISC

HP-UX IA64

Integration option for Microsoft SharePoint software XI 3.1 FixPack Mobile XI FixPack BI Widgets XI FixPack

FixPack language support
BusinessObjects FixPacks support product language pack updates for the following languages: • Czech • Danish • Dutch • English • Finnish • French • German • Italian • Japanese • Korean • Norwegian • Polish • Portuguese • Russian • Simplified Chinese • Spanish • Swedish • Thai • Traditional Chinese

14

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

Planning FixPack installation limitations and restrictions

2

Note:

The Czech Language Pack was first released with FixPack 1.3. The Finnish Language Pack was first released with FixPack 1.4 The FixPack installation program automatically updates previously installed language packs. You cannot install a new language pack when installing a FixPack. If you are installing a Language Pack that was not available during earlier FixPacks, you must ensure that your BusinessObjects Enterprise deployment is at the same level or higher than the Language Pack that you are installing. For example, if your deployment is at FixPack 1.2 and you want to add the Czech Language Pack from FixPack 1.3, you must either • Update your deployment to FixPack 1.3, which is the same level as the Czech Language Pack, and then install the Czech Language Pack, or • Update your deployment to a higher level than the Language Pack, such as FixPack 2.1, install the Czech Language Pack from FixPack 1.3, and then apply the FixPack 2.1 Language Pack update. If you want to install a Language Pack that is at a lower level than the level of your BusinessObjects Enterprise deployment, install the Language Pack and then apply the Language Pack update so that the Language Pack is at the same level as your deployment. For information about installing an additional language pack, see the BusinessObjects Enterprise XI 3.1 Installation Guide for your platform.

FixPack installation limitations and restrictions
The following limitations and restrictions apply to FixPack installation: • FixPacks are patch installations, not complete product installations. A BusinessObjects product must be installed in order to install a FixPack. • A FixPack only updates files that are already installed. For example, if you previously performed a custom installation, the FixPack will only update the subset of files that were installed during the original, custom installation. • FixPacks only contain updates and fixes for existing product features. New features are not included in FixPack releases.

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

15

2

Planning FixPack installation limitations and restrictions

• •

FixPacks can only be installed in their entirety. You cannot install a subset of FixPack updates. It is required that all components in a BusinessObjects system be at the same Service Pack and FixPack level. For example, BusinessObjects server, client, and web components must be at the same Service Pack and FixPack level. If you update one component of your BusinessObjects system, you must also update the other components. If you uninstall a FixPack for one component in your system, you must uninstall the same FixPack for the other components. If you install a new BusinessObjects product or component to your system after FixPack installation, you must apply the FixPack to the machine where you installed the new product or component to ensure that all BusinessObjects products and components are at the same FixPack level. FixPacks can only be installed on a deployment that is at the same Service Pack level. For example, FixPack 1.x can be installed on BusinessObjects Enterprise XI 3.1, but cannot be installed on BusinessObjects Enterprise XI 3.1 Service Pack 2. You cannot install an earlier FixPack on top of a later FixPack. For example, you cannot install FixPack 1 if FixPack 2 is already installed.
Note:

FixPacks are cumulative. For example, FixPack 2 contains all FixPack 1 updates as well as FixPack 2 updates. • Starting with BusinessObjects XI 3.1 Service Pack 2, if you uninstall a core product, the FixPacks for that product are not automatically uninstalled. You must manually uninstall the FixPacks. For example, if you uninstall BusinessObjects XI 3.1 Service Pack 2, you must manually uninstall 2.x FixPacks from your system. It is only possible to automatically redeploy BusinessObjects web application components using the FixPack installation program if you originally deployed the web application components using the BusinessObjects installation program. For more information see Updating web application components. If you are running Crystal Reports 2008 version 12.0.0.549 or lower, you must upgrade to Crystal Reports 2008 or Crystal Reports Service Pack 1 before applying a FixPack. To determine the version of your Crystal Reports 2008 installation, launch the Crystal Reports Designer and click on Help > About Crystal Reports.

16

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

Planning Planning your FixPack installation

2

You cannot install a new language when applying a FixPack. BusinessObjects FixPacks only update languages that were previously installed with your BusinessObjects installation. For information about installing an additional language for BusinessObjects products, see the BusinessObjects Enterprise XI 3.1 Installation Guide.

Planning your FixPack installation
Before applying a FixPack to your BusinessObjects system the following planning steps are recommended: • Review the FixPack Fixed Issues document to determine if defects addressed by the FixPack are relevant to your BusinessObjects installation.
Note:

If you are installing a FixPack on top of a Limited Availability FixPack ensure that the items addressed by the Limited Availability FixPack are included in the FixPack you want to apply. Review the FixPack Fixed Issues document to see what is included in a FixPack. • • Review the FixPack Release Notes for important issues, limitations, and works-arounds for the FixPack release. Identify all BusinessObjects products and components that require updates. For the BusinessObjects XI 3.1 release, FixPacks are provided for each BusinessObjects product that has its own installer. Refer to BusinessObjects FixPacks to identify the FixPacks required for your upgrade. It is required that all BusinessObjects products and components be at the same Service Pack and FixPack level. If you have a distributed installation or you are running multiple BusinessObjects products, ensure that all products and distributed components are updated. This includes BusinessObjects Enterprise servers, client tools, web components, and other BusinessObjects products such as Crystal Reports, Live Office, and integrations kits. If you have BusinessObjects web application components installed, ensure that you have defined an update path for these components. The update path depends on how you initially deployed the web application

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

17

2

Planning Downloading FixPacks

components. For more information, see Updating web application components. • • • Before you begin, review FixPack installation limitations and restrictions. Review FixPack installation scenarios. The scenarios may be of assistance in planning your upgrade. Before you begin, gather all required documentation. Depending on your upgrade, additional BusinessObjects documentation such as the BusinessObjects Enterprise XI 3.1 Installation Guide may be required. Refer to the "Introduction" for links to additional documentation.

Downloading FixPacks
BusinessObjects FixPacks are available for download from the SAP Support Portal: http://service.sap.com/patches. FixPacks for Crystal Reports are available from the SAP Community Network: https://www.sdn.sap.com/irj/boc/businessobjects-downloads

18

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

Installation scenarios

3

3

Installation scenarios FixPack installation scenarios

FixPack installation scenarios
This topic describes common FixPack installation scenarios that may be of assistance in planning your FixPack installation.
Scenario 1: Applying a FixPack to a BusinessObjects Enterprise installation

In this scenario you must apply the BusinessObjects Enterprise FixPack.
Note:

A typical BusinessObjects Enterprise installation includes client tools. The BusinessObjects Enterprise XI 3.1 FixPack will update client tools that were installed as part of the BusinessObjects Enterprise installation. If you installed client tools using the BusinessObjects Client Tools installer, see Scenario 2.

Scenario 2: Applying a FixPack to a machine with a BusinessObjects Enterprise Client Tools installation

If you originally installed BusinessObjects client tools using the BusinessObjects Client Tools installer, you must apply the BusinessObjects Client Tools FixPack. If you attempt to use a BusinessObjects Enterprise Fix Pack to upgrade a BusinessObjects Client Tools installation, the installer will fail and you will receive an error message.
Scenario 3: Applying a FixPack to a BusinessObjects Enterprise installation that has services distributed across two or more servers

In this scenario you must apply the BusinessObjects Enterprise FixPack on each server to ensure that distributed services are at the same FixPack level. It is required that all BusinessObjects products and components be at the same FixPack and Service Pack level.
Scenario 4: Applying FixPacks to a system with multiple BusinessObjects products

Due to product interdependencies, it is required that all BusinessObjects products be at the same maintenance level. For example, if you want to apply a FixPack to Crystal Reports 2008 Service Pack 1 on a system where you run Crystal Reports, Live Office, and BusinessObjects Enterprise, you must apply FixPacks for all three products so that all products are running

20

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

Installation scenarios Updating a distributed BusinessObjects Enterprise deployment

3

at the same FixPack level. In this scenario, you must apply a Crystal Reports 2008 Service Pack 1 FixPack, a Live Office FixPack, and a BusinessObjects Enterprise FixPack.
Scenario 5: Applying FixPack updates to web application components

How you apply FixPack updates to web application components depends on how components were originally deployed. For more information about applying updates to BusinessObjects web application components, see Updating web application components.

Updating a distributed BusinessObjects Enterprise deployment
If you are installing a FixPack on a distributed BusinessObjects Enterprise deployment, where servers and components are installed across multiple computers, you must first install the FixPack on the computer where the Central Management Server (CMS) is installed. If your deployment has multiple clusters, the credentials for the first CMS that you upgrade must be used when upgrading the other clusters.

Updating web application components
How you apply a FixPack update to BusinessObjects web application components depends on how the components were originally deployed. One of the following three scenarios apply: • If you deployed BusinessObjects web components using the BusinessObjects installation program, the FixPack installation program allows you to update web components automatically when you apply a BusinessObjects FixPack. Follow the FixPack installation steps in this guide to update web application components using the BusinessObjects Enterprise FixPack installation program. • If you deployed BusinessObjects web application components manually, updates must be applied manually after installing the BusinessObjects Enterprise FixPack.

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

21

3

Installation scenarios Saving web.xml file modifications

Manual deployment instructions for web application components are found in the BusinessObjects Enterprise XI 3.1 Web Application Deployment Guide. • If you deployed BusinessObjects web application components using the wdeploy tool, you can apply updates manually or use the wdeploy tool after installing the BusinessObjects Enterprise FixPack. Instructions for the wdeploy tool are found in the BusinessObjects Enterprise XI 3.1 Web Application Deployment Guide. If you deploy web components manually or using the wdeploy tool, you must first install the BusinessObjects Enterprise FixPack to obtain the updated WAR files. The BusinessObjects WAR files are required for web application deployment. For more information, refer to the wdeploy or manual deployment instructions in the BusinessObjects Enterprise XI 3.1 Web Application Deployment Guide.
Note:

If your BusinessObjects system includes web components, you must update the web components as part of your FixPack upgrade. It is required that all BusinessObjects components, including web components, be at the same Service Pack and FixPack level.

Saving web.xml file modifications
When a FixPack is installed, the web.xml files for BusinessObjects web applications that have been deployed to a web application server are overwritten. This means that any customizations that you've made by changing the web.xml files are lost after applying a FixPack update. If you modified a web.xml file for a BusinessObjects web application and do not want to lose your modification, you must make the modifications in the BusinessObjects Enterprise installation directory. On Windows systems, this directory is <InstallDir>\BusinessObjects Enterprise 12.0\warfiles\WebApps. On UNIX systems, this directory is <In stallDir>/bobje/enterprise120/warfiles/WebApps. Then, after you've applied the FixPack, rebuild the affected .war files and redeploy the .war files to the web application server.

22

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

FixPack installation on Windows

4

4

FixPack installation on Windows To install BusinessObjects FixPacks for server components on Windows

You must have Administrator privileges on your Windows system to run a BusinessObjects FixPack installation. In order to free resources on the machine on which you are installing this FixPack, it is recommended that you use the Central Management Console (CMC) to stop all of the BusinessObjects Enterprise servers on the machine before installing the FixPack, with the following exceptions: • Server Intelligence Agent (SIA) • Central Management Server (CMS) • Input and Output File Repository Servers (FRS) • CMS system database These services and servers must be running for the installation to proceed.
Note:

• •

If you have modified web.xml files for BusinessObjects web applications, see Saving web.xml file modifications before you apply a FixPack. Starting from BusinessObjects Enterprise XI 3.1 FixPack 1.5 and later, if you are updating a product that contains server components, the installation setup program prompts you for information for your deployment's Central Management Server (CMS). This is required to update content that is stored in the CMS database, such as localized strings for server properties.

To install BusinessObjects FixPacks for server components on Windows
This procedure is used to install FixPacks that update BusinessObjects Enterprise server components running on Windows. This includes the following packages: • BusinessObjects Enterprise XI 3.1 • BusinessObjects XI 3.1 LifeCycle Manager • BusinessObjects Enterprise XI 3.1 Integration for SAP Solutions • BusinessObjects Enterprise XI 3.1 Integration for PeopleSoft Enterprise • BusinessObjects XI 3.1 Integration for Siebel • BusinessObjects XI 3.1 Integration for JD Edwards EnterpriseOne • BusinessObjects XI 3.1 Integration for Oracle E-Business Suite

24

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

FixPack installation on Windows To install BusinessObjects FixPacks for server components on Windows

4

• •

Integration Option for Microsoft SharePoint Software XI 3.1 BusinessObjects Mobile XI 3.1

1. Launch the installation by running setup.exe 2. Choose a language for the installation setup program to use during the installation process, and click OK. 3. On the "Welcome" dialog, click Next to proceed. 4. On the "License Agreement" dialog, review the contents of the End User License Agreement, and click Next to proceed if you agree to the terms. 5. If the product you are updating includes server components, the "CMS" dialog is displayed. Type the Hostname, Port Number, and Administrator Password for your deployment's CMS, and click Next to continue. 6. If the product you are updating includes web components that were automatically deployed during your original BusinessObjects installation, the "Automatically Re-Deploy Web Applications?" dialog is displayed. Choose from one of two options: • Yes, automatically re-deploy the web applications. This option redeploys BusinessObjects web application components that were previously deployed. Additional configuration dialogs specific to the web application server type are presented. Provide the required information and click Next to continue.
Note:

For additional information about specific configuration settings for each web application server, refer to the BusinessObjects XI 3.1 Installation Guide for Windows. • No, I will re-deploy the web applications after installation. Select this option if you want to deploy web application server components manually or using the wdeploy tool. Refer to the BusinessObjects XI 3.1 Web Application Deployment Guide for Windows for information about manual installation of web components or installation using the wdeploy tool.
Note:

It is only possible to automatically redeploy web application components to the same web application server type you deployed to during your original BusinessObjects installation.

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

25

4

FixPack installation on Windows To install BusinessObjects FixPacks for client components on Windows

7. On the "Start Installation" dialog, click Next to begin the installation. 8. If you updated BusinessObjects Enterprise, verify that BusinessObjects services are running after the system is restarted. If any services are not running, start them manually using the BusinessObjects Central Management Console (CMC), Central Configuration Manager (CCM), or Windows Services panel. The CMC or CCM can be accessed under Start > Programs > BusinessObjects XI 3.1 > BusinessObjects Enterprise.
Note:

To review details of the installation, you can view the contents of the installation log file located in <INSTALLDIR>\BusinessObjects Enterprise 12.0\Logging

To install BusinessObjects FixPacks for client components on Windows
This procedure is used to install FixPacks for BusinessObjects client applications. This includes the following packages: • Crystal Reports 2008 Service Pack 1 • BusinessObjects Live Office XI 3.1 • BusinessObjects BI Widgets XI 3.1 1. Launch the installation by running setup.exe 2. On the "Welcome" dialog, click Next. 3. On the "License Agreement" dialog, review the contents of the End User License Agreement, and click Next to proceed if you agree to the terms. 4. On the "Start Installation" dialog, click Next to begin the installation. The "Installation Progress" dialog appears.

26

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

FixPack installation on Windows Silent installation on Windows

4

Silent installation on Windows
To run a silent installation using a response file on Windows
BusinessObjects FixPacks can be installed silently using a response file. Silent installation is particularly useful when you need to quickly perform multiple installations or automate installations. To run a silent installation using a response file you must first create a .ini file using the BusinessObjects setup program. Once you have created the .ini file, you can run a silent installation by running the setup.exe command and specifying the path to the .ini file. 1. Create an installation .ini file (a response file). a. Open a command line console. b. From the directory that contains the BusinessObjects setup.exe file, run the setup.exe command with the write option (-w) specified: setup.exe -w filename.ini responsefilepath where filename.ini is the name you have given to the response file and responsefilepath is the location where you want the file created.
Note:

If a file path is not specified, the file is stored in the directory that setup.exe is run from. The installation program must have write permissions on this directory. c. Press Enter to launch the installation setup program. d. Follow the on-screen instructions to enter your preferred installation settings until you reach the Start installation dialog of the setup program. e. Click Cancel to abort the installation setup. All parameters from the installation setup program, both user defined and default, are recorded in the .ini file which is saved to the directory you specified.

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

27

4

FixPack installation on Windows Silent installation on Windows

2. You can now run a response file installation using the .ini file by issuing setup.exe command with the read option specified (-r): setup.exe -r <filepath/filename.ini> where <filepath/filename.ini> is the path to the .ini file you created.
Note:

You can specify the -l option when running a response file installation to create an installation log file in the specified file path. If a file path is not specified, the log file is created in the directory that setup.exe is run from. -l <filepath/filename.ini>

Silent installation parameters on Windows
The following table lists parameters that are used for response file silent installation on Windows. It is recommended that you create response files using the BusinessObjects setup program (setup.exe) as described in To run a silent installation using a response file on Windows.

28

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

FixPack installation on Windows Silent installation on Windows

4

Parameter CLIENTLANGUAGE

Description

Specifies the language used by the installer: • CS=Czech • DA=Danish • DE=German • EN=English • ES=Spanish • FI=Finnish • FR=French • IT=Italian • JA=Japanese • KO=Korean • NB=Norwegian • NL=Dutch • PL=Polish • PT=Portuguese • RU=Russian • SV=Swedish • TH=Thai • ZH_CN=Simplified Chinese • ZH_TW=Traditional Chinese
Note:

If this parameter is not specified, you will be prompted to select a language when the installation setup begins. CLIENTLANGUAGE="EN"
/qn

Specifies not to prompt during the installation.
Note:

You must also enter the CLIENTLANGUAGE parameter as part of your silent install string or the language selection screen will appear at the beginning of your installation.
/qn+

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

29

4

FixPack installation on Windows Silent installation on Windows

Parameter

Description

Specifies to prompt when the installation is complete.
Note:

You must also enter the CLIENTLANGUAGE parameter as part of your silent install string or the language selection screen will appear at the beginning of your installation.
AS_ADMIN_IS_SECURE

Specifies that an administrator credential must be passed to access the web application server. This setting only valid for WebSphere 6 and Oracle. AS_ADMIN_IS_SECURE="true"

AS_ADMIN_PASSWORD

Password used by the administrator account to access the web application server. AS_ADMIN_PASSWORD="pass"

AS_ADMIN_PORT

Administration port of the application server. Mandatory for NetWeaver, Oracle Application Server, and WebLogic. • For WebSphere, the SOAP port. If not set, the default SOAP port will be used. • For Oracle Application Server (oas1013): wdeploy expects the request port of the <notification-server> element in the [opmn.xml] file.

AS_ADMIN_USERNAME

Specifies the account name used by the administrator to access the web application server. AS_ADMIN_USERNAME="admin"

AS_DIR

Specifies the installation directory for the web application server. AS_DIR="<INSTALLDIR>/Tomcat55"

30

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

FixPack installation on Windows Silent installation on Windows

4

Parameter AS_INSTANCE

Description

Specifies the name of the current web application server instance. AS_INSTANCE="localhost"

AS_SERVER

Web application type used in installation. the following options are available: • Use tomcat55 for Tomcat • Use oas1013 for Oracle Application Server 10g R3 • Use weblogic9 for WebLogic 9 • Use weblogic10 for WebLogic 10 • Use websphere6 for WebSphere 6.1 AS_SERVER="tomcat55"

AS_SERVICESpecifies the name of the Windows service if the application NAME

server will be installed as a service on Windows. AS_SERVICE_NAME="BOE120Tomcat"

AS_VIRTUAL_HOST

Specifies virtual host to which the application must be bound. AS_VIRTUAL_HOST="hostname"

AUTODESpecifies if the web application (.war) files are to be automatPLOY_W AR_FILES

ically deployed by the installation setup program. • To have the installation setup program automatically deploy .war files, type AUTODEPLOY_WAR_FILES=1 • To deploy .war files manually after the installation setup program runs, type AUTODEPLOY_WAR_FILES=0

CMSPASSWORD

Specifies the password for the Administrator account for the Central Management Server (CMS). Only required if a nonblank password was used when the core product was first installed. CMSPASSWORD="myPassword"

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

31

4

FixPack installation on Windows Silent installation on Windows

Parameter

Description

ENABLELOGSpecifies if a log file will be created for the installation. FILE

ENABLELOGFILE="1"
INSTALLDIR

Specifies the directory where you want to install BusinessObjects. INSTALLDIR="C:\Program Files\Business Ob jects\"

NAMESERVER

Specifies the name of the CMS NAMESERVER="servername"

NSPORT

Specifies the port used by the CMS NSPORT="6400"

The following parameters are automatically generated parameters that should not be modified in the .ini file.

32

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

FixPack installation on Windows Uninstalling BusinessObjects FixPacks on Windows

4

Parameter name ADDLOCAL ADDSOURCE ADVERTISE REMOVE SKIP_DEPLOYMENT WDEPLOY_LATER

Uninstalling BusinessObjects FixPacks on Windows
FixPacks can only be uninstalled one at a time, in the reverse order of installation. When uninstalling FixPacks, you must uninstall other FixPacks, in reverse order, so that all of the products in your deployment are at the same update level. For example, assume that you've installed the following products and updates in the order specified: • BusinessObjects Enterprise XI 3.1 • Crystal Reports 2008 Service Pack 1 • BusinessObjects Enterprise XI 3.1 Service Pack 2 • Crystal Reports 2008 Service Pack 2 • BusinessObjects Enterprise XI 3.1 FixPack 2.1 • Crystal Reports 2008 Service Pack 2 FixPack 2.1 • BusinessObjects Enterprise XI 3.1 FixPack 2.2 • Crystal Reports 2008 Service Pack 2 FixPack 2.2 If you want to revert back to the Service Pack 2 level, you must uninstall the FixPacks in the following order: • Crystal Reports 2008 Service Pack 2 FixPack 2.2. • BusinessObjects Enterprise XI 3.1 FixPack 2.2. • Crystal Reports 2008 Service Pack 2 FixPack 2.1. • BusinessObjects Enterprise XI 3.1 FixPack 2.1.

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

33

4

FixPack installation on Windows Uninstalling BusinessObjects FixPacks on Windows

If you uninstalling updates or services packs from BusinessObjects XI 3.1 Service Pack 2 or earlier and you uninstall updates and service packs out of order, your system is in an unsupported state, and you must perform a repair install with the latest Service Pack and FixPack. For example, if your deployment has Crystal Reports 2008, with FixPack 1.2, Service Pack 2, FixPacks 2.1 and 2.2, and Service Pack 3, and you uninstall Service Pack 2, you must run a repair install on Service Pack 3 to return your system to a supported state. From FixPack 2.1 and onwards, FixPacks appear as separate entries in the "Add or Remove Programs" dialog. Previous FixPack versions appear as sub-entries of the core product.

To uninstall BusinessObjects FixPacks on Windows
To uninstall a FixPack, perform the following steps: 1. In Windows, click Start, point to Settings, and then select Control Panel. 2. Double-click Add or Remove Programs. The "Add or Remove Programs" dialog displays the most recent FixPack that has been installed. For example, BusinessObjects Enterprise XI 3.1 FP2.1 update. From FixPack 2.1 onwards, FixPacks appear as a separate entry in the "Add or Remove Programs" dialog, and not as a sub-entry of a core product. 3. Highlight the FixPack entry in the list of programs and click Remove. 4. The "Add or Remove Programs" dialog box prompts you to confirm that you want to remove the FixPack from your computer. Click Yes. 5. Wait while the appropriate files are removed and the necessary configuration is carried out. Click Finish. After the FixPack is uninstalled you are returned to the "Add or Remove Programs" dialog. For information about uninstalling BusinessObjects web application components, see Uninstalling web application components.

34

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

FixPack installation on UNIX

5

5

FixPack installation on UNIX To install the BusinessObjects Enterprise FixPack on UNIX

To install the BusinessObjects Enterprise FixPack on UNIX
In order to free resources on the machine on which you are installing this FixPack, it is recommended that you use the Central Management Console (CMC) to stop all of the BusinessObjects Enterprise servers on the machine before installing the FixPack, with the following exceptions: • Server Intelligence Agent (SIA) • Central Management Server (CMS) • Input and Output File Repository Servers (FRS) • CMS system database These services and servers must be running for the installation to proceed.
Note:

• •

If you have modified web.xml files for BusinessObjects web applications, see Saving web.xml file modifications before you apply a FixPack. Starting from BusinessObjects Enterprise XI 3.1 FixPack 1.5 and later, if you are updating a product that contains server components, the installation setup program prompts you for information for your deployment's Central Management Server (CMS). This is required to update content that is stored in the CMS database, such as localized strings for server properties.

Perform the following steps to install the FixPack: 1. Launch the installation by running the following command from the FixPack installation source file location: install.sh<INSTALLDIR> where <INSTALLDIR> is the installation directory of your BusinessObjects product. 2. Review the content of the License agreement and proceed by selecting Y. 3. If the product you are updating includes server components, the "Enter information for existing CMS" dialog is displayed. Type the Hostname, Port Number, and Administrator Password for your deployment's CMS, and press Enter to continue.

36

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

FixPack installation on UNIX To install the BusinessObjects Enterprise FixPack on UNIX

5

4. If the product you are updating includes web components that were automatically deployed during your original BusinessObjects installation, the "Redeploy Web Applications" dialog is displayed. Specify whether or not you want the installation setup program to redeploy the web application components that were previously deployed. Choose from one of two options: • Yes. Additional configuration dialogs specific to the web application server type are presented. Provide the required information and press Enter to continue.
Note:

For additional information about specific configuration settings for each web application server, refer to the BusinessObjects XI 3.1 Installation Guide for UNIX. • No. Select this option if you want to deploy web application server components manually or using the wdeploy tool. Refer to the BusinessObjects XI 3.1 Web Application Deployment Guide for UNIX for information about manual installation of web components or installation using the wdeploy tool.
Note:

It is only possible to automatically redeploy web components to the same web application server type you deployed to during your original BusinessObjects installation. 5. A dialog appears that shows the installation directory you have specified. Verify the installation directory and press Enter to start the installation. The progress indicator displays the status of the installation. 6. Press Enter to complete the installation.
Note:

The FixPack installer creates a backup of modified files in <IN STALLDIR>/setup/backup. It is recommended that you not modify or remove these files. To review details of the installation, you can view the contents of the installation log file located in <INSTALLDIR>/setup/logs/

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

37

5

FixPack installation on UNIX Silent installation on UNIX

Silent installation on UNIX
To run a silent installation using a response file on UNIX
BusinessObjects FixPacks can be installed silently using a response file. Silent installation is particularly useful when you need to quickly perform multiple installations or automate installations. To run a silent installation using a response file you must first create a response file. The following steps describe how to create a response file using the BusinessObjects installation program. Once you have created the response file, you can run a silent installation by running the ./install.sh command and specifying the path to the response file. 1. Create a response file. a. From the FixPack installation source file location, run the .in stall.sh command with the write option (-WRITERESPONSEPATH) specified: ./install.sh <INSTALLDIR> -WRITERESPONSEPATH <re sponse_file_path> where <INSTALLDIR> is the BusinessObjects installation directory and <response_file_path> is the path and file name for the response file you are creating. b. Press Enter to launch the installation setup program. c. Follow the on-screen instructions to enter your preferred installation settings until you reach the Start installation dialog of the setup program. The settings are recorded in the response file. d. Press [Ctrl -X] to abort the installation setup. The parameters from the installation setup program, both user defined and default, are recorded in the response file which is saved to the directory you specified.

38

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

FixPack installation on UNIX Silent installation on UNIX

5

2. You can now run a response file installation by issuing ./install.sh command with the -READRESPONSEPATH option specified: ./install.sh <INSTALLDIR> -READRESPONSEPATH sponse_file_path> 3. Press Enter to launch the installation. <re

Response file installation parameters for UNIX
The following table lists parameters that are commonly used for response file silent installation on UNIX. It is recommended that you create a response files using ./install.sh and the -WRITERESPONSEPATH parameter, as described in To run a silent installation using a response file on UNIX.

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

39

5

FixPack installation on UNIX Silent installation on UNIX

Parameter CDDIR

Description

Path to the DISK_1 directory on the distribution CD or directory location for your FixPack installation files. This path defaults to the CD directory. CDDIR="<CD>/BusinessObjects/DISK_1"

CLIENTLANGUAGE

The language setting used for the installation program. • chs=Simplified Chinese • cht=Traditional Chinese • cs=Czech • da=Danish • de=German • en=English • es=Spanish • fi=Finnish • fr=French • it=Italian • jp=Japanese • ko=Korean • nb=Norwegian • nl=Dutch • pl=Polish • pt=Portuguese • ru=Russian • sv=Swedish • th=Thai CLIENTLANGUAGE="en"

INSpecifies a comma-delimited list for the BusinessObjects STALLMODE

Enterprise installer operating modes. This parameter supports the following options: • interactive, install • silent, install INSTALLMODE=silent,install

40

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

FixPack installation on UNIX Silent installation on UNIX

5

Parameter REDEPLOYWEBAPPS

Description

Specifies whether the installation program automatically deploys the web applications. REDEPLOYWEBAPPS=true

AS_DIR

Specifies the path of the application server directory if the server is being installed. The path is automatically set using the installation directory. AS_DIR=“<INSTALLDIR>/bobje/tomcat/”

AS_SERVER

Specifies the name of the application server being installed. • Use tomcat55 for Tomcat • Use oas1013 for Oracle Application Server 10g R3 • Use weblogic9 for WebLogic 9 • Use weblogic10 for WebLogic 10 • Use websphere6 for WebSphere 6.1 AS_SERVER=“tomcat55”

AS_INSTANCE

Specifies the name of the current web application server instance. AS_INSTANCE="localhost"

AS_VIRTUAL_HOST

Specifies virtual host to which the application must be bound. AS_VIRTUAL_HOST="hostname"

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

41

5

FixPack installation on UNIX Silent installation on UNIX

Parameter AS_ADMIN_PORT

Description

Administration port of the application server. Mandatory for NetWeaver, Oracle Application Server, and WebLogic. • For WebSphere, the SOAP port. If not set, the default SOAP port will be used. • For Oracle Application Server (oas1013): wdeploy expects the request port of the <notification-server> element in the [opmn.xml] file.

AS_ADMIN_USERNAME

Specifies the account name used by the administrator to access the web application server. AS_ADMIN_USERNAME="admin"

AS_ADMIN_PASSWORD

Password used by the administrator account to access the web application server. AS_ADMIN_PASSWORD="pass"

AS_ADMIN_IS_SECURE

Specifies is administrator credential must be passed to access the web application server. This setting only valid for WebSphere 6 and Oracle. AS_ADMIN_IS_SECURE="true"

CMSNAMESERVER

Specifies the name of the CMS CMSNAMESERVER="servername"

CMSPORTNUMBER

Specifies the port used by the CMS CMSPORTNUMBER="6400"

42

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

FixPack installation on UNIX Silent installation on UNIX

5

Parameter CMSPASSWORD

Description

Specifies the password for the Administrator account for the Central Management Server (CMS). Only required if a nonblank password was used when the core product was first installed. CMSPASSWORD="myPassword"

ENABLEMP

Specifies which specific products to manually enable. Each product must be separated by a comma. For a custom installation this setting is used to enable those products typically not installed in a new installation. ENABLEMP=BusinessObjects.WebTier Components,

DISABLEMP

Specifies which specific products to manually disable. Each product must be separated by a comma. For a custom installation this setting is used to disable those products typically not installed in a new installation. DISABLEMP=BusinessObjects.WebTierComponents,

The following parameters are automatically generated parameters that should not be modified in the response file.
Parameter name BOBJDIR CDDIR FUNCTION INSTALLLEVEL LANGPACKS_TO_INSTALL LICENSEDIR LOCALNAMESERVER MACHINENAME

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

43

5

FixPack installation on UNIX To uninstall BusinessObjects FixPacks on UNIX

Parameter name PRODUCTID_NAME PRODUCTID_VER ProductVersion VERSION_IN_RANGE

To uninstall BusinessObjects FixPacks on UNIX
FixPacks can only be uninstalled one at a time, in the reverse order of installation. For example, if you installed FixPack 2.1 and then FixPack 2.2, you must uninstall FixPack 2.2 before you can uninstall FixPack 2.1. To uninstall a FixPack, perform the following steps: 1. To uninstall a FixPack, execute the following command from the root directory of your BusinessObjects installation: ./AddOrRemovePrograms.sh The "Add or Remove Programs" dialog is displayed. 2. Select the BusinessObjects FixPack you want to remove and press Enter. 3. Select Uninstall Product and press Enter. A confirmation dialog is displayed. 4. Select Yes and press Enter. The uninstall process begins. For information about uninstalling BusinessObjects web application components, see Uninstalling web application components.

44

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

Uninstalling web application components

6

6

Uninstalling web application components

If you are uninstalling BusinessObjects web applications components from a Windows machine, the previous versions of the web applications are not automatically redeployed. You must either redeploy the web applications manually or by using wdeploy. If you are uninstalling BusinessObjects web application components from a UNIX machine, the previous versions of the web applications are only automatically redeployed if the .war files were automatically deployed when the previous version was installed. For instructions on redeploying .war files, please refer to the “Deploying with wdeploy” chapter of the BusinessObjects Enterprise Deployment guide for Windows or the BusinessObjects Enterprise Deployment guide for UNIX, available at http://help.sap.com/businessobjects.

46

BusinessObjects XI 3.1 FixPack 2.1 and above Installation and Deployment Guide

Sign up to vote on this title
UsefulNot useful