SAP BusinessObjects Edge BI 3.1 FixPack Installation and Deployment Guide SAP BusinessObjects Edge BI 3.1 FixPack 1.2

2010-01-07

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. 2010-01-07

Contents

Chapter 1
Introduction.....5 SAP BusinessObjects FixPacks....5 Folder Structure....7 FixPack platform support....10 FixPack language support...11 Planning your FixPack installation...12 FixPack installation scenarios....12 Updating web application components...13 FixPack installation limitations and restrictions..14 Saving web.xml file modifications...15 Downloading FixPacks....15 Crystal Reports FixPack compatibility...15 FixPack installation on Windows...17 Installing SAP BusinessObjects Edge BI 3.1 FixPack on Windows...17 FixPack installation on Linux....19 Installing SAP BusinessObjects Edge BI 3.1 FixPack on Linux..19 Silent FixPack installation....21 Silent installation on Windows...21 Running a silent installation using a response file on Windows..21 Silent installation parameters (Windows)...22 Silent installation on Linux....25 Running a silent installation using a response file on Linux..25 Response file installation parameters (Linux)...26 Uninstalling FixPacks...31 Uninstalling SAP BusinessObjects Edge BI FixPacks on Windows...31 Uninstalling SAP BusinessObjects Edge BI 3.1 FixPacks on Linux...31 Uninstalling web application components...32
1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 1.10 1.11

Chapter 2

Chapter 3

Chapter 4

4.1 4.1.1 4.1.2 4.2 4.2.1 4.2.2

Chapter 5

5.1 5.2 5.3

Introduction

This guide is intended for the system administrators or IT professionals, who are responsible for the installation, deployment, and maintenance of SAP BusinessObjects Edge BI 3.1 products. Topics covered in this guide include: FixPack installation on Windows FixPack installation on Linux Silent FixPack installation Uninstalling FixPacks General product documentation, including installation, administration, and reference guides, is available at: http://help.sap.com/.
1.1 SAP BusinessObjects FixPacks
A separate FixPack is available for each SAP BusinessObjects product, as outlined in the table below. Note: The SAP BusinessObjects Edge BI 3.1 FixPack contains client tools updates but will only update client tools that were installed as part of a SAP BusinessObjects Edge BI 3.1 installation. If you installed client tools separately, using the SAP BusinessObjects Edge Series 3.1 Client Tools installer, you must use the SAP BusinessObjects Edge BI 3.1 Client Tools FixPack to perform your upgrade. When you attempt to install the Web Intelligence Rich Client package that you have downloaded through InfoView on a system where SAP BusinessObjects Edge BI 3.1 or SAP BusinessObjects Edge BI 3.1 Client Tools are already installed, the installation fails. If you have either one of these products installed and want to install the Web Intelligence Rich Client, then in Add or Remove Programs, select BusinessObjects Enterprise, and use the Modify feature to add the Web Intelligence Rich Client to your system.

FixPack

Description

SAP BusinessObjects Edge BI 3.1 FixPack
Use this FixPack to update SAP BusinessObjects Edge BI 3.1 installations. Use this FixPack to update SAP BusinessObjects Edge BI 3.1 Client Tools installations. Client tools include: Desktop Intelligence Web Intelligence Rich Client Data Source Migration Wizard Report Conversion Tool Import Wizard Query as a Web Service Universe Designer Developer Components BusinessObjects Enterprise Java SDK BusinessObjects Enterprise Web Services SDK Translation Manager
SAP BusinessObjects Edge BI 3.1 Client Tools FixPack
Note: The SAP BusinessObjects Client Tools FixPack is only available for Windows. Crystal Reports 2008 Service Pack 1 FixPack Use this FixPack to update Crystal Reports 2008 Service Pack 1 installations. Note: If you are running Crystal Reports 2008, see FixPack installation limitations and restrictions. BusinessObjects Enterprise Live Office XI 3.1 Use this FixPack to update Live Office XI 3.1 installaFixPack tions. BusinessObjects Enterprise XI 3.1 Integration Use this FixPack to update Integration for SAP solufor SAP Solutions FixPack tions. BusinessObjects Enterprise XI 3.1 Integration Use this FixPack to update Integration for PeopleSoft for PeopleSoft Enterprise FixPack Enterprise. Note: FixPacks for other SAP BusinessObjects products may become available at a later date. Refer to the SAP Support Portal for an up-to-date list of available SAP BusinessObjects FixPacks: http://ser vice.sap.com/patches.

1.2 Folder Structure

The following table shows the folder structure for all the products for Windows operating system: Note: SAP Integration Solutions patch installer is applicable only if you have the SAP Integration Solutions licensed package.
Product Name Patch Folder Structure
Server Patch installer Client installer SAP Integration Solutions installer EBS Integration Kit Patch installer SAP BusinessObjects Edge 3.1 Standard JDE Integration Kit Patch installer Siebel Integration Kit Patch installer PeopleSoft Integration Kit Patch installer Live Office installer BI Widgets installer
\setup.exe \collaterals\ClientInstaller\setup.exe \collaterals\SAP Integration Solutions\setup.exe \collaterals\EBS Integration\setup.exe \collaterals\JDE Integration\setup.exe \collaterals\SIEBEL Integration \setup.exe \collaterals\PeopleSoft Integration\setup.exe \collaterals\Add-Ons\Live Office\setup.exe \collaterals\Add-Ons\BI Widgets\setup.exe

Product Name

Folder Structure
Server Patch installer Client installer SAP Integration Solutions installer EBS Integration Kit Patch installer JDE Integration Kit Patch installer Siebel Integration Kit Patch installer PeopleSoft Integration Kit Patch installer Live Office installer BI Widgets installer Data Services installer

