Beruflich Dokumente
Kultur Dokumente
2012-08-16
Copyright
2012 SAP AG. All rights reserved.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP
BusinessObjects Explorer, StreamWork, SAP HANA 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 Software Ltd. Business Objects is an SAP company.Sybase and
Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services
mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase,
Inc. Sybase is an SAP company. Crossgate, m@gic EDDY, B2B 360, B2B 360 Services are
registered trademarks of Crossgate AG in Germany and other countries. Crossgate 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.
2012-08-16
Contents
Chapter 1
Installation...............................................................................................................................5
1.1
1.1.1
1.1.2
1.1.3
Chapter 2
Planning..................................................................................................................................7
2.1
2.2
2.3
2.4
2.5
2.6
Chapter 3
Installation scenarios............................................................................................................13
3.1
3.2
3.3
3.4
Chapter 4
4.1
4.2
4.3
4.3.1
4.3.2
4.4
4.4.1
Chapter 5
5.1
Purpose...................................................................................................................................5
Constraints..............................................................................................................................5
Variables..................................................................................................................................6
2012-08-16
Contents
5.2
5.2.1
5.2.2
5.3
2012-08-16
Installation
Installation
1.1.1 Purpose
This document is intended as a reference for use by system administrators when updating the BI suite
with the most recent Patch. For the latest information, updates, and other information, visit the support
site at service.sap.com/bosap-support.
1.1.2 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 SAP BusinessObjects Business Intelligence platform
can be installed. Refer to the vendor documentation for more information on installing or upgrading
these components.
2012-08-16
Installation
1.1.3 Variables
The following variables are used throughout this guide.
Variable
Description
<INSTALLDIR>
2012-08-16
Planning
Planning
2012-08-16
Planning
Patch
Description
Use this Patch to update SAP Crystal Reports for Enterprise installations.
2012-08-16
Planning
Patch
Description
Windows
AIX
Solaris
Linux
2012-08-16
Planning
Patches designed for the same Support Package level are cumulative. Therefore, it is unnecessary
to install an earlier Patch from a particular Support Package level on top of a later Patch at that same
level.
The Patch installation program can automatically redeploy web application components to the web
application server only if the bundled Tomcat web server was used, and those components were
deployed automatically at initial installation time. If the web application components were initially
deployed using the WDeploy tool, you must use WDeploy to redeploy those components after
installing the Patch. For more information see "Updating web application components".
If you are performing a silent installation using a response file, you must create the response file
with the setup.exe or install.sh file from the target Patch installation package. Response files
generated for a Patch installation are specific to that Patch, and cannot be shared between full
installations and update installations, or between Support Package installations and Patch installations.
10
Review the Patch Release Notes and Fixed Issues document to determine if defects addressed by
the Patch are relevant to your SAP BusinessObjects installation, and for important issues, limitations,
and works-arounds for the Patch release.
2012-08-16
Planning
Identify all SAP BusinessObjects products and components that require updates.
For the SAP BusinessObjects 4.0 release, Patches are provided for each product that has its own
installer. Refer to "SAP BusinessObjects Patches" to identify the Patches required for your upgrade.
On windows, installed patches can be determined from the Windows Add/Remove Programs
list.
On unix, installed patches can be determined by running <install
path>\modifyorremoveproduct.sh
It is required that all SAP BusinessObjects products and components be at the same support package
and patch level. If you have a distributed installation or you are running multiple SAP BusinessObjects
products, ensure that all products and distributed components are updated. This includes BI platform
servers, client tools, web components, and other SAP BusinessObjects products such as SAP
Crystal Reports and Live Office.
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".
11
2012-08-16
Planning
12
2012-08-16
Installation scenarios
Installation scenarios
This topic describes common Patch installation scenarios that may help you plan your Patch installation.
13
If you deployed the BI platform WAR files to the default, bundled Tomcat server using the installation
program, the patch installation program allows you to update them automatically.
2012-08-16
Installation scenarios
If you deployed the BI platform WAR files manually to your web application server, updates must
be applied manually after installing the patch.
Manual deployment instructions for web application components are found in the SAP
BusinessObjects Business Intelligence Platform Web Application Deployment Guide.
If you deployed the BI platform WAR files using the WDeploy tool to your web application server,
you can apply updates manually or use the WDeploy tool after installing the patch.
Instructions for the WDeploy tool are found in the SAP BusinessObjects Business Intelligence
Platform Web Application Deployment Guide.
You must first install the patch to obtain the updated WAR files in order to redeploy them manually or
using the WDeploy tool. If you are applying multiple patch updates in a row, install all updates first to
obtain a final set of WAR files once that can be redeployed once.
Note:
You must update any deployed BI platform WAR files as part of your Patch upgrade. It is required that
all BI suite components, including web applications, be at the same version level.
14
2012-08-16
You must have Administrator privileges on your Windows system to run a SAP BusinessObjects Patch
installation.
In order to free resources on the machine on which you are installing this patch, it is recommended that
you use the Central Management Console (CMC) to stop all of the BI platform servers on the machine
before installing the patch, 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 web applications, see "Saving web.xml file modifications" before
you apply a patch.
Note:
If you are updating a product that contains server components, the installation 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.
15
2012-08-16
6. Type the Hostname, Port Number, and Administrator Password for your deployment's CMS, and
click Next to continue.
7. In the "Start Installation" dialog box, click Next to begin the installation.
The update will install.
Note:
If web applications are updated as part of the patch, depending on the options you chose when you
originally installed SAP BusinessObjects BI Platform a post installation dialog box may appear with
additional instructions for redeploying your .war files.
8. Click Finish.
16
2012-08-16
If you are performing a silent installation using a response file, you must create the response file
with the setup.exe or install.sh file from the target Support Package or Patch installation
package. Response files cannot be shared between refresh installations,update installations, Support
Package installations or Patch installations.
When creating a response file with the GUI installation program, passwords entered via the GUI are
not written to the response file: Replace the starred entries (********) with your passwords before
performing a silent installation.
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 program.
d. Follow the on-screen instructions to enter your preferred installation settings until you reach the
Start installation dialog box.
e. Click Cancel to abort the installation setup.
All parameters from the installation program, both user defined and default, are recorded in the
.ini file which is saved to the directory you specified.
2. You can now run a response file installation using the .ini file by issuing setup.exe command
with the read option specified (-r):
Log files for the install are stored at <install dir>\InstallData\logs.
17
2012-08-16
RemoteCMSname
Description
remotecmsport
Specifies the password for the Administrator account for the CMS.
remotecmspassword="<myPassword>"
18
2012-08-16
19
2012-08-16
20
2012-08-16
In order to free resources on the machine on which you are installing this patch, it is recommended that
you use the Central Management Console (CMC) to stop all of the BI platform servers on the machine
before installing the patch, 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 web applications, see "Saving web.xml file modifications" before
you apply a Patch.
Note:
If you are updating server components, the installation 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.
21
2012-08-16
If you are performing a silent installation using a response file, you must create the response file
with the setup.exe or setup.sh file from the target support package or patch installation package.
Response files cannot be shared between support package installations and patch installations.
When creating a response file with the GUI installation program, passwords entered via the GUI are
not written to the response file: Replace the starred entries (********) with your passwords before
performing a silent installation.
22
2012-08-16
a. From the patch installation source file location, run the .setup.sh command with the write
option (-w) specified:
./setup.sh installDir=<INSTALLDIR> -w <responsefilepath/filename.ini>
<responsefilepath/filename.ini>
where <responsefilepath/filename.ini> is the path and name of the response file you
created.
3. Press Enter to launch the installation.
RemoteCMSname
Description
23
2012-08-16
Parameter
remotecmsport
Description
Specifies the password for the Administrator account for the CMS.
remotecmspassword="<myPassword>"
24
2012-08-16