\setup.exe \collaterals\ClientInstaller\setup.exe \collaterals\SAP Integration Solutions\setup.exe \collaterals\EBS Integration\setup.exe \collaterals\JDE Integration\setup.exe \collaterals\SIEBEL Integration \setup.exe \collaterals\PeopleSoft Integration\setup.exe \collaterals\Add-Ons\Live Office\setup.exe \collaterals\Add-Ons\BI Widgets\setup.exe \DataServices\setup.exe
SAP BusinessObjects Edge 3.1 with Data Integrator
SAP BusinessObjects Edge 3.1 with Data Management
The following table shows the folder structure for all the products for Linux operating system: Note: SAP Integration Solutions patch installer is applicable only if you have the SAP Integration Solutions licensed package.
Server Patch installer SAP Integration Solutions installer SAP BusinessObjects Edge 3.1 Standard EBS Integration Kit Patch installer JDE Integration Kit Patch installer PeopleSoft Integration Kit Patch installer
\DISK_1\install.sh \collaterals\SAP Integration Solutions\\DISK_1\install.sh \collaterals\EBS Integration\DISK_1\install.sh \collaterals\JDE Integration\DISK_1\install.sh \collaterals\PeopleSoft Integration\DISK_1\install.sh
Server Patch installer SAP Integration Solutions installer SAP BusinessObjects Edge 3.1 with Data Integrator EBS Integration Kit Patch installer JDE Integration Kit Patch installer PeopleSoft Integration Kit Patch installer Data Services installer Server Patch installer SAP Integration Solutions installer SAP BusinessObjects Edge 3.1 with Data Management EBS Integration Kit Patch installer JDE Integration Kit Patch installer PeopleSoft Integration Kit Patch installer Data Services installer
\DISK_1\install.sh \collaterals\SAP Integration Solutions\DISK_1\install.sh \collaterals\EBS Integration\DISK_1\install.sh \collaterals\JDE Integration\DISK_1\install.sh \collaterals\PeopleSoft Integration\DISK_1\install.sh \DataServices\install.sh \DISK_1\install.sh \collaterals\SAP Integration Solutions\DISK_1\install.sh \collaterals\EBS Integration\DISK_1\install.sh \collaterals\JDE Integration\DISK_1\install.sh \collaterals\PeopleSoft Integration\DISK_1\install.sh \DataServices\install.sh
1.3 FixPack platform support
The following table shows the platform support for each SAP BusinessObjects FixPack.

Windows

SAP BusinessObjects Edge BI 3.1 FixPack SAP BusinessObjects Edge BI 3.1 Client Tools FixPack Crystal Reports 2008 Service Pack 1 FixPack BusinessObjects Enterprise Live Office XI 3.1 FixPack BusinessObjects Enterprise XI 3.1 Integration for SAP Solutions FixPack BusinessObjects Enterprise XI 3.1 Integration for PeopleSoft Enterprise FixPack
1.4 FixPack language support
SAP BusinessObjects FixPacks support product language pack updates for the following languages: Danish Dutch English French German Italian Japanese Korean Norwegian Polish Portuguese Russian Simplified Chinese Spanish Swedish Thai Traditional Chinese Note: The FixPack installation program automatically updates previously installed language packs. You cannot install a new language pack when installing a FixPack. For more information on installing an additional language pack, see SAP BusinessObjects Edge Series 3.1 Installation Guide for your platform.

1.5 Planning your FixPack installation
Before applying a FixPack to your SAP BusinessObjects system, the following planning steps are recommended: Review the FixPack Release Notes for important issues, limitations, and workarounds for the FixPack release. Identify all SAP BusinessObjects products and components that require updates. For SAP BusinessObjects Edge BI 3.1 release, FixPacks are provided for each SAP BusinessObjects product that has its own installer. Refer to SAP BusinessObjects FixPacks to identify the FixPacks required for your upgrade. It is required that all SAP BusinessObjects products and components be at the same Service Pack and FixPack level. If you have SAP 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 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 SAP BusinessObjects documentation such as the SAP BusinessObjects Edge Series 3.1 Installation Guide may be required. See http://help.sap.com for additional documentation.
1.6 FixPack installation scenarios
This topic describes common FixPack installation scenarios that might be of assistance in planning your FixPack installation. Scenario 1: Applying a FixPack to an SAP BusinessObjects Edge Series installation In this scenario you must apply the SAP BusinessObjects Edge BI 3.1 FixPack. Note: A typical SAP BusinessObjects Edge Series installation includes client tools. The SAP BusinessObjects Edge BI 3.1 FixPack will update client tools that were installed as part of the SAP BusinessObjects Edge Series 3.1 installation. If you installed client tools using the SAP BusinessObjects Client Tools installer, see Scenario 2.
Scenario 2: Applying a FixPack to a system with an SAP BusinessObjects Edge Series 3.1 Client Tools installation If you originally installed SAP BusinessObjects client tools using the SAP BusinessObjects Client Tools installer, you must apply the SAP BusinessObjects Client Tools FixPack. If you attempt to use an SAP BusinessObjects Edge BI 3.1 FixPack to upgrade an SAP BusinessObjects Client Tools installation, the installer will fail and you will receive an error message. Scenario 3: Applying FixPacks to a system with multiple SAP BusinessObjects products Due to product interdependencies, it is required that all SAP 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 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 4: 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 on applying updates to SAP BusinessObjects web application components, see Updating web application components.

1.7 Updating web application components
How you apply a FixPack update to SAP BusinessObjects web application components depends on how the components were originally deployed. One of the following scenarios is applicable: If you deployed SAP BusinessObjects web components using the SAP BusinessObjects installation program, the FixPack installation program allows you to update web components automatically when you apply an SAP BusinessObjects FixPack. Follow the FixPack installation steps in this guide to update web application components using the SAP BusinessObjects Edge BI 3.1 FixPack installation program. If you deployed SAP BusinessObjects web application components manually, updates must be applied manually after installing the SAP BusinessObjects Edge BI 3.1 FixPack. For more information on manual deployment instructions for web application components, see BusinessObjects Enterprise XI 3.1 Web Application Deployment Guide. If you deployed SAP BusinessObjects web application components using the wdeploy tool, you can apply updates manually or use the wdeploy tool after installing the SAP BusinessObjects Edge BI 3.1 FixPack. For more information on working with wdeploy tool, see 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 SAP BusinessObjects Edge BI 3.1 FixPack to obtain the updated WAR files. The SAP BusinessObjects WAR files are required for web application deployment. For more information on wdeploy or manual deployment, see BusinessObjects Enterprise XI 3.1 Web Application Deployment Guide. Note: If your SAP BusinessObjects system includes web components, you must update the web components as part of your FixPack upgrade. It is required that all SAP BusinessObjects components, including web components, be at the same Service Pack and FixPack level.
1.8 FixPack installation limitations and restrictions
The following limitations and restrictions apply to FixPack installation: FixPacks are patch installations, not complete product installations. An SAP BusinessObjects product must be installed in order to install a FixPack. A FixPack only updates files that are already installed. FixPacks only contain updates and fixes for existing product features. New features are not included in FixPack releases. FixPacks can only be installed in their entirety. You cannot install a subset of FixPack updates. It is required that all components in an SAP BusinessObjects system be at the same Service Pack and FixPack level. For example, SAP BusinessObjects server, client, and web components must be at the same Service Pack and FixPack level. If you update one component of your SAP BusinessObjects system, you must also update the other components. If you install a new SAP BusinessObjects product or component to your system after FixPack installation, you must apply the FixPack to the system where you installed the new product or component to ensure that all SAP BusinessObjects products and components are at the same FixPack level. 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. It is only possible to automatically redeploy SAP BusinessObjects web application components using the FixPack installation program if you originally deployed the web application components using the SAP 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.

You cannot install a new language when applying a FixPack. SAP BusinessObjects FixPacks only update languages that were previously installed with your SAP BusinessObjects installation. For information on installing an additional language for SAP BusinessObjects products, see the SAP BusinessObjects Edge Series 3.1 Installation Guide. For more information, see Fixed Issues list, note: 1331016, and Release Notes, note 1331015 and FixPack Installation and Deployment Guide, note 1279452 available at http://www.sdn.sap.com.
1.9 Saving web.xml file modifications
When a FixPack is installed, the web.xml files for SAP BusinessObjects web applications are overwritten by a default web.xml file. If you modified a web.xml file for an SAP BusinessObjects web application and do not want to lose your modification, copy the modified web.xml to the appropriate web application subdirectory of the SAP BusinessObjectswarfiles directory before you apply a FixPack. The FixPack installer will read the modified web.xml file from this location and maintain your modifications. For example, if the web.xml file in [INSTALLDIR]\Business Objects\Tomcat55\WebApps\InfoViewApp\WEB-INF has been modified, copy the modified web.xml file to [INSTALLDIR]\BusinessObjects Enterprise 12.0\warfiles\WebApps\InfoViewApp\WEB-INF\ before you apply a FixPack.
1.10 Downloading FixPacks
SAP BusinessObjects FixPacks are available for download from the SAP Support Portal: http://ser vice.sap.com/patches. FixPacks for Crystal Reports are available from the SAP Community Portal: https://www.sdn.sap.com/irj/boc/downloads.
1.11 Crystal Reports FixPack compatibility
SAP BusinessObjects Edge BI 3.1 FixPack 1.2 is compatible with Crystal Reports 2008 V1 FixPack 1.5.
FixPack installation on Windows
2.1 Installing SAP BusinessObjects Edge BI 3.1 FixPack on Windows
You must have Administrator or Power User privileges on your Windows system to run an SAP BusinessObjects FixPack installation. In order to free resources on the system on which you are installing this FixPack, it is recommended that you stop all the SAP BusinessObjects Edge Series servers before installing the FixPack. However, the following services and servers must be running for the installation to proceed: Server Intelligence Agent (SIA) Central Management Server (CMS) Input and Output File Repository Servers (FRS) CMS database Before you install this FixPack on Windows 2003, you must ensure that you have installed the Update for Windows Server 2003 (KB925336) patch that is available from http://support.microsoft.com/kb/925336. Note: If you have modified web.xml files for SAP BusinessObjects web applications, see Saving web.xml file modifications before you apply a FixPack. To install the FixPack, perform the following steps: 1. Launch the installation by running setup.exe The "Welcome to BusinessObjects Edge Series 3.1 FixPack 1.2 Installation Wizard" screen appears. 2. Click Next. The "License Agreement" screen appears. 3. Review the content of the End User License Agreement and click Next to proceed if you accept the terms. The "CMS" screen appears. 4. Enter the values for Existing CMS Hostname, Existing CMS Port, and CMS Administrator Password. Click Next. If the product you are updating includes web components that were automatically deployed during your original SAP BusinessObjects Edge Series 3.1 installation, the "Automatically Re-Deploy Web Applications?" screen appears. 5. Choose from one of the following options:

Yes, automatically re-deploy the web applications. This option redeploys SAP BusinessObjects web application components that were previously deployed. The "Configure Web Application Server" screen appears. Enter the values specific to the web application server and click Next. Note: For more information on specific configuration settings for each web application server, see SAP BusinessObjects Edge Series 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. For information on manual installation of web components or installation using the wdeploy tool, see BusinessObjects XI 3.1 Web Application Deployment Guide for Windows.
Note: It is possible to automatically redeploy web application components to the same web application server type you had deployed during your original SAP BusinessObjects Edge Series 3.1 installation. The "Start Installation" screen appears. 6. Click Next to begin the installation. 7. If you update SAP BusinessObjects Edge Series 3.1, verify that SAP BusinessObjects services are running after the system is restarted. If any services are not running, start them manually using the SAP BusinessObjects Central Management Console (CMC), Central Configuration Manager (CCM), or Windows Services panel. The CMC or CCM can be accessed underStart > Programs > BusinessObjects XI 3.1 > BusinessObjects Edge Series. 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.
FixPack installation on Linux
3.1 Installing SAP BusinessObjects Edge BI 3.1 FixPack on Linux
In order to free resources on the system on which you are installing this FixPack, it is recommended that you stop all of the SAP BusinessObjects Edge Series 3.1 servers before installing the FixPack. However, the following services and servers must be running for the installation to proceed: Server Intelligence Agent (SIA) Central Management Server (CMS) Input and Output File Repository Servers (FRS) CMS database Note: If you have modified web.xml files for SAP BusinessObjects web applications, see Saving web.xml file modifications before you apply a FixPack. To install the FixPack, perform the following steps: 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 SAP BusinessObjects product. The "License Agreement" screen appears. 2. Review the content of the License agreement and proceed by selecting Y. The "CMS" screen appears. 3. Enter the values for Existing CMS Hostname, Existing CMS Port, and CMS Administrator Password, and press Enter. If the product you are updating includes web components that were automatically deployed during your original SAP BusinessObjects Edge Series 3.1 installation, the "Automatically Re-Deploy Web Applications" screen appears. 4. Choose from one of the following options: Yes, automatically re-deploy the web applications. This option redeploys SAP BusinessObjects web application components that were previously deployed. The "Configure Web Application Server" screen appears. Enter the values specific to the web application server and press Enter.

Note: For more information on specific configuration settings for each web application server, refer to SAP BusinessObjects Edge Series 3.1 Installation Guide for Linux. 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. For information on manual installation of web components or installation using the wdeploy tool, see BusinessObjects XI 3.1 Web Application Deployment Guide for UNIX. Note: It is only possible to automatically redeploy web components to the same web application server type you had previously deployed during your original SAP BusinessObjects Edge Series 3.1 installation. The "Confirm Installation" screen appears. 5. 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 at <INSTALLDIR>/setup/backup. It is recommended that you do not modify or remove these files. To review details of the installation, you can view the contents of the installation log file at the following location: <INSTALLDIR>/setup/logs/.
Silent FixPack installation
SAP 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. Related Topics Running a silent installation using a response file on Windows Running a silent installation using a response file on Linux
4.1 Silent installation on Windows
4.1.1 Running a silent installation using a response file on Windows
To run a silent installation using a response file you must first create a.ini file using the SAP 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. To run a silent installation, perform the following steps: 1. Create an installation.ini file (a response file). a. Open a command line console. b. From the SAP BusinessObjects Edge BI 3.1 FixPack directory, run the setup.exe file with the write option (-w) by using the following command:
setup.exe -w <filepath><filename>
where filename is the name of the response file and filepath is the location where you want the file to be created. Note: If a file path is not specified, the file is stored in the same directory from where setup.exe is run. 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 till you reach the Start installation screen 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 that you specified. 2. You can now run a response file installation using the.ini file by executing setup.exe command with the read option specified (-r) as follows:

setup.exe -r <filepath><filename.ini>
where filepath is the path to the response file you created, and filename.ini is the name of the response file. 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 from where setup.exe is run.
-l <filepath><filename>
4.1.2 Silent installation parameters (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 SAP BusinessObjects Edge BI 3.1 FixPack setup program (setup.exe) as described in Running a silent installation using a response file on Windows.

Parameter

CLIENTLANGUAGE
Specifies the language used by the installer: DA=Danish DE=German EN=English ES=Spanish 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"
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.
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_SESpecifies that an administrator credential must be passed to access the web apCURE plication server. This setting is valid only for WebSphere 6 and Oracle.
AS_ADMIN_IS_SECURE="true"
AS_ADMIN_PASSPassword used by the administrator account to access the web application server. WORD
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_USERSpecifies the account name used by the administrator to access the web applicaNAME tion server.
AS_ADMIN_USERNAME="admin"

AS_DIR

Specifies the installation directory for the web application server.

AS_DIR="<INSTALLDIR>/Tomcat55"

AS_INSTANCE

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_SERVICENAME

Specifies the name of the Windows service if the application 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"

ENABLELOGFILE

Specifies if a log file will be created for the installation.
ENABLELOGFILE="1"

INSTALLDIR

Specifies the directory where you want to install SAP BusinessObjects Edge BI FixPack.
INSTALLDIR="C:\Program Files\Business Objects\"
The following parameters are automatically generated parameters that should not be modified in the.ini file.

Parameter name

ADDLOCAL ADDSOURCE ADVERTISE REMOVE SKIP_DEPLOYMENT WDEPLOY_LATER
4.2 Silent installation on Linux
4.2.1 Running a silent installation using a response file on Linux
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 SAP BusinessObjects Edge BI 3.1 FixPack installation. 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.install.sh command with the write option WRITERESPONSEPATH as follows:
./install.sh <INSTALLDIR> WRITERESPONSEPATH=<response_file_path>
where <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 that you specified. 2. You can now run a response file installation by issuing./install.sh command with the read option READRESPONSEPATH as follows:

./install.sh <INSTALLDIR> READRESPONSEPATH=<response_file_path>
3. Press Enter to launch the installation.
4.2.2 Response file installation parameters (Linux)
The following table lists parameters that are commonly used for response file silent installation on Linux. It is recommended that you create a response file using./install.sh and the -WRITERESPONSEPATH parameter as described in Running a silent installation using a response file on Linux.
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"

BOBJELANG

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

BOBJELANG="en"

INSTALLMODE
Specifies a comma-delimited list for the SAP BusinessObjects Edge Series installer operating modes. This parameter supports the following options: interactive, install silent, install
INSTALLMODE=silent, install

REDEPLOYWEBAPPS

Specifies whether the installation program automatically deploys the web applications.

REDEPLOYWEBAPPS=true

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/
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_ADMIN_IS_SESpecifies if administrator credential must be passed to access the web application CURE server. This setting is valid only for WebSphere 6 and Oracle.

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:
AUTODEPLOY_WAR_FILES BOBJDIR CDDIR CMSNAMESERVER CMSPORTNUMBER CMSPASSWORD FUNCTION INSTALLLEVEL LANGPACKS_TO_INSTALL LICENSEDIR LOCALNAMESERVER MACHINENAME PRODUCTID_NAME PRODUCTID_VER ProductVersion VERSION_IN_RANGE

Uninstalling FixPacks

5.1 Uninstalling SAP BusinessObjects Edge BI FixPacks on Windows
FixPacks can only be uninstalled one at a time, in the reverse order of installation. For example, if you installed FixPack 1 and then FixPack 2, you must uninstall FixPack 2 before you can uninstall FixPack 1. To uninstall a FixPack, perform the following steps: 1. 2. 3. 4. 5. 6. Select Start > Settings > Control Panel. Double-click Add or Remove Programs. Highlight the SAP BusinessObjects entry in the list of programs. Click the Show updates check box to display installed FixPacks. Select the FixPack and click Remove. The "Add or Remove Programs" dialog box prompts you to confirm that you want to remove the FixPack from your computer. Click Yes. 7. 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 on uninstalling SAP BusinessObjects web application components, see Uninstalling web application components.
5.2 Uninstalling SAP BusinessObjects Edge BI 3.1 FixPacks on Linux
FixPacks can only be uninstalled one at a time, in the reverse order of installation. For example, if you installed FixPack 1 and then FixPack 2, you must uninstall FixPack 2 before you can uninstall FixPack 1. To uninstall a FixPack, perform the following steps: 1. Execute the following command from the root directory of your SAP BusinessObjects Edge BI 3.1 installation:

./AddOrRemovePrograms.sh

The "Add or Remove Programs" dialog is displayed.
2. Select the SAP BusinessObjects Edge BI 3.1 FixPack you want to uninstall and press Enter. 3. Select Uninstall Product and press Enter. A confirmation screen appears. 4. Select Yes and press Enter. The uninstall process begins. For information on uninstalling SAP BusinessObjects web application components, see Uninstalling web application components.

5.3 Uninstalling web application components
The method for uninstalling SAP BusinessObjects web application components depends on which types of web application components are installed and the method used to install them: If you installed Tomcat 5.5 on the same system as SAP BusinessObjects Edge Series 3.1 using the SAP BusinessObjects installation program, web component updates are uninstalled when you uninstall the SAP BusinessObjects Edge BI 3.1 FixPack. If you manually deployed SAP BusinessObjects web application components, you can remove them manually or use the wdeploy tool. If you deployed web application components using the wdeploy tool, you can remove the components manually or use the wdeploy tool. For wdeploy or manual uninstall instructions, see BusinessObjects XI 3.1 Web Application Deployment Guide for your platform. Note: Uninstalling web components manually or using the wdeploy tool removes components entirely. If you want to use an earlier version of the web application components, you must redeploy the earlier version manually or using the wdeploy tool. All components in an SAP BusinessObjects system are required to be at the same Service Pack and FixPack level. If you change the level of one SAP BusinessObjects system component, you must also change the other components in your SAP BusinessObjects system to the same level.

SAP BusinessObjects Edge 3.1 with Data Integrator
BI Widgets installer Data Services installer
SAP BusinessObjects Edge 3.1 with Data Management
The following table shows the folder structure for all the products for Linux operating system:
Patch Server Patch installer SAP Integration Solutions installer
Folder Structure \DISK_1\install.sh \collaterals\SAP Integration Solutions\\DISK_1\install.sh \collaterals\EBS Integration\DISK_1\install.sh \collaterals\JDE Integration\DISK_1\install.sh \collaterals\PeopleSoft Integration\DISK_1\install.sh \DISK_1\install.sh \collaterals\SAP Integration Solutions\DISK_1\install.sh \collaterals\EBS Integration\DISK_1\install.sh \collaterals\JDE Integration\DISK_1\install.sh \collaterals\PeopleSoft Integration\DISK_1\install.sh \DataServices\install.sh
SAP BusinessObEBS Integration Kit jects Edge 3.1 Stan- Patch installer dard JDE Integration Kit Patch installer PeopleSoft Integration Kit Patch installer Server Patch installer SAP Integration Solutions installer EBS Integration Kit Patch installer JDE Integration Kit Patch installer PeopleSoft Integration Kit Patch installer Data Services installer
Introduction FixPack platform support
Patch Server Patch installer SAP Integration Solutions installer EBS Integration Kit Patch installer JDE Integration Kit Patch installer PeopleSoft Integration Kit Patch installer Data Services installer
Folder Structure \DISK_1\install.sh \collaterals\SAP Integration Solutions\DISK_1\install.sh \collaterals\EBS Integration\DISK_1\install.sh \collaterals\JDE Integration\DISK_1\install.sh \collaterals\PeopleSoft Integration\DISK_1\install.sh \DataServices\install.sh

FixPack platform support

The following table shows the platform support for each SAP BusinessObjects FixPack.
FixPack SAP BusinessObjects Edge BI 3.1 FixPack SAP BusinessObjects Edge BI 3.1 Client Tools FixPack Crystal Reports 2008 FixPack SAP BusinessObjects Live Office XI 3.1 FixPack SAP BusinessObjects XI 3.1 Integration for SAP Solutions FixPack SAP BusinessObjects XI 3.1 Integration for PeopleSoft Enterprise FixPack Windows Linux
Introduction FixPack language support
FixPack SAP BusinessObjects XI Integration for JD Edwards EnterpriseOne SAP BusinessObjects XI Integration for Oracle E-Business Suite SAP BusinessObjects XI Integration for Siebel

Windows

FixPack language support
SAP BusinessObjects FixPacks support product language pack updates for the following languages: Danish Dutch English French German Italian Japanese Korean Norwegian Polish Portuguese Russian Simplified Chinese Spanish Swedish Thai Traditional Chinese
The FixPack installation program automatically updates previously installed language packs. You cannot install a new language pack when installing a FixPack. For more information on installing an additional language pack, see SAP BusinessObjects Edge Series 3.1 Installation Guide for your platform.

Introduction Planning your FixPack installation
Planning your FixPack installation
Before applying a FixPack to your SAP BusinessObjects system, the following planning steps are recommended: Review the FixPack Release Notes for important issues, limitations, and workarounds for the FixPack release. Identify all SAP BusinessObjects products and components that require updates. For SAP BusinessObjects Edge BI 3.1 release, FixPacks are provided for each SAP BusinessObjects product that has its own installer. Refer to SAP BusinessObjects FixPacks to identify the FixPacks required for your upgrade. It is required that all SAP BusinessObjects products and components be at the same FixPack level. If you have SAP 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 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 SAP BusinessObjects documentation such as the SAP BusinessObjects Edge Series 3.1 Installation Guide may be required. See http://help.sap.com for additional documentation.
FixPack installation scenarios
This topic describes common FixPack installation scenarios that might be of assistance in planning your FixPack installation.
Introduction FixPack installation scenarios
Scenario 1: Applying a FixPack to an SAP BusinessObjects Edge BI installation
In this scenario you must apply the SAP BusinessObjects Edge BI 3.1 FixPack.
A typical SAP BusinessObjects Edge BI installation includes client tools. The SAP BusinessObjects Edge BI 3.1 FixPack will update client tools that were installed as part of the SAP BusinessObjects Edge BI 3.1 installation. If you installed client tools using the SAP BusinessObjects Client Tools installer, see Scenario 2.
Scenario 2: Applying a FixPack to a system with an SAP BusinessObjects Edge BI 3.1 Client Tools installation
If you originally installed SAP BusinessObjects client tools using the SAP BusinessObjects Client Tools installer, you must apply the SAP BusinessObjects Client Tools FixPack. If you attempt to use an SAP BusinessObjects Edge BI 3.1 FixPack to upgrade an SAP BusinessObjects Client Tools installation, the installer will fail and you will receive an error message.

If your SAP BusinessObjects system includes web components, you must update the web components as part of your FixPack upgrade. It is required that all SAP BusinessObjects components, including web components, be at the same FixPack level.
Introduction FixPack installation limitations and restrictions
FixPack installation limitations and restrictions
The following limitations and restrictions apply to FixPack installation: FixPacks are patch installations, not complete product installations. An SAP BusinessObjects product must be installed in order to install a FixPack. A FixPack only updates files that are already installed. FixPacks only contain updates and fixes for existing product features. New features are not included in FixPack releases. FixPacks can only be installed in their entirety. You cannot install a subset of FixPack updates. It is required that all components in an SAP BusinessObjects system be at the same FixPack level. For example, SAP BusinessObjects server, client, and web components must be at the same FixPack level. If you update one component of your SAP BusinessObjects system, you must also update the other components. If you install a new SAP BusinessObjects product or component to your system after FixPack installation, you must apply the FixPack to the system where you installed the new product or component to ensure that all SAP BusinessObjects products and components are at the same FixPack level. You cannot install an earlier FixPack on top of a later FixPack. For example, you cannot install FixPack 1.2 if FixPack 2.1 is already installed.
FixPacks are cumulative. For example, FixPack 2.1 contains all FixPack 1.2 updates as well as FixPack 2.1 updates. It is only possible to automatically redeploy SAP BusinessObjects web application components using the FixPack installation program if you originally deployed the web application components using the SAP 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 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.

Introduction Saving web.xml file modifications
You cannot install a new language when applying a FixPack. SAP BusinessObjects FixPacks only update languages that were previously installed with your SAP BusinessObjects installation. For information on installing an additional language for SAP BusinessObjects products, see the SAP BusinessObjects Edge Series 3.1 Installation Guide.
Saving web.xml file modifications
When a FixPack is installed, the web.xml files for SAP BusinessObjects web applications are overwritten by a default web.xml file. If you modified a web.xml file for an SAP BusinessObjects web application and do not want to lose your modification, copy the modified web.xml to the appropriate web application subdirectory of the SAP BusinessObjectswarfiles directory before you apply a FixPack. The FixPack installer will read the modified web.xml file from this location and maintain your modifications. For example, if the web.xml file in <INSTALLDIR>\Business Objects\Tomcat55\WebApps\InfoViewApp\WEB-INF has been modified, copy the modified web.xml file to <INSTALLDIR>\BusinessObjects Enterprise 12.0\warfiles\WebApps\InfoViewApp\WEB-INF\ before you apply a FixPack.

Downloading FixPacks

SAP 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 Portal: https://www.sdn.sap.com/irj/boc/downloads.
Crystal Reports FixPack compatibility
SAP BusinessObjects Edge BI 3.1 FixPack 2.1 is compatible with Crystal Reports 2008 V1 FixPack 1.5.
Introduction Crystal Reports FixPack compatibility
FixPack installation on Windows
FixPack installation on Windows Installing SAP BusinessObjects Edge BI 3.1 FixPack on Windows
Installing SAP BusinessObjects Edge BI 3.1 FixPack on Windows
You must have Administrator or Power User privileges on your Windows system to run an SAP BusinessObjects FixPack installation.
To install SAP BusinessObjects Edge BI 3.1 FixPack 2.1 on your system you must have SAP BusinessObjects Edge BI 3.1 Service Pack 2 installed on the system. In order to free resources on the system on which you are installing this FixPack, it is recommended that you stop all the SAP BusinessObjects Edge BI servers before installing the FixPack. However, the following services and servers must be running for the installation to proceed: Server Intelligence Agent (SIA) Central Management Server (CMS) Input and Output File Repository Servers (FRS) CMS database Before you install this FixPack on Windows 2003, you must ensure that you have installed the Update for Windows Server 2003 (KB925336) patch, that is available at http://support.microsoft.com/kb/925336.

If you have modified web.xml files for SAP BusinessObjects web applications, see Saving web.xml file modifications before you apply a FixPack. To install the FixPack, perform the following steps: 1. Launch the installation by running setup.exe The "Welcome to BusinessObjects Edge Series 3.1 FixPack 2.1 Installation Wizard" screen appears. 2. Click Next. The "License Agreement" screen appears. 3. Review the content of the End User License Agreement and click Next to proceed if you accept the terms. The "CMS" screen appears.
22 SAP BusinessObjects Edge BI 3.1 FixPack Installation and Deployment Guide
4. Enter the values for Existing CMS Hostname, Existing CMS Port, and CMS Administrator Password. Click Next. If the product you are updating includes web components that were automatically deployed during your original SAP BusinessObjects Edge BI 3.1 installation, the "Automatically Re-Deploy Web Applications?" screen appears. 5. Choose from one of the following options: Yes, automatically re-deploy the web applications. This option redeploys SAP BusinessObjects web application components that were previously deployed. The "Configure Web Application Server" screen appears. Enter the values specific to the web application server and click Next.
For more information on specific configuration settings for each web application server, see SAP BusinessObjects Edge Series 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. For information on manual installation of web components or installation using the wdeploy tool, see BusinessObjects XI 3.1 Web Application Deployment Guide for Windows.
It is possible to automatically redeploy web application components to the same web application server type you had deployed during your original SAP BusinessObjects Edge BI 3.1 installation. The "Start Installation" screen appears. 6. Click Next to begin the installation. 7. If you update SAP BusinessObjects Edge BI 3.1, verify that SAP BusinessObjects services are running after the system is restarted. If any services are not running, start them manually using the SAP BusinessObjects Central Management Console (CMC), Central Configuration Manager (CCM), or Windows Services panel. The CMC or CCM can be accessed underStart > Programs > BusinessObjects XI 3.1 > BusinessObjects Edge Series.

To review details of the installation, you can view the contents of the installation log file located in <INSTALLDIR>\BusinessObjects Enterprise 12.0\Logging.
FixPack installation on Linux
FixPack installation on Linux Installing SAP BusinessObjects Edge BI 3.1 FixPack on Linux
Installing SAP BusinessObjects Edge BI 3.1 FixPack on Linux
In order to free resources on the system on which you are installing this FixPack, it is recommended that you stop all of the SAP BusinessObjects Edge BI 3.1 servers before installing the FixPack. However, the following services and servers must be running for the installation to proceed: Server Intelligence Agent (SIA) Central Management Server (CMS) Input and Output File Repository Servers (FRS) CMS database
If you have modified web.xml files for SAP BusinessObjects web applications, see Saving web.xml file modifications before you apply a FixPack. To install the FixPack, perform the following steps: 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 SAP BusinessObjects product. The "License Agreement" screen appears. 2. Review the content of the License agreement and proceed by selecting Y. The "CMS" screen appears. 3. Enter the values for Existing CMS Hostname, Existing CMS Port, and CMS Administrator Password, and press Enter. If the product you are updating includes web components that were automatically deployed during your original SAP BusinessObjects Edge BI 3.1 installation, the "Automatically Re-Deploy Web Applications" screen appears. 4. Choose from one of the following options:
Yes, automatically re-deploy the web applications. This option redeploys SAP BusinessObjects web application components that were previously deployed. The "Configure Web Application Server" screen appears. Enter the values specific to the web application server and press Enter.
For more information on specific configuration settings for each web application server, refer to SAP BusinessObjects Edge Series 3.1 Installation Guide for Linux. 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. For information on manual installation of web components or installation using the wdeploy tool, see BusinessObjects XI 3.1 Web Application Deployment Guide for UNIX.

It is only possible to automatically redeploy web components to the same web application server type you had previously deployed during your original SAP BusinessObjects Edge BI 3.1 installation. The "Confirm Installation" screen appears. 5. 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.
The FixPack installer creates a backup of modified files at <IN STALLDIR>/setup/backup. It is recommended that you do not modify or remove these files. To review details of the installation, you can view the contents of the installation log file at the following location: <INSTALLDIR>/set up/logs/.
Silent FixPack installation
Silent FixPack installation Silent installation on Windows
SAP 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.

Related Topics

Running a silent installation using a response file on Windows Running a silent installation using a response file on Linux
Silent installation on Windows
Running a silent installation using a response file on Windows
To run a silent installation using a response file you must first create a.ini file using the SAP 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. To run a silent installation, perform the following steps: 1. Create an installation.ini file (a response file). a. Open a command line console. b. From the SAP BusinessObjects Edge BI 3.1 FixPack directory, run the setup.exe file with the write option (-w) by using the following command: setup.exe -w <filepath><filename> where filename is the name of the response file and filepath is the location where you want the file to be created.
If a file path is not specified, the file is stored in the same directory from where setup.exe is run. 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 till you reach the Start installation screen 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 that you specified. 2. You can now run a response file installation using the.ini file by executing setup.exe command with the read option specified (-r) as follows: setup.exe -r <filepath><filename.ini> where filepath is the path to the response file you created, and filename.ini is the name of the response file.

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 from where setup.exe is run. -l <filepath><filename>
Silent installation parameters (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 SAP BusinessObjects Edge BI 3.1 FixPack setup program (set up.exe) as described in Running a silent installation using a response file on Windows.

Parameter CLIENTLANGUAGE

Specifies the language used by the installer: DA=Danish DE=German EN=English ES=Spanish 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
If this parameter is not specified, you will be prompted to select a language when the installation setup begins. CLIENTLANGUAGE="EN"
Specifies not to prompt during the installation.
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.

Parameter

Specifies to prompt when the installation is complete.

AS_ADMIN_IS_SECURE

Specifies that an administrator credential must be passed to access the web application server. This setting is valid only 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"

Parameter AS_INSTANCE

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 Web Application Container Server (WACS) 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"
ENABLELOGSpecifies if a log file will be created for the installation. FILE
ENABLELOGFILE="1"

INSTALLDIR

Specifies the directory where you want to install SAP BusinessObjects Edge BI FixPack. INSTALLDIR="C:\Program Files\Business Ob jects\"
The following parameters are automatically generated parameters that should not be modified in the.ini file.
Silent FixPack installation Silent installation on Linux
Parameter name ADDLOCAL ADDSOURCE ADVERTISE REMOVE SKIP_DEPLOYMENT WDEPLOY_LATER
Silent installation on Linux
Running a silent installation using a response file on Linux
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 SAP BusinessObjects Edge BI 3.1 FixPack installation. 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.
To install SAP BusinessObjects Edge BI 3.1 FixPack 2.1 on your system you must have SAP BusinessObjects Edge BI 3.1 Service Pack 2 installed on the system. 1. Create a response file. a. From the FixPack installation source file location, run the.in stall.sh command with the write option WRITERESPONSEPATH as follows:./install.sh <INSTALLDIR> WRITERESPONSEPATH=<re sponse_file_path> where <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 screen 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 that you specified. 2. You can now run a response file installation by issuing./install.sh command with the read option READRESPONSEPATH as follows:./install.sh <INSTALLDIR> READRESPONSEPATH=<re sponse_file_path> 3. Press Enter to launch the installation.

Response file installation parameters (Linux)
The following table lists parameters that are commonly used for response file silent installation on Linux. It is recommended that you create a response file using./install.sh and the -WRITERESPONSEPATH parameter as described in Running a silent installation using a response file on Linux.

Parameter CDDIR

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"

BOBJELANG

The language setting used for the installation program. chs=Simplified Chinese cht=Traditional Chinese da=Danish de=German en=English es=Spanish fr=French it=Italian jp=Japanese ko=Korean nb=Norwegian nl=Dutch pl=Polish pt=Portuguese ru=Russian sv=Swedish th=Thai BOBJELANG="en"
INSpecifies a comma-delimited list for the SAP BusinessObSTALLMODE
jects Edge BI installer operating modes. This parameter supports the following options: interactive, install silent, install INSTALLMODE=silent, install

REDEPLOYWEBAPPS

Specifies whether the installation program automatically deploys the web applications. REDEPLOYWEBAPPS=true
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/
Specifies the name of the application server being installed. Use tomcat55 for Tomcat AS_SERVER=tomcat55

AS_INSTANCE

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

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 AUTODEPLOY_WAR_FILES BOBJDIR CDDIR CMSNAMESERVER CMSPORTNUMBER CMSPASSWORD FUNCTION INSTALLLEVEL LANGPACKS_TO_INSTALL LICENSEDIR LOCALNAMESERVER MACHINENAME PRODUCTID_NAME PRODUCTID_VER ProductVersion VERSION_IN_RANGE

Uninstalling FixPacks

Uninstalling FixPacks Uninstalling SAP BusinessObjects Edge BI FixPacks on Windows
Uninstalling SAP BusinessObjects Edge BI FixPacks on Windows
FixPacks can only be uninstalled one at a time, in the reverse order of installation. For example, if you installed FixPack 1 and then FixPack 2, you must uninstall FixPack 2 before you can uninstall FixPack 1. To uninstall a FixPack, perform the following steps: 1. 2. 3. 4. 5. 6. Select Start > Settings > Control Panel. Double-click Add or Remove Programs. Highlight the SAP BusinessObjects entry in the list of programs. Click the Show updates check box to display installed FixPacks. Select the FixPack and click Remove. The "Add or Remove Programs" screen prompts you to confirm that you want to remove the FixPack from your computer. Click Yes. 7. 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" screen. For information on uninstalling SAP BusinessObjects web application components, see Uninstalling web application components.
Uninstalling SAP BusinessObjects Edge BI 3.1 FixPacks on Linux
FixPacks can only be uninstalled one at a time, in the reverse order of installation. For example, if you installed FixPack 1 and then FixPack 2, you must uninstall FixPack 2 before you can uninstall FixPack 1. To uninstall a FixPack, perform the following steps: 1. Execute the following command from the root directory of your SAP BusinessObjects Edge BI 3.1 installation:./AddOrRemovePrograms.sh The "Add or Remove Programs" screen is displayed.
Uninstalling FixPacks Uninstalling web application components
2. Select the SAP BusinessObjects Edge BI 3.1 FixPack you want to uninstall and press Enter. 3. Select Uninstall Product and press Enter. A confirmation screen appears. 4. Select Yes and press Enter. The uninstall process begins. For information on uninstalling SAP BusinessObjects web application components, see Uninstalling web application components.
Uninstalling web application components
The method for uninstalling SAP BusinessObjects web application components depends on which types of web application components are installed and the method used to install them: If you installed Tomcat 5.5 on the same system as SAP BusinessObjects Edge BI 3.1 using the SAP BusinessObjects installation program, web component updates are uninstalled when you uninstall the SAP BusinessObjects Edge BI 3.1 FixPack. If you manually deployed SAP BusinessObjects web application components, you can remove them manually or use the wdeploy tool. If you deployed web application components using the wdeploy tool, you can remove the components manually or use the wdeploy tool. For wdeploy or manual uninstall instructions, see BusinessObjects XI 3.1 Web Application Deployment Guide for your platform.

Uninstalling web components manually or using the wdeploy tool removes components entirely. If you want to use an earlier version of the web application components, you must redeploy the earlier version manually or using the wdeploy tool. All components in an SAP BusinessObjects system are required to be at the same FixPack level. If you change the level of one SAP BusinessObjects system component, you must also change the other components in your SAP BusinessObjects system to the same level.