Spstack Guide Nw702 Sps12
-
Upload
vmedina2009 -
Category
Documents
-
view
52 -
download
4
Transcript of Spstack Guide Nw702 Sps12
Support Package Stack GuideSAP NetWeaver 70 Including Enhancement Package 2 SPS 12
For UNIX Windows IBM i
Target Audience Implementation Consultants System Administrators
CUSTOMERDocument version 100 ndash 2012-08-30
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 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 countriesBusiness 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 companySybase 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
260 CUSTOMER 2012-08-30
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll 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 varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) 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
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-08-30 CUSTOMER 360
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
460 CUSTOMER 2012-08-30
Document History
CAUTION
Before you start the implementation make sure you have the latest version of this document
You can find the latest version on SAP Service Marketplace at httpservicesapcom
instguides
The following table provides an overview on the most important document changes
Version Date Description
100 2012-08-30 First version
2012-08-30 CUSTOMER 560
Table of Contents
Chapter 1 Overview 9
11 Before You Start 9
12 Types of Support Packages 11
13 Downloading Support Package Stacks 12
Chapter 2 Applying Support Packages to Installable Software Units of SAP
NetWeaver 70 Including Enhancement Package 2 15
21 Application Server ABAP and ABAP-Based Software Components 15
211 Planning 15
212 Preparation 16
213 Updating the Application Server ABAP and ABAP-Based Software
Components 16
214 Post-Installation Steps 19
22 Application Server Java and Java-Based Software Components 19
221 Planning 20
222 Preparation for Applying a Support Package Stack 21
223 Updating the Application Server Java and Java-Based
Components 23
224 Post-Installation Steps 28
23 Parallel Update of Dual-Stack Systems 28
24 Process Integration 29
241 Planning 29
242 Updating Units of Process Integration 31
243 Post-Installation Steps 32
25 Business Intelligence 34
251 Planning 34
252 Preparation 35
253 Updating Units of Business Intelligence 36
26 EP Core 37
261 Planning 37
262 Preparation 37
660 CUSTOMER 2012-08-30
263 Updating EP Core 37
264 Post-Installation Steps for EP Core 37
27 Enterprise Portal 38
271 Planning 38
272 Updating Enterprise Portal 38
273 Post-Installation Steps for Enterprise Portal 39
28 Development Infrastructure 40
281 Planning 40
282 Updating Development Infrastructure 41
29 Mobile Infrastructure 43
291 Planning 43
292 Preparation 43
293 Updating Mobile Infrastructure 43
210 Standalone Engines 44
2101 Search and Classification (TREX) 44
21011 Planning 44
21012 Preparation 44
21013 Updating TREX 45
2102 BI Accelerator 47
21021 Planning 47
21022 Preparation 48
21023 Updating BI Accelerator 48
21024 Post-Installation Steps 49
2103 Gateway 50
2104 SAP Web Dispatcher 50
2105 Other Standalone Engines 50
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2 51
2111 SAP GUI Family 51
2112 Business Explorer (BI Add-On BW Add-On) 51
2113 Other Clients 52
212 SAP Library 52
Chapter A Appendix 55
A1 Determining the Current Component Versions 55
A2 Tools Used During the System Update 56
A21 SAPCAR 56
A22 ABAP Support Package Manager and Add-On Installation Tool 57
A23 Java Support Package Manager 58
2012-08-30 CUSTOMER 760
A3 System Profile Parameters 58
860 CUSTOMER 2012-08-30
1 Overview
This document describes how to install Support Package Stacks (SP Stacks) for SAP NetWeaver 70
including enhancement package 2 You can find all information related to the SP Stacks on SAP Service
Marketplace at httpservicesapcomsp-stacks
11 Before You Start
CAUTION
If you intend to update your system to the latest SP Stack level and plan to upgrade it within the
next 6 months first check the availability of the equivalent SP Stack for the target release The
delivery dates of the equivalent SP Stacks for your source and target release might be several
months apart
Be aware that you cannot upgrade to a target release that does not include the equivalent SP Stack
level
To avoid a deadlock situation we recommend that you check SAP Service Marketplace at
httpservicesapcomsp-stacks SP Stack Information and consider not applying the
latest SP Stack on your source release system
Updated Document Versions
The Support Package Stack Guide is regularly updated on SAP Service Marketplace at http
servicesapcommaintenanceNW70
NOTE
Make sure you have the latest version of the Support Package Stack Guide by checking SAP Service
Marketplace immediately before you start to apply or import Support Packages
SAP Notes
You must read SAP Note 1460321 before you read this document as it may contain corrections and
further information about the Support Package Stack installation
SAP Library
You must inform yourself about enhancements and changes to the Support Package Stack to be applied
from SAP Library under SAP Library SAP NetWeaver Whatrsquos New in SAP NetWeaver 70 ndash Release
Notes You can access the SAP Library in one of the following ways
SAP Help Portal at httphelpsapcomnw702 Application Help SAP Library ltLanguagegt
1 Overview
11 Before You Start
2012-08-30 CUSTOMER 960
NOTE
The SAP Help Portal always provides the up-to-date version of the SAP Library Therefore
we recommend that you use this channel to access the SAP Library
Local installation of the SAP Library from the online documentation DVD
CAUTION
In order to inform yourself about the current Support Package Stack you first have to update
your local installation of the SAP Library to the corresponding SPS level Follow the
instructions in section SAP Library [page 52]
Naming Conventions
In this document the following naming conventions apply
Variables
Variables Description
ltSAPSIDgt
ltsapsidgt
ltSIDgt
SAP system ID
ltINSTDIRgt Installation directory for the SAP system
lthostgt Host name
ltinstance_nogt Instance number of a system instance
ltdatabasegt Name of database
ltsapinst_directorygt Installation directory for the SAP installation tool SAPinst
ltsp_directorygt Temporary directory which the archives of a Support Package are downloaded or copied to
ltOSgt Operating system
ltOS_DIRgt OS-dependent directory consisting of a folder for the platform and a subfolder of your OS versionFor example if you operating system is Sun OS 64bit ltOS_DIRgt stands for UNIXSUNOS64
ltSP_Stackgt Number of Support Package Stack
ltSPgt Support Package level
ltPLgt Support Package patch level
ltRELgt Release number
ltLOCALEgt Language definitionFor example the German locale is _de
ltkrnl_directorygt Kernel directory which the profile parameter DIR_CT_RUN usually refers to
ltsdm_homegt Program file location of the Software Deployment Manager (SDM)
ltSAPGLOBALHOSTgt SAP global host the host where the global directories of an SAP system reside
ltSAPLOCALHOSTgt SAP local host the host where a particular instance of an SAP system is running
1 Overview
11 Before You Start
1060 CUSTOMER 2012-08-30
12 Types of Support Packages
The following table explains the terms used in the correction process as part of the software maintenance
process for SAP NetWeaver
Correction Process Description
Standard correction process
Support Package Stack Description
A Support Package Stack is a set of Support Packages and patches for the respective product version that must be used in the given combination
Version numbersSupport Package Stacks have a release number and a stack number for example SAP NetWeaver 70 Support Package Stack 05
DeliveryThere is no dedicated delivery format for the Support Package Stacks The included Support Package files have their delivery formats and must be applied using the tools as described below
Kernel Patches Version numbers
SAP Kernel patches have a release number and a patch number The patch number is increased with each correction
DeliverySAP Kernel patches are delivered as SAR files They are installed by extracting the SAR files to the kernel directory using SAPCAR Separate SAR files are shipped for the different kernel types depending on UNICODENON-UNICODE and the platform
ABAP Support Packages Description
ABAP Support Packages contain corrections and adjustments for the ABAP-based Software Components of the SAP system
DependenciesIn contrast to Java Support Packages ABAP Support Packages are non-cumulative Therefore ABAP Support Packages must be installed in the correct sequence one after the other You cannot skip any intermediate Support Packages
DeliveryABAP Support Packages are delivered as SAR files They are installed using the Support Package Manager (SPAM)
Java Support Packages Description
Java Support Packages contain corrections for the Java-based Software Components of the SAP system
DependenciesJava Support Packages always contain a full delivery of the Software Components Therefore you only need to apply the latest Support Package to update the software If there are dependencies with other Java Support Packages these are specified in an SAP Note
DeliveryJava Support Packages are delivered as Software Component Archives (SCAs) They are applied using the Java Support Package Manager (JSPM)
1 Overview
12 Types of Support Packages
2012-08-30 CUSTOMER 1160
Correction Process Description
Emergency correction process
SAP Note Correction (ABAP) Description
SAP Note corrections contain single ABAP fixes Delivery
SAP Note corrections are delivered with SAP Notes If required you apply them using the SAP Note Assistant
Java Support Package Patch Description
A Java Support Package patch contains corrections for the Java Software Components Java Support Package patches are created and released on demand A Java Support Package patch corresponds to an SAP Note that describes the same correction
DependenciesA Java Support Package patch always contains a full package of the corresponding Software Component and is applied using JSPM
13 Downloading Support Package Stacks
The Maintenance Optimizer in SAP Solution Manager is the only source from which you can receive
maintenance updates for SAP NetWeaver 70 and higher releases as well as for all applications running
on top of SAP NetWeaver The Maintenance Optimizer supports you in selecting and downloading all
required maintenance files In addition the Maintenance Optimizer generates a stack XML file and
saves it to the EPS inbox directory of SAP Solution Manager
Prerequisites
You have configured the Maintenance Optimizer in SAP Solution Manager as described on SAP Help
Portal at httphelpsapcom SAP Solutions SAP Solution Manager SAP Solution Manager ltReleasegt
ltLanguagegt Change Management Maintenance Optimizer Planning and Monitoring Product Maintenance and
also in section Automatically Calculating Product Maintenance Files
Procedure
To download a Support Package Stack proceed as follows
1 Start SAP Solution Manager using the transaction solution_manager To start the Maintenance
Optimizer choose Operations Change Management Maintenance Optimizer
2 In the Maintenance Optimizer choose the solution for which you want to download SP Stack files
3 Choose Create New Maintenance Transaction
4 Select the product version for which you want to apply a Support Package Stack
The Maintenance Optimizer displays all the systems assigned to the selected product version
5 Select the checkbox for the system that you want to update and choose Continue
6 On the subsequent screen select the Maintenance option and then choose Find Download Files
1 Overview
13 Downloading Support Package Stacks
1260 CUSTOMER 2012-08-30
7 Select the target SP Stack level and the relevant usage types according to the IT scenario to be
updated
8 Choose Find Download Files for the Stack Version
The Maintenance Optimizer displays the product maintenance files in three successive lists
9 Select the required files from the displayed lists
The first list shows all files that are dependent on the type of your operating system and
database
Select the files that correspond to the combination of your operating system and database and
the database-independent files
If your system is distributed on several hosts make sure to select all operating systems used
by the NetWeaver instances You can see all the kernels detected on your system on the Deployed
Components tab page on JSPM user interface (under the SAP KERNEL node) All detected kernels
must be updated to the same version
You get to the second list by choosing Continue This list displays all Support Package files that
are not assigned to the selected Support Package Stack Before you continue with the selection
you must check whether the Support Package files listed here are suitable for your product
maintenance procedure
You get to the third list by choosing Continue The list displays all product maintenance files
that are part of the selected Support Package Stack
Ensure that all files that are assigned to the Support Package Stack are selected here Files that
are not selected will not be included later in the download
10 Choose Continue Use the Download Basket to download the maintenance files
11 Choose Continue once the files have been put in your Download Basket and then Confirm Files in
Download Basket
A dialog window appears and displays all files
12 Confirm the download for all files
13 Open your Download Manager and download the files
NOTE
The stack XML file is generated by the Maintenance Optimizer and automatically saved to
the EPS inbox directory of SAP Solution Manager
More Information
For more information about the Maintenance Optimizer see SAP Support Portal at http
servicesapcomsolman-mopz
1 Overview
13 Downloading Support Package Stacks
2012-08-30 CUSTOMER 1360
This page is left blank for documents that are printed on both sides
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
This chapter describes how to apply Support Packages to installable software units of SAP NetWeaver
70 including enhancement package 2 SAP NetWeaver distinguishes three types of installable software
units
Systems with one or multiple usage types
Standalone engines
Clients
A scenario implementation usually involves several installed software units
RECOMMENDATION
We strongly recommend that you always update all software units belonging to one scenario
together in order to retain a consistent system state Due to the fact that some installable software
units can be commonly shared in different scenarios you must consequently update all scenarios
using the common software units at the same time
21 Application Server ABAP and ABAP-Based Software Components
211 Planning
Procedure
The following components belong to the usage type SAP NetWeaver Application Server ABAP
Software Components of Application Server ABAP
Component to Be Updated SP File Name Tool Used to Apply SP
SAP KERNEL 720 32-64-BIT Non-UNICODEUNICODE SAPEXESAR
SAPEXEDBSAR
JSPMmanually
SAP IGS 700 igsexesar
SAP ABA 702 SAPKA702ltSPgt SPAMSAINT
SAP BASIS 702 SAPKB702ltSPgt
SAP BW 702 SAPKW702ltSPgt
PI_BASIS 702 SAPK-702ltSPgtINPIBASIS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
2012-08-30 CUSTOMER 1560
NOTE
This table contains only software components that belong to the usage type AS ABAP Software
components of other usage types and application units are listed in the corresponding sections
NOTE
SAP delivers intermediate Support Packages for the component SAP BW 702 between two
subsequent SP levels besides the Support Packages delivered along with the Support Package
Stacks Therefore the highest SP level of SAP BW 702 does not necessarily match the target SP
Stack level
CAUTION
When applying a Support Package Stack to a dual-stack system (ABAP+Java) the Java Support
Package Manager (JSPM) will necessarily restart the system several times to make the changes
effective The ABAP part will only be restarted when JSPM is updating the SAP kernel and IGS
212 Preparation
Procedure
Read SAP Note 822379 and all related SAP Notes that the first one refers to
213 Updating the Application Server ABAP and ABAP-Based Software Components
Procedure
Applying Support Packages to SAP NetWeaver Application Server ABAP and ABAP-Based Components
You can update the SAP NetWeaver Application Server ABAP and all ABAP-based software components
running on it using the Support Package Manager (transaction SPAM)
NOTE
If a particular Support Package Stack requires the installation or upgrade of some add-on
components you must use the ABAP Add-on Installation Tool (transaction SAINT) instead of the
Support Package Manager In this case SAINT is able to import both the add-on components and
the related Support Packages of ordinary SAP components
Proceed as follows
1 Log on to the SAP NetWeaver AS system with client 000
2 Start the Support Package Manager by calling transaction SPAM or
start the Add-On Installation Tool by calling transaction SAINT
3 Load the relevant Support Packages or add-on installation packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
1660 CUSTOMER 2012-08-30
4 Define an import queue
5 Perform the import of the defined queue
NOTE
If you have modified SAP objects in your system and these objects are included in the Support
Packages you must perform modification adjustment during the import using the
transactions SPDD (for ABAP Dictionary objects) and SPAU (for Repository objects)
To import the queue you use the standard scenario You can choose between the conventional
import mode and downtime-minimized import mode
Conventional Import Mode
This option comprises the following steps
1 Update the SAP kernel and SAP IGS as described in section Updating SAP Kernel and SAP IGS below
Start the system after the kernel update
2 Import the ABAP Support Packages with the Support Package Manager (SPAM)
Import Mode Downtime-Minimized
This option can be used to reduce system downtime during the update It comprises the following
steps
1 In transaction SPAM enable the downtime-minimized import mode by choosing Extras
Settings then on the Import queue tab page choose Standard and activate the option Import Mode
Downtime-Minimized
2 Import the ABAP Support Packages into the system in an inactive state in the downtime-minimized
mode during system uptime
3 Update the SAP kernel and SAP IGS as described in section Updating SAP Kernel and SAP IGS below
Start the system after the kernel update
4 Complete the ABAP Support Packages import
CAUTION
During this step the system cannot carry out any business transactions (business downtime)
NOTE
In rare cases due to the dependencies of some Support Packages on a particular kernel patch level
the downtime-minimized update does not work In such cases the Support Package Manager
informs you that you must update the SAP kernel before importing ABAP Support Packages You
must proceed with the conventional import procedure
Updating SAP Kernel and SAP IGS
In general the SAP kernel and IGS binaries are located in the global kernel directory DIR_CT_RUN on
the host indicated by the profile parameter SAPGLOBALHOST Once the files in this directory have been
updated to a new patch level a system restart distributes them by means of the program SAPCPE to the
local directories DIR_EXECUTABLE on the hosts where the instances of the SAP system are running
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
2012-08-30 CUSTOMER 1760
CAUTION
The automatic distribution by means of SAPCPE depends on the settings of the profile parameters
DIR_CT_RUN for the global kernel directory and DIR_EXECUTABLE for the local directory of the
executables Before you continue check the instance profiles for the settings of these parameters
in systems that are not installed using SAPinst (for example systems upgraded from older releases
copied or migrated systems)
CAUTION
If your system is a dual-stack system (ABAP+Java) and the ABAP stack has a non-Unicode kernel
be aware that the SCS instance has a Unicode kernel You have to update both kernels (together
with SAP IGS) prior to updating the ABAP and Java Support Package stacks This ensures
compatibility and reduces system downtime
RECOMMENDATION
If you perform an update of a dual-stack system (ABAP+Java) we recommend that prior to
applying ABAP and Java Support Package stacks you use the Single Support Packages option in JSPM
and select for update only the components SAP KERNEL and BC-FES-IGS
For more information about updating a dual-stack system see Parallel Update of Dual-Stack Systems
[page 28]
If you perform an update of an ABAP system the following procedure applies for updating the SAP
kernel and IGS manually
1 Log on as user ltsapsidgtadm to the instance host to be updated
2 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory using
SAPCAR [page 56]
3 Stop the ABAP system that you want to update
NOTE
If the system is running in a high availability (HA) environment make sure that the HA
software does not restart the system automatically during the update
4 Back up the kernel directory ltkrnl_directorygt
5 Copy or move the extracted programs from the temporary directory to the SAP kernel directory
6 Only valid for UNIX |
Execute the following command sequence on UNIX platforms
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
1860 CUSTOMER 2012-08-30
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
7 Restart the SAP system
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS) runs
on a dedicated host You need to perform the kernel update for the ASCS instance manually but
excluding the IGS update because the IGS is not required in an ASCS instance
In rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of such instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances manually Proceed as described
in section Manually Updating Instances with Kernel Directory Located on Separate Hosts below in this document
214 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the ABAP system
22 Application Server Java and Java-Based Software Components
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system which includes
JSPM itself
SAP Kernel and SAP IGS
All Java-based usage types installed in the system
Software Deployment Manager (SDM) - the deployment service of the system
RECOMMENDATION
We strongly recommend that you apply the target Support Package Stack to your system as a
whole This ensures consistency on both the system and the application levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 1960
221 Planning
Procedure
Java Support Package files (SCAs) contain all software objects of the corresponding software
components Thus it is sufficient to apply the Java Support Package files of the intended Support Package
Stack directly to the Java system to be updated It is not necessary to apply the Support Package Stacks
between the start SP Stack level and the target SP Stack level successively
CAUTION
When applying a Support Package Stack to a Java system the Java Support Package Manager (JSPM)
will necessarily restart the system several times to make the changes effective With a dual-stack
system (ABAP+Java) the ABAP part will only be restarted when JSPM is updating the SAP kernel
and IGS
The following components belong to the usage type SAP NetWeaver Application Server Java (AS Java)
Software Components of Application Server Java
Component to Be Updated SP File Name Tool Used to Apply SP
SAP Kernel 720 32-64-BIT UNICODE SAPEXESAR
SAPEXEDBSAR
JSPM
SAP IGS 700 igsexesar
BI META MODEL REPOSITORY 702 BIMMRltSPgt_ltPLgtSCA
J2EE ENGINE CORE TOOLS 702 CORETOOLSltSPgt_ltPLgtSCA
J2EE ENGINE BASE TABLES 702 BASETABLESltSPgt_ltPLgtSCA
BI UDI 702 BIUDIltSPgt_ltPLgtSCA
DI BUILD TOOL 702 SAPBUILDTltSPgt_ltPLgtSCA
SAP CAF 702 CAFltSPgt_ltPLgtSCA
SAP IKS 702 KMKWJIKSltSPgt_ltPLgtSCA
JAVA LOG VIEWER 702 JLOGVIEWltSPgt_ltPLgtSCA
SAP J2EE ENGINE CORE 702 SAPJEECORltSPgt_ltPLgtSCA
SAP JAVA TECH SERVICES 702 SAPJTECHSltSPgt_ltPLgtSCA
SAP TECH S OFFLINE 702 SAPJTECHFltSPgt_ltPLgtSCA
SAP J2EE ENGINE 702 SAPJEEltSPgt_ltPLgtSCA
JAVA SP MANAGER 702 JSPMltSPgt_ltPLgtSCA
ADOBE DOCUMENT SERVICES 702 ADSSAPltSPgt_ltPLgtSCA
UME ADMINISTRATION 702 UMEADMINltSPgt_ltPLgtSCA
LIFECYCLE MGMT TOOLS 702 LMTOOLSltSPgt_ltPLgtSCA
SAP CAF-UM 702 CAFUMltSPgt_ltPLgtSCA
SAP SOFTW DELIV MANAGER 702 SDMKITltSPgt_ltPLgtJAR
SOFTWARE LIFECYCLE MANAGER 702 SWLIFECYCLltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2060 CUSTOMER 2012-08-30
NOTE
This table contains only software components that belong to the usage type AS Java Software
components of other usage types and Java application units are listed in the corresponding
sections
NOTE
As of Support Package 09 you can update your system with SAP Kernel 720 instead of SAP Kernel
701
222 Preparation for Applying a Support Package Stack
Procedure
1 Download the Support Package Stack with all usage types to be updated and the stack definition
XML file as described in Downloading Support Package Stacks [page 12]
NOTE
You can find the activated usage types in an existing Java system on the Deployed Components tab
page on the JSPM user interface
NOTE
You do not need to download the SP Stacks between the source SP Stack level and target SP
Stack level By default the target SP Stack level is the latest available SP Stack
2 Make sure the following requirements are met prior to applying the Support Package Stack
You have familiarized yourself with SAP Note 891983 before you start the Java Support Package
Manager
The system to be updated is fully functional
The Support Package Stack you want to apply and the corresponding stack definition XML
file are available in the EPS inbox directory usrsaptransEPSin By default this location
can be also referred to as ldquoJSPM inboxrdquo
The SAP NetWeaver Application Server Java (AS Java) and the database have been backed up
You have not deleted renamed or created any directories and files in the following directories
and their subdirectories usrsapltSAPSIDgtSYSexe and usrsapltSAPSIDgtSYS
profile
Otherwise JSPM cannot detect the kernel and the system profiles and cannot be started If a
backup of the kernel and the system profiles has been required it has been created in a different
directory
The ltsapsidgtadm user has Read permissions for the EPS inbox directory usrsaptransEPS
in
If your database is SAP MaxDB the overwrite mode for the log area has been activated
The database and the SDM repository have been synchronized
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2160
For more information see the online documentation for JSPM on SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70 Library
(including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library Administrators Guide
Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems AS Java
(Application Server for Java) Software Logistics Software Maintenance Java Support Package Manager
Then choose Troubleshooting JSPM Does Not Update the Versions of the Deployed Components
There is enough disk space
For more information see SAP Note 891895
Your current SAPCAR tool is able to extract the Support Packages for the SAP kernel and
other OS level binaries delivered as SAR files
RECOMMENDATION
You can download the latest version of SAPCAR from SAP Service Marketplace at
httpservicesapcompatches Entry by Application Group Additional Components
SAPCAR
Put the downloaded version in the same directory in the JSPM inbox in which the kernel
SAR files reside so that JSPM can use this version for extracting the SAR files
3 Only valid for Linux |
For RHEL 4 and SLES 9 you need to install additional operating system packages For more
information see SAP Note 1021236End of Linux |
4 Only valid for Windows |
For Windows you need to install additional operating system packages For more information see
SAP Note 684106End of Windows |
5 To prevent the Software Deployment Manager (SDM) from temporarily exceeding the available
disk space during the update process you can change the file transfer directory of SDM in a system
of SPS09 or higher using the following command sequence
Only valid for Windows |
cd ltsdm_homegt
StopServerbat
sdmbat jstartup mode=standalone
sdmbat filetransferdir dir=ltnew_dirgt
sdmbat jstartup mode=integrated
StartServerbat
End of Windows |
Only valid for IBM i5OSUNIX |
cd ltsdm_homegt
StopServersh
sdmsh jstartup mode=standalone
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2260 CUSTOMER 2012-08-30
sdmsh filetransferdir dir=ltnew_dirgt
sdmsh jstartup mode=integrated
StartServersh
End of IBM i5OSUNIX |
6 To prevent deployment errors during the update process proceed as follows
1 Log on to the Central Instance host
2 Start the ConfigTool and in the navigation area choose Cluster-data Global server configuration
Managers ServiceManager
3 In the Global properties panel set the Custom value of the EventTimeout property to 120
4 Choose Save
5 Restart the Central Instance
7 Check whether the used JDK version and the Java VM settings of the Java runtime system comply
with the requirements in SAP Note 723909 Update the JDK and adjust the settings if necessary
NOTE
An update of the used JDK version possibly changes the JVM path In this case you must
make the new path available to all Dialog Instances of the J2EE engine by implementing option
1 of SAP Note 718901
8 Make sure that the J2EE administrator password stored in the secure store for offline usage is
identical with the one stored in the User Management Engine (UME) You can change the password
in the secure store as described in SAP Note 870445
9 If you are running a high availability system on Windows you might need to prepare your system
as described in the online documentation for JSPM see section Preparing Systems That Run in High
Availability Environment
223 Updating the Application Server Java and Java-Based Components
Procedure
Applying a Support Package Stack to SAP NetWeaver Application Server Java and Java-Based Components
NOTE
The JSPM GUI might not work properly on some UNIX systems For more information and the
solution see SAP Note 1013976
1 Log on as user ltsapsidgtadm to the Central Instance host
NOTE
If your operating system is IBM i log on as user ltSIDgtADM or ltSIDgtOFR
2 Close the SAP Management Console (SAP MMC) and the SDM remote GUI client
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2360
3 For UNIX and Windows To start the JSPM navigate to the directory ltINSTDIRgtltSIDgt
ltCentral_Instance_Namegtj2eeJSPM and run the go script file
NOTE
If your system is running on IBM i to start the JSPM proceed as follows
1 To prevent JSPM from automatically starting its GUI in the file usrsapltSIDgt
ltCentral_Instance_Namegtj2eeJSPMparamjspm_configtxt change the
property dialogSDTServerConnectionSDTGuilaunch from true to false
2 On the IBM i host run the go script file using the following command
QSH CMD(usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPMgo)
3 In the mounted directory usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPM run
the StartGui script file The JSPM GUI appears
4 In the Host field enter the target IBM i host
NOTE
Depending on the system type ltCentral_Instance_Namegt has the following syntax
Standalone Java system JCltinstance_nogt
Add-On system DVEBMGSltinstance_nogt
4 Enter your SDM password to log on to the SDM
5 On the Deployment tab page select the Java Support Package Manager option and update the software
component sapcomJSPM to the target SPS level
6 Restart the JSPM and log on with the SDM password
RECOMMENDATION
We strongly recommend that you use the Support and Enhancement Package Stack option when
applying a Support Package Stack Other options can lead to unintended consistency issues
NOTE
If you need to include the latest patches for a particular component during the update process
with the Support and Enhancement Package Stack option stop the JSPM after restart and apply SAP
Note 1080821 Then start the JSPM again
7 On the Deployment tab page select the Support and Enhancement Package Stack option and choose Next
The Support Package Stacks that are available for deployment in the global EPS inbox directory
are displayed
8 In the Target SP Stack Level dropdown box select the Support Package Stack to be applied and choose
Next
In this step JSPM performs various status validations and displays the result of each software
component included in the stack definition XML file on the subsequent screen which includes
the following possible statuses
OK Indicates that the SPS level of the corresponding software component is applicable
WARNING We recommend that you view the details about the component by choosing Show
Details
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2460 CUSTOMER 2012-08-30
This status may indicate that the corresponding software component comprises custom
modifications in an NWDI-controlled system
If your system is used for NWDI development and it is either a DEV or a CONS system
you will be informed that JSPM will not deploy the modified software components but
only transport them to the CMS transport directory JSPM will deploy only the software
components that are not modified
If your system is not used for NWDI development or if your system is used for NWDI
development and it is either a TEST or a PROD system you will be informed that JSPM
has found newer versions of modified software components and will automatically replace
the original versions with the newer versions JSPM will deploy all software components
that are not modified together with the replaced versions of the modified software
components
CAUTION
You may get a warning telling you that there are patches installed in your system
containing fixes which might not be included in the target SP Stack This is possible if
you have applied patches of the start SP Stack level that were delivered later than the
target SP Stack delivery date In order not to lose these fixes you need to download and
apply the corresponding patches of the target SP Stack level
If you are performing an update from SAP NetWeaver 70 including enhancement
package 1 SPS00 and you have not applied any patches for the software component with
status WARNING before the update then you can ignore warnings such as the following
example
The new version of the development component sapcomcomsapnetweaver
bcrfmoni is 70100200806121227180000 and is lower than the already
deployed version 70100200807090143420000
REVISE Indicates inconsistencies with the corresponding software component
The deployment cannot be performed until all problems have been resolved You can view
the problems by choosing Show Details
9 If the status of the selected SP Stack is OK or WARNING you can start the system update by choosing
Start JSPM then changes the status to SCHEDULED
If the SP Stack to be applied includes a kernel update and the current kernel is not already of the
corresponding patch level JSPM arranges the kernel update as the very first Support Package to
be applied JSPM updates the kernel binaries of all instances (including Dialog Instances and SCS
instances in a HA environment) whose kernel directories DIR_CT_RUN effectively reside on the host
indicated by the profile parameter SAPGLOBALHOST
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2560
CAUTION
Kernel binaries of instances whose kernel directories DIR_CT_RUN are not effectively linked
to the host SAPGLOBALHOST must be updated individually as described in section Manually
Updating Instances with Kernel Directory Located on Separate Hosts below
The kernel update (includes update of SAP Kernel and SAP IGS) using JSPM consists of the following
steps
1 JSPM stops the Central Instance automatically and prompts you to stop the remote SCS and
Dialog Instances manually
2 After you have stopped all the instances choose the Next button in the dialog box
The kernel update starts
NOTE
If the system is running in a high availability environment make sure that the HA
software does not restart the instance automatically during the update
NOTE
If kernel binaries of the SCS instance need to be updated manually (see Manually Updating
Instances with Kernel Directory Located on Separate Hosts below) you must perform this at the
time when JSPM is updating the kernel binaries of the Central Instance In any case the
SCS kernel must be up-to-date before the next restart
When the kernel update is finished a dialog box appears in which you are prompted to restart
the SCS instance manually
3 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries
before you can proceed with the next step For more information see Adjusting the Ownership and
Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
4 Choose Next in the dialog box when the SCS instance is running again
After the kernel update JSPM restarts the system for further deployment of the remaining Support
Packages in the stack
RECOMMENDATION
If you need to update the kernel binaries of any Dialog Instances manually (see Manually
Updating Instances with Kernel Directory Located on Separate Hosts below) perform the update when
JSPM is updating the remaining Support Packages in the stack in order to save time
The deployment of each Support Package can end with one of the following statuses
DEPLOYED
The Support Package has been successfully deployed
DEPLOYED WITH WARNING
The Support Package has been deployed but it possibly may not work properly with other
deployed components
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2660 CUSTOMER 2012-08-30
You can view the details by choosing Show Details or examining the log files You can also view
the details about the component by choosing the Deployed Components tab page
ERROR
An error has occurred during the deployment You can view the details by choosing Show
Details or examining the log files
You must correct the error to be able to continue with the SP Stack update
You can proceed as described for a deployment that finished with status DEPLOYED WITH
WARNING
If the error correction does not change the contents in the JSPM inbox you can continue
the deployment by choosing Resume
If the error correction changes the contents in the JSPM inbox you can choose New
Deployment to redeploy the SP Stack
NOT DEPLOYED
JSPM has not attempted to deploy the software component for certain reasons
If your system is not used for NWDI development you can proceed as described for a
deployment that finished with status ERROR
If your system is used for NWDI development and it is either a DEV or a CONS system
the status of the modified software components is always NOT DEPLOYED JSPM has
transported the software components of the Support Package Stack both modified and
not modified to the CMS transport directory The deployment of the modified software
components is handled by NWDI
Manually Updating Instances with Kernel Directory Located on Separate Hosts
JSPM performs kernel update for all instances (including Dialog Instances and SCS instances in a HA
environment) whose kernel directories DIR_CT_RUN effectively reside on the host indicated by the profile
parameter SAPGLOBALHOST (by using folder sharing on Windows or file system mounting on UNIX) In
rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of those sort of instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances individually
To update the kernel of an instance manually proceed as follows
1 Log on as user ltsapsidgtadm to the host of the instance to be updated
2 Back up the kernel directory which is specified by the profile parameter DIR_CT_RUN
3 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory with
SAPCAR [page 56]
4 Stop the instance being updated
NOTE
If the system is running in a HA environment make sure that the HA software does not
restart the instance automatically during the update
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2760
5 Copy or move the extracted programs from the temporary directory to the local kernel directory
6 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries as
described in section Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
7 Restart the instance after JSPM has finished the deployment of all packages on the Central Instance
Only valid for UNIX |
Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms
On UNIX platforms you must adjust the ownership and execution permissions of the kernel binaries
after the update regardless whether you performed the update manually or by using JSPM because
both update procedures are performed with the ltsapsidgtadm user Enter the following command
sequence
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
224 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the Java system
23 Parallel Update of Dual-Stack Systems
If you perform an update of a dual-stack system (ABAP+Java) we recommend that you follow the
procedure described below The procedure has been validated to update the ABAP stack and the Java
stack of a NetWeaver system in parallel thus reducing the overall system downtime by half
Procedure
1 Before applying ABAP and Java Support Packages use the Single Support Packages option in JSPM and
select for update only the components SAP KERNEL and BC-FES-IGS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
23 Parallel Update of Dual-Stack Systems
2860 CUSTOMER 2012-08-30
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS)
runs on a dedicated host In this case JSPM does not support update of kernel binaries and
you need to update them manually Perform the update manually as described under Updating
SAP Kernel and SAP IGS in section Updating the Application Server ABAP and ABAP-Based Software
Components [page 16]
2 Import the Support Packages for the component SAP_BASIS into the ABAP stack using the ABAP
Support Package Manager (SPAM)
3 Import the remaining ABAP Support Packages with SPAM and in parallel apply the Java Support
Package Stack with JSPM
Proceed as described in Updating the Application Server ABAP and ABAP-Based Software Components [page
16] and Updating the Application Server Java and Java-Based Software Components [page 23]
24 Process Integration
241 Planning
Procedure
This section covers all the units of Process Integration that should be updated Particularly the following
units must always have the same Support Package level (the patch level can be different)
Integration Server
XI Adapter Engine
Partner Connectivity Kit
System with the Usage Type Process Integration
Software components of Integration Server
Components to Be Updated SP File Name Tool Used to Apply SP
Java stack
XI TOOLS 702 SAPXITOOLltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
ABAP stack
XI CONTENT SAP_BASIS 702 SAPBASISltSPgt_ltPLgtZIP File upload
XI CONTENT SAP_ABA 702 SAPABAltSPgt_ltPLgtZIP
SAP NetWeaver Application Server ABAP (see table Software components of Application Server ABAP [page 15])Note that update of the following software components of the ABAP system is not required SAP ABA 702 SAP BW 702 PI_BASIS 702
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 2960
J2EE Adapter Engine
If your implemented scenario includes a J2EE Adapter Engine then it must always be of the same
Support Package level as the Integration Server
Components of the J2EE Adapter Engine
Component to Be Updated SP File NameTool Used to Apply SP
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
J2SE Adapter Engine
The installation of the J2SE Adapter Engine depends on the implemented scenario
Components of the J2SE Adapter Engine
Component to Be Updated SP File Name Tool Used to Apply SP
XI CONNECTIVITY SE 702 SAPXICONSltSPgt_ltPLgtSCA ZIP tool (for example WinZip)
Partner Connectivity Kit
If your implemented scenario includes a Partner Connectivity Kit (PCK) then it must always be of the
same Support Package level as the Integration Server
Software components of Partner Connectivity Kit
Components to Be Updated SP File NameTool Used to Apply SP
XI PCK 702 SAPXIPCKltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of the Application Server Java [page 20])
System Landscape Directory (SLD)
The System Landscape Directory is required for the PI operations Although updating the SLD is not
necessarily required it is advisable to update the SLD server and the SAP Master Data Content within
it from time to time The update of the SLD includes
1 The system where the SLD is running
2 The SAP Master Data Content within this SLD
SAP GUI
See table Compatible SAP GUI Versions [page 51]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3060 CUSTOMER 2012-08-30
242 Updating Units of Process Integration
Procedure
Before you start the update perform the following steps
In the Runtime Workbench use Communication Channel Monitoring to stop all sender channels
for all adapter types on all your Adapter Engines
On the Integration Server use transaction SMQR and deregister all qRFC queues
System with the Usage Type Process Integration
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the XI instance is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system where the XI instance is running
For more information see Application Server Java and Java-Based Software Components [page 19]
System Landscape Directory (Optional)
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the SLD is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the entire Support Package Stack to the system where the SLD is running
For more information see Application Server Java and Java-Based Software Components [page 19]
J2EE Adapter Engine
Apply the Support Package Stack to the system where the Adapter Engine is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Partner Connectivity Kit
Apply the Support Package Stack to the system where the PCK is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Front End GUIs
Update the SAP GUI components if necessary
For more information see SAP GUI Family [page 51]
ABAP 700 Business System (Optional)
Apply the Support Packages for SAP NetWeaver Application Server ABAP (including SAP kernel and
the Support Package for SAP BASIS 700)
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 640 Business System (Optional)
Apply the Support Packages for SAP Web Application Server ABAP 640 (including SAP kernel and the
Support Package for SAP BASIS 640)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3160
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 620 Business System (Optional)
1 Update the SAP Kernel 620
2 Import the released Basis Support Packages for SAP Web AS 620 as well as the most recent Add-
On Support Package for APPINT 200_620 in the order described in SAP Note 439915
J2SE Adapter Engine (Optional)
NOTE
The XI Adapter Engine (J2SE) and all its adapters are provided for compatibility reasons only and
are not developed any further You have to use the XI Adapter Engine running on SAP NetWeaver
AS Java For more information see the Master Guide ndash SAP NetWeaver 70 available on SAP Service
Marketplace at httpservicesapcominstallNW70 Planning
1 Extract the SAPXICONSltSPgt_ltPLgtSCA (XI Connectivity SE 700) archive (ZIP format) to a temporary
directory
2 Save the old configuration files as described in the document Adapterpdf in directory
lttemp_directorygttech_adapterAdministrationDocumentation
3 Unpack the ZIP archive TechnicalAdapterssda to the installation directory of the XI Adapter
Engine (J2SE)
4 Restore the configuration files with restore_configuration
243 Post-Installation Steps
Procedure
Communication Channels and Queues
Restart all stopped sender channels and register all deregistered qRFC queues
XI Content
In the system with usage type PI import the XI content from the archives SAPBASISltSPgt_ltPLgtZIP
and SAPABAltSPgt_ltPLgtZIP as follows
1 Unpack the archives using a ZIP tool of your choice
2 Copy the corresponding export files (with file extension tpz) to the import directory ltINSTDIRgt
ltSAPSIDgtSYSglobalxirepository_serverimport
3 Start the Integration Builder (transaction SXMB_IFR)
4 Enter the Integration Repository by choosing Repository (Design)
5 Choose Tools Import design objects
6 Import the tpz files containing the XI content
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3260 CUSTOMER 2012-08-30
NOTE
For more information see SAP Note 836200
Role Generation on the Integration Server
On the Integration Server execute transaction SUPC (mass generation of roles) for all SAP_XI roles in
each of your clients to regenerate possibly changed roles
NOTE
Do not forget to make a user comparison for regenerated roles afterwards
Partner Connectivity Kit (Optional)
Perform the post-installation steps for PCK as described in SAP Note 746328
SAP Master Data within the SLD (Optional)
In the system where your SLD is running import the latest SLD content as described in SAP Note
669669
Receiver-Based EOIO Serialization in J2EE Adapter Engine (Optional)
The J2EE Adapter Engine can be switched to receiver-based EOIO serialization The switch can be
triggered on demand and is executed asynchronously It includes a database migration step during
which all EOIO processing in the Adapter Engine is disabled See SAP Note 973894 for details about how
to start the EOIO serialization migration
Service Metering (Optional)
Service metering gathers information about a service caller transfers it to the service provider and
counts on the service provisioning side how many times a service is called and by which service caller
Service metering is performed for the XI message protocol and the WS message protocol Service
metering is automatically enabled after applying a Support Package Stack By default only non-sensitive
data is transmitted to internal or external service providers in a compatible way
Service metering can be configured in PI in the Integration Engine on sender-side and in the Integration
Directory
Service metering can be configured in AS ABAP in transaction SOAMANAGER
Only if the service provider is allowed to receive more detailed information about the service caller set
the metering level to higher than the default
For more information see SAP Note 1239428
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3360
25 Business Intelligence
251 Planning
Procedure
Business Intelligence includes one or many of the following units that must be updated depending on
your implemented scenarios The usage types Business Intelligence (BI) and Business Intelligence Java
Components (BI-Java) must always have the same Support Package level
Business Intelligence
Software Components of Business Intelligence
Component to Be Updated SP File Name Tool Used to Apply SP
BI CONT ADDON 70x SAPK-70ltxgtltSPgtINBICONT SAINT
SAP NetWeaver Application Server ABAP (see table Software Components of Application Server ABAP [page 15])
NOTE
For information about the dependencies applying to BI Content Support Packages see SAP Note
653814 BI CONT 703 Support Packages are not part of the NetWeaver SP Stacks Updates can be
performed when applicable Alternatively BI CONT 704 Support Packages can be imported See
the BI Content release strategy in SAP Note 153967
Business Intelligence Java Components
BI Java Components
Component to Be Updated SP File NameTool Used to Apply SP
BI REPORTING AND PLANNING 702 BIREPPLANltSPgt_ltPLgtSCA JSPM
BI WEBDYNPRO ALV 702 BIWDALVltSPgt_ltPLgtSCA
BI INFORM BROADCASTING 702 BIIBCltSPgt_ltPLgtSCA
BI WEB APPLICATIONS 702 BIWEBAPPltSPgt_ltPLgtSCA
BI BASE SERVICES 702 BIBASESltSPgt_ltPLgtSCA
VISUAL COMPOSER BI KITS 702 VCKITBIltSPgt_ltPLgtSCA
Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
BI Precalculation Service
Components of the BI Precalculation Service
Component to Be Updated SP File Name Tool Used to Apply SP
BI Pre-calculation Service 700 xPreCalServerltSPgt_ltPLgtexe Installer
Search and Classification (TREX)
See table TREX Component [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3460 CUSTOMER 2012-08-30
BI Accelerator
The BI Accelerator is based on the TREX technology It is a special Linux 64-bit version of SAP NetWeaver
70 Search and Classification (TREX) which is delivered on preconfigured hardware
NOTE
You cannot use a TREX installation based on 32-bit architecture that is configured for searching
in metadata and documents for the BI Accelerator And vice versa a BI Accelerator box cannot
be used for searching in metadata and documents
If you want to use the search functionality as well as the BI Accelerator you require two separate
installations For more information see BI Accelerator [page 47]
Clients
Depending on your implemented scenarios you have to update SAP GUI Components and Business
Explorer (BI Add-OnBW Add-On)
NOTE
See SAP Note 889314 to determine when to use the BI Add-On and the BW Add-On
NOTE
As SAP GUI 640 is no longer supported BI Frontend Support Package 1800 resp patch 1801 is the
last Support Package resp patch based on SAP GUI 640 For more information see SAP Note
1231292 (Frontend Add-in Strategy 640710 GUI Version)
For more information about the new release strategy for the BI Frontend see SAP Note 1231363
(Changed Delivery Strategy for BI Frontend)
252 Preparation
Procedure
For the Support Packages of the most important Business Intelligence units so called SAPBINews
(SAPBWNews) Notes are created Read these Notes before updating Business Intelligence For SAP
NetWeaver 70 including enhancement package 2 SPS 12 these are the following
Business Intelligence ABAP SAP Note 1680996
Business Intelligence Java Components SAP Note 1726461
BI 70 Frontend Add-On for SAP GUI 710 SAP Note 1413032
BI 70 Frontend Add-On for SAP GUI 720 SAP Note 1630112
BI 70 Frontend Add-On for SAP GUI 730 SAP Note 1726739
For more information about BI Support Packages see SAP Community Network at http
scnsapcomcommunitydata-warehousingnetweaver-bw Related Resources SAP NW BW Support
Packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
2012-08-30 CUSTOMER 3560
253 Updating Units of Business Intelligence
Procedure
Business Intelligence
1 Update the SAP NetWeaver Application Server ABAP (with BI CONT 70x if necessary) with the
appropriate Support Packages
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
NOTE
When applying the component SAP BW 702 some generation errors might occur When
you start importing the BI Support Packages in transaction SPAM choose the menu path
Extras Ignore generation errors For more information see SAP Note 114134
2 Apply the Support Package Stack to the system with the usage type BI-Java
For more information see Application Server Java and Java-Based Software Components [page 19]
3 Update the BI Precalculation Service that is used in your scenario
4 Update the standalone engine Search and Classification (TREX) that is used in your scenario For more
information see Standalone Engine Search and Classification (TREX) [page 44]
NOTE
You have to update TREX to the newest version if you use search capabilities within Business
Intelligence
5 Update the BI Accelerator to the newest available version For more information see BI
Accelerator [page 47]
6 Update the SAP GUI and Business Explorer (BI Add-On BW Add-On) on all remote client hosts
that are involved in the scenario
For more information see SAP GUI Family [page 51] and Business Explorer (BI Add-On BW Add-On)
[page 51]
BI Precalculation Service
1 Log on to the host as a user with administration rights
2 Install the Support Package of the BI Precalculation Service by executing the
xPreCalServerexe file
The welcome screen of the BI Precalculation Server setup wizard appears
The setup now checks the system for the prerequisites
3 Choose the option Update for updating the BI Precalculation service to the current patch level and
then Finish
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3660 CUSTOMER 2012-08-30
26 EP Core
261 Planning
Procedure
The following installable software units must be updated
EP Core
Software Components of EP Core
Component to Be Updated SP File Name Tool Used to Apply SP
PORTAL CORE SERVICES 702 EPBCltSPgt_ltPLgtSCA JSPM
PORTAL FRAMEWORK 702 EPBC2ltSPgt_ltPLgtSCA
PORTAL 702 EPPSERVltSPgt_ltPLgtSCA
PORTAL WEB DYNPRO 702 EPWDCltSPgt_ltPLgtSCA
UWL COLL PROCESS ENGINE 702 UWLJWFltSPgt_ltPLgtSCA
CAF EU 702 SAPEUltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
262 Preparation
Procedure
Backing Up the Portal Runtime Configuration
If you have made changes to the standard Portal Runtime configuration you have to make a backup
of the configuration before the update process For more information see SAP Note 1064468
263 Updating EP Core
Procedure
Apply the Support Package Stack to a system with usage type EP Core
For more information see Application Server Java and Java-Based Software Components [page 19]
264 Post-Installation Steps for EP Core
Procedure
Restoring the Portal Runtime Configuration
To make your changes to the standard Portal Runtime Configuration effective you have to restore
the backup of the configuration done before the update process For more information see SAP Note
1064468
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
26 EP Core
2012-08-30 CUSTOMER 3760
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +4918 0534 34 34F +4918 0534 34 20
wwwsapcom
copy Copyright 2012 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors
Microsoft Windows Excel Outlook PowerPoint Silverlight and Visual Studio are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database System i System i5 System p System p5 System x System z System z10 z10 zVM zOS OS390 zEnterprise PowerVM Power Architecture Power Systems POWER7 POWER6+ POWER6 POWER PowerHA pureScale PowerPC BladeCenter System Storage Storwize XIV GPFS HACMP RETAIN DB2 Connect RACF Redbooks OS2 AIX Intelligent Miner WebSphere Tivoli Informix and Smarter Planet are trademarks or registered trademarks of IBM CorporationLinux is the registered trademark of Linus Torvalds in the United States and other countriesAdobe the Adobe logo Acrobat PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countriesOracle and Java are registered trademarks of Oracle and its affiliatesUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyApple App Store iBooks iPad iPhone iPhoto iPod iTunes Multi-Touch Objective-C Retina Safari Siri and Xcode are trademarks or registered trademarks of Apple IncIOS is a registered trademark of Cisco Systems IncRIM BlackBerry BBM BlackBerry Curve BlackBerry Bold BlackBerry Pearl BlackBerry Torch BlackBerry Storm BlackBerry Storm2 BlackBerry PlayBook and BlackBerry App World are trademarks or registered trademarks of Research in Motion LimitedGoogle App Engine Google Apps Google Checkout Google Data API Google Maps Google Mobile Ads Google Mobile Updater Google Mobile Google Store Google Sync Google Updater Google Voice Google Mail Gmail YouTube Dalvik and Android are trademarks or registered trademarks of Google IncINTERMEC is a registered trademark of Intermec Technologies CorporationWi-Fi is a registered trademark of Wi-Fi AllianceBluetooth is a registered trademark of Bluetooth SIG IncMotorola is a registered trademark of Motorola Trademark Holdings LLCComputop is a registered trademark of Computop Wirtschaftsinformatik GmbHSAP R3 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 countriesBusiness 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 companySybase 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
260 CUSTOMER 2012-08-30
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll 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 varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) 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
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-08-30 CUSTOMER 360
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
460 CUSTOMER 2012-08-30
Document History
CAUTION
Before you start the implementation make sure you have the latest version of this document
You can find the latest version on SAP Service Marketplace at httpservicesapcom
instguides
The following table provides an overview on the most important document changes
Version Date Description
100 2012-08-30 First version
2012-08-30 CUSTOMER 560
Table of Contents
Chapter 1 Overview 9
11 Before You Start 9
12 Types of Support Packages 11
13 Downloading Support Package Stacks 12
Chapter 2 Applying Support Packages to Installable Software Units of SAP
NetWeaver 70 Including Enhancement Package 2 15
21 Application Server ABAP and ABAP-Based Software Components 15
211 Planning 15
212 Preparation 16
213 Updating the Application Server ABAP and ABAP-Based Software
Components 16
214 Post-Installation Steps 19
22 Application Server Java and Java-Based Software Components 19
221 Planning 20
222 Preparation for Applying a Support Package Stack 21
223 Updating the Application Server Java and Java-Based
Components 23
224 Post-Installation Steps 28
23 Parallel Update of Dual-Stack Systems 28
24 Process Integration 29
241 Planning 29
242 Updating Units of Process Integration 31
243 Post-Installation Steps 32
25 Business Intelligence 34
251 Planning 34
252 Preparation 35
253 Updating Units of Business Intelligence 36
26 EP Core 37
261 Planning 37
262 Preparation 37
660 CUSTOMER 2012-08-30
263 Updating EP Core 37
264 Post-Installation Steps for EP Core 37
27 Enterprise Portal 38
271 Planning 38
272 Updating Enterprise Portal 38
273 Post-Installation Steps for Enterprise Portal 39
28 Development Infrastructure 40
281 Planning 40
282 Updating Development Infrastructure 41
29 Mobile Infrastructure 43
291 Planning 43
292 Preparation 43
293 Updating Mobile Infrastructure 43
210 Standalone Engines 44
2101 Search and Classification (TREX) 44
21011 Planning 44
21012 Preparation 44
21013 Updating TREX 45
2102 BI Accelerator 47
21021 Planning 47
21022 Preparation 48
21023 Updating BI Accelerator 48
21024 Post-Installation Steps 49
2103 Gateway 50
2104 SAP Web Dispatcher 50
2105 Other Standalone Engines 50
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2 51
2111 SAP GUI Family 51
2112 Business Explorer (BI Add-On BW Add-On) 51
2113 Other Clients 52
212 SAP Library 52
Chapter A Appendix 55
A1 Determining the Current Component Versions 55
A2 Tools Used During the System Update 56
A21 SAPCAR 56
A22 ABAP Support Package Manager and Add-On Installation Tool 57
A23 Java Support Package Manager 58
2012-08-30 CUSTOMER 760
A3 System Profile Parameters 58
860 CUSTOMER 2012-08-30
1 Overview
This document describes how to install Support Package Stacks (SP Stacks) for SAP NetWeaver 70
including enhancement package 2 You can find all information related to the SP Stacks on SAP Service
Marketplace at httpservicesapcomsp-stacks
11 Before You Start
CAUTION
If you intend to update your system to the latest SP Stack level and plan to upgrade it within the
next 6 months first check the availability of the equivalent SP Stack for the target release The
delivery dates of the equivalent SP Stacks for your source and target release might be several
months apart
Be aware that you cannot upgrade to a target release that does not include the equivalent SP Stack
level
To avoid a deadlock situation we recommend that you check SAP Service Marketplace at
httpservicesapcomsp-stacks SP Stack Information and consider not applying the
latest SP Stack on your source release system
Updated Document Versions
The Support Package Stack Guide is regularly updated on SAP Service Marketplace at http
servicesapcommaintenanceNW70
NOTE
Make sure you have the latest version of the Support Package Stack Guide by checking SAP Service
Marketplace immediately before you start to apply or import Support Packages
SAP Notes
You must read SAP Note 1460321 before you read this document as it may contain corrections and
further information about the Support Package Stack installation
SAP Library
You must inform yourself about enhancements and changes to the Support Package Stack to be applied
from SAP Library under SAP Library SAP NetWeaver Whatrsquos New in SAP NetWeaver 70 ndash Release
Notes You can access the SAP Library in one of the following ways
SAP Help Portal at httphelpsapcomnw702 Application Help SAP Library ltLanguagegt
1 Overview
11 Before You Start
2012-08-30 CUSTOMER 960
NOTE
The SAP Help Portal always provides the up-to-date version of the SAP Library Therefore
we recommend that you use this channel to access the SAP Library
Local installation of the SAP Library from the online documentation DVD
CAUTION
In order to inform yourself about the current Support Package Stack you first have to update
your local installation of the SAP Library to the corresponding SPS level Follow the
instructions in section SAP Library [page 52]
Naming Conventions
In this document the following naming conventions apply
Variables
Variables Description
ltSAPSIDgt
ltsapsidgt
ltSIDgt
SAP system ID
ltINSTDIRgt Installation directory for the SAP system
lthostgt Host name
ltinstance_nogt Instance number of a system instance
ltdatabasegt Name of database
ltsapinst_directorygt Installation directory for the SAP installation tool SAPinst
ltsp_directorygt Temporary directory which the archives of a Support Package are downloaded or copied to
ltOSgt Operating system
ltOS_DIRgt OS-dependent directory consisting of a folder for the platform and a subfolder of your OS versionFor example if you operating system is Sun OS 64bit ltOS_DIRgt stands for UNIXSUNOS64
ltSP_Stackgt Number of Support Package Stack
ltSPgt Support Package level
ltPLgt Support Package patch level
ltRELgt Release number
ltLOCALEgt Language definitionFor example the German locale is _de
ltkrnl_directorygt Kernel directory which the profile parameter DIR_CT_RUN usually refers to
ltsdm_homegt Program file location of the Software Deployment Manager (SDM)
ltSAPGLOBALHOSTgt SAP global host the host where the global directories of an SAP system reside
ltSAPLOCALHOSTgt SAP local host the host where a particular instance of an SAP system is running
1 Overview
11 Before You Start
1060 CUSTOMER 2012-08-30
12 Types of Support Packages
The following table explains the terms used in the correction process as part of the software maintenance
process for SAP NetWeaver
Correction Process Description
Standard correction process
Support Package Stack Description
A Support Package Stack is a set of Support Packages and patches for the respective product version that must be used in the given combination
Version numbersSupport Package Stacks have a release number and a stack number for example SAP NetWeaver 70 Support Package Stack 05
DeliveryThere is no dedicated delivery format for the Support Package Stacks The included Support Package files have their delivery formats and must be applied using the tools as described below
Kernel Patches Version numbers
SAP Kernel patches have a release number and a patch number The patch number is increased with each correction
DeliverySAP Kernel patches are delivered as SAR files They are installed by extracting the SAR files to the kernel directory using SAPCAR Separate SAR files are shipped for the different kernel types depending on UNICODENON-UNICODE and the platform
ABAP Support Packages Description
ABAP Support Packages contain corrections and adjustments for the ABAP-based Software Components of the SAP system
DependenciesIn contrast to Java Support Packages ABAP Support Packages are non-cumulative Therefore ABAP Support Packages must be installed in the correct sequence one after the other You cannot skip any intermediate Support Packages
DeliveryABAP Support Packages are delivered as SAR files They are installed using the Support Package Manager (SPAM)
Java Support Packages Description
Java Support Packages contain corrections for the Java-based Software Components of the SAP system
DependenciesJava Support Packages always contain a full delivery of the Software Components Therefore you only need to apply the latest Support Package to update the software If there are dependencies with other Java Support Packages these are specified in an SAP Note
DeliveryJava Support Packages are delivered as Software Component Archives (SCAs) They are applied using the Java Support Package Manager (JSPM)
1 Overview
12 Types of Support Packages
2012-08-30 CUSTOMER 1160
Correction Process Description
Emergency correction process
SAP Note Correction (ABAP) Description
SAP Note corrections contain single ABAP fixes Delivery
SAP Note corrections are delivered with SAP Notes If required you apply them using the SAP Note Assistant
Java Support Package Patch Description
A Java Support Package patch contains corrections for the Java Software Components Java Support Package patches are created and released on demand A Java Support Package patch corresponds to an SAP Note that describes the same correction
DependenciesA Java Support Package patch always contains a full package of the corresponding Software Component and is applied using JSPM
13 Downloading Support Package Stacks
The Maintenance Optimizer in SAP Solution Manager is the only source from which you can receive
maintenance updates for SAP NetWeaver 70 and higher releases as well as for all applications running
on top of SAP NetWeaver The Maintenance Optimizer supports you in selecting and downloading all
required maintenance files In addition the Maintenance Optimizer generates a stack XML file and
saves it to the EPS inbox directory of SAP Solution Manager
Prerequisites
You have configured the Maintenance Optimizer in SAP Solution Manager as described on SAP Help
Portal at httphelpsapcom SAP Solutions SAP Solution Manager SAP Solution Manager ltReleasegt
ltLanguagegt Change Management Maintenance Optimizer Planning and Monitoring Product Maintenance and
also in section Automatically Calculating Product Maintenance Files
Procedure
To download a Support Package Stack proceed as follows
1 Start SAP Solution Manager using the transaction solution_manager To start the Maintenance
Optimizer choose Operations Change Management Maintenance Optimizer
2 In the Maintenance Optimizer choose the solution for which you want to download SP Stack files
3 Choose Create New Maintenance Transaction
4 Select the product version for which you want to apply a Support Package Stack
The Maintenance Optimizer displays all the systems assigned to the selected product version
5 Select the checkbox for the system that you want to update and choose Continue
6 On the subsequent screen select the Maintenance option and then choose Find Download Files
1 Overview
13 Downloading Support Package Stacks
1260 CUSTOMER 2012-08-30
7 Select the target SP Stack level and the relevant usage types according to the IT scenario to be
updated
8 Choose Find Download Files for the Stack Version
The Maintenance Optimizer displays the product maintenance files in three successive lists
9 Select the required files from the displayed lists
The first list shows all files that are dependent on the type of your operating system and
database
Select the files that correspond to the combination of your operating system and database and
the database-independent files
If your system is distributed on several hosts make sure to select all operating systems used
by the NetWeaver instances You can see all the kernels detected on your system on the Deployed
Components tab page on JSPM user interface (under the SAP KERNEL node) All detected kernels
must be updated to the same version
You get to the second list by choosing Continue This list displays all Support Package files that
are not assigned to the selected Support Package Stack Before you continue with the selection
you must check whether the Support Package files listed here are suitable for your product
maintenance procedure
You get to the third list by choosing Continue The list displays all product maintenance files
that are part of the selected Support Package Stack
Ensure that all files that are assigned to the Support Package Stack are selected here Files that
are not selected will not be included later in the download
10 Choose Continue Use the Download Basket to download the maintenance files
11 Choose Continue once the files have been put in your Download Basket and then Confirm Files in
Download Basket
A dialog window appears and displays all files
12 Confirm the download for all files
13 Open your Download Manager and download the files
NOTE
The stack XML file is generated by the Maintenance Optimizer and automatically saved to
the EPS inbox directory of SAP Solution Manager
More Information
For more information about the Maintenance Optimizer see SAP Support Portal at http
servicesapcomsolman-mopz
1 Overview
13 Downloading Support Package Stacks
2012-08-30 CUSTOMER 1360
This page is left blank for documents that are printed on both sides
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
This chapter describes how to apply Support Packages to installable software units of SAP NetWeaver
70 including enhancement package 2 SAP NetWeaver distinguishes three types of installable software
units
Systems with one or multiple usage types
Standalone engines
Clients
A scenario implementation usually involves several installed software units
RECOMMENDATION
We strongly recommend that you always update all software units belonging to one scenario
together in order to retain a consistent system state Due to the fact that some installable software
units can be commonly shared in different scenarios you must consequently update all scenarios
using the common software units at the same time
21 Application Server ABAP and ABAP-Based Software Components
211 Planning
Procedure
The following components belong to the usage type SAP NetWeaver Application Server ABAP
Software Components of Application Server ABAP
Component to Be Updated SP File Name Tool Used to Apply SP
SAP KERNEL 720 32-64-BIT Non-UNICODEUNICODE SAPEXESAR
SAPEXEDBSAR
JSPMmanually
SAP IGS 700 igsexesar
SAP ABA 702 SAPKA702ltSPgt SPAMSAINT
SAP BASIS 702 SAPKB702ltSPgt
SAP BW 702 SAPKW702ltSPgt
PI_BASIS 702 SAPK-702ltSPgtINPIBASIS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
2012-08-30 CUSTOMER 1560
NOTE
This table contains only software components that belong to the usage type AS ABAP Software
components of other usage types and application units are listed in the corresponding sections
NOTE
SAP delivers intermediate Support Packages for the component SAP BW 702 between two
subsequent SP levels besides the Support Packages delivered along with the Support Package
Stacks Therefore the highest SP level of SAP BW 702 does not necessarily match the target SP
Stack level
CAUTION
When applying a Support Package Stack to a dual-stack system (ABAP+Java) the Java Support
Package Manager (JSPM) will necessarily restart the system several times to make the changes
effective The ABAP part will only be restarted when JSPM is updating the SAP kernel and IGS
212 Preparation
Procedure
Read SAP Note 822379 and all related SAP Notes that the first one refers to
213 Updating the Application Server ABAP and ABAP-Based Software Components
Procedure
Applying Support Packages to SAP NetWeaver Application Server ABAP and ABAP-Based Components
You can update the SAP NetWeaver Application Server ABAP and all ABAP-based software components
running on it using the Support Package Manager (transaction SPAM)
NOTE
If a particular Support Package Stack requires the installation or upgrade of some add-on
components you must use the ABAP Add-on Installation Tool (transaction SAINT) instead of the
Support Package Manager In this case SAINT is able to import both the add-on components and
the related Support Packages of ordinary SAP components
Proceed as follows
1 Log on to the SAP NetWeaver AS system with client 000
2 Start the Support Package Manager by calling transaction SPAM or
start the Add-On Installation Tool by calling transaction SAINT
3 Load the relevant Support Packages or add-on installation packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
1660 CUSTOMER 2012-08-30
4 Define an import queue
5 Perform the import of the defined queue
NOTE
If you have modified SAP objects in your system and these objects are included in the Support
Packages you must perform modification adjustment during the import using the
transactions SPDD (for ABAP Dictionary objects) and SPAU (for Repository objects)
To import the queue you use the standard scenario You can choose between the conventional
import mode and downtime-minimized import mode
Conventional Import Mode
This option comprises the following steps
1 Update the SAP kernel and SAP IGS as described in section Updating SAP Kernel and SAP IGS below
Start the system after the kernel update
2 Import the ABAP Support Packages with the Support Package Manager (SPAM)
Import Mode Downtime-Minimized
This option can be used to reduce system downtime during the update It comprises the following
steps
1 In transaction SPAM enable the downtime-minimized import mode by choosing Extras
Settings then on the Import queue tab page choose Standard and activate the option Import Mode
Downtime-Minimized
2 Import the ABAP Support Packages into the system in an inactive state in the downtime-minimized
mode during system uptime
3 Update the SAP kernel and SAP IGS as described in section Updating SAP Kernel and SAP IGS below
Start the system after the kernel update
4 Complete the ABAP Support Packages import
CAUTION
During this step the system cannot carry out any business transactions (business downtime)
NOTE
In rare cases due to the dependencies of some Support Packages on a particular kernel patch level
the downtime-minimized update does not work In such cases the Support Package Manager
informs you that you must update the SAP kernel before importing ABAP Support Packages You
must proceed with the conventional import procedure
Updating SAP Kernel and SAP IGS
In general the SAP kernel and IGS binaries are located in the global kernel directory DIR_CT_RUN on
the host indicated by the profile parameter SAPGLOBALHOST Once the files in this directory have been
updated to a new patch level a system restart distributes them by means of the program SAPCPE to the
local directories DIR_EXECUTABLE on the hosts where the instances of the SAP system are running
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
2012-08-30 CUSTOMER 1760
CAUTION
The automatic distribution by means of SAPCPE depends on the settings of the profile parameters
DIR_CT_RUN for the global kernel directory and DIR_EXECUTABLE for the local directory of the
executables Before you continue check the instance profiles for the settings of these parameters
in systems that are not installed using SAPinst (for example systems upgraded from older releases
copied or migrated systems)
CAUTION
If your system is a dual-stack system (ABAP+Java) and the ABAP stack has a non-Unicode kernel
be aware that the SCS instance has a Unicode kernel You have to update both kernels (together
with SAP IGS) prior to updating the ABAP and Java Support Package stacks This ensures
compatibility and reduces system downtime
RECOMMENDATION
If you perform an update of a dual-stack system (ABAP+Java) we recommend that prior to
applying ABAP and Java Support Package stacks you use the Single Support Packages option in JSPM
and select for update only the components SAP KERNEL and BC-FES-IGS
For more information about updating a dual-stack system see Parallel Update of Dual-Stack Systems
[page 28]
If you perform an update of an ABAP system the following procedure applies for updating the SAP
kernel and IGS manually
1 Log on as user ltsapsidgtadm to the instance host to be updated
2 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory using
SAPCAR [page 56]
3 Stop the ABAP system that you want to update
NOTE
If the system is running in a high availability (HA) environment make sure that the HA
software does not restart the system automatically during the update
4 Back up the kernel directory ltkrnl_directorygt
5 Copy or move the extracted programs from the temporary directory to the SAP kernel directory
6 Only valid for UNIX |
Execute the following command sequence on UNIX platforms
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
1860 CUSTOMER 2012-08-30
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
7 Restart the SAP system
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS) runs
on a dedicated host You need to perform the kernel update for the ASCS instance manually but
excluding the IGS update because the IGS is not required in an ASCS instance
In rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of such instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances manually Proceed as described
in section Manually Updating Instances with Kernel Directory Located on Separate Hosts below in this document
214 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the ABAP system
22 Application Server Java and Java-Based Software Components
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system which includes
JSPM itself
SAP Kernel and SAP IGS
All Java-based usage types installed in the system
Software Deployment Manager (SDM) - the deployment service of the system
RECOMMENDATION
We strongly recommend that you apply the target Support Package Stack to your system as a
whole This ensures consistency on both the system and the application levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 1960
221 Planning
Procedure
Java Support Package files (SCAs) contain all software objects of the corresponding software
components Thus it is sufficient to apply the Java Support Package files of the intended Support Package
Stack directly to the Java system to be updated It is not necessary to apply the Support Package Stacks
between the start SP Stack level and the target SP Stack level successively
CAUTION
When applying a Support Package Stack to a Java system the Java Support Package Manager (JSPM)
will necessarily restart the system several times to make the changes effective With a dual-stack
system (ABAP+Java) the ABAP part will only be restarted when JSPM is updating the SAP kernel
and IGS
The following components belong to the usage type SAP NetWeaver Application Server Java (AS Java)
Software Components of Application Server Java
Component to Be Updated SP File Name Tool Used to Apply SP
SAP Kernel 720 32-64-BIT UNICODE SAPEXESAR
SAPEXEDBSAR
JSPM
SAP IGS 700 igsexesar
BI META MODEL REPOSITORY 702 BIMMRltSPgt_ltPLgtSCA
J2EE ENGINE CORE TOOLS 702 CORETOOLSltSPgt_ltPLgtSCA
J2EE ENGINE BASE TABLES 702 BASETABLESltSPgt_ltPLgtSCA
BI UDI 702 BIUDIltSPgt_ltPLgtSCA
DI BUILD TOOL 702 SAPBUILDTltSPgt_ltPLgtSCA
SAP CAF 702 CAFltSPgt_ltPLgtSCA
SAP IKS 702 KMKWJIKSltSPgt_ltPLgtSCA
JAVA LOG VIEWER 702 JLOGVIEWltSPgt_ltPLgtSCA
SAP J2EE ENGINE CORE 702 SAPJEECORltSPgt_ltPLgtSCA
SAP JAVA TECH SERVICES 702 SAPJTECHSltSPgt_ltPLgtSCA
SAP TECH S OFFLINE 702 SAPJTECHFltSPgt_ltPLgtSCA
SAP J2EE ENGINE 702 SAPJEEltSPgt_ltPLgtSCA
JAVA SP MANAGER 702 JSPMltSPgt_ltPLgtSCA
ADOBE DOCUMENT SERVICES 702 ADSSAPltSPgt_ltPLgtSCA
UME ADMINISTRATION 702 UMEADMINltSPgt_ltPLgtSCA
LIFECYCLE MGMT TOOLS 702 LMTOOLSltSPgt_ltPLgtSCA
SAP CAF-UM 702 CAFUMltSPgt_ltPLgtSCA
SAP SOFTW DELIV MANAGER 702 SDMKITltSPgt_ltPLgtJAR
SOFTWARE LIFECYCLE MANAGER 702 SWLIFECYCLltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2060 CUSTOMER 2012-08-30
NOTE
This table contains only software components that belong to the usage type AS Java Software
components of other usage types and Java application units are listed in the corresponding
sections
NOTE
As of Support Package 09 you can update your system with SAP Kernel 720 instead of SAP Kernel
701
222 Preparation for Applying a Support Package Stack
Procedure
1 Download the Support Package Stack with all usage types to be updated and the stack definition
XML file as described in Downloading Support Package Stacks [page 12]
NOTE
You can find the activated usage types in an existing Java system on the Deployed Components tab
page on the JSPM user interface
NOTE
You do not need to download the SP Stacks between the source SP Stack level and target SP
Stack level By default the target SP Stack level is the latest available SP Stack
2 Make sure the following requirements are met prior to applying the Support Package Stack
You have familiarized yourself with SAP Note 891983 before you start the Java Support Package
Manager
The system to be updated is fully functional
The Support Package Stack you want to apply and the corresponding stack definition XML
file are available in the EPS inbox directory usrsaptransEPSin By default this location
can be also referred to as ldquoJSPM inboxrdquo
The SAP NetWeaver Application Server Java (AS Java) and the database have been backed up
You have not deleted renamed or created any directories and files in the following directories
and their subdirectories usrsapltSAPSIDgtSYSexe and usrsapltSAPSIDgtSYS
profile
Otherwise JSPM cannot detect the kernel and the system profiles and cannot be started If a
backup of the kernel and the system profiles has been required it has been created in a different
directory
The ltsapsidgtadm user has Read permissions for the EPS inbox directory usrsaptransEPS
in
If your database is SAP MaxDB the overwrite mode for the log area has been activated
The database and the SDM repository have been synchronized
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2160
For more information see the online documentation for JSPM on SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70 Library
(including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library Administrators Guide
Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems AS Java
(Application Server for Java) Software Logistics Software Maintenance Java Support Package Manager
Then choose Troubleshooting JSPM Does Not Update the Versions of the Deployed Components
There is enough disk space
For more information see SAP Note 891895
Your current SAPCAR tool is able to extract the Support Packages for the SAP kernel and
other OS level binaries delivered as SAR files
RECOMMENDATION
You can download the latest version of SAPCAR from SAP Service Marketplace at
httpservicesapcompatches Entry by Application Group Additional Components
SAPCAR
Put the downloaded version in the same directory in the JSPM inbox in which the kernel
SAR files reside so that JSPM can use this version for extracting the SAR files
3 Only valid for Linux |
For RHEL 4 and SLES 9 you need to install additional operating system packages For more
information see SAP Note 1021236End of Linux |
4 Only valid for Windows |
For Windows you need to install additional operating system packages For more information see
SAP Note 684106End of Windows |
5 To prevent the Software Deployment Manager (SDM) from temporarily exceeding the available
disk space during the update process you can change the file transfer directory of SDM in a system
of SPS09 or higher using the following command sequence
Only valid for Windows |
cd ltsdm_homegt
StopServerbat
sdmbat jstartup mode=standalone
sdmbat filetransferdir dir=ltnew_dirgt
sdmbat jstartup mode=integrated
StartServerbat
End of Windows |
Only valid for IBM i5OSUNIX |
cd ltsdm_homegt
StopServersh
sdmsh jstartup mode=standalone
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2260 CUSTOMER 2012-08-30
sdmsh filetransferdir dir=ltnew_dirgt
sdmsh jstartup mode=integrated
StartServersh
End of IBM i5OSUNIX |
6 To prevent deployment errors during the update process proceed as follows
1 Log on to the Central Instance host
2 Start the ConfigTool and in the navigation area choose Cluster-data Global server configuration
Managers ServiceManager
3 In the Global properties panel set the Custom value of the EventTimeout property to 120
4 Choose Save
5 Restart the Central Instance
7 Check whether the used JDK version and the Java VM settings of the Java runtime system comply
with the requirements in SAP Note 723909 Update the JDK and adjust the settings if necessary
NOTE
An update of the used JDK version possibly changes the JVM path In this case you must
make the new path available to all Dialog Instances of the J2EE engine by implementing option
1 of SAP Note 718901
8 Make sure that the J2EE administrator password stored in the secure store for offline usage is
identical with the one stored in the User Management Engine (UME) You can change the password
in the secure store as described in SAP Note 870445
9 If you are running a high availability system on Windows you might need to prepare your system
as described in the online documentation for JSPM see section Preparing Systems That Run in High
Availability Environment
223 Updating the Application Server Java and Java-Based Components
Procedure
Applying a Support Package Stack to SAP NetWeaver Application Server Java and Java-Based Components
NOTE
The JSPM GUI might not work properly on some UNIX systems For more information and the
solution see SAP Note 1013976
1 Log on as user ltsapsidgtadm to the Central Instance host
NOTE
If your operating system is IBM i log on as user ltSIDgtADM or ltSIDgtOFR
2 Close the SAP Management Console (SAP MMC) and the SDM remote GUI client
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2360
3 For UNIX and Windows To start the JSPM navigate to the directory ltINSTDIRgtltSIDgt
ltCentral_Instance_Namegtj2eeJSPM and run the go script file
NOTE
If your system is running on IBM i to start the JSPM proceed as follows
1 To prevent JSPM from automatically starting its GUI in the file usrsapltSIDgt
ltCentral_Instance_Namegtj2eeJSPMparamjspm_configtxt change the
property dialogSDTServerConnectionSDTGuilaunch from true to false
2 On the IBM i host run the go script file using the following command
QSH CMD(usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPMgo)
3 In the mounted directory usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPM run
the StartGui script file The JSPM GUI appears
4 In the Host field enter the target IBM i host
NOTE
Depending on the system type ltCentral_Instance_Namegt has the following syntax
Standalone Java system JCltinstance_nogt
Add-On system DVEBMGSltinstance_nogt
4 Enter your SDM password to log on to the SDM
5 On the Deployment tab page select the Java Support Package Manager option and update the software
component sapcomJSPM to the target SPS level
6 Restart the JSPM and log on with the SDM password
RECOMMENDATION
We strongly recommend that you use the Support and Enhancement Package Stack option when
applying a Support Package Stack Other options can lead to unintended consistency issues
NOTE
If you need to include the latest patches for a particular component during the update process
with the Support and Enhancement Package Stack option stop the JSPM after restart and apply SAP
Note 1080821 Then start the JSPM again
7 On the Deployment tab page select the Support and Enhancement Package Stack option and choose Next
The Support Package Stacks that are available for deployment in the global EPS inbox directory
are displayed
8 In the Target SP Stack Level dropdown box select the Support Package Stack to be applied and choose
Next
In this step JSPM performs various status validations and displays the result of each software
component included in the stack definition XML file on the subsequent screen which includes
the following possible statuses
OK Indicates that the SPS level of the corresponding software component is applicable
WARNING We recommend that you view the details about the component by choosing Show
Details
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2460 CUSTOMER 2012-08-30
This status may indicate that the corresponding software component comprises custom
modifications in an NWDI-controlled system
If your system is used for NWDI development and it is either a DEV or a CONS system
you will be informed that JSPM will not deploy the modified software components but
only transport them to the CMS transport directory JSPM will deploy only the software
components that are not modified
If your system is not used for NWDI development or if your system is used for NWDI
development and it is either a TEST or a PROD system you will be informed that JSPM
has found newer versions of modified software components and will automatically replace
the original versions with the newer versions JSPM will deploy all software components
that are not modified together with the replaced versions of the modified software
components
CAUTION
You may get a warning telling you that there are patches installed in your system
containing fixes which might not be included in the target SP Stack This is possible if
you have applied patches of the start SP Stack level that were delivered later than the
target SP Stack delivery date In order not to lose these fixes you need to download and
apply the corresponding patches of the target SP Stack level
If you are performing an update from SAP NetWeaver 70 including enhancement
package 1 SPS00 and you have not applied any patches for the software component with
status WARNING before the update then you can ignore warnings such as the following
example
The new version of the development component sapcomcomsapnetweaver
bcrfmoni is 70100200806121227180000 and is lower than the already
deployed version 70100200807090143420000
REVISE Indicates inconsistencies with the corresponding software component
The deployment cannot be performed until all problems have been resolved You can view
the problems by choosing Show Details
9 If the status of the selected SP Stack is OK or WARNING you can start the system update by choosing
Start JSPM then changes the status to SCHEDULED
If the SP Stack to be applied includes a kernel update and the current kernel is not already of the
corresponding patch level JSPM arranges the kernel update as the very first Support Package to
be applied JSPM updates the kernel binaries of all instances (including Dialog Instances and SCS
instances in a HA environment) whose kernel directories DIR_CT_RUN effectively reside on the host
indicated by the profile parameter SAPGLOBALHOST
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2560
CAUTION
Kernel binaries of instances whose kernel directories DIR_CT_RUN are not effectively linked
to the host SAPGLOBALHOST must be updated individually as described in section Manually
Updating Instances with Kernel Directory Located on Separate Hosts below
The kernel update (includes update of SAP Kernel and SAP IGS) using JSPM consists of the following
steps
1 JSPM stops the Central Instance automatically and prompts you to stop the remote SCS and
Dialog Instances manually
2 After you have stopped all the instances choose the Next button in the dialog box
The kernel update starts
NOTE
If the system is running in a high availability environment make sure that the HA
software does not restart the instance automatically during the update
NOTE
If kernel binaries of the SCS instance need to be updated manually (see Manually Updating
Instances with Kernel Directory Located on Separate Hosts below) you must perform this at the
time when JSPM is updating the kernel binaries of the Central Instance In any case the
SCS kernel must be up-to-date before the next restart
When the kernel update is finished a dialog box appears in which you are prompted to restart
the SCS instance manually
3 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries
before you can proceed with the next step For more information see Adjusting the Ownership and
Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
4 Choose Next in the dialog box when the SCS instance is running again
After the kernel update JSPM restarts the system for further deployment of the remaining Support
Packages in the stack
RECOMMENDATION
If you need to update the kernel binaries of any Dialog Instances manually (see Manually
Updating Instances with Kernel Directory Located on Separate Hosts below) perform the update when
JSPM is updating the remaining Support Packages in the stack in order to save time
The deployment of each Support Package can end with one of the following statuses
DEPLOYED
The Support Package has been successfully deployed
DEPLOYED WITH WARNING
The Support Package has been deployed but it possibly may not work properly with other
deployed components
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2660 CUSTOMER 2012-08-30
You can view the details by choosing Show Details or examining the log files You can also view
the details about the component by choosing the Deployed Components tab page
ERROR
An error has occurred during the deployment You can view the details by choosing Show
Details or examining the log files
You must correct the error to be able to continue with the SP Stack update
You can proceed as described for a deployment that finished with status DEPLOYED WITH
WARNING
If the error correction does not change the contents in the JSPM inbox you can continue
the deployment by choosing Resume
If the error correction changes the contents in the JSPM inbox you can choose New
Deployment to redeploy the SP Stack
NOT DEPLOYED
JSPM has not attempted to deploy the software component for certain reasons
If your system is not used for NWDI development you can proceed as described for a
deployment that finished with status ERROR
If your system is used for NWDI development and it is either a DEV or a CONS system
the status of the modified software components is always NOT DEPLOYED JSPM has
transported the software components of the Support Package Stack both modified and
not modified to the CMS transport directory The deployment of the modified software
components is handled by NWDI
Manually Updating Instances with Kernel Directory Located on Separate Hosts
JSPM performs kernel update for all instances (including Dialog Instances and SCS instances in a HA
environment) whose kernel directories DIR_CT_RUN effectively reside on the host indicated by the profile
parameter SAPGLOBALHOST (by using folder sharing on Windows or file system mounting on UNIX) In
rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of those sort of instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances individually
To update the kernel of an instance manually proceed as follows
1 Log on as user ltsapsidgtadm to the host of the instance to be updated
2 Back up the kernel directory which is specified by the profile parameter DIR_CT_RUN
3 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory with
SAPCAR [page 56]
4 Stop the instance being updated
NOTE
If the system is running in a HA environment make sure that the HA software does not
restart the instance automatically during the update
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2760
5 Copy or move the extracted programs from the temporary directory to the local kernel directory
6 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries as
described in section Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
7 Restart the instance after JSPM has finished the deployment of all packages on the Central Instance
Only valid for UNIX |
Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms
On UNIX platforms you must adjust the ownership and execution permissions of the kernel binaries
after the update regardless whether you performed the update manually or by using JSPM because
both update procedures are performed with the ltsapsidgtadm user Enter the following command
sequence
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
224 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the Java system
23 Parallel Update of Dual-Stack Systems
If you perform an update of a dual-stack system (ABAP+Java) we recommend that you follow the
procedure described below The procedure has been validated to update the ABAP stack and the Java
stack of a NetWeaver system in parallel thus reducing the overall system downtime by half
Procedure
1 Before applying ABAP and Java Support Packages use the Single Support Packages option in JSPM and
select for update only the components SAP KERNEL and BC-FES-IGS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
23 Parallel Update of Dual-Stack Systems
2860 CUSTOMER 2012-08-30
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS)
runs on a dedicated host In this case JSPM does not support update of kernel binaries and
you need to update them manually Perform the update manually as described under Updating
SAP Kernel and SAP IGS in section Updating the Application Server ABAP and ABAP-Based Software
Components [page 16]
2 Import the Support Packages for the component SAP_BASIS into the ABAP stack using the ABAP
Support Package Manager (SPAM)
3 Import the remaining ABAP Support Packages with SPAM and in parallel apply the Java Support
Package Stack with JSPM
Proceed as described in Updating the Application Server ABAP and ABAP-Based Software Components [page
16] and Updating the Application Server Java and Java-Based Software Components [page 23]
24 Process Integration
241 Planning
Procedure
This section covers all the units of Process Integration that should be updated Particularly the following
units must always have the same Support Package level (the patch level can be different)
Integration Server
XI Adapter Engine
Partner Connectivity Kit
System with the Usage Type Process Integration
Software components of Integration Server
Components to Be Updated SP File Name Tool Used to Apply SP
Java stack
XI TOOLS 702 SAPXITOOLltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
ABAP stack
XI CONTENT SAP_BASIS 702 SAPBASISltSPgt_ltPLgtZIP File upload
XI CONTENT SAP_ABA 702 SAPABAltSPgt_ltPLgtZIP
SAP NetWeaver Application Server ABAP (see table Software components of Application Server ABAP [page 15])Note that update of the following software components of the ABAP system is not required SAP ABA 702 SAP BW 702 PI_BASIS 702
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 2960
J2EE Adapter Engine
If your implemented scenario includes a J2EE Adapter Engine then it must always be of the same
Support Package level as the Integration Server
Components of the J2EE Adapter Engine
Component to Be Updated SP File NameTool Used to Apply SP
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
J2SE Adapter Engine
The installation of the J2SE Adapter Engine depends on the implemented scenario
Components of the J2SE Adapter Engine
Component to Be Updated SP File Name Tool Used to Apply SP
XI CONNECTIVITY SE 702 SAPXICONSltSPgt_ltPLgtSCA ZIP tool (for example WinZip)
Partner Connectivity Kit
If your implemented scenario includes a Partner Connectivity Kit (PCK) then it must always be of the
same Support Package level as the Integration Server
Software components of Partner Connectivity Kit
Components to Be Updated SP File NameTool Used to Apply SP
XI PCK 702 SAPXIPCKltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of the Application Server Java [page 20])
System Landscape Directory (SLD)
The System Landscape Directory is required for the PI operations Although updating the SLD is not
necessarily required it is advisable to update the SLD server and the SAP Master Data Content within
it from time to time The update of the SLD includes
1 The system where the SLD is running
2 The SAP Master Data Content within this SLD
SAP GUI
See table Compatible SAP GUI Versions [page 51]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3060 CUSTOMER 2012-08-30
242 Updating Units of Process Integration
Procedure
Before you start the update perform the following steps
In the Runtime Workbench use Communication Channel Monitoring to stop all sender channels
for all adapter types on all your Adapter Engines
On the Integration Server use transaction SMQR and deregister all qRFC queues
System with the Usage Type Process Integration
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the XI instance is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system where the XI instance is running
For more information see Application Server Java and Java-Based Software Components [page 19]
System Landscape Directory (Optional)
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the SLD is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the entire Support Package Stack to the system where the SLD is running
For more information see Application Server Java and Java-Based Software Components [page 19]
J2EE Adapter Engine
Apply the Support Package Stack to the system where the Adapter Engine is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Partner Connectivity Kit
Apply the Support Package Stack to the system where the PCK is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Front End GUIs
Update the SAP GUI components if necessary
For more information see SAP GUI Family [page 51]
ABAP 700 Business System (Optional)
Apply the Support Packages for SAP NetWeaver Application Server ABAP (including SAP kernel and
the Support Package for SAP BASIS 700)
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 640 Business System (Optional)
Apply the Support Packages for SAP Web Application Server ABAP 640 (including SAP kernel and the
Support Package for SAP BASIS 640)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3160
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 620 Business System (Optional)
1 Update the SAP Kernel 620
2 Import the released Basis Support Packages for SAP Web AS 620 as well as the most recent Add-
On Support Package for APPINT 200_620 in the order described in SAP Note 439915
J2SE Adapter Engine (Optional)
NOTE
The XI Adapter Engine (J2SE) and all its adapters are provided for compatibility reasons only and
are not developed any further You have to use the XI Adapter Engine running on SAP NetWeaver
AS Java For more information see the Master Guide ndash SAP NetWeaver 70 available on SAP Service
Marketplace at httpservicesapcominstallNW70 Planning
1 Extract the SAPXICONSltSPgt_ltPLgtSCA (XI Connectivity SE 700) archive (ZIP format) to a temporary
directory
2 Save the old configuration files as described in the document Adapterpdf in directory
lttemp_directorygttech_adapterAdministrationDocumentation
3 Unpack the ZIP archive TechnicalAdapterssda to the installation directory of the XI Adapter
Engine (J2SE)
4 Restore the configuration files with restore_configuration
243 Post-Installation Steps
Procedure
Communication Channels and Queues
Restart all stopped sender channels and register all deregistered qRFC queues
XI Content
In the system with usage type PI import the XI content from the archives SAPBASISltSPgt_ltPLgtZIP
and SAPABAltSPgt_ltPLgtZIP as follows
1 Unpack the archives using a ZIP tool of your choice
2 Copy the corresponding export files (with file extension tpz) to the import directory ltINSTDIRgt
ltSAPSIDgtSYSglobalxirepository_serverimport
3 Start the Integration Builder (transaction SXMB_IFR)
4 Enter the Integration Repository by choosing Repository (Design)
5 Choose Tools Import design objects
6 Import the tpz files containing the XI content
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3260 CUSTOMER 2012-08-30
NOTE
For more information see SAP Note 836200
Role Generation on the Integration Server
On the Integration Server execute transaction SUPC (mass generation of roles) for all SAP_XI roles in
each of your clients to regenerate possibly changed roles
NOTE
Do not forget to make a user comparison for regenerated roles afterwards
Partner Connectivity Kit (Optional)
Perform the post-installation steps for PCK as described in SAP Note 746328
SAP Master Data within the SLD (Optional)
In the system where your SLD is running import the latest SLD content as described in SAP Note
669669
Receiver-Based EOIO Serialization in J2EE Adapter Engine (Optional)
The J2EE Adapter Engine can be switched to receiver-based EOIO serialization The switch can be
triggered on demand and is executed asynchronously It includes a database migration step during
which all EOIO processing in the Adapter Engine is disabled See SAP Note 973894 for details about how
to start the EOIO serialization migration
Service Metering (Optional)
Service metering gathers information about a service caller transfers it to the service provider and
counts on the service provisioning side how many times a service is called and by which service caller
Service metering is performed for the XI message protocol and the WS message protocol Service
metering is automatically enabled after applying a Support Package Stack By default only non-sensitive
data is transmitted to internal or external service providers in a compatible way
Service metering can be configured in PI in the Integration Engine on sender-side and in the Integration
Directory
Service metering can be configured in AS ABAP in transaction SOAMANAGER
Only if the service provider is allowed to receive more detailed information about the service caller set
the metering level to higher than the default
For more information see SAP Note 1239428
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3360
25 Business Intelligence
251 Planning
Procedure
Business Intelligence includes one or many of the following units that must be updated depending on
your implemented scenarios The usage types Business Intelligence (BI) and Business Intelligence Java
Components (BI-Java) must always have the same Support Package level
Business Intelligence
Software Components of Business Intelligence
Component to Be Updated SP File Name Tool Used to Apply SP
BI CONT ADDON 70x SAPK-70ltxgtltSPgtINBICONT SAINT
SAP NetWeaver Application Server ABAP (see table Software Components of Application Server ABAP [page 15])
NOTE
For information about the dependencies applying to BI Content Support Packages see SAP Note
653814 BI CONT 703 Support Packages are not part of the NetWeaver SP Stacks Updates can be
performed when applicable Alternatively BI CONT 704 Support Packages can be imported See
the BI Content release strategy in SAP Note 153967
Business Intelligence Java Components
BI Java Components
Component to Be Updated SP File NameTool Used to Apply SP
BI REPORTING AND PLANNING 702 BIREPPLANltSPgt_ltPLgtSCA JSPM
BI WEBDYNPRO ALV 702 BIWDALVltSPgt_ltPLgtSCA
BI INFORM BROADCASTING 702 BIIBCltSPgt_ltPLgtSCA
BI WEB APPLICATIONS 702 BIWEBAPPltSPgt_ltPLgtSCA
BI BASE SERVICES 702 BIBASESltSPgt_ltPLgtSCA
VISUAL COMPOSER BI KITS 702 VCKITBIltSPgt_ltPLgtSCA
Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
BI Precalculation Service
Components of the BI Precalculation Service
Component to Be Updated SP File Name Tool Used to Apply SP
BI Pre-calculation Service 700 xPreCalServerltSPgt_ltPLgtexe Installer
Search and Classification (TREX)
See table TREX Component [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3460 CUSTOMER 2012-08-30
BI Accelerator
The BI Accelerator is based on the TREX technology It is a special Linux 64-bit version of SAP NetWeaver
70 Search and Classification (TREX) which is delivered on preconfigured hardware
NOTE
You cannot use a TREX installation based on 32-bit architecture that is configured for searching
in metadata and documents for the BI Accelerator And vice versa a BI Accelerator box cannot
be used for searching in metadata and documents
If you want to use the search functionality as well as the BI Accelerator you require two separate
installations For more information see BI Accelerator [page 47]
Clients
Depending on your implemented scenarios you have to update SAP GUI Components and Business
Explorer (BI Add-OnBW Add-On)
NOTE
See SAP Note 889314 to determine when to use the BI Add-On and the BW Add-On
NOTE
As SAP GUI 640 is no longer supported BI Frontend Support Package 1800 resp patch 1801 is the
last Support Package resp patch based on SAP GUI 640 For more information see SAP Note
1231292 (Frontend Add-in Strategy 640710 GUI Version)
For more information about the new release strategy for the BI Frontend see SAP Note 1231363
(Changed Delivery Strategy for BI Frontend)
252 Preparation
Procedure
For the Support Packages of the most important Business Intelligence units so called SAPBINews
(SAPBWNews) Notes are created Read these Notes before updating Business Intelligence For SAP
NetWeaver 70 including enhancement package 2 SPS 12 these are the following
Business Intelligence ABAP SAP Note 1680996
Business Intelligence Java Components SAP Note 1726461
BI 70 Frontend Add-On for SAP GUI 710 SAP Note 1413032
BI 70 Frontend Add-On for SAP GUI 720 SAP Note 1630112
BI 70 Frontend Add-On for SAP GUI 730 SAP Note 1726739
For more information about BI Support Packages see SAP Community Network at http
scnsapcomcommunitydata-warehousingnetweaver-bw Related Resources SAP NW BW Support
Packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
2012-08-30 CUSTOMER 3560
253 Updating Units of Business Intelligence
Procedure
Business Intelligence
1 Update the SAP NetWeaver Application Server ABAP (with BI CONT 70x if necessary) with the
appropriate Support Packages
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
NOTE
When applying the component SAP BW 702 some generation errors might occur When
you start importing the BI Support Packages in transaction SPAM choose the menu path
Extras Ignore generation errors For more information see SAP Note 114134
2 Apply the Support Package Stack to the system with the usage type BI-Java
For more information see Application Server Java and Java-Based Software Components [page 19]
3 Update the BI Precalculation Service that is used in your scenario
4 Update the standalone engine Search and Classification (TREX) that is used in your scenario For more
information see Standalone Engine Search and Classification (TREX) [page 44]
NOTE
You have to update TREX to the newest version if you use search capabilities within Business
Intelligence
5 Update the BI Accelerator to the newest available version For more information see BI
Accelerator [page 47]
6 Update the SAP GUI and Business Explorer (BI Add-On BW Add-On) on all remote client hosts
that are involved in the scenario
For more information see SAP GUI Family [page 51] and Business Explorer (BI Add-On BW Add-On)
[page 51]
BI Precalculation Service
1 Log on to the host as a user with administration rights
2 Install the Support Package of the BI Precalculation Service by executing the
xPreCalServerexe file
The welcome screen of the BI Precalculation Server setup wizard appears
The setup now checks the system for the prerequisites
3 Choose the option Update for updating the BI Precalculation service to the current patch level and
then Finish
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3660 CUSTOMER 2012-08-30
26 EP Core
261 Planning
Procedure
The following installable software units must be updated
EP Core
Software Components of EP Core
Component to Be Updated SP File Name Tool Used to Apply SP
PORTAL CORE SERVICES 702 EPBCltSPgt_ltPLgtSCA JSPM
PORTAL FRAMEWORK 702 EPBC2ltSPgt_ltPLgtSCA
PORTAL 702 EPPSERVltSPgt_ltPLgtSCA
PORTAL WEB DYNPRO 702 EPWDCltSPgt_ltPLgtSCA
UWL COLL PROCESS ENGINE 702 UWLJWFltSPgt_ltPLgtSCA
CAF EU 702 SAPEUltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
262 Preparation
Procedure
Backing Up the Portal Runtime Configuration
If you have made changes to the standard Portal Runtime configuration you have to make a backup
of the configuration before the update process For more information see SAP Note 1064468
263 Updating EP Core
Procedure
Apply the Support Package Stack to a system with usage type EP Core
For more information see Application Server Java and Java-Based Software Components [page 19]
264 Post-Installation Steps for EP Core
Procedure
Restoring the Portal Runtime Configuration
To make your changes to the standard Portal Runtime Configuration effective you have to restore
the backup of the configuration done before the update process For more information see SAP Note
1064468
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
26 EP Core
2012-08-30 CUSTOMER 3760
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
Crossgate mgic EDDY B2B 360deg and B2B 360deg Services are registered trademarks of Crossgate AG in Germany and other countries Crossgate is an SAP companyAll 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 varyThese materials are subject to change without notice These materials are provided by SAP AG and its affiliated companies (ldquoSAP Grouprdquo) 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
DisclaimerSome components of this product are based on Javatrade Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited as is any decompilation of these componentsAny Javatrade Source Code delivered with this product is only to be used by SAPrsquos Support Services and may not be modified or altered in any way
Documentation in the SAP Service MarketplaceYou can find this document at the following address httpservicesapcominstguides
2012-08-30 CUSTOMER 360
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
460 CUSTOMER 2012-08-30
Document History
CAUTION
Before you start the implementation make sure you have the latest version of this document
You can find the latest version on SAP Service Marketplace at httpservicesapcom
instguides
The following table provides an overview on the most important document changes
Version Date Description
100 2012-08-30 First version
2012-08-30 CUSTOMER 560
Table of Contents
Chapter 1 Overview 9
11 Before You Start 9
12 Types of Support Packages 11
13 Downloading Support Package Stacks 12
Chapter 2 Applying Support Packages to Installable Software Units of SAP
NetWeaver 70 Including Enhancement Package 2 15
21 Application Server ABAP and ABAP-Based Software Components 15
211 Planning 15
212 Preparation 16
213 Updating the Application Server ABAP and ABAP-Based Software
Components 16
214 Post-Installation Steps 19
22 Application Server Java and Java-Based Software Components 19
221 Planning 20
222 Preparation for Applying a Support Package Stack 21
223 Updating the Application Server Java and Java-Based
Components 23
224 Post-Installation Steps 28
23 Parallel Update of Dual-Stack Systems 28
24 Process Integration 29
241 Planning 29
242 Updating Units of Process Integration 31
243 Post-Installation Steps 32
25 Business Intelligence 34
251 Planning 34
252 Preparation 35
253 Updating Units of Business Intelligence 36
26 EP Core 37
261 Planning 37
262 Preparation 37
660 CUSTOMER 2012-08-30
263 Updating EP Core 37
264 Post-Installation Steps for EP Core 37
27 Enterprise Portal 38
271 Planning 38
272 Updating Enterprise Portal 38
273 Post-Installation Steps for Enterprise Portal 39
28 Development Infrastructure 40
281 Planning 40
282 Updating Development Infrastructure 41
29 Mobile Infrastructure 43
291 Planning 43
292 Preparation 43
293 Updating Mobile Infrastructure 43
210 Standalone Engines 44
2101 Search and Classification (TREX) 44
21011 Planning 44
21012 Preparation 44
21013 Updating TREX 45
2102 BI Accelerator 47
21021 Planning 47
21022 Preparation 48
21023 Updating BI Accelerator 48
21024 Post-Installation Steps 49
2103 Gateway 50
2104 SAP Web Dispatcher 50
2105 Other Standalone Engines 50
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2 51
2111 SAP GUI Family 51
2112 Business Explorer (BI Add-On BW Add-On) 51
2113 Other Clients 52
212 SAP Library 52
Chapter A Appendix 55
A1 Determining the Current Component Versions 55
A2 Tools Used During the System Update 56
A21 SAPCAR 56
A22 ABAP Support Package Manager and Add-On Installation Tool 57
A23 Java Support Package Manager 58
2012-08-30 CUSTOMER 760
A3 System Profile Parameters 58
860 CUSTOMER 2012-08-30
1 Overview
This document describes how to install Support Package Stacks (SP Stacks) for SAP NetWeaver 70
including enhancement package 2 You can find all information related to the SP Stacks on SAP Service
Marketplace at httpservicesapcomsp-stacks
11 Before You Start
CAUTION
If you intend to update your system to the latest SP Stack level and plan to upgrade it within the
next 6 months first check the availability of the equivalent SP Stack for the target release The
delivery dates of the equivalent SP Stacks for your source and target release might be several
months apart
Be aware that you cannot upgrade to a target release that does not include the equivalent SP Stack
level
To avoid a deadlock situation we recommend that you check SAP Service Marketplace at
httpservicesapcomsp-stacks SP Stack Information and consider not applying the
latest SP Stack on your source release system
Updated Document Versions
The Support Package Stack Guide is regularly updated on SAP Service Marketplace at http
servicesapcommaintenanceNW70
NOTE
Make sure you have the latest version of the Support Package Stack Guide by checking SAP Service
Marketplace immediately before you start to apply or import Support Packages
SAP Notes
You must read SAP Note 1460321 before you read this document as it may contain corrections and
further information about the Support Package Stack installation
SAP Library
You must inform yourself about enhancements and changes to the Support Package Stack to be applied
from SAP Library under SAP Library SAP NetWeaver Whatrsquos New in SAP NetWeaver 70 ndash Release
Notes You can access the SAP Library in one of the following ways
SAP Help Portal at httphelpsapcomnw702 Application Help SAP Library ltLanguagegt
1 Overview
11 Before You Start
2012-08-30 CUSTOMER 960
NOTE
The SAP Help Portal always provides the up-to-date version of the SAP Library Therefore
we recommend that you use this channel to access the SAP Library
Local installation of the SAP Library from the online documentation DVD
CAUTION
In order to inform yourself about the current Support Package Stack you first have to update
your local installation of the SAP Library to the corresponding SPS level Follow the
instructions in section SAP Library [page 52]
Naming Conventions
In this document the following naming conventions apply
Variables
Variables Description
ltSAPSIDgt
ltsapsidgt
ltSIDgt
SAP system ID
ltINSTDIRgt Installation directory for the SAP system
lthostgt Host name
ltinstance_nogt Instance number of a system instance
ltdatabasegt Name of database
ltsapinst_directorygt Installation directory for the SAP installation tool SAPinst
ltsp_directorygt Temporary directory which the archives of a Support Package are downloaded or copied to
ltOSgt Operating system
ltOS_DIRgt OS-dependent directory consisting of a folder for the platform and a subfolder of your OS versionFor example if you operating system is Sun OS 64bit ltOS_DIRgt stands for UNIXSUNOS64
ltSP_Stackgt Number of Support Package Stack
ltSPgt Support Package level
ltPLgt Support Package patch level
ltRELgt Release number
ltLOCALEgt Language definitionFor example the German locale is _de
ltkrnl_directorygt Kernel directory which the profile parameter DIR_CT_RUN usually refers to
ltsdm_homegt Program file location of the Software Deployment Manager (SDM)
ltSAPGLOBALHOSTgt SAP global host the host where the global directories of an SAP system reside
ltSAPLOCALHOSTgt SAP local host the host where a particular instance of an SAP system is running
1 Overview
11 Before You Start
1060 CUSTOMER 2012-08-30
12 Types of Support Packages
The following table explains the terms used in the correction process as part of the software maintenance
process for SAP NetWeaver
Correction Process Description
Standard correction process
Support Package Stack Description
A Support Package Stack is a set of Support Packages and patches for the respective product version that must be used in the given combination
Version numbersSupport Package Stacks have a release number and a stack number for example SAP NetWeaver 70 Support Package Stack 05
DeliveryThere is no dedicated delivery format for the Support Package Stacks The included Support Package files have their delivery formats and must be applied using the tools as described below
Kernel Patches Version numbers
SAP Kernel patches have a release number and a patch number The patch number is increased with each correction
DeliverySAP Kernel patches are delivered as SAR files They are installed by extracting the SAR files to the kernel directory using SAPCAR Separate SAR files are shipped for the different kernel types depending on UNICODENON-UNICODE and the platform
ABAP Support Packages Description
ABAP Support Packages contain corrections and adjustments for the ABAP-based Software Components of the SAP system
DependenciesIn contrast to Java Support Packages ABAP Support Packages are non-cumulative Therefore ABAP Support Packages must be installed in the correct sequence one after the other You cannot skip any intermediate Support Packages
DeliveryABAP Support Packages are delivered as SAR files They are installed using the Support Package Manager (SPAM)
Java Support Packages Description
Java Support Packages contain corrections for the Java-based Software Components of the SAP system
DependenciesJava Support Packages always contain a full delivery of the Software Components Therefore you only need to apply the latest Support Package to update the software If there are dependencies with other Java Support Packages these are specified in an SAP Note
DeliveryJava Support Packages are delivered as Software Component Archives (SCAs) They are applied using the Java Support Package Manager (JSPM)
1 Overview
12 Types of Support Packages
2012-08-30 CUSTOMER 1160
Correction Process Description
Emergency correction process
SAP Note Correction (ABAP) Description
SAP Note corrections contain single ABAP fixes Delivery
SAP Note corrections are delivered with SAP Notes If required you apply them using the SAP Note Assistant
Java Support Package Patch Description
A Java Support Package patch contains corrections for the Java Software Components Java Support Package patches are created and released on demand A Java Support Package patch corresponds to an SAP Note that describes the same correction
DependenciesA Java Support Package patch always contains a full package of the corresponding Software Component and is applied using JSPM
13 Downloading Support Package Stacks
The Maintenance Optimizer in SAP Solution Manager is the only source from which you can receive
maintenance updates for SAP NetWeaver 70 and higher releases as well as for all applications running
on top of SAP NetWeaver The Maintenance Optimizer supports you in selecting and downloading all
required maintenance files In addition the Maintenance Optimizer generates a stack XML file and
saves it to the EPS inbox directory of SAP Solution Manager
Prerequisites
You have configured the Maintenance Optimizer in SAP Solution Manager as described on SAP Help
Portal at httphelpsapcom SAP Solutions SAP Solution Manager SAP Solution Manager ltReleasegt
ltLanguagegt Change Management Maintenance Optimizer Planning and Monitoring Product Maintenance and
also in section Automatically Calculating Product Maintenance Files
Procedure
To download a Support Package Stack proceed as follows
1 Start SAP Solution Manager using the transaction solution_manager To start the Maintenance
Optimizer choose Operations Change Management Maintenance Optimizer
2 In the Maintenance Optimizer choose the solution for which you want to download SP Stack files
3 Choose Create New Maintenance Transaction
4 Select the product version for which you want to apply a Support Package Stack
The Maintenance Optimizer displays all the systems assigned to the selected product version
5 Select the checkbox for the system that you want to update and choose Continue
6 On the subsequent screen select the Maintenance option and then choose Find Download Files
1 Overview
13 Downloading Support Package Stacks
1260 CUSTOMER 2012-08-30
7 Select the target SP Stack level and the relevant usage types according to the IT scenario to be
updated
8 Choose Find Download Files for the Stack Version
The Maintenance Optimizer displays the product maintenance files in three successive lists
9 Select the required files from the displayed lists
The first list shows all files that are dependent on the type of your operating system and
database
Select the files that correspond to the combination of your operating system and database and
the database-independent files
If your system is distributed on several hosts make sure to select all operating systems used
by the NetWeaver instances You can see all the kernels detected on your system on the Deployed
Components tab page on JSPM user interface (under the SAP KERNEL node) All detected kernels
must be updated to the same version
You get to the second list by choosing Continue This list displays all Support Package files that
are not assigned to the selected Support Package Stack Before you continue with the selection
you must check whether the Support Package files listed here are suitable for your product
maintenance procedure
You get to the third list by choosing Continue The list displays all product maintenance files
that are part of the selected Support Package Stack
Ensure that all files that are assigned to the Support Package Stack are selected here Files that
are not selected will not be included later in the download
10 Choose Continue Use the Download Basket to download the maintenance files
11 Choose Continue once the files have been put in your Download Basket and then Confirm Files in
Download Basket
A dialog window appears and displays all files
12 Confirm the download for all files
13 Open your Download Manager and download the files
NOTE
The stack XML file is generated by the Maintenance Optimizer and automatically saved to
the EPS inbox directory of SAP Solution Manager
More Information
For more information about the Maintenance Optimizer see SAP Support Portal at http
servicesapcomsolman-mopz
1 Overview
13 Downloading Support Package Stacks
2012-08-30 CUSTOMER 1360
This page is left blank for documents that are printed on both sides
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
This chapter describes how to apply Support Packages to installable software units of SAP NetWeaver
70 including enhancement package 2 SAP NetWeaver distinguishes three types of installable software
units
Systems with one or multiple usage types
Standalone engines
Clients
A scenario implementation usually involves several installed software units
RECOMMENDATION
We strongly recommend that you always update all software units belonging to one scenario
together in order to retain a consistent system state Due to the fact that some installable software
units can be commonly shared in different scenarios you must consequently update all scenarios
using the common software units at the same time
21 Application Server ABAP and ABAP-Based Software Components
211 Planning
Procedure
The following components belong to the usage type SAP NetWeaver Application Server ABAP
Software Components of Application Server ABAP
Component to Be Updated SP File Name Tool Used to Apply SP
SAP KERNEL 720 32-64-BIT Non-UNICODEUNICODE SAPEXESAR
SAPEXEDBSAR
JSPMmanually
SAP IGS 700 igsexesar
SAP ABA 702 SAPKA702ltSPgt SPAMSAINT
SAP BASIS 702 SAPKB702ltSPgt
SAP BW 702 SAPKW702ltSPgt
PI_BASIS 702 SAPK-702ltSPgtINPIBASIS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
2012-08-30 CUSTOMER 1560
NOTE
This table contains only software components that belong to the usage type AS ABAP Software
components of other usage types and application units are listed in the corresponding sections
NOTE
SAP delivers intermediate Support Packages for the component SAP BW 702 between two
subsequent SP levels besides the Support Packages delivered along with the Support Package
Stacks Therefore the highest SP level of SAP BW 702 does not necessarily match the target SP
Stack level
CAUTION
When applying a Support Package Stack to a dual-stack system (ABAP+Java) the Java Support
Package Manager (JSPM) will necessarily restart the system several times to make the changes
effective The ABAP part will only be restarted when JSPM is updating the SAP kernel and IGS
212 Preparation
Procedure
Read SAP Note 822379 and all related SAP Notes that the first one refers to
213 Updating the Application Server ABAP and ABAP-Based Software Components
Procedure
Applying Support Packages to SAP NetWeaver Application Server ABAP and ABAP-Based Components
You can update the SAP NetWeaver Application Server ABAP and all ABAP-based software components
running on it using the Support Package Manager (transaction SPAM)
NOTE
If a particular Support Package Stack requires the installation or upgrade of some add-on
components you must use the ABAP Add-on Installation Tool (transaction SAINT) instead of the
Support Package Manager In this case SAINT is able to import both the add-on components and
the related Support Packages of ordinary SAP components
Proceed as follows
1 Log on to the SAP NetWeaver AS system with client 000
2 Start the Support Package Manager by calling transaction SPAM or
start the Add-On Installation Tool by calling transaction SAINT
3 Load the relevant Support Packages or add-on installation packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
1660 CUSTOMER 2012-08-30
4 Define an import queue
5 Perform the import of the defined queue
NOTE
If you have modified SAP objects in your system and these objects are included in the Support
Packages you must perform modification adjustment during the import using the
transactions SPDD (for ABAP Dictionary objects) and SPAU (for Repository objects)
To import the queue you use the standard scenario You can choose between the conventional
import mode and downtime-minimized import mode
Conventional Import Mode
This option comprises the following steps
1 Update the SAP kernel and SAP IGS as described in section Updating SAP Kernel and SAP IGS below
Start the system after the kernel update
2 Import the ABAP Support Packages with the Support Package Manager (SPAM)
Import Mode Downtime-Minimized
This option can be used to reduce system downtime during the update It comprises the following
steps
1 In transaction SPAM enable the downtime-minimized import mode by choosing Extras
Settings then on the Import queue tab page choose Standard and activate the option Import Mode
Downtime-Minimized
2 Import the ABAP Support Packages into the system in an inactive state in the downtime-minimized
mode during system uptime
3 Update the SAP kernel and SAP IGS as described in section Updating SAP Kernel and SAP IGS below
Start the system after the kernel update
4 Complete the ABAP Support Packages import
CAUTION
During this step the system cannot carry out any business transactions (business downtime)
NOTE
In rare cases due to the dependencies of some Support Packages on a particular kernel patch level
the downtime-minimized update does not work In such cases the Support Package Manager
informs you that you must update the SAP kernel before importing ABAP Support Packages You
must proceed with the conventional import procedure
Updating SAP Kernel and SAP IGS
In general the SAP kernel and IGS binaries are located in the global kernel directory DIR_CT_RUN on
the host indicated by the profile parameter SAPGLOBALHOST Once the files in this directory have been
updated to a new patch level a system restart distributes them by means of the program SAPCPE to the
local directories DIR_EXECUTABLE on the hosts where the instances of the SAP system are running
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
2012-08-30 CUSTOMER 1760
CAUTION
The automatic distribution by means of SAPCPE depends on the settings of the profile parameters
DIR_CT_RUN for the global kernel directory and DIR_EXECUTABLE for the local directory of the
executables Before you continue check the instance profiles for the settings of these parameters
in systems that are not installed using SAPinst (for example systems upgraded from older releases
copied or migrated systems)
CAUTION
If your system is a dual-stack system (ABAP+Java) and the ABAP stack has a non-Unicode kernel
be aware that the SCS instance has a Unicode kernel You have to update both kernels (together
with SAP IGS) prior to updating the ABAP and Java Support Package stacks This ensures
compatibility and reduces system downtime
RECOMMENDATION
If you perform an update of a dual-stack system (ABAP+Java) we recommend that prior to
applying ABAP and Java Support Package stacks you use the Single Support Packages option in JSPM
and select for update only the components SAP KERNEL and BC-FES-IGS
For more information about updating a dual-stack system see Parallel Update of Dual-Stack Systems
[page 28]
If you perform an update of an ABAP system the following procedure applies for updating the SAP
kernel and IGS manually
1 Log on as user ltsapsidgtadm to the instance host to be updated
2 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory using
SAPCAR [page 56]
3 Stop the ABAP system that you want to update
NOTE
If the system is running in a high availability (HA) environment make sure that the HA
software does not restart the system automatically during the update
4 Back up the kernel directory ltkrnl_directorygt
5 Copy or move the extracted programs from the temporary directory to the SAP kernel directory
6 Only valid for UNIX |
Execute the following command sequence on UNIX platforms
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
1860 CUSTOMER 2012-08-30
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
7 Restart the SAP system
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS) runs
on a dedicated host You need to perform the kernel update for the ASCS instance manually but
excluding the IGS update because the IGS is not required in an ASCS instance
In rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of such instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances manually Proceed as described
in section Manually Updating Instances with Kernel Directory Located on Separate Hosts below in this document
214 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the ABAP system
22 Application Server Java and Java-Based Software Components
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system which includes
JSPM itself
SAP Kernel and SAP IGS
All Java-based usage types installed in the system
Software Deployment Manager (SDM) - the deployment service of the system
RECOMMENDATION
We strongly recommend that you apply the target Support Package Stack to your system as a
whole This ensures consistency on both the system and the application levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 1960
221 Planning
Procedure
Java Support Package files (SCAs) contain all software objects of the corresponding software
components Thus it is sufficient to apply the Java Support Package files of the intended Support Package
Stack directly to the Java system to be updated It is not necessary to apply the Support Package Stacks
between the start SP Stack level and the target SP Stack level successively
CAUTION
When applying a Support Package Stack to a Java system the Java Support Package Manager (JSPM)
will necessarily restart the system several times to make the changes effective With a dual-stack
system (ABAP+Java) the ABAP part will only be restarted when JSPM is updating the SAP kernel
and IGS
The following components belong to the usage type SAP NetWeaver Application Server Java (AS Java)
Software Components of Application Server Java
Component to Be Updated SP File Name Tool Used to Apply SP
SAP Kernel 720 32-64-BIT UNICODE SAPEXESAR
SAPEXEDBSAR
JSPM
SAP IGS 700 igsexesar
BI META MODEL REPOSITORY 702 BIMMRltSPgt_ltPLgtSCA
J2EE ENGINE CORE TOOLS 702 CORETOOLSltSPgt_ltPLgtSCA
J2EE ENGINE BASE TABLES 702 BASETABLESltSPgt_ltPLgtSCA
BI UDI 702 BIUDIltSPgt_ltPLgtSCA
DI BUILD TOOL 702 SAPBUILDTltSPgt_ltPLgtSCA
SAP CAF 702 CAFltSPgt_ltPLgtSCA
SAP IKS 702 KMKWJIKSltSPgt_ltPLgtSCA
JAVA LOG VIEWER 702 JLOGVIEWltSPgt_ltPLgtSCA
SAP J2EE ENGINE CORE 702 SAPJEECORltSPgt_ltPLgtSCA
SAP JAVA TECH SERVICES 702 SAPJTECHSltSPgt_ltPLgtSCA
SAP TECH S OFFLINE 702 SAPJTECHFltSPgt_ltPLgtSCA
SAP J2EE ENGINE 702 SAPJEEltSPgt_ltPLgtSCA
JAVA SP MANAGER 702 JSPMltSPgt_ltPLgtSCA
ADOBE DOCUMENT SERVICES 702 ADSSAPltSPgt_ltPLgtSCA
UME ADMINISTRATION 702 UMEADMINltSPgt_ltPLgtSCA
LIFECYCLE MGMT TOOLS 702 LMTOOLSltSPgt_ltPLgtSCA
SAP CAF-UM 702 CAFUMltSPgt_ltPLgtSCA
SAP SOFTW DELIV MANAGER 702 SDMKITltSPgt_ltPLgtJAR
SOFTWARE LIFECYCLE MANAGER 702 SWLIFECYCLltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2060 CUSTOMER 2012-08-30
NOTE
This table contains only software components that belong to the usage type AS Java Software
components of other usage types and Java application units are listed in the corresponding
sections
NOTE
As of Support Package 09 you can update your system with SAP Kernel 720 instead of SAP Kernel
701
222 Preparation for Applying a Support Package Stack
Procedure
1 Download the Support Package Stack with all usage types to be updated and the stack definition
XML file as described in Downloading Support Package Stacks [page 12]
NOTE
You can find the activated usage types in an existing Java system on the Deployed Components tab
page on the JSPM user interface
NOTE
You do not need to download the SP Stacks between the source SP Stack level and target SP
Stack level By default the target SP Stack level is the latest available SP Stack
2 Make sure the following requirements are met prior to applying the Support Package Stack
You have familiarized yourself with SAP Note 891983 before you start the Java Support Package
Manager
The system to be updated is fully functional
The Support Package Stack you want to apply and the corresponding stack definition XML
file are available in the EPS inbox directory usrsaptransEPSin By default this location
can be also referred to as ldquoJSPM inboxrdquo
The SAP NetWeaver Application Server Java (AS Java) and the database have been backed up
You have not deleted renamed or created any directories and files in the following directories
and their subdirectories usrsapltSAPSIDgtSYSexe and usrsapltSAPSIDgtSYS
profile
Otherwise JSPM cannot detect the kernel and the system profiles and cannot be started If a
backup of the kernel and the system profiles has been required it has been created in a different
directory
The ltsapsidgtadm user has Read permissions for the EPS inbox directory usrsaptransEPS
in
If your database is SAP MaxDB the overwrite mode for the log area has been activated
The database and the SDM repository have been synchronized
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2160
For more information see the online documentation for JSPM on SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70 Library
(including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library Administrators Guide
Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems AS Java
(Application Server for Java) Software Logistics Software Maintenance Java Support Package Manager
Then choose Troubleshooting JSPM Does Not Update the Versions of the Deployed Components
There is enough disk space
For more information see SAP Note 891895
Your current SAPCAR tool is able to extract the Support Packages for the SAP kernel and
other OS level binaries delivered as SAR files
RECOMMENDATION
You can download the latest version of SAPCAR from SAP Service Marketplace at
httpservicesapcompatches Entry by Application Group Additional Components
SAPCAR
Put the downloaded version in the same directory in the JSPM inbox in which the kernel
SAR files reside so that JSPM can use this version for extracting the SAR files
3 Only valid for Linux |
For RHEL 4 and SLES 9 you need to install additional operating system packages For more
information see SAP Note 1021236End of Linux |
4 Only valid for Windows |
For Windows you need to install additional operating system packages For more information see
SAP Note 684106End of Windows |
5 To prevent the Software Deployment Manager (SDM) from temporarily exceeding the available
disk space during the update process you can change the file transfer directory of SDM in a system
of SPS09 or higher using the following command sequence
Only valid for Windows |
cd ltsdm_homegt
StopServerbat
sdmbat jstartup mode=standalone
sdmbat filetransferdir dir=ltnew_dirgt
sdmbat jstartup mode=integrated
StartServerbat
End of Windows |
Only valid for IBM i5OSUNIX |
cd ltsdm_homegt
StopServersh
sdmsh jstartup mode=standalone
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2260 CUSTOMER 2012-08-30
sdmsh filetransferdir dir=ltnew_dirgt
sdmsh jstartup mode=integrated
StartServersh
End of IBM i5OSUNIX |
6 To prevent deployment errors during the update process proceed as follows
1 Log on to the Central Instance host
2 Start the ConfigTool and in the navigation area choose Cluster-data Global server configuration
Managers ServiceManager
3 In the Global properties panel set the Custom value of the EventTimeout property to 120
4 Choose Save
5 Restart the Central Instance
7 Check whether the used JDK version and the Java VM settings of the Java runtime system comply
with the requirements in SAP Note 723909 Update the JDK and adjust the settings if necessary
NOTE
An update of the used JDK version possibly changes the JVM path In this case you must
make the new path available to all Dialog Instances of the J2EE engine by implementing option
1 of SAP Note 718901
8 Make sure that the J2EE administrator password stored in the secure store for offline usage is
identical with the one stored in the User Management Engine (UME) You can change the password
in the secure store as described in SAP Note 870445
9 If you are running a high availability system on Windows you might need to prepare your system
as described in the online documentation for JSPM see section Preparing Systems That Run in High
Availability Environment
223 Updating the Application Server Java and Java-Based Components
Procedure
Applying a Support Package Stack to SAP NetWeaver Application Server Java and Java-Based Components
NOTE
The JSPM GUI might not work properly on some UNIX systems For more information and the
solution see SAP Note 1013976
1 Log on as user ltsapsidgtadm to the Central Instance host
NOTE
If your operating system is IBM i log on as user ltSIDgtADM or ltSIDgtOFR
2 Close the SAP Management Console (SAP MMC) and the SDM remote GUI client
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2360
3 For UNIX and Windows To start the JSPM navigate to the directory ltINSTDIRgtltSIDgt
ltCentral_Instance_Namegtj2eeJSPM and run the go script file
NOTE
If your system is running on IBM i to start the JSPM proceed as follows
1 To prevent JSPM from automatically starting its GUI in the file usrsapltSIDgt
ltCentral_Instance_Namegtj2eeJSPMparamjspm_configtxt change the
property dialogSDTServerConnectionSDTGuilaunch from true to false
2 On the IBM i host run the go script file using the following command
QSH CMD(usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPMgo)
3 In the mounted directory usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPM run
the StartGui script file The JSPM GUI appears
4 In the Host field enter the target IBM i host
NOTE
Depending on the system type ltCentral_Instance_Namegt has the following syntax
Standalone Java system JCltinstance_nogt
Add-On system DVEBMGSltinstance_nogt
4 Enter your SDM password to log on to the SDM
5 On the Deployment tab page select the Java Support Package Manager option and update the software
component sapcomJSPM to the target SPS level
6 Restart the JSPM and log on with the SDM password
RECOMMENDATION
We strongly recommend that you use the Support and Enhancement Package Stack option when
applying a Support Package Stack Other options can lead to unintended consistency issues
NOTE
If you need to include the latest patches for a particular component during the update process
with the Support and Enhancement Package Stack option stop the JSPM after restart and apply SAP
Note 1080821 Then start the JSPM again
7 On the Deployment tab page select the Support and Enhancement Package Stack option and choose Next
The Support Package Stacks that are available for deployment in the global EPS inbox directory
are displayed
8 In the Target SP Stack Level dropdown box select the Support Package Stack to be applied and choose
Next
In this step JSPM performs various status validations and displays the result of each software
component included in the stack definition XML file on the subsequent screen which includes
the following possible statuses
OK Indicates that the SPS level of the corresponding software component is applicable
WARNING We recommend that you view the details about the component by choosing Show
Details
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2460 CUSTOMER 2012-08-30
This status may indicate that the corresponding software component comprises custom
modifications in an NWDI-controlled system
If your system is used for NWDI development and it is either a DEV or a CONS system
you will be informed that JSPM will not deploy the modified software components but
only transport them to the CMS transport directory JSPM will deploy only the software
components that are not modified
If your system is not used for NWDI development or if your system is used for NWDI
development and it is either a TEST or a PROD system you will be informed that JSPM
has found newer versions of modified software components and will automatically replace
the original versions with the newer versions JSPM will deploy all software components
that are not modified together with the replaced versions of the modified software
components
CAUTION
You may get a warning telling you that there are patches installed in your system
containing fixes which might not be included in the target SP Stack This is possible if
you have applied patches of the start SP Stack level that were delivered later than the
target SP Stack delivery date In order not to lose these fixes you need to download and
apply the corresponding patches of the target SP Stack level
If you are performing an update from SAP NetWeaver 70 including enhancement
package 1 SPS00 and you have not applied any patches for the software component with
status WARNING before the update then you can ignore warnings such as the following
example
The new version of the development component sapcomcomsapnetweaver
bcrfmoni is 70100200806121227180000 and is lower than the already
deployed version 70100200807090143420000
REVISE Indicates inconsistencies with the corresponding software component
The deployment cannot be performed until all problems have been resolved You can view
the problems by choosing Show Details
9 If the status of the selected SP Stack is OK or WARNING you can start the system update by choosing
Start JSPM then changes the status to SCHEDULED
If the SP Stack to be applied includes a kernel update and the current kernel is not already of the
corresponding patch level JSPM arranges the kernel update as the very first Support Package to
be applied JSPM updates the kernel binaries of all instances (including Dialog Instances and SCS
instances in a HA environment) whose kernel directories DIR_CT_RUN effectively reside on the host
indicated by the profile parameter SAPGLOBALHOST
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2560
CAUTION
Kernel binaries of instances whose kernel directories DIR_CT_RUN are not effectively linked
to the host SAPGLOBALHOST must be updated individually as described in section Manually
Updating Instances with Kernel Directory Located on Separate Hosts below
The kernel update (includes update of SAP Kernel and SAP IGS) using JSPM consists of the following
steps
1 JSPM stops the Central Instance automatically and prompts you to stop the remote SCS and
Dialog Instances manually
2 After you have stopped all the instances choose the Next button in the dialog box
The kernel update starts
NOTE
If the system is running in a high availability environment make sure that the HA
software does not restart the instance automatically during the update
NOTE
If kernel binaries of the SCS instance need to be updated manually (see Manually Updating
Instances with Kernel Directory Located on Separate Hosts below) you must perform this at the
time when JSPM is updating the kernel binaries of the Central Instance In any case the
SCS kernel must be up-to-date before the next restart
When the kernel update is finished a dialog box appears in which you are prompted to restart
the SCS instance manually
3 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries
before you can proceed with the next step For more information see Adjusting the Ownership and
Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
4 Choose Next in the dialog box when the SCS instance is running again
After the kernel update JSPM restarts the system for further deployment of the remaining Support
Packages in the stack
RECOMMENDATION
If you need to update the kernel binaries of any Dialog Instances manually (see Manually
Updating Instances with Kernel Directory Located on Separate Hosts below) perform the update when
JSPM is updating the remaining Support Packages in the stack in order to save time
The deployment of each Support Package can end with one of the following statuses
DEPLOYED
The Support Package has been successfully deployed
DEPLOYED WITH WARNING
The Support Package has been deployed but it possibly may not work properly with other
deployed components
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2660 CUSTOMER 2012-08-30
You can view the details by choosing Show Details or examining the log files You can also view
the details about the component by choosing the Deployed Components tab page
ERROR
An error has occurred during the deployment You can view the details by choosing Show
Details or examining the log files
You must correct the error to be able to continue with the SP Stack update
You can proceed as described for a deployment that finished with status DEPLOYED WITH
WARNING
If the error correction does not change the contents in the JSPM inbox you can continue
the deployment by choosing Resume
If the error correction changes the contents in the JSPM inbox you can choose New
Deployment to redeploy the SP Stack
NOT DEPLOYED
JSPM has not attempted to deploy the software component for certain reasons
If your system is not used for NWDI development you can proceed as described for a
deployment that finished with status ERROR
If your system is used for NWDI development and it is either a DEV or a CONS system
the status of the modified software components is always NOT DEPLOYED JSPM has
transported the software components of the Support Package Stack both modified and
not modified to the CMS transport directory The deployment of the modified software
components is handled by NWDI
Manually Updating Instances with Kernel Directory Located on Separate Hosts
JSPM performs kernel update for all instances (including Dialog Instances and SCS instances in a HA
environment) whose kernel directories DIR_CT_RUN effectively reside on the host indicated by the profile
parameter SAPGLOBALHOST (by using folder sharing on Windows or file system mounting on UNIX) In
rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of those sort of instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances individually
To update the kernel of an instance manually proceed as follows
1 Log on as user ltsapsidgtadm to the host of the instance to be updated
2 Back up the kernel directory which is specified by the profile parameter DIR_CT_RUN
3 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory with
SAPCAR [page 56]
4 Stop the instance being updated
NOTE
If the system is running in a HA environment make sure that the HA software does not
restart the instance automatically during the update
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2760
5 Copy or move the extracted programs from the temporary directory to the local kernel directory
6 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries as
described in section Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
7 Restart the instance after JSPM has finished the deployment of all packages on the Central Instance
Only valid for UNIX |
Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms
On UNIX platforms you must adjust the ownership and execution permissions of the kernel binaries
after the update regardless whether you performed the update manually or by using JSPM because
both update procedures are performed with the ltsapsidgtadm user Enter the following command
sequence
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
224 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the Java system
23 Parallel Update of Dual-Stack Systems
If you perform an update of a dual-stack system (ABAP+Java) we recommend that you follow the
procedure described below The procedure has been validated to update the ABAP stack and the Java
stack of a NetWeaver system in parallel thus reducing the overall system downtime by half
Procedure
1 Before applying ABAP and Java Support Packages use the Single Support Packages option in JSPM and
select for update only the components SAP KERNEL and BC-FES-IGS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
23 Parallel Update of Dual-Stack Systems
2860 CUSTOMER 2012-08-30
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS)
runs on a dedicated host In this case JSPM does not support update of kernel binaries and
you need to update them manually Perform the update manually as described under Updating
SAP Kernel and SAP IGS in section Updating the Application Server ABAP and ABAP-Based Software
Components [page 16]
2 Import the Support Packages for the component SAP_BASIS into the ABAP stack using the ABAP
Support Package Manager (SPAM)
3 Import the remaining ABAP Support Packages with SPAM and in parallel apply the Java Support
Package Stack with JSPM
Proceed as described in Updating the Application Server ABAP and ABAP-Based Software Components [page
16] and Updating the Application Server Java and Java-Based Software Components [page 23]
24 Process Integration
241 Planning
Procedure
This section covers all the units of Process Integration that should be updated Particularly the following
units must always have the same Support Package level (the patch level can be different)
Integration Server
XI Adapter Engine
Partner Connectivity Kit
System with the Usage Type Process Integration
Software components of Integration Server
Components to Be Updated SP File Name Tool Used to Apply SP
Java stack
XI TOOLS 702 SAPXITOOLltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
ABAP stack
XI CONTENT SAP_BASIS 702 SAPBASISltSPgt_ltPLgtZIP File upload
XI CONTENT SAP_ABA 702 SAPABAltSPgt_ltPLgtZIP
SAP NetWeaver Application Server ABAP (see table Software components of Application Server ABAP [page 15])Note that update of the following software components of the ABAP system is not required SAP ABA 702 SAP BW 702 PI_BASIS 702
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 2960
J2EE Adapter Engine
If your implemented scenario includes a J2EE Adapter Engine then it must always be of the same
Support Package level as the Integration Server
Components of the J2EE Adapter Engine
Component to Be Updated SP File NameTool Used to Apply SP
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
J2SE Adapter Engine
The installation of the J2SE Adapter Engine depends on the implemented scenario
Components of the J2SE Adapter Engine
Component to Be Updated SP File Name Tool Used to Apply SP
XI CONNECTIVITY SE 702 SAPXICONSltSPgt_ltPLgtSCA ZIP tool (for example WinZip)
Partner Connectivity Kit
If your implemented scenario includes a Partner Connectivity Kit (PCK) then it must always be of the
same Support Package level as the Integration Server
Software components of Partner Connectivity Kit
Components to Be Updated SP File NameTool Used to Apply SP
XI PCK 702 SAPXIPCKltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of the Application Server Java [page 20])
System Landscape Directory (SLD)
The System Landscape Directory is required for the PI operations Although updating the SLD is not
necessarily required it is advisable to update the SLD server and the SAP Master Data Content within
it from time to time The update of the SLD includes
1 The system where the SLD is running
2 The SAP Master Data Content within this SLD
SAP GUI
See table Compatible SAP GUI Versions [page 51]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3060 CUSTOMER 2012-08-30
242 Updating Units of Process Integration
Procedure
Before you start the update perform the following steps
In the Runtime Workbench use Communication Channel Monitoring to stop all sender channels
for all adapter types on all your Adapter Engines
On the Integration Server use transaction SMQR and deregister all qRFC queues
System with the Usage Type Process Integration
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the XI instance is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system where the XI instance is running
For more information see Application Server Java and Java-Based Software Components [page 19]
System Landscape Directory (Optional)
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the SLD is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the entire Support Package Stack to the system where the SLD is running
For more information see Application Server Java and Java-Based Software Components [page 19]
J2EE Adapter Engine
Apply the Support Package Stack to the system where the Adapter Engine is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Partner Connectivity Kit
Apply the Support Package Stack to the system where the PCK is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Front End GUIs
Update the SAP GUI components if necessary
For more information see SAP GUI Family [page 51]
ABAP 700 Business System (Optional)
Apply the Support Packages for SAP NetWeaver Application Server ABAP (including SAP kernel and
the Support Package for SAP BASIS 700)
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 640 Business System (Optional)
Apply the Support Packages for SAP Web Application Server ABAP 640 (including SAP kernel and the
Support Package for SAP BASIS 640)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3160
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 620 Business System (Optional)
1 Update the SAP Kernel 620
2 Import the released Basis Support Packages for SAP Web AS 620 as well as the most recent Add-
On Support Package for APPINT 200_620 in the order described in SAP Note 439915
J2SE Adapter Engine (Optional)
NOTE
The XI Adapter Engine (J2SE) and all its adapters are provided for compatibility reasons only and
are not developed any further You have to use the XI Adapter Engine running on SAP NetWeaver
AS Java For more information see the Master Guide ndash SAP NetWeaver 70 available on SAP Service
Marketplace at httpservicesapcominstallNW70 Planning
1 Extract the SAPXICONSltSPgt_ltPLgtSCA (XI Connectivity SE 700) archive (ZIP format) to a temporary
directory
2 Save the old configuration files as described in the document Adapterpdf in directory
lttemp_directorygttech_adapterAdministrationDocumentation
3 Unpack the ZIP archive TechnicalAdapterssda to the installation directory of the XI Adapter
Engine (J2SE)
4 Restore the configuration files with restore_configuration
243 Post-Installation Steps
Procedure
Communication Channels and Queues
Restart all stopped sender channels and register all deregistered qRFC queues
XI Content
In the system with usage type PI import the XI content from the archives SAPBASISltSPgt_ltPLgtZIP
and SAPABAltSPgt_ltPLgtZIP as follows
1 Unpack the archives using a ZIP tool of your choice
2 Copy the corresponding export files (with file extension tpz) to the import directory ltINSTDIRgt
ltSAPSIDgtSYSglobalxirepository_serverimport
3 Start the Integration Builder (transaction SXMB_IFR)
4 Enter the Integration Repository by choosing Repository (Design)
5 Choose Tools Import design objects
6 Import the tpz files containing the XI content
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3260 CUSTOMER 2012-08-30
NOTE
For more information see SAP Note 836200
Role Generation on the Integration Server
On the Integration Server execute transaction SUPC (mass generation of roles) for all SAP_XI roles in
each of your clients to regenerate possibly changed roles
NOTE
Do not forget to make a user comparison for regenerated roles afterwards
Partner Connectivity Kit (Optional)
Perform the post-installation steps for PCK as described in SAP Note 746328
SAP Master Data within the SLD (Optional)
In the system where your SLD is running import the latest SLD content as described in SAP Note
669669
Receiver-Based EOIO Serialization in J2EE Adapter Engine (Optional)
The J2EE Adapter Engine can be switched to receiver-based EOIO serialization The switch can be
triggered on demand and is executed asynchronously It includes a database migration step during
which all EOIO processing in the Adapter Engine is disabled See SAP Note 973894 for details about how
to start the EOIO serialization migration
Service Metering (Optional)
Service metering gathers information about a service caller transfers it to the service provider and
counts on the service provisioning side how many times a service is called and by which service caller
Service metering is performed for the XI message protocol and the WS message protocol Service
metering is automatically enabled after applying a Support Package Stack By default only non-sensitive
data is transmitted to internal or external service providers in a compatible way
Service metering can be configured in PI in the Integration Engine on sender-side and in the Integration
Directory
Service metering can be configured in AS ABAP in transaction SOAMANAGER
Only if the service provider is allowed to receive more detailed information about the service caller set
the metering level to higher than the default
For more information see SAP Note 1239428
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3360
25 Business Intelligence
251 Planning
Procedure
Business Intelligence includes one or many of the following units that must be updated depending on
your implemented scenarios The usage types Business Intelligence (BI) and Business Intelligence Java
Components (BI-Java) must always have the same Support Package level
Business Intelligence
Software Components of Business Intelligence
Component to Be Updated SP File Name Tool Used to Apply SP
BI CONT ADDON 70x SAPK-70ltxgtltSPgtINBICONT SAINT
SAP NetWeaver Application Server ABAP (see table Software Components of Application Server ABAP [page 15])
NOTE
For information about the dependencies applying to BI Content Support Packages see SAP Note
653814 BI CONT 703 Support Packages are not part of the NetWeaver SP Stacks Updates can be
performed when applicable Alternatively BI CONT 704 Support Packages can be imported See
the BI Content release strategy in SAP Note 153967
Business Intelligence Java Components
BI Java Components
Component to Be Updated SP File NameTool Used to Apply SP
BI REPORTING AND PLANNING 702 BIREPPLANltSPgt_ltPLgtSCA JSPM
BI WEBDYNPRO ALV 702 BIWDALVltSPgt_ltPLgtSCA
BI INFORM BROADCASTING 702 BIIBCltSPgt_ltPLgtSCA
BI WEB APPLICATIONS 702 BIWEBAPPltSPgt_ltPLgtSCA
BI BASE SERVICES 702 BIBASESltSPgt_ltPLgtSCA
VISUAL COMPOSER BI KITS 702 VCKITBIltSPgt_ltPLgtSCA
Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
BI Precalculation Service
Components of the BI Precalculation Service
Component to Be Updated SP File Name Tool Used to Apply SP
BI Pre-calculation Service 700 xPreCalServerltSPgt_ltPLgtexe Installer
Search and Classification (TREX)
See table TREX Component [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3460 CUSTOMER 2012-08-30
BI Accelerator
The BI Accelerator is based on the TREX technology It is a special Linux 64-bit version of SAP NetWeaver
70 Search and Classification (TREX) which is delivered on preconfigured hardware
NOTE
You cannot use a TREX installation based on 32-bit architecture that is configured for searching
in metadata and documents for the BI Accelerator And vice versa a BI Accelerator box cannot
be used for searching in metadata and documents
If you want to use the search functionality as well as the BI Accelerator you require two separate
installations For more information see BI Accelerator [page 47]
Clients
Depending on your implemented scenarios you have to update SAP GUI Components and Business
Explorer (BI Add-OnBW Add-On)
NOTE
See SAP Note 889314 to determine when to use the BI Add-On and the BW Add-On
NOTE
As SAP GUI 640 is no longer supported BI Frontend Support Package 1800 resp patch 1801 is the
last Support Package resp patch based on SAP GUI 640 For more information see SAP Note
1231292 (Frontend Add-in Strategy 640710 GUI Version)
For more information about the new release strategy for the BI Frontend see SAP Note 1231363
(Changed Delivery Strategy for BI Frontend)
252 Preparation
Procedure
For the Support Packages of the most important Business Intelligence units so called SAPBINews
(SAPBWNews) Notes are created Read these Notes before updating Business Intelligence For SAP
NetWeaver 70 including enhancement package 2 SPS 12 these are the following
Business Intelligence ABAP SAP Note 1680996
Business Intelligence Java Components SAP Note 1726461
BI 70 Frontend Add-On for SAP GUI 710 SAP Note 1413032
BI 70 Frontend Add-On for SAP GUI 720 SAP Note 1630112
BI 70 Frontend Add-On for SAP GUI 730 SAP Note 1726739
For more information about BI Support Packages see SAP Community Network at http
scnsapcomcommunitydata-warehousingnetweaver-bw Related Resources SAP NW BW Support
Packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
2012-08-30 CUSTOMER 3560
253 Updating Units of Business Intelligence
Procedure
Business Intelligence
1 Update the SAP NetWeaver Application Server ABAP (with BI CONT 70x if necessary) with the
appropriate Support Packages
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
NOTE
When applying the component SAP BW 702 some generation errors might occur When
you start importing the BI Support Packages in transaction SPAM choose the menu path
Extras Ignore generation errors For more information see SAP Note 114134
2 Apply the Support Package Stack to the system with the usage type BI-Java
For more information see Application Server Java and Java-Based Software Components [page 19]
3 Update the BI Precalculation Service that is used in your scenario
4 Update the standalone engine Search and Classification (TREX) that is used in your scenario For more
information see Standalone Engine Search and Classification (TREX) [page 44]
NOTE
You have to update TREX to the newest version if you use search capabilities within Business
Intelligence
5 Update the BI Accelerator to the newest available version For more information see BI
Accelerator [page 47]
6 Update the SAP GUI and Business Explorer (BI Add-On BW Add-On) on all remote client hosts
that are involved in the scenario
For more information see SAP GUI Family [page 51] and Business Explorer (BI Add-On BW Add-On)
[page 51]
BI Precalculation Service
1 Log on to the host as a user with administration rights
2 Install the Support Package of the BI Precalculation Service by executing the
xPreCalServerexe file
The welcome screen of the BI Precalculation Server setup wizard appears
The setup now checks the system for the prerequisites
3 Choose the option Update for updating the BI Precalculation service to the current patch level and
then Finish
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3660 CUSTOMER 2012-08-30
26 EP Core
261 Planning
Procedure
The following installable software units must be updated
EP Core
Software Components of EP Core
Component to Be Updated SP File Name Tool Used to Apply SP
PORTAL CORE SERVICES 702 EPBCltSPgt_ltPLgtSCA JSPM
PORTAL FRAMEWORK 702 EPBC2ltSPgt_ltPLgtSCA
PORTAL 702 EPPSERVltSPgt_ltPLgtSCA
PORTAL WEB DYNPRO 702 EPWDCltSPgt_ltPLgtSCA
UWL COLL PROCESS ENGINE 702 UWLJWFltSPgt_ltPLgtSCA
CAF EU 702 SAPEUltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
262 Preparation
Procedure
Backing Up the Portal Runtime Configuration
If you have made changes to the standard Portal Runtime configuration you have to make a backup
of the configuration before the update process For more information see SAP Note 1064468
263 Updating EP Core
Procedure
Apply the Support Package Stack to a system with usage type EP Core
For more information see Application Server Java and Java-Based Software Components [page 19]
264 Post-Installation Steps for EP Core
Procedure
Restoring the Portal Runtime Configuration
To make your changes to the standard Portal Runtime Configuration effective you have to restore
the backup of the configuration done before the update process For more information see SAP Note
1064468
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
26 EP Core
2012-08-30 CUSTOMER 3760
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
Typographic Conventions
Example Description
ltExamplegt Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system for example ldquoEnter your ltUser Namegtrdquo
ExampleExample
Arrows separating the parts of a navigation path for example menu options
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear in the documentation
httpwwwsapcom Textual cross-references to an internet address
example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web
123456 Hyperlink to an SAP Note for example SAP Note 123456
Example Words or characters quoted from the screen These include field labels screen titles pushbutton labels menu names and menu options
Cross-references to other documentation or published works
Example Output on the screen following a user action for example messages Source code or syntax quoted directly from a program File and directory names and their paths names of variables and parameters and
names of installation upgrade and database tools
EXAMPLE Technical names of system objects These include report names program names transaction codes database table names and key concepts of a programming language when they are surrounded by body text for example SELECT and INCLUDE
EXAMPLE Keys on the keyboard
460 CUSTOMER 2012-08-30
Document History
CAUTION
Before you start the implementation make sure you have the latest version of this document
You can find the latest version on SAP Service Marketplace at httpservicesapcom
instguides
The following table provides an overview on the most important document changes
Version Date Description
100 2012-08-30 First version
2012-08-30 CUSTOMER 560
Table of Contents
Chapter 1 Overview 9
11 Before You Start 9
12 Types of Support Packages 11
13 Downloading Support Package Stacks 12
Chapter 2 Applying Support Packages to Installable Software Units of SAP
NetWeaver 70 Including Enhancement Package 2 15
21 Application Server ABAP and ABAP-Based Software Components 15
211 Planning 15
212 Preparation 16
213 Updating the Application Server ABAP and ABAP-Based Software
Components 16
214 Post-Installation Steps 19
22 Application Server Java and Java-Based Software Components 19
221 Planning 20
222 Preparation for Applying a Support Package Stack 21
223 Updating the Application Server Java and Java-Based
Components 23
224 Post-Installation Steps 28
23 Parallel Update of Dual-Stack Systems 28
24 Process Integration 29
241 Planning 29
242 Updating Units of Process Integration 31
243 Post-Installation Steps 32
25 Business Intelligence 34
251 Planning 34
252 Preparation 35
253 Updating Units of Business Intelligence 36
26 EP Core 37
261 Planning 37
262 Preparation 37
660 CUSTOMER 2012-08-30
263 Updating EP Core 37
264 Post-Installation Steps for EP Core 37
27 Enterprise Portal 38
271 Planning 38
272 Updating Enterprise Portal 38
273 Post-Installation Steps for Enterprise Portal 39
28 Development Infrastructure 40
281 Planning 40
282 Updating Development Infrastructure 41
29 Mobile Infrastructure 43
291 Planning 43
292 Preparation 43
293 Updating Mobile Infrastructure 43
210 Standalone Engines 44
2101 Search and Classification (TREX) 44
21011 Planning 44
21012 Preparation 44
21013 Updating TREX 45
2102 BI Accelerator 47
21021 Planning 47
21022 Preparation 48
21023 Updating BI Accelerator 48
21024 Post-Installation Steps 49
2103 Gateway 50
2104 SAP Web Dispatcher 50
2105 Other Standalone Engines 50
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2 51
2111 SAP GUI Family 51
2112 Business Explorer (BI Add-On BW Add-On) 51
2113 Other Clients 52
212 SAP Library 52
Chapter A Appendix 55
A1 Determining the Current Component Versions 55
A2 Tools Used During the System Update 56
A21 SAPCAR 56
A22 ABAP Support Package Manager and Add-On Installation Tool 57
A23 Java Support Package Manager 58
2012-08-30 CUSTOMER 760
A3 System Profile Parameters 58
860 CUSTOMER 2012-08-30
1 Overview
This document describes how to install Support Package Stacks (SP Stacks) for SAP NetWeaver 70
including enhancement package 2 You can find all information related to the SP Stacks on SAP Service
Marketplace at httpservicesapcomsp-stacks
11 Before You Start
CAUTION
If you intend to update your system to the latest SP Stack level and plan to upgrade it within the
next 6 months first check the availability of the equivalent SP Stack for the target release The
delivery dates of the equivalent SP Stacks for your source and target release might be several
months apart
Be aware that you cannot upgrade to a target release that does not include the equivalent SP Stack
level
To avoid a deadlock situation we recommend that you check SAP Service Marketplace at
httpservicesapcomsp-stacks SP Stack Information and consider not applying the
latest SP Stack on your source release system
Updated Document Versions
The Support Package Stack Guide is regularly updated on SAP Service Marketplace at http
servicesapcommaintenanceNW70
NOTE
Make sure you have the latest version of the Support Package Stack Guide by checking SAP Service
Marketplace immediately before you start to apply or import Support Packages
SAP Notes
You must read SAP Note 1460321 before you read this document as it may contain corrections and
further information about the Support Package Stack installation
SAP Library
You must inform yourself about enhancements and changes to the Support Package Stack to be applied
from SAP Library under SAP Library SAP NetWeaver Whatrsquos New in SAP NetWeaver 70 ndash Release
Notes You can access the SAP Library in one of the following ways
SAP Help Portal at httphelpsapcomnw702 Application Help SAP Library ltLanguagegt
1 Overview
11 Before You Start
2012-08-30 CUSTOMER 960
NOTE
The SAP Help Portal always provides the up-to-date version of the SAP Library Therefore
we recommend that you use this channel to access the SAP Library
Local installation of the SAP Library from the online documentation DVD
CAUTION
In order to inform yourself about the current Support Package Stack you first have to update
your local installation of the SAP Library to the corresponding SPS level Follow the
instructions in section SAP Library [page 52]
Naming Conventions
In this document the following naming conventions apply
Variables
Variables Description
ltSAPSIDgt
ltsapsidgt
ltSIDgt
SAP system ID
ltINSTDIRgt Installation directory for the SAP system
lthostgt Host name
ltinstance_nogt Instance number of a system instance
ltdatabasegt Name of database
ltsapinst_directorygt Installation directory for the SAP installation tool SAPinst
ltsp_directorygt Temporary directory which the archives of a Support Package are downloaded or copied to
ltOSgt Operating system
ltOS_DIRgt OS-dependent directory consisting of a folder for the platform and a subfolder of your OS versionFor example if you operating system is Sun OS 64bit ltOS_DIRgt stands for UNIXSUNOS64
ltSP_Stackgt Number of Support Package Stack
ltSPgt Support Package level
ltPLgt Support Package patch level
ltRELgt Release number
ltLOCALEgt Language definitionFor example the German locale is _de
ltkrnl_directorygt Kernel directory which the profile parameter DIR_CT_RUN usually refers to
ltsdm_homegt Program file location of the Software Deployment Manager (SDM)
ltSAPGLOBALHOSTgt SAP global host the host where the global directories of an SAP system reside
ltSAPLOCALHOSTgt SAP local host the host where a particular instance of an SAP system is running
1 Overview
11 Before You Start
1060 CUSTOMER 2012-08-30
12 Types of Support Packages
The following table explains the terms used in the correction process as part of the software maintenance
process for SAP NetWeaver
Correction Process Description
Standard correction process
Support Package Stack Description
A Support Package Stack is a set of Support Packages and patches for the respective product version that must be used in the given combination
Version numbersSupport Package Stacks have a release number and a stack number for example SAP NetWeaver 70 Support Package Stack 05
DeliveryThere is no dedicated delivery format for the Support Package Stacks The included Support Package files have their delivery formats and must be applied using the tools as described below
Kernel Patches Version numbers
SAP Kernel patches have a release number and a patch number The patch number is increased with each correction
DeliverySAP Kernel patches are delivered as SAR files They are installed by extracting the SAR files to the kernel directory using SAPCAR Separate SAR files are shipped for the different kernel types depending on UNICODENON-UNICODE and the platform
ABAP Support Packages Description
ABAP Support Packages contain corrections and adjustments for the ABAP-based Software Components of the SAP system
DependenciesIn contrast to Java Support Packages ABAP Support Packages are non-cumulative Therefore ABAP Support Packages must be installed in the correct sequence one after the other You cannot skip any intermediate Support Packages
DeliveryABAP Support Packages are delivered as SAR files They are installed using the Support Package Manager (SPAM)
Java Support Packages Description
Java Support Packages contain corrections for the Java-based Software Components of the SAP system
DependenciesJava Support Packages always contain a full delivery of the Software Components Therefore you only need to apply the latest Support Package to update the software If there are dependencies with other Java Support Packages these are specified in an SAP Note
DeliveryJava Support Packages are delivered as Software Component Archives (SCAs) They are applied using the Java Support Package Manager (JSPM)
1 Overview
12 Types of Support Packages
2012-08-30 CUSTOMER 1160
Correction Process Description
Emergency correction process
SAP Note Correction (ABAP) Description
SAP Note corrections contain single ABAP fixes Delivery
SAP Note corrections are delivered with SAP Notes If required you apply them using the SAP Note Assistant
Java Support Package Patch Description
A Java Support Package patch contains corrections for the Java Software Components Java Support Package patches are created and released on demand A Java Support Package patch corresponds to an SAP Note that describes the same correction
DependenciesA Java Support Package patch always contains a full package of the corresponding Software Component and is applied using JSPM
13 Downloading Support Package Stacks
The Maintenance Optimizer in SAP Solution Manager is the only source from which you can receive
maintenance updates for SAP NetWeaver 70 and higher releases as well as for all applications running
on top of SAP NetWeaver The Maintenance Optimizer supports you in selecting and downloading all
required maintenance files In addition the Maintenance Optimizer generates a stack XML file and
saves it to the EPS inbox directory of SAP Solution Manager
Prerequisites
You have configured the Maintenance Optimizer in SAP Solution Manager as described on SAP Help
Portal at httphelpsapcom SAP Solutions SAP Solution Manager SAP Solution Manager ltReleasegt
ltLanguagegt Change Management Maintenance Optimizer Planning and Monitoring Product Maintenance and
also in section Automatically Calculating Product Maintenance Files
Procedure
To download a Support Package Stack proceed as follows
1 Start SAP Solution Manager using the transaction solution_manager To start the Maintenance
Optimizer choose Operations Change Management Maintenance Optimizer
2 In the Maintenance Optimizer choose the solution for which you want to download SP Stack files
3 Choose Create New Maintenance Transaction
4 Select the product version for which you want to apply a Support Package Stack
The Maintenance Optimizer displays all the systems assigned to the selected product version
5 Select the checkbox for the system that you want to update and choose Continue
6 On the subsequent screen select the Maintenance option and then choose Find Download Files
1 Overview
13 Downloading Support Package Stacks
1260 CUSTOMER 2012-08-30
7 Select the target SP Stack level and the relevant usage types according to the IT scenario to be
updated
8 Choose Find Download Files for the Stack Version
The Maintenance Optimizer displays the product maintenance files in three successive lists
9 Select the required files from the displayed lists
The first list shows all files that are dependent on the type of your operating system and
database
Select the files that correspond to the combination of your operating system and database and
the database-independent files
If your system is distributed on several hosts make sure to select all operating systems used
by the NetWeaver instances You can see all the kernels detected on your system on the Deployed
Components tab page on JSPM user interface (under the SAP KERNEL node) All detected kernels
must be updated to the same version
You get to the second list by choosing Continue This list displays all Support Package files that
are not assigned to the selected Support Package Stack Before you continue with the selection
you must check whether the Support Package files listed here are suitable for your product
maintenance procedure
You get to the third list by choosing Continue The list displays all product maintenance files
that are part of the selected Support Package Stack
Ensure that all files that are assigned to the Support Package Stack are selected here Files that
are not selected will not be included later in the download
10 Choose Continue Use the Download Basket to download the maintenance files
11 Choose Continue once the files have been put in your Download Basket and then Confirm Files in
Download Basket
A dialog window appears and displays all files
12 Confirm the download for all files
13 Open your Download Manager and download the files
NOTE
The stack XML file is generated by the Maintenance Optimizer and automatically saved to
the EPS inbox directory of SAP Solution Manager
More Information
For more information about the Maintenance Optimizer see SAP Support Portal at http
servicesapcomsolman-mopz
1 Overview
13 Downloading Support Package Stacks
2012-08-30 CUSTOMER 1360
This page is left blank for documents that are printed on both sides
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
This chapter describes how to apply Support Packages to installable software units of SAP NetWeaver
70 including enhancement package 2 SAP NetWeaver distinguishes three types of installable software
units
Systems with one or multiple usage types
Standalone engines
Clients
A scenario implementation usually involves several installed software units
RECOMMENDATION
We strongly recommend that you always update all software units belonging to one scenario
together in order to retain a consistent system state Due to the fact that some installable software
units can be commonly shared in different scenarios you must consequently update all scenarios
using the common software units at the same time
21 Application Server ABAP and ABAP-Based Software Components
211 Planning
Procedure
The following components belong to the usage type SAP NetWeaver Application Server ABAP
Software Components of Application Server ABAP
Component to Be Updated SP File Name Tool Used to Apply SP
SAP KERNEL 720 32-64-BIT Non-UNICODEUNICODE SAPEXESAR
SAPEXEDBSAR
JSPMmanually
SAP IGS 700 igsexesar
SAP ABA 702 SAPKA702ltSPgt SPAMSAINT
SAP BASIS 702 SAPKB702ltSPgt
SAP BW 702 SAPKW702ltSPgt
PI_BASIS 702 SAPK-702ltSPgtINPIBASIS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
2012-08-30 CUSTOMER 1560
NOTE
This table contains only software components that belong to the usage type AS ABAP Software
components of other usage types and application units are listed in the corresponding sections
NOTE
SAP delivers intermediate Support Packages for the component SAP BW 702 between two
subsequent SP levels besides the Support Packages delivered along with the Support Package
Stacks Therefore the highest SP level of SAP BW 702 does not necessarily match the target SP
Stack level
CAUTION
When applying a Support Package Stack to a dual-stack system (ABAP+Java) the Java Support
Package Manager (JSPM) will necessarily restart the system several times to make the changes
effective The ABAP part will only be restarted when JSPM is updating the SAP kernel and IGS
212 Preparation
Procedure
Read SAP Note 822379 and all related SAP Notes that the first one refers to
213 Updating the Application Server ABAP and ABAP-Based Software Components
Procedure
Applying Support Packages to SAP NetWeaver Application Server ABAP and ABAP-Based Components
You can update the SAP NetWeaver Application Server ABAP and all ABAP-based software components
running on it using the Support Package Manager (transaction SPAM)
NOTE
If a particular Support Package Stack requires the installation or upgrade of some add-on
components you must use the ABAP Add-on Installation Tool (transaction SAINT) instead of the
Support Package Manager In this case SAINT is able to import both the add-on components and
the related Support Packages of ordinary SAP components
Proceed as follows
1 Log on to the SAP NetWeaver AS system with client 000
2 Start the Support Package Manager by calling transaction SPAM or
start the Add-On Installation Tool by calling transaction SAINT
3 Load the relevant Support Packages or add-on installation packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
1660 CUSTOMER 2012-08-30
4 Define an import queue
5 Perform the import of the defined queue
NOTE
If you have modified SAP objects in your system and these objects are included in the Support
Packages you must perform modification adjustment during the import using the
transactions SPDD (for ABAP Dictionary objects) and SPAU (for Repository objects)
To import the queue you use the standard scenario You can choose between the conventional
import mode and downtime-minimized import mode
Conventional Import Mode
This option comprises the following steps
1 Update the SAP kernel and SAP IGS as described in section Updating SAP Kernel and SAP IGS below
Start the system after the kernel update
2 Import the ABAP Support Packages with the Support Package Manager (SPAM)
Import Mode Downtime-Minimized
This option can be used to reduce system downtime during the update It comprises the following
steps
1 In transaction SPAM enable the downtime-minimized import mode by choosing Extras
Settings then on the Import queue tab page choose Standard and activate the option Import Mode
Downtime-Minimized
2 Import the ABAP Support Packages into the system in an inactive state in the downtime-minimized
mode during system uptime
3 Update the SAP kernel and SAP IGS as described in section Updating SAP Kernel and SAP IGS below
Start the system after the kernel update
4 Complete the ABAP Support Packages import
CAUTION
During this step the system cannot carry out any business transactions (business downtime)
NOTE
In rare cases due to the dependencies of some Support Packages on a particular kernel patch level
the downtime-minimized update does not work In such cases the Support Package Manager
informs you that you must update the SAP kernel before importing ABAP Support Packages You
must proceed with the conventional import procedure
Updating SAP Kernel and SAP IGS
In general the SAP kernel and IGS binaries are located in the global kernel directory DIR_CT_RUN on
the host indicated by the profile parameter SAPGLOBALHOST Once the files in this directory have been
updated to a new patch level a system restart distributes them by means of the program SAPCPE to the
local directories DIR_EXECUTABLE on the hosts where the instances of the SAP system are running
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
2012-08-30 CUSTOMER 1760
CAUTION
The automatic distribution by means of SAPCPE depends on the settings of the profile parameters
DIR_CT_RUN for the global kernel directory and DIR_EXECUTABLE for the local directory of the
executables Before you continue check the instance profiles for the settings of these parameters
in systems that are not installed using SAPinst (for example systems upgraded from older releases
copied or migrated systems)
CAUTION
If your system is a dual-stack system (ABAP+Java) and the ABAP stack has a non-Unicode kernel
be aware that the SCS instance has a Unicode kernel You have to update both kernels (together
with SAP IGS) prior to updating the ABAP and Java Support Package stacks This ensures
compatibility and reduces system downtime
RECOMMENDATION
If you perform an update of a dual-stack system (ABAP+Java) we recommend that prior to
applying ABAP and Java Support Package stacks you use the Single Support Packages option in JSPM
and select for update only the components SAP KERNEL and BC-FES-IGS
For more information about updating a dual-stack system see Parallel Update of Dual-Stack Systems
[page 28]
If you perform an update of an ABAP system the following procedure applies for updating the SAP
kernel and IGS manually
1 Log on as user ltsapsidgtadm to the instance host to be updated
2 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory using
SAPCAR [page 56]
3 Stop the ABAP system that you want to update
NOTE
If the system is running in a high availability (HA) environment make sure that the HA
software does not restart the system automatically during the update
4 Back up the kernel directory ltkrnl_directorygt
5 Copy or move the extracted programs from the temporary directory to the SAP kernel directory
6 Only valid for UNIX |
Execute the following command sequence on UNIX platforms
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
1860 CUSTOMER 2012-08-30
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
7 Restart the SAP system
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS) runs
on a dedicated host You need to perform the kernel update for the ASCS instance manually but
excluding the IGS update because the IGS is not required in an ASCS instance
In rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of such instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances manually Proceed as described
in section Manually Updating Instances with Kernel Directory Located on Separate Hosts below in this document
214 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the ABAP system
22 Application Server Java and Java-Based Software Components
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system which includes
JSPM itself
SAP Kernel and SAP IGS
All Java-based usage types installed in the system
Software Deployment Manager (SDM) - the deployment service of the system
RECOMMENDATION
We strongly recommend that you apply the target Support Package Stack to your system as a
whole This ensures consistency on both the system and the application levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 1960
221 Planning
Procedure
Java Support Package files (SCAs) contain all software objects of the corresponding software
components Thus it is sufficient to apply the Java Support Package files of the intended Support Package
Stack directly to the Java system to be updated It is not necessary to apply the Support Package Stacks
between the start SP Stack level and the target SP Stack level successively
CAUTION
When applying a Support Package Stack to a Java system the Java Support Package Manager (JSPM)
will necessarily restart the system several times to make the changes effective With a dual-stack
system (ABAP+Java) the ABAP part will only be restarted when JSPM is updating the SAP kernel
and IGS
The following components belong to the usage type SAP NetWeaver Application Server Java (AS Java)
Software Components of Application Server Java
Component to Be Updated SP File Name Tool Used to Apply SP
SAP Kernel 720 32-64-BIT UNICODE SAPEXESAR
SAPEXEDBSAR
JSPM
SAP IGS 700 igsexesar
BI META MODEL REPOSITORY 702 BIMMRltSPgt_ltPLgtSCA
J2EE ENGINE CORE TOOLS 702 CORETOOLSltSPgt_ltPLgtSCA
J2EE ENGINE BASE TABLES 702 BASETABLESltSPgt_ltPLgtSCA
BI UDI 702 BIUDIltSPgt_ltPLgtSCA
DI BUILD TOOL 702 SAPBUILDTltSPgt_ltPLgtSCA
SAP CAF 702 CAFltSPgt_ltPLgtSCA
SAP IKS 702 KMKWJIKSltSPgt_ltPLgtSCA
JAVA LOG VIEWER 702 JLOGVIEWltSPgt_ltPLgtSCA
SAP J2EE ENGINE CORE 702 SAPJEECORltSPgt_ltPLgtSCA
SAP JAVA TECH SERVICES 702 SAPJTECHSltSPgt_ltPLgtSCA
SAP TECH S OFFLINE 702 SAPJTECHFltSPgt_ltPLgtSCA
SAP J2EE ENGINE 702 SAPJEEltSPgt_ltPLgtSCA
JAVA SP MANAGER 702 JSPMltSPgt_ltPLgtSCA
ADOBE DOCUMENT SERVICES 702 ADSSAPltSPgt_ltPLgtSCA
UME ADMINISTRATION 702 UMEADMINltSPgt_ltPLgtSCA
LIFECYCLE MGMT TOOLS 702 LMTOOLSltSPgt_ltPLgtSCA
SAP CAF-UM 702 CAFUMltSPgt_ltPLgtSCA
SAP SOFTW DELIV MANAGER 702 SDMKITltSPgt_ltPLgtJAR
SOFTWARE LIFECYCLE MANAGER 702 SWLIFECYCLltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2060 CUSTOMER 2012-08-30
NOTE
This table contains only software components that belong to the usage type AS Java Software
components of other usage types and Java application units are listed in the corresponding
sections
NOTE
As of Support Package 09 you can update your system with SAP Kernel 720 instead of SAP Kernel
701
222 Preparation for Applying a Support Package Stack
Procedure
1 Download the Support Package Stack with all usage types to be updated and the stack definition
XML file as described in Downloading Support Package Stacks [page 12]
NOTE
You can find the activated usage types in an existing Java system on the Deployed Components tab
page on the JSPM user interface
NOTE
You do not need to download the SP Stacks between the source SP Stack level and target SP
Stack level By default the target SP Stack level is the latest available SP Stack
2 Make sure the following requirements are met prior to applying the Support Package Stack
You have familiarized yourself with SAP Note 891983 before you start the Java Support Package
Manager
The system to be updated is fully functional
The Support Package Stack you want to apply and the corresponding stack definition XML
file are available in the EPS inbox directory usrsaptransEPSin By default this location
can be also referred to as ldquoJSPM inboxrdquo
The SAP NetWeaver Application Server Java (AS Java) and the database have been backed up
You have not deleted renamed or created any directories and files in the following directories
and their subdirectories usrsapltSAPSIDgtSYSexe and usrsapltSAPSIDgtSYS
profile
Otherwise JSPM cannot detect the kernel and the system profiles and cannot be started If a
backup of the kernel and the system profiles has been required it has been created in a different
directory
The ltsapsidgtadm user has Read permissions for the EPS inbox directory usrsaptransEPS
in
If your database is SAP MaxDB the overwrite mode for the log area has been activated
The database and the SDM repository have been synchronized
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2160
For more information see the online documentation for JSPM on SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70 Library
(including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library Administrators Guide
Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems AS Java
(Application Server for Java) Software Logistics Software Maintenance Java Support Package Manager
Then choose Troubleshooting JSPM Does Not Update the Versions of the Deployed Components
There is enough disk space
For more information see SAP Note 891895
Your current SAPCAR tool is able to extract the Support Packages for the SAP kernel and
other OS level binaries delivered as SAR files
RECOMMENDATION
You can download the latest version of SAPCAR from SAP Service Marketplace at
httpservicesapcompatches Entry by Application Group Additional Components
SAPCAR
Put the downloaded version in the same directory in the JSPM inbox in which the kernel
SAR files reside so that JSPM can use this version for extracting the SAR files
3 Only valid for Linux |
For RHEL 4 and SLES 9 you need to install additional operating system packages For more
information see SAP Note 1021236End of Linux |
4 Only valid for Windows |
For Windows you need to install additional operating system packages For more information see
SAP Note 684106End of Windows |
5 To prevent the Software Deployment Manager (SDM) from temporarily exceeding the available
disk space during the update process you can change the file transfer directory of SDM in a system
of SPS09 or higher using the following command sequence
Only valid for Windows |
cd ltsdm_homegt
StopServerbat
sdmbat jstartup mode=standalone
sdmbat filetransferdir dir=ltnew_dirgt
sdmbat jstartup mode=integrated
StartServerbat
End of Windows |
Only valid for IBM i5OSUNIX |
cd ltsdm_homegt
StopServersh
sdmsh jstartup mode=standalone
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2260 CUSTOMER 2012-08-30
sdmsh filetransferdir dir=ltnew_dirgt
sdmsh jstartup mode=integrated
StartServersh
End of IBM i5OSUNIX |
6 To prevent deployment errors during the update process proceed as follows
1 Log on to the Central Instance host
2 Start the ConfigTool and in the navigation area choose Cluster-data Global server configuration
Managers ServiceManager
3 In the Global properties panel set the Custom value of the EventTimeout property to 120
4 Choose Save
5 Restart the Central Instance
7 Check whether the used JDK version and the Java VM settings of the Java runtime system comply
with the requirements in SAP Note 723909 Update the JDK and adjust the settings if necessary
NOTE
An update of the used JDK version possibly changes the JVM path In this case you must
make the new path available to all Dialog Instances of the J2EE engine by implementing option
1 of SAP Note 718901
8 Make sure that the J2EE administrator password stored in the secure store for offline usage is
identical with the one stored in the User Management Engine (UME) You can change the password
in the secure store as described in SAP Note 870445
9 If you are running a high availability system on Windows you might need to prepare your system
as described in the online documentation for JSPM see section Preparing Systems That Run in High
Availability Environment
223 Updating the Application Server Java and Java-Based Components
Procedure
Applying a Support Package Stack to SAP NetWeaver Application Server Java and Java-Based Components
NOTE
The JSPM GUI might not work properly on some UNIX systems For more information and the
solution see SAP Note 1013976
1 Log on as user ltsapsidgtadm to the Central Instance host
NOTE
If your operating system is IBM i log on as user ltSIDgtADM or ltSIDgtOFR
2 Close the SAP Management Console (SAP MMC) and the SDM remote GUI client
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2360
3 For UNIX and Windows To start the JSPM navigate to the directory ltINSTDIRgtltSIDgt
ltCentral_Instance_Namegtj2eeJSPM and run the go script file
NOTE
If your system is running on IBM i to start the JSPM proceed as follows
1 To prevent JSPM from automatically starting its GUI in the file usrsapltSIDgt
ltCentral_Instance_Namegtj2eeJSPMparamjspm_configtxt change the
property dialogSDTServerConnectionSDTGuilaunch from true to false
2 On the IBM i host run the go script file using the following command
QSH CMD(usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPMgo)
3 In the mounted directory usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPM run
the StartGui script file The JSPM GUI appears
4 In the Host field enter the target IBM i host
NOTE
Depending on the system type ltCentral_Instance_Namegt has the following syntax
Standalone Java system JCltinstance_nogt
Add-On system DVEBMGSltinstance_nogt
4 Enter your SDM password to log on to the SDM
5 On the Deployment tab page select the Java Support Package Manager option and update the software
component sapcomJSPM to the target SPS level
6 Restart the JSPM and log on with the SDM password
RECOMMENDATION
We strongly recommend that you use the Support and Enhancement Package Stack option when
applying a Support Package Stack Other options can lead to unintended consistency issues
NOTE
If you need to include the latest patches for a particular component during the update process
with the Support and Enhancement Package Stack option stop the JSPM after restart and apply SAP
Note 1080821 Then start the JSPM again
7 On the Deployment tab page select the Support and Enhancement Package Stack option and choose Next
The Support Package Stacks that are available for deployment in the global EPS inbox directory
are displayed
8 In the Target SP Stack Level dropdown box select the Support Package Stack to be applied and choose
Next
In this step JSPM performs various status validations and displays the result of each software
component included in the stack definition XML file on the subsequent screen which includes
the following possible statuses
OK Indicates that the SPS level of the corresponding software component is applicable
WARNING We recommend that you view the details about the component by choosing Show
Details
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2460 CUSTOMER 2012-08-30
This status may indicate that the corresponding software component comprises custom
modifications in an NWDI-controlled system
If your system is used for NWDI development and it is either a DEV or a CONS system
you will be informed that JSPM will not deploy the modified software components but
only transport them to the CMS transport directory JSPM will deploy only the software
components that are not modified
If your system is not used for NWDI development or if your system is used for NWDI
development and it is either a TEST or a PROD system you will be informed that JSPM
has found newer versions of modified software components and will automatically replace
the original versions with the newer versions JSPM will deploy all software components
that are not modified together with the replaced versions of the modified software
components
CAUTION
You may get a warning telling you that there are patches installed in your system
containing fixes which might not be included in the target SP Stack This is possible if
you have applied patches of the start SP Stack level that were delivered later than the
target SP Stack delivery date In order not to lose these fixes you need to download and
apply the corresponding patches of the target SP Stack level
If you are performing an update from SAP NetWeaver 70 including enhancement
package 1 SPS00 and you have not applied any patches for the software component with
status WARNING before the update then you can ignore warnings such as the following
example
The new version of the development component sapcomcomsapnetweaver
bcrfmoni is 70100200806121227180000 and is lower than the already
deployed version 70100200807090143420000
REVISE Indicates inconsistencies with the corresponding software component
The deployment cannot be performed until all problems have been resolved You can view
the problems by choosing Show Details
9 If the status of the selected SP Stack is OK or WARNING you can start the system update by choosing
Start JSPM then changes the status to SCHEDULED
If the SP Stack to be applied includes a kernel update and the current kernel is not already of the
corresponding patch level JSPM arranges the kernel update as the very first Support Package to
be applied JSPM updates the kernel binaries of all instances (including Dialog Instances and SCS
instances in a HA environment) whose kernel directories DIR_CT_RUN effectively reside on the host
indicated by the profile parameter SAPGLOBALHOST
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2560
CAUTION
Kernel binaries of instances whose kernel directories DIR_CT_RUN are not effectively linked
to the host SAPGLOBALHOST must be updated individually as described in section Manually
Updating Instances with Kernel Directory Located on Separate Hosts below
The kernel update (includes update of SAP Kernel and SAP IGS) using JSPM consists of the following
steps
1 JSPM stops the Central Instance automatically and prompts you to stop the remote SCS and
Dialog Instances manually
2 After you have stopped all the instances choose the Next button in the dialog box
The kernel update starts
NOTE
If the system is running in a high availability environment make sure that the HA
software does not restart the instance automatically during the update
NOTE
If kernel binaries of the SCS instance need to be updated manually (see Manually Updating
Instances with Kernel Directory Located on Separate Hosts below) you must perform this at the
time when JSPM is updating the kernel binaries of the Central Instance In any case the
SCS kernel must be up-to-date before the next restart
When the kernel update is finished a dialog box appears in which you are prompted to restart
the SCS instance manually
3 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries
before you can proceed with the next step For more information see Adjusting the Ownership and
Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
4 Choose Next in the dialog box when the SCS instance is running again
After the kernel update JSPM restarts the system for further deployment of the remaining Support
Packages in the stack
RECOMMENDATION
If you need to update the kernel binaries of any Dialog Instances manually (see Manually
Updating Instances with Kernel Directory Located on Separate Hosts below) perform the update when
JSPM is updating the remaining Support Packages in the stack in order to save time
The deployment of each Support Package can end with one of the following statuses
DEPLOYED
The Support Package has been successfully deployed
DEPLOYED WITH WARNING
The Support Package has been deployed but it possibly may not work properly with other
deployed components
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2660 CUSTOMER 2012-08-30
You can view the details by choosing Show Details or examining the log files You can also view
the details about the component by choosing the Deployed Components tab page
ERROR
An error has occurred during the deployment You can view the details by choosing Show
Details or examining the log files
You must correct the error to be able to continue with the SP Stack update
You can proceed as described for a deployment that finished with status DEPLOYED WITH
WARNING
If the error correction does not change the contents in the JSPM inbox you can continue
the deployment by choosing Resume
If the error correction changes the contents in the JSPM inbox you can choose New
Deployment to redeploy the SP Stack
NOT DEPLOYED
JSPM has not attempted to deploy the software component for certain reasons
If your system is not used for NWDI development you can proceed as described for a
deployment that finished with status ERROR
If your system is used for NWDI development and it is either a DEV or a CONS system
the status of the modified software components is always NOT DEPLOYED JSPM has
transported the software components of the Support Package Stack both modified and
not modified to the CMS transport directory The deployment of the modified software
components is handled by NWDI
Manually Updating Instances with Kernel Directory Located on Separate Hosts
JSPM performs kernel update for all instances (including Dialog Instances and SCS instances in a HA
environment) whose kernel directories DIR_CT_RUN effectively reside on the host indicated by the profile
parameter SAPGLOBALHOST (by using folder sharing on Windows or file system mounting on UNIX) In
rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of those sort of instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances individually
To update the kernel of an instance manually proceed as follows
1 Log on as user ltsapsidgtadm to the host of the instance to be updated
2 Back up the kernel directory which is specified by the profile parameter DIR_CT_RUN
3 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory with
SAPCAR [page 56]
4 Stop the instance being updated
NOTE
If the system is running in a HA environment make sure that the HA software does not
restart the instance automatically during the update
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2760
5 Copy or move the extracted programs from the temporary directory to the local kernel directory
6 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries as
described in section Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
7 Restart the instance after JSPM has finished the deployment of all packages on the Central Instance
Only valid for UNIX |
Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms
On UNIX platforms you must adjust the ownership and execution permissions of the kernel binaries
after the update regardless whether you performed the update manually or by using JSPM because
both update procedures are performed with the ltsapsidgtadm user Enter the following command
sequence
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
224 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the Java system
23 Parallel Update of Dual-Stack Systems
If you perform an update of a dual-stack system (ABAP+Java) we recommend that you follow the
procedure described below The procedure has been validated to update the ABAP stack and the Java
stack of a NetWeaver system in parallel thus reducing the overall system downtime by half
Procedure
1 Before applying ABAP and Java Support Packages use the Single Support Packages option in JSPM and
select for update only the components SAP KERNEL and BC-FES-IGS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
23 Parallel Update of Dual-Stack Systems
2860 CUSTOMER 2012-08-30
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS)
runs on a dedicated host In this case JSPM does not support update of kernel binaries and
you need to update them manually Perform the update manually as described under Updating
SAP Kernel and SAP IGS in section Updating the Application Server ABAP and ABAP-Based Software
Components [page 16]
2 Import the Support Packages for the component SAP_BASIS into the ABAP stack using the ABAP
Support Package Manager (SPAM)
3 Import the remaining ABAP Support Packages with SPAM and in parallel apply the Java Support
Package Stack with JSPM
Proceed as described in Updating the Application Server ABAP and ABAP-Based Software Components [page
16] and Updating the Application Server Java and Java-Based Software Components [page 23]
24 Process Integration
241 Planning
Procedure
This section covers all the units of Process Integration that should be updated Particularly the following
units must always have the same Support Package level (the patch level can be different)
Integration Server
XI Adapter Engine
Partner Connectivity Kit
System with the Usage Type Process Integration
Software components of Integration Server
Components to Be Updated SP File Name Tool Used to Apply SP
Java stack
XI TOOLS 702 SAPXITOOLltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
ABAP stack
XI CONTENT SAP_BASIS 702 SAPBASISltSPgt_ltPLgtZIP File upload
XI CONTENT SAP_ABA 702 SAPABAltSPgt_ltPLgtZIP
SAP NetWeaver Application Server ABAP (see table Software components of Application Server ABAP [page 15])Note that update of the following software components of the ABAP system is not required SAP ABA 702 SAP BW 702 PI_BASIS 702
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 2960
J2EE Adapter Engine
If your implemented scenario includes a J2EE Adapter Engine then it must always be of the same
Support Package level as the Integration Server
Components of the J2EE Adapter Engine
Component to Be Updated SP File NameTool Used to Apply SP
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
J2SE Adapter Engine
The installation of the J2SE Adapter Engine depends on the implemented scenario
Components of the J2SE Adapter Engine
Component to Be Updated SP File Name Tool Used to Apply SP
XI CONNECTIVITY SE 702 SAPXICONSltSPgt_ltPLgtSCA ZIP tool (for example WinZip)
Partner Connectivity Kit
If your implemented scenario includes a Partner Connectivity Kit (PCK) then it must always be of the
same Support Package level as the Integration Server
Software components of Partner Connectivity Kit
Components to Be Updated SP File NameTool Used to Apply SP
XI PCK 702 SAPXIPCKltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of the Application Server Java [page 20])
System Landscape Directory (SLD)
The System Landscape Directory is required for the PI operations Although updating the SLD is not
necessarily required it is advisable to update the SLD server and the SAP Master Data Content within
it from time to time The update of the SLD includes
1 The system where the SLD is running
2 The SAP Master Data Content within this SLD
SAP GUI
See table Compatible SAP GUI Versions [page 51]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3060 CUSTOMER 2012-08-30
242 Updating Units of Process Integration
Procedure
Before you start the update perform the following steps
In the Runtime Workbench use Communication Channel Monitoring to stop all sender channels
for all adapter types on all your Adapter Engines
On the Integration Server use transaction SMQR and deregister all qRFC queues
System with the Usage Type Process Integration
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the XI instance is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system where the XI instance is running
For more information see Application Server Java and Java-Based Software Components [page 19]
System Landscape Directory (Optional)
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the SLD is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the entire Support Package Stack to the system where the SLD is running
For more information see Application Server Java and Java-Based Software Components [page 19]
J2EE Adapter Engine
Apply the Support Package Stack to the system where the Adapter Engine is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Partner Connectivity Kit
Apply the Support Package Stack to the system where the PCK is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Front End GUIs
Update the SAP GUI components if necessary
For more information see SAP GUI Family [page 51]
ABAP 700 Business System (Optional)
Apply the Support Packages for SAP NetWeaver Application Server ABAP (including SAP kernel and
the Support Package for SAP BASIS 700)
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 640 Business System (Optional)
Apply the Support Packages for SAP Web Application Server ABAP 640 (including SAP kernel and the
Support Package for SAP BASIS 640)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3160
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 620 Business System (Optional)
1 Update the SAP Kernel 620
2 Import the released Basis Support Packages for SAP Web AS 620 as well as the most recent Add-
On Support Package for APPINT 200_620 in the order described in SAP Note 439915
J2SE Adapter Engine (Optional)
NOTE
The XI Adapter Engine (J2SE) and all its adapters are provided for compatibility reasons only and
are not developed any further You have to use the XI Adapter Engine running on SAP NetWeaver
AS Java For more information see the Master Guide ndash SAP NetWeaver 70 available on SAP Service
Marketplace at httpservicesapcominstallNW70 Planning
1 Extract the SAPXICONSltSPgt_ltPLgtSCA (XI Connectivity SE 700) archive (ZIP format) to a temporary
directory
2 Save the old configuration files as described in the document Adapterpdf in directory
lttemp_directorygttech_adapterAdministrationDocumentation
3 Unpack the ZIP archive TechnicalAdapterssda to the installation directory of the XI Adapter
Engine (J2SE)
4 Restore the configuration files with restore_configuration
243 Post-Installation Steps
Procedure
Communication Channels and Queues
Restart all stopped sender channels and register all deregistered qRFC queues
XI Content
In the system with usage type PI import the XI content from the archives SAPBASISltSPgt_ltPLgtZIP
and SAPABAltSPgt_ltPLgtZIP as follows
1 Unpack the archives using a ZIP tool of your choice
2 Copy the corresponding export files (with file extension tpz) to the import directory ltINSTDIRgt
ltSAPSIDgtSYSglobalxirepository_serverimport
3 Start the Integration Builder (transaction SXMB_IFR)
4 Enter the Integration Repository by choosing Repository (Design)
5 Choose Tools Import design objects
6 Import the tpz files containing the XI content
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3260 CUSTOMER 2012-08-30
NOTE
For more information see SAP Note 836200
Role Generation on the Integration Server
On the Integration Server execute transaction SUPC (mass generation of roles) for all SAP_XI roles in
each of your clients to regenerate possibly changed roles
NOTE
Do not forget to make a user comparison for regenerated roles afterwards
Partner Connectivity Kit (Optional)
Perform the post-installation steps for PCK as described in SAP Note 746328
SAP Master Data within the SLD (Optional)
In the system where your SLD is running import the latest SLD content as described in SAP Note
669669
Receiver-Based EOIO Serialization in J2EE Adapter Engine (Optional)
The J2EE Adapter Engine can be switched to receiver-based EOIO serialization The switch can be
triggered on demand and is executed asynchronously It includes a database migration step during
which all EOIO processing in the Adapter Engine is disabled See SAP Note 973894 for details about how
to start the EOIO serialization migration
Service Metering (Optional)
Service metering gathers information about a service caller transfers it to the service provider and
counts on the service provisioning side how many times a service is called and by which service caller
Service metering is performed for the XI message protocol and the WS message protocol Service
metering is automatically enabled after applying a Support Package Stack By default only non-sensitive
data is transmitted to internal or external service providers in a compatible way
Service metering can be configured in PI in the Integration Engine on sender-side and in the Integration
Directory
Service metering can be configured in AS ABAP in transaction SOAMANAGER
Only if the service provider is allowed to receive more detailed information about the service caller set
the metering level to higher than the default
For more information see SAP Note 1239428
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3360
25 Business Intelligence
251 Planning
Procedure
Business Intelligence includes one or many of the following units that must be updated depending on
your implemented scenarios The usage types Business Intelligence (BI) and Business Intelligence Java
Components (BI-Java) must always have the same Support Package level
Business Intelligence
Software Components of Business Intelligence
Component to Be Updated SP File Name Tool Used to Apply SP
BI CONT ADDON 70x SAPK-70ltxgtltSPgtINBICONT SAINT
SAP NetWeaver Application Server ABAP (see table Software Components of Application Server ABAP [page 15])
NOTE
For information about the dependencies applying to BI Content Support Packages see SAP Note
653814 BI CONT 703 Support Packages are not part of the NetWeaver SP Stacks Updates can be
performed when applicable Alternatively BI CONT 704 Support Packages can be imported See
the BI Content release strategy in SAP Note 153967
Business Intelligence Java Components
BI Java Components
Component to Be Updated SP File NameTool Used to Apply SP
BI REPORTING AND PLANNING 702 BIREPPLANltSPgt_ltPLgtSCA JSPM
BI WEBDYNPRO ALV 702 BIWDALVltSPgt_ltPLgtSCA
BI INFORM BROADCASTING 702 BIIBCltSPgt_ltPLgtSCA
BI WEB APPLICATIONS 702 BIWEBAPPltSPgt_ltPLgtSCA
BI BASE SERVICES 702 BIBASESltSPgt_ltPLgtSCA
VISUAL COMPOSER BI KITS 702 VCKITBIltSPgt_ltPLgtSCA
Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
BI Precalculation Service
Components of the BI Precalculation Service
Component to Be Updated SP File Name Tool Used to Apply SP
BI Pre-calculation Service 700 xPreCalServerltSPgt_ltPLgtexe Installer
Search and Classification (TREX)
See table TREX Component [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3460 CUSTOMER 2012-08-30
BI Accelerator
The BI Accelerator is based on the TREX technology It is a special Linux 64-bit version of SAP NetWeaver
70 Search and Classification (TREX) which is delivered on preconfigured hardware
NOTE
You cannot use a TREX installation based on 32-bit architecture that is configured for searching
in metadata and documents for the BI Accelerator And vice versa a BI Accelerator box cannot
be used for searching in metadata and documents
If you want to use the search functionality as well as the BI Accelerator you require two separate
installations For more information see BI Accelerator [page 47]
Clients
Depending on your implemented scenarios you have to update SAP GUI Components and Business
Explorer (BI Add-OnBW Add-On)
NOTE
See SAP Note 889314 to determine when to use the BI Add-On and the BW Add-On
NOTE
As SAP GUI 640 is no longer supported BI Frontend Support Package 1800 resp patch 1801 is the
last Support Package resp patch based on SAP GUI 640 For more information see SAP Note
1231292 (Frontend Add-in Strategy 640710 GUI Version)
For more information about the new release strategy for the BI Frontend see SAP Note 1231363
(Changed Delivery Strategy for BI Frontend)
252 Preparation
Procedure
For the Support Packages of the most important Business Intelligence units so called SAPBINews
(SAPBWNews) Notes are created Read these Notes before updating Business Intelligence For SAP
NetWeaver 70 including enhancement package 2 SPS 12 these are the following
Business Intelligence ABAP SAP Note 1680996
Business Intelligence Java Components SAP Note 1726461
BI 70 Frontend Add-On for SAP GUI 710 SAP Note 1413032
BI 70 Frontend Add-On for SAP GUI 720 SAP Note 1630112
BI 70 Frontend Add-On for SAP GUI 730 SAP Note 1726739
For more information about BI Support Packages see SAP Community Network at http
scnsapcomcommunitydata-warehousingnetweaver-bw Related Resources SAP NW BW Support
Packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
2012-08-30 CUSTOMER 3560
253 Updating Units of Business Intelligence
Procedure
Business Intelligence
1 Update the SAP NetWeaver Application Server ABAP (with BI CONT 70x if necessary) with the
appropriate Support Packages
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
NOTE
When applying the component SAP BW 702 some generation errors might occur When
you start importing the BI Support Packages in transaction SPAM choose the menu path
Extras Ignore generation errors For more information see SAP Note 114134
2 Apply the Support Package Stack to the system with the usage type BI-Java
For more information see Application Server Java and Java-Based Software Components [page 19]
3 Update the BI Precalculation Service that is used in your scenario
4 Update the standalone engine Search and Classification (TREX) that is used in your scenario For more
information see Standalone Engine Search and Classification (TREX) [page 44]
NOTE
You have to update TREX to the newest version if you use search capabilities within Business
Intelligence
5 Update the BI Accelerator to the newest available version For more information see BI
Accelerator [page 47]
6 Update the SAP GUI and Business Explorer (BI Add-On BW Add-On) on all remote client hosts
that are involved in the scenario
For more information see SAP GUI Family [page 51] and Business Explorer (BI Add-On BW Add-On)
[page 51]
BI Precalculation Service
1 Log on to the host as a user with administration rights
2 Install the Support Package of the BI Precalculation Service by executing the
xPreCalServerexe file
The welcome screen of the BI Precalculation Server setup wizard appears
The setup now checks the system for the prerequisites
3 Choose the option Update for updating the BI Precalculation service to the current patch level and
then Finish
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3660 CUSTOMER 2012-08-30
26 EP Core
261 Planning
Procedure
The following installable software units must be updated
EP Core
Software Components of EP Core
Component to Be Updated SP File Name Tool Used to Apply SP
PORTAL CORE SERVICES 702 EPBCltSPgt_ltPLgtSCA JSPM
PORTAL FRAMEWORK 702 EPBC2ltSPgt_ltPLgtSCA
PORTAL 702 EPPSERVltSPgt_ltPLgtSCA
PORTAL WEB DYNPRO 702 EPWDCltSPgt_ltPLgtSCA
UWL COLL PROCESS ENGINE 702 UWLJWFltSPgt_ltPLgtSCA
CAF EU 702 SAPEUltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
262 Preparation
Procedure
Backing Up the Portal Runtime Configuration
If you have made changes to the standard Portal Runtime configuration you have to make a backup
of the configuration before the update process For more information see SAP Note 1064468
263 Updating EP Core
Procedure
Apply the Support Package Stack to a system with usage type EP Core
For more information see Application Server Java and Java-Based Software Components [page 19]
264 Post-Installation Steps for EP Core
Procedure
Restoring the Portal Runtime Configuration
To make your changes to the standard Portal Runtime Configuration effective you have to restore
the backup of the configuration done before the update process For more information see SAP Note
1064468
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
26 EP Core
2012-08-30 CUSTOMER 3760
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
Document History
CAUTION
Before you start the implementation make sure you have the latest version of this document
You can find the latest version on SAP Service Marketplace at httpservicesapcom
instguides
The following table provides an overview on the most important document changes
Version Date Description
100 2012-08-30 First version
2012-08-30 CUSTOMER 560
Table of Contents
Chapter 1 Overview 9
11 Before You Start 9
12 Types of Support Packages 11
13 Downloading Support Package Stacks 12
Chapter 2 Applying Support Packages to Installable Software Units of SAP
NetWeaver 70 Including Enhancement Package 2 15
21 Application Server ABAP and ABAP-Based Software Components 15
211 Planning 15
212 Preparation 16
213 Updating the Application Server ABAP and ABAP-Based Software
Components 16
214 Post-Installation Steps 19
22 Application Server Java and Java-Based Software Components 19
221 Planning 20
222 Preparation for Applying a Support Package Stack 21
223 Updating the Application Server Java and Java-Based
Components 23
224 Post-Installation Steps 28
23 Parallel Update of Dual-Stack Systems 28
24 Process Integration 29
241 Planning 29
242 Updating Units of Process Integration 31
243 Post-Installation Steps 32
25 Business Intelligence 34
251 Planning 34
252 Preparation 35
253 Updating Units of Business Intelligence 36
26 EP Core 37
261 Planning 37
262 Preparation 37
660 CUSTOMER 2012-08-30
263 Updating EP Core 37
264 Post-Installation Steps for EP Core 37
27 Enterprise Portal 38
271 Planning 38
272 Updating Enterprise Portal 38
273 Post-Installation Steps for Enterprise Portal 39
28 Development Infrastructure 40
281 Planning 40
282 Updating Development Infrastructure 41
29 Mobile Infrastructure 43
291 Planning 43
292 Preparation 43
293 Updating Mobile Infrastructure 43
210 Standalone Engines 44
2101 Search and Classification (TREX) 44
21011 Planning 44
21012 Preparation 44
21013 Updating TREX 45
2102 BI Accelerator 47
21021 Planning 47
21022 Preparation 48
21023 Updating BI Accelerator 48
21024 Post-Installation Steps 49
2103 Gateway 50
2104 SAP Web Dispatcher 50
2105 Other Standalone Engines 50
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2 51
2111 SAP GUI Family 51
2112 Business Explorer (BI Add-On BW Add-On) 51
2113 Other Clients 52
212 SAP Library 52
Chapter A Appendix 55
A1 Determining the Current Component Versions 55
A2 Tools Used During the System Update 56
A21 SAPCAR 56
A22 ABAP Support Package Manager and Add-On Installation Tool 57
A23 Java Support Package Manager 58
2012-08-30 CUSTOMER 760
A3 System Profile Parameters 58
860 CUSTOMER 2012-08-30
1 Overview
This document describes how to install Support Package Stacks (SP Stacks) for SAP NetWeaver 70
including enhancement package 2 You can find all information related to the SP Stacks on SAP Service
Marketplace at httpservicesapcomsp-stacks
11 Before You Start
CAUTION
If you intend to update your system to the latest SP Stack level and plan to upgrade it within the
next 6 months first check the availability of the equivalent SP Stack for the target release The
delivery dates of the equivalent SP Stacks for your source and target release might be several
months apart
Be aware that you cannot upgrade to a target release that does not include the equivalent SP Stack
level
To avoid a deadlock situation we recommend that you check SAP Service Marketplace at
httpservicesapcomsp-stacks SP Stack Information and consider not applying the
latest SP Stack on your source release system
Updated Document Versions
The Support Package Stack Guide is regularly updated on SAP Service Marketplace at http
servicesapcommaintenanceNW70
NOTE
Make sure you have the latest version of the Support Package Stack Guide by checking SAP Service
Marketplace immediately before you start to apply or import Support Packages
SAP Notes
You must read SAP Note 1460321 before you read this document as it may contain corrections and
further information about the Support Package Stack installation
SAP Library
You must inform yourself about enhancements and changes to the Support Package Stack to be applied
from SAP Library under SAP Library SAP NetWeaver Whatrsquos New in SAP NetWeaver 70 ndash Release
Notes You can access the SAP Library in one of the following ways
SAP Help Portal at httphelpsapcomnw702 Application Help SAP Library ltLanguagegt
1 Overview
11 Before You Start
2012-08-30 CUSTOMER 960
NOTE
The SAP Help Portal always provides the up-to-date version of the SAP Library Therefore
we recommend that you use this channel to access the SAP Library
Local installation of the SAP Library from the online documentation DVD
CAUTION
In order to inform yourself about the current Support Package Stack you first have to update
your local installation of the SAP Library to the corresponding SPS level Follow the
instructions in section SAP Library [page 52]
Naming Conventions
In this document the following naming conventions apply
Variables
Variables Description
ltSAPSIDgt
ltsapsidgt
ltSIDgt
SAP system ID
ltINSTDIRgt Installation directory for the SAP system
lthostgt Host name
ltinstance_nogt Instance number of a system instance
ltdatabasegt Name of database
ltsapinst_directorygt Installation directory for the SAP installation tool SAPinst
ltsp_directorygt Temporary directory which the archives of a Support Package are downloaded or copied to
ltOSgt Operating system
ltOS_DIRgt OS-dependent directory consisting of a folder for the platform and a subfolder of your OS versionFor example if you operating system is Sun OS 64bit ltOS_DIRgt stands for UNIXSUNOS64
ltSP_Stackgt Number of Support Package Stack
ltSPgt Support Package level
ltPLgt Support Package patch level
ltRELgt Release number
ltLOCALEgt Language definitionFor example the German locale is _de
ltkrnl_directorygt Kernel directory which the profile parameter DIR_CT_RUN usually refers to
ltsdm_homegt Program file location of the Software Deployment Manager (SDM)
ltSAPGLOBALHOSTgt SAP global host the host where the global directories of an SAP system reside
ltSAPLOCALHOSTgt SAP local host the host where a particular instance of an SAP system is running
1 Overview
11 Before You Start
1060 CUSTOMER 2012-08-30
12 Types of Support Packages
The following table explains the terms used in the correction process as part of the software maintenance
process for SAP NetWeaver
Correction Process Description
Standard correction process
Support Package Stack Description
A Support Package Stack is a set of Support Packages and patches for the respective product version that must be used in the given combination
Version numbersSupport Package Stacks have a release number and a stack number for example SAP NetWeaver 70 Support Package Stack 05
DeliveryThere is no dedicated delivery format for the Support Package Stacks The included Support Package files have their delivery formats and must be applied using the tools as described below
Kernel Patches Version numbers
SAP Kernel patches have a release number and a patch number The patch number is increased with each correction
DeliverySAP Kernel patches are delivered as SAR files They are installed by extracting the SAR files to the kernel directory using SAPCAR Separate SAR files are shipped for the different kernel types depending on UNICODENON-UNICODE and the platform
ABAP Support Packages Description
ABAP Support Packages contain corrections and adjustments for the ABAP-based Software Components of the SAP system
DependenciesIn contrast to Java Support Packages ABAP Support Packages are non-cumulative Therefore ABAP Support Packages must be installed in the correct sequence one after the other You cannot skip any intermediate Support Packages
DeliveryABAP Support Packages are delivered as SAR files They are installed using the Support Package Manager (SPAM)
Java Support Packages Description
Java Support Packages contain corrections for the Java-based Software Components of the SAP system
DependenciesJava Support Packages always contain a full delivery of the Software Components Therefore you only need to apply the latest Support Package to update the software If there are dependencies with other Java Support Packages these are specified in an SAP Note
DeliveryJava Support Packages are delivered as Software Component Archives (SCAs) They are applied using the Java Support Package Manager (JSPM)
1 Overview
12 Types of Support Packages
2012-08-30 CUSTOMER 1160
Correction Process Description
Emergency correction process
SAP Note Correction (ABAP) Description
SAP Note corrections contain single ABAP fixes Delivery
SAP Note corrections are delivered with SAP Notes If required you apply them using the SAP Note Assistant
Java Support Package Patch Description
A Java Support Package patch contains corrections for the Java Software Components Java Support Package patches are created and released on demand A Java Support Package patch corresponds to an SAP Note that describes the same correction
DependenciesA Java Support Package patch always contains a full package of the corresponding Software Component and is applied using JSPM
13 Downloading Support Package Stacks
The Maintenance Optimizer in SAP Solution Manager is the only source from which you can receive
maintenance updates for SAP NetWeaver 70 and higher releases as well as for all applications running
on top of SAP NetWeaver The Maintenance Optimizer supports you in selecting and downloading all
required maintenance files In addition the Maintenance Optimizer generates a stack XML file and
saves it to the EPS inbox directory of SAP Solution Manager
Prerequisites
You have configured the Maintenance Optimizer in SAP Solution Manager as described on SAP Help
Portal at httphelpsapcom SAP Solutions SAP Solution Manager SAP Solution Manager ltReleasegt
ltLanguagegt Change Management Maintenance Optimizer Planning and Monitoring Product Maintenance and
also in section Automatically Calculating Product Maintenance Files
Procedure
To download a Support Package Stack proceed as follows
1 Start SAP Solution Manager using the transaction solution_manager To start the Maintenance
Optimizer choose Operations Change Management Maintenance Optimizer
2 In the Maintenance Optimizer choose the solution for which you want to download SP Stack files
3 Choose Create New Maintenance Transaction
4 Select the product version for which you want to apply a Support Package Stack
The Maintenance Optimizer displays all the systems assigned to the selected product version
5 Select the checkbox for the system that you want to update and choose Continue
6 On the subsequent screen select the Maintenance option and then choose Find Download Files
1 Overview
13 Downloading Support Package Stacks
1260 CUSTOMER 2012-08-30
7 Select the target SP Stack level and the relevant usage types according to the IT scenario to be
updated
8 Choose Find Download Files for the Stack Version
The Maintenance Optimizer displays the product maintenance files in three successive lists
9 Select the required files from the displayed lists
The first list shows all files that are dependent on the type of your operating system and
database
Select the files that correspond to the combination of your operating system and database and
the database-independent files
If your system is distributed on several hosts make sure to select all operating systems used
by the NetWeaver instances You can see all the kernels detected on your system on the Deployed
Components tab page on JSPM user interface (under the SAP KERNEL node) All detected kernels
must be updated to the same version
You get to the second list by choosing Continue This list displays all Support Package files that
are not assigned to the selected Support Package Stack Before you continue with the selection
you must check whether the Support Package files listed here are suitable for your product
maintenance procedure
You get to the third list by choosing Continue The list displays all product maintenance files
that are part of the selected Support Package Stack
Ensure that all files that are assigned to the Support Package Stack are selected here Files that
are not selected will not be included later in the download
10 Choose Continue Use the Download Basket to download the maintenance files
11 Choose Continue once the files have been put in your Download Basket and then Confirm Files in
Download Basket
A dialog window appears and displays all files
12 Confirm the download for all files
13 Open your Download Manager and download the files
NOTE
The stack XML file is generated by the Maintenance Optimizer and automatically saved to
the EPS inbox directory of SAP Solution Manager
More Information
For more information about the Maintenance Optimizer see SAP Support Portal at http
servicesapcomsolman-mopz
1 Overview
13 Downloading Support Package Stacks
2012-08-30 CUSTOMER 1360
This page is left blank for documents that are printed on both sides
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
This chapter describes how to apply Support Packages to installable software units of SAP NetWeaver
70 including enhancement package 2 SAP NetWeaver distinguishes three types of installable software
units
Systems with one or multiple usage types
Standalone engines
Clients
A scenario implementation usually involves several installed software units
RECOMMENDATION
We strongly recommend that you always update all software units belonging to one scenario
together in order to retain a consistent system state Due to the fact that some installable software
units can be commonly shared in different scenarios you must consequently update all scenarios
using the common software units at the same time
21 Application Server ABAP and ABAP-Based Software Components
211 Planning
Procedure
The following components belong to the usage type SAP NetWeaver Application Server ABAP
Software Components of Application Server ABAP
Component to Be Updated SP File Name Tool Used to Apply SP
SAP KERNEL 720 32-64-BIT Non-UNICODEUNICODE SAPEXESAR
SAPEXEDBSAR
JSPMmanually
SAP IGS 700 igsexesar
SAP ABA 702 SAPKA702ltSPgt SPAMSAINT
SAP BASIS 702 SAPKB702ltSPgt
SAP BW 702 SAPKW702ltSPgt
PI_BASIS 702 SAPK-702ltSPgtINPIBASIS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
2012-08-30 CUSTOMER 1560
NOTE
This table contains only software components that belong to the usage type AS ABAP Software
components of other usage types and application units are listed in the corresponding sections
NOTE
SAP delivers intermediate Support Packages for the component SAP BW 702 between two
subsequent SP levels besides the Support Packages delivered along with the Support Package
Stacks Therefore the highest SP level of SAP BW 702 does not necessarily match the target SP
Stack level
CAUTION
When applying a Support Package Stack to a dual-stack system (ABAP+Java) the Java Support
Package Manager (JSPM) will necessarily restart the system several times to make the changes
effective The ABAP part will only be restarted when JSPM is updating the SAP kernel and IGS
212 Preparation
Procedure
Read SAP Note 822379 and all related SAP Notes that the first one refers to
213 Updating the Application Server ABAP and ABAP-Based Software Components
Procedure
Applying Support Packages to SAP NetWeaver Application Server ABAP and ABAP-Based Components
You can update the SAP NetWeaver Application Server ABAP and all ABAP-based software components
running on it using the Support Package Manager (transaction SPAM)
NOTE
If a particular Support Package Stack requires the installation or upgrade of some add-on
components you must use the ABAP Add-on Installation Tool (transaction SAINT) instead of the
Support Package Manager In this case SAINT is able to import both the add-on components and
the related Support Packages of ordinary SAP components
Proceed as follows
1 Log on to the SAP NetWeaver AS system with client 000
2 Start the Support Package Manager by calling transaction SPAM or
start the Add-On Installation Tool by calling transaction SAINT
3 Load the relevant Support Packages or add-on installation packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
1660 CUSTOMER 2012-08-30
4 Define an import queue
5 Perform the import of the defined queue
NOTE
If you have modified SAP objects in your system and these objects are included in the Support
Packages you must perform modification adjustment during the import using the
transactions SPDD (for ABAP Dictionary objects) and SPAU (for Repository objects)
To import the queue you use the standard scenario You can choose between the conventional
import mode and downtime-minimized import mode
Conventional Import Mode
This option comprises the following steps
1 Update the SAP kernel and SAP IGS as described in section Updating SAP Kernel and SAP IGS below
Start the system after the kernel update
2 Import the ABAP Support Packages with the Support Package Manager (SPAM)
Import Mode Downtime-Minimized
This option can be used to reduce system downtime during the update It comprises the following
steps
1 In transaction SPAM enable the downtime-minimized import mode by choosing Extras
Settings then on the Import queue tab page choose Standard and activate the option Import Mode
Downtime-Minimized
2 Import the ABAP Support Packages into the system in an inactive state in the downtime-minimized
mode during system uptime
3 Update the SAP kernel and SAP IGS as described in section Updating SAP Kernel and SAP IGS below
Start the system after the kernel update
4 Complete the ABAP Support Packages import
CAUTION
During this step the system cannot carry out any business transactions (business downtime)
NOTE
In rare cases due to the dependencies of some Support Packages on a particular kernel patch level
the downtime-minimized update does not work In such cases the Support Package Manager
informs you that you must update the SAP kernel before importing ABAP Support Packages You
must proceed with the conventional import procedure
Updating SAP Kernel and SAP IGS
In general the SAP kernel and IGS binaries are located in the global kernel directory DIR_CT_RUN on
the host indicated by the profile parameter SAPGLOBALHOST Once the files in this directory have been
updated to a new patch level a system restart distributes them by means of the program SAPCPE to the
local directories DIR_EXECUTABLE on the hosts where the instances of the SAP system are running
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
2012-08-30 CUSTOMER 1760
CAUTION
The automatic distribution by means of SAPCPE depends on the settings of the profile parameters
DIR_CT_RUN for the global kernel directory and DIR_EXECUTABLE for the local directory of the
executables Before you continue check the instance profiles for the settings of these parameters
in systems that are not installed using SAPinst (for example systems upgraded from older releases
copied or migrated systems)
CAUTION
If your system is a dual-stack system (ABAP+Java) and the ABAP stack has a non-Unicode kernel
be aware that the SCS instance has a Unicode kernel You have to update both kernels (together
with SAP IGS) prior to updating the ABAP and Java Support Package stacks This ensures
compatibility and reduces system downtime
RECOMMENDATION
If you perform an update of a dual-stack system (ABAP+Java) we recommend that prior to
applying ABAP and Java Support Package stacks you use the Single Support Packages option in JSPM
and select for update only the components SAP KERNEL and BC-FES-IGS
For more information about updating a dual-stack system see Parallel Update of Dual-Stack Systems
[page 28]
If you perform an update of an ABAP system the following procedure applies for updating the SAP
kernel and IGS manually
1 Log on as user ltsapsidgtadm to the instance host to be updated
2 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory using
SAPCAR [page 56]
3 Stop the ABAP system that you want to update
NOTE
If the system is running in a high availability (HA) environment make sure that the HA
software does not restart the system automatically during the update
4 Back up the kernel directory ltkrnl_directorygt
5 Copy or move the extracted programs from the temporary directory to the SAP kernel directory
6 Only valid for UNIX |
Execute the following command sequence on UNIX platforms
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
1860 CUSTOMER 2012-08-30
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
7 Restart the SAP system
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS) runs
on a dedicated host You need to perform the kernel update for the ASCS instance manually but
excluding the IGS update because the IGS is not required in an ASCS instance
In rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of such instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances manually Proceed as described
in section Manually Updating Instances with Kernel Directory Located on Separate Hosts below in this document
214 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the ABAP system
22 Application Server Java and Java-Based Software Components
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system which includes
JSPM itself
SAP Kernel and SAP IGS
All Java-based usage types installed in the system
Software Deployment Manager (SDM) - the deployment service of the system
RECOMMENDATION
We strongly recommend that you apply the target Support Package Stack to your system as a
whole This ensures consistency on both the system and the application levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 1960
221 Planning
Procedure
Java Support Package files (SCAs) contain all software objects of the corresponding software
components Thus it is sufficient to apply the Java Support Package files of the intended Support Package
Stack directly to the Java system to be updated It is not necessary to apply the Support Package Stacks
between the start SP Stack level and the target SP Stack level successively
CAUTION
When applying a Support Package Stack to a Java system the Java Support Package Manager (JSPM)
will necessarily restart the system several times to make the changes effective With a dual-stack
system (ABAP+Java) the ABAP part will only be restarted when JSPM is updating the SAP kernel
and IGS
The following components belong to the usage type SAP NetWeaver Application Server Java (AS Java)
Software Components of Application Server Java
Component to Be Updated SP File Name Tool Used to Apply SP
SAP Kernel 720 32-64-BIT UNICODE SAPEXESAR
SAPEXEDBSAR
JSPM
SAP IGS 700 igsexesar
BI META MODEL REPOSITORY 702 BIMMRltSPgt_ltPLgtSCA
J2EE ENGINE CORE TOOLS 702 CORETOOLSltSPgt_ltPLgtSCA
J2EE ENGINE BASE TABLES 702 BASETABLESltSPgt_ltPLgtSCA
BI UDI 702 BIUDIltSPgt_ltPLgtSCA
DI BUILD TOOL 702 SAPBUILDTltSPgt_ltPLgtSCA
SAP CAF 702 CAFltSPgt_ltPLgtSCA
SAP IKS 702 KMKWJIKSltSPgt_ltPLgtSCA
JAVA LOG VIEWER 702 JLOGVIEWltSPgt_ltPLgtSCA
SAP J2EE ENGINE CORE 702 SAPJEECORltSPgt_ltPLgtSCA
SAP JAVA TECH SERVICES 702 SAPJTECHSltSPgt_ltPLgtSCA
SAP TECH S OFFLINE 702 SAPJTECHFltSPgt_ltPLgtSCA
SAP J2EE ENGINE 702 SAPJEEltSPgt_ltPLgtSCA
JAVA SP MANAGER 702 JSPMltSPgt_ltPLgtSCA
ADOBE DOCUMENT SERVICES 702 ADSSAPltSPgt_ltPLgtSCA
UME ADMINISTRATION 702 UMEADMINltSPgt_ltPLgtSCA
LIFECYCLE MGMT TOOLS 702 LMTOOLSltSPgt_ltPLgtSCA
SAP CAF-UM 702 CAFUMltSPgt_ltPLgtSCA
SAP SOFTW DELIV MANAGER 702 SDMKITltSPgt_ltPLgtJAR
SOFTWARE LIFECYCLE MANAGER 702 SWLIFECYCLltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2060 CUSTOMER 2012-08-30
NOTE
This table contains only software components that belong to the usage type AS Java Software
components of other usage types and Java application units are listed in the corresponding
sections
NOTE
As of Support Package 09 you can update your system with SAP Kernel 720 instead of SAP Kernel
701
222 Preparation for Applying a Support Package Stack
Procedure
1 Download the Support Package Stack with all usage types to be updated and the stack definition
XML file as described in Downloading Support Package Stacks [page 12]
NOTE
You can find the activated usage types in an existing Java system on the Deployed Components tab
page on the JSPM user interface
NOTE
You do not need to download the SP Stacks between the source SP Stack level and target SP
Stack level By default the target SP Stack level is the latest available SP Stack
2 Make sure the following requirements are met prior to applying the Support Package Stack
You have familiarized yourself with SAP Note 891983 before you start the Java Support Package
Manager
The system to be updated is fully functional
The Support Package Stack you want to apply and the corresponding stack definition XML
file are available in the EPS inbox directory usrsaptransEPSin By default this location
can be also referred to as ldquoJSPM inboxrdquo
The SAP NetWeaver Application Server Java (AS Java) and the database have been backed up
You have not deleted renamed or created any directories and files in the following directories
and their subdirectories usrsapltSAPSIDgtSYSexe and usrsapltSAPSIDgtSYS
profile
Otherwise JSPM cannot detect the kernel and the system profiles and cannot be started If a
backup of the kernel and the system profiles has been required it has been created in a different
directory
The ltsapsidgtadm user has Read permissions for the EPS inbox directory usrsaptransEPS
in
If your database is SAP MaxDB the overwrite mode for the log area has been activated
The database and the SDM repository have been synchronized
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2160
For more information see the online documentation for JSPM on SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70 Library
(including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library Administrators Guide
Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems AS Java
(Application Server for Java) Software Logistics Software Maintenance Java Support Package Manager
Then choose Troubleshooting JSPM Does Not Update the Versions of the Deployed Components
There is enough disk space
For more information see SAP Note 891895
Your current SAPCAR tool is able to extract the Support Packages for the SAP kernel and
other OS level binaries delivered as SAR files
RECOMMENDATION
You can download the latest version of SAPCAR from SAP Service Marketplace at
httpservicesapcompatches Entry by Application Group Additional Components
SAPCAR
Put the downloaded version in the same directory in the JSPM inbox in which the kernel
SAR files reside so that JSPM can use this version for extracting the SAR files
3 Only valid for Linux |
For RHEL 4 and SLES 9 you need to install additional operating system packages For more
information see SAP Note 1021236End of Linux |
4 Only valid for Windows |
For Windows you need to install additional operating system packages For more information see
SAP Note 684106End of Windows |
5 To prevent the Software Deployment Manager (SDM) from temporarily exceeding the available
disk space during the update process you can change the file transfer directory of SDM in a system
of SPS09 or higher using the following command sequence
Only valid for Windows |
cd ltsdm_homegt
StopServerbat
sdmbat jstartup mode=standalone
sdmbat filetransferdir dir=ltnew_dirgt
sdmbat jstartup mode=integrated
StartServerbat
End of Windows |
Only valid for IBM i5OSUNIX |
cd ltsdm_homegt
StopServersh
sdmsh jstartup mode=standalone
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2260 CUSTOMER 2012-08-30
sdmsh filetransferdir dir=ltnew_dirgt
sdmsh jstartup mode=integrated
StartServersh
End of IBM i5OSUNIX |
6 To prevent deployment errors during the update process proceed as follows
1 Log on to the Central Instance host
2 Start the ConfigTool and in the navigation area choose Cluster-data Global server configuration
Managers ServiceManager
3 In the Global properties panel set the Custom value of the EventTimeout property to 120
4 Choose Save
5 Restart the Central Instance
7 Check whether the used JDK version and the Java VM settings of the Java runtime system comply
with the requirements in SAP Note 723909 Update the JDK and adjust the settings if necessary
NOTE
An update of the used JDK version possibly changes the JVM path In this case you must
make the new path available to all Dialog Instances of the J2EE engine by implementing option
1 of SAP Note 718901
8 Make sure that the J2EE administrator password stored in the secure store for offline usage is
identical with the one stored in the User Management Engine (UME) You can change the password
in the secure store as described in SAP Note 870445
9 If you are running a high availability system on Windows you might need to prepare your system
as described in the online documentation for JSPM see section Preparing Systems That Run in High
Availability Environment
223 Updating the Application Server Java and Java-Based Components
Procedure
Applying a Support Package Stack to SAP NetWeaver Application Server Java and Java-Based Components
NOTE
The JSPM GUI might not work properly on some UNIX systems For more information and the
solution see SAP Note 1013976
1 Log on as user ltsapsidgtadm to the Central Instance host
NOTE
If your operating system is IBM i log on as user ltSIDgtADM or ltSIDgtOFR
2 Close the SAP Management Console (SAP MMC) and the SDM remote GUI client
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2360
3 For UNIX and Windows To start the JSPM navigate to the directory ltINSTDIRgtltSIDgt
ltCentral_Instance_Namegtj2eeJSPM and run the go script file
NOTE
If your system is running on IBM i to start the JSPM proceed as follows
1 To prevent JSPM from automatically starting its GUI in the file usrsapltSIDgt
ltCentral_Instance_Namegtj2eeJSPMparamjspm_configtxt change the
property dialogSDTServerConnectionSDTGuilaunch from true to false
2 On the IBM i host run the go script file using the following command
QSH CMD(usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPMgo)
3 In the mounted directory usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPM run
the StartGui script file The JSPM GUI appears
4 In the Host field enter the target IBM i host
NOTE
Depending on the system type ltCentral_Instance_Namegt has the following syntax
Standalone Java system JCltinstance_nogt
Add-On system DVEBMGSltinstance_nogt
4 Enter your SDM password to log on to the SDM
5 On the Deployment tab page select the Java Support Package Manager option and update the software
component sapcomJSPM to the target SPS level
6 Restart the JSPM and log on with the SDM password
RECOMMENDATION
We strongly recommend that you use the Support and Enhancement Package Stack option when
applying a Support Package Stack Other options can lead to unintended consistency issues
NOTE
If you need to include the latest patches for a particular component during the update process
with the Support and Enhancement Package Stack option stop the JSPM after restart and apply SAP
Note 1080821 Then start the JSPM again
7 On the Deployment tab page select the Support and Enhancement Package Stack option and choose Next
The Support Package Stacks that are available for deployment in the global EPS inbox directory
are displayed
8 In the Target SP Stack Level dropdown box select the Support Package Stack to be applied and choose
Next
In this step JSPM performs various status validations and displays the result of each software
component included in the stack definition XML file on the subsequent screen which includes
the following possible statuses
OK Indicates that the SPS level of the corresponding software component is applicable
WARNING We recommend that you view the details about the component by choosing Show
Details
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2460 CUSTOMER 2012-08-30
This status may indicate that the corresponding software component comprises custom
modifications in an NWDI-controlled system
If your system is used for NWDI development and it is either a DEV or a CONS system
you will be informed that JSPM will not deploy the modified software components but
only transport them to the CMS transport directory JSPM will deploy only the software
components that are not modified
If your system is not used for NWDI development or if your system is used for NWDI
development and it is either a TEST or a PROD system you will be informed that JSPM
has found newer versions of modified software components and will automatically replace
the original versions with the newer versions JSPM will deploy all software components
that are not modified together with the replaced versions of the modified software
components
CAUTION
You may get a warning telling you that there are patches installed in your system
containing fixes which might not be included in the target SP Stack This is possible if
you have applied patches of the start SP Stack level that were delivered later than the
target SP Stack delivery date In order not to lose these fixes you need to download and
apply the corresponding patches of the target SP Stack level
If you are performing an update from SAP NetWeaver 70 including enhancement
package 1 SPS00 and you have not applied any patches for the software component with
status WARNING before the update then you can ignore warnings such as the following
example
The new version of the development component sapcomcomsapnetweaver
bcrfmoni is 70100200806121227180000 and is lower than the already
deployed version 70100200807090143420000
REVISE Indicates inconsistencies with the corresponding software component
The deployment cannot be performed until all problems have been resolved You can view
the problems by choosing Show Details
9 If the status of the selected SP Stack is OK or WARNING you can start the system update by choosing
Start JSPM then changes the status to SCHEDULED
If the SP Stack to be applied includes a kernel update and the current kernel is not already of the
corresponding patch level JSPM arranges the kernel update as the very first Support Package to
be applied JSPM updates the kernel binaries of all instances (including Dialog Instances and SCS
instances in a HA environment) whose kernel directories DIR_CT_RUN effectively reside on the host
indicated by the profile parameter SAPGLOBALHOST
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2560
CAUTION
Kernel binaries of instances whose kernel directories DIR_CT_RUN are not effectively linked
to the host SAPGLOBALHOST must be updated individually as described in section Manually
Updating Instances with Kernel Directory Located on Separate Hosts below
The kernel update (includes update of SAP Kernel and SAP IGS) using JSPM consists of the following
steps
1 JSPM stops the Central Instance automatically and prompts you to stop the remote SCS and
Dialog Instances manually
2 After you have stopped all the instances choose the Next button in the dialog box
The kernel update starts
NOTE
If the system is running in a high availability environment make sure that the HA
software does not restart the instance automatically during the update
NOTE
If kernel binaries of the SCS instance need to be updated manually (see Manually Updating
Instances with Kernel Directory Located on Separate Hosts below) you must perform this at the
time when JSPM is updating the kernel binaries of the Central Instance In any case the
SCS kernel must be up-to-date before the next restart
When the kernel update is finished a dialog box appears in which you are prompted to restart
the SCS instance manually
3 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries
before you can proceed with the next step For more information see Adjusting the Ownership and
Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
4 Choose Next in the dialog box when the SCS instance is running again
After the kernel update JSPM restarts the system for further deployment of the remaining Support
Packages in the stack
RECOMMENDATION
If you need to update the kernel binaries of any Dialog Instances manually (see Manually
Updating Instances with Kernel Directory Located on Separate Hosts below) perform the update when
JSPM is updating the remaining Support Packages in the stack in order to save time
The deployment of each Support Package can end with one of the following statuses
DEPLOYED
The Support Package has been successfully deployed
DEPLOYED WITH WARNING
The Support Package has been deployed but it possibly may not work properly with other
deployed components
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2660 CUSTOMER 2012-08-30
You can view the details by choosing Show Details or examining the log files You can also view
the details about the component by choosing the Deployed Components tab page
ERROR
An error has occurred during the deployment You can view the details by choosing Show
Details or examining the log files
You must correct the error to be able to continue with the SP Stack update
You can proceed as described for a deployment that finished with status DEPLOYED WITH
WARNING
If the error correction does not change the contents in the JSPM inbox you can continue
the deployment by choosing Resume
If the error correction changes the contents in the JSPM inbox you can choose New
Deployment to redeploy the SP Stack
NOT DEPLOYED
JSPM has not attempted to deploy the software component for certain reasons
If your system is not used for NWDI development you can proceed as described for a
deployment that finished with status ERROR
If your system is used for NWDI development and it is either a DEV or a CONS system
the status of the modified software components is always NOT DEPLOYED JSPM has
transported the software components of the Support Package Stack both modified and
not modified to the CMS transport directory The deployment of the modified software
components is handled by NWDI
Manually Updating Instances with Kernel Directory Located on Separate Hosts
JSPM performs kernel update for all instances (including Dialog Instances and SCS instances in a HA
environment) whose kernel directories DIR_CT_RUN effectively reside on the host indicated by the profile
parameter SAPGLOBALHOST (by using folder sharing on Windows or file system mounting on UNIX) In
rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of those sort of instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances individually
To update the kernel of an instance manually proceed as follows
1 Log on as user ltsapsidgtadm to the host of the instance to be updated
2 Back up the kernel directory which is specified by the profile parameter DIR_CT_RUN
3 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory with
SAPCAR [page 56]
4 Stop the instance being updated
NOTE
If the system is running in a HA environment make sure that the HA software does not
restart the instance automatically during the update
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2760
5 Copy or move the extracted programs from the temporary directory to the local kernel directory
6 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries as
described in section Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
7 Restart the instance after JSPM has finished the deployment of all packages on the Central Instance
Only valid for UNIX |
Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms
On UNIX platforms you must adjust the ownership and execution permissions of the kernel binaries
after the update regardless whether you performed the update manually or by using JSPM because
both update procedures are performed with the ltsapsidgtadm user Enter the following command
sequence
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
224 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the Java system
23 Parallel Update of Dual-Stack Systems
If you perform an update of a dual-stack system (ABAP+Java) we recommend that you follow the
procedure described below The procedure has been validated to update the ABAP stack and the Java
stack of a NetWeaver system in parallel thus reducing the overall system downtime by half
Procedure
1 Before applying ABAP and Java Support Packages use the Single Support Packages option in JSPM and
select for update only the components SAP KERNEL and BC-FES-IGS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
23 Parallel Update of Dual-Stack Systems
2860 CUSTOMER 2012-08-30
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS)
runs on a dedicated host In this case JSPM does not support update of kernel binaries and
you need to update them manually Perform the update manually as described under Updating
SAP Kernel and SAP IGS in section Updating the Application Server ABAP and ABAP-Based Software
Components [page 16]
2 Import the Support Packages for the component SAP_BASIS into the ABAP stack using the ABAP
Support Package Manager (SPAM)
3 Import the remaining ABAP Support Packages with SPAM and in parallel apply the Java Support
Package Stack with JSPM
Proceed as described in Updating the Application Server ABAP and ABAP-Based Software Components [page
16] and Updating the Application Server Java and Java-Based Software Components [page 23]
24 Process Integration
241 Planning
Procedure
This section covers all the units of Process Integration that should be updated Particularly the following
units must always have the same Support Package level (the patch level can be different)
Integration Server
XI Adapter Engine
Partner Connectivity Kit
System with the Usage Type Process Integration
Software components of Integration Server
Components to Be Updated SP File Name Tool Used to Apply SP
Java stack
XI TOOLS 702 SAPXITOOLltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
ABAP stack
XI CONTENT SAP_BASIS 702 SAPBASISltSPgt_ltPLgtZIP File upload
XI CONTENT SAP_ABA 702 SAPABAltSPgt_ltPLgtZIP
SAP NetWeaver Application Server ABAP (see table Software components of Application Server ABAP [page 15])Note that update of the following software components of the ABAP system is not required SAP ABA 702 SAP BW 702 PI_BASIS 702
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 2960
J2EE Adapter Engine
If your implemented scenario includes a J2EE Adapter Engine then it must always be of the same
Support Package level as the Integration Server
Components of the J2EE Adapter Engine
Component to Be Updated SP File NameTool Used to Apply SP
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
J2SE Adapter Engine
The installation of the J2SE Adapter Engine depends on the implemented scenario
Components of the J2SE Adapter Engine
Component to Be Updated SP File Name Tool Used to Apply SP
XI CONNECTIVITY SE 702 SAPXICONSltSPgt_ltPLgtSCA ZIP tool (for example WinZip)
Partner Connectivity Kit
If your implemented scenario includes a Partner Connectivity Kit (PCK) then it must always be of the
same Support Package level as the Integration Server
Software components of Partner Connectivity Kit
Components to Be Updated SP File NameTool Used to Apply SP
XI PCK 702 SAPXIPCKltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of the Application Server Java [page 20])
System Landscape Directory (SLD)
The System Landscape Directory is required for the PI operations Although updating the SLD is not
necessarily required it is advisable to update the SLD server and the SAP Master Data Content within
it from time to time The update of the SLD includes
1 The system where the SLD is running
2 The SAP Master Data Content within this SLD
SAP GUI
See table Compatible SAP GUI Versions [page 51]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3060 CUSTOMER 2012-08-30
242 Updating Units of Process Integration
Procedure
Before you start the update perform the following steps
In the Runtime Workbench use Communication Channel Monitoring to stop all sender channels
for all adapter types on all your Adapter Engines
On the Integration Server use transaction SMQR and deregister all qRFC queues
System with the Usage Type Process Integration
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the XI instance is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system where the XI instance is running
For more information see Application Server Java and Java-Based Software Components [page 19]
System Landscape Directory (Optional)
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the SLD is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the entire Support Package Stack to the system where the SLD is running
For more information see Application Server Java and Java-Based Software Components [page 19]
J2EE Adapter Engine
Apply the Support Package Stack to the system where the Adapter Engine is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Partner Connectivity Kit
Apply the Support Package Stack to the system where the PCK is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Front End GUIs
Update the SAP GUI components if necessary
For more information see SAP GUI Family [page 51]
ABAP 700 Business System (Optional)
Apply the Support Packages for SAP NetWeaver Application Server ABAP (including SAP kernel and
the Support Package for SAP BASIS 700)
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 640 Business System (Optional)
Apply the Support Packages for SAP Web Application Server ABAP 640 (including SAP kernel and the
Support Package for SAP BASIS 640)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3160
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 620 Business System (Optional)
1 Update the SAP Kernel 620
2 Import the released Basis Support Packages for SAP Web AS 620 as well as the most recent Add-
On Support Package for APPINT 200_620 in the order described in SAP Note 439915
J2SE Adapter Engine (Optional)
NOTE
The XI Adapter Engine (J2SE) and all its adapters are provided for compatibility reasons only and
are not developed any further You have to use the XI Adapter Engine running on SAP NetWeaver
AS Java For more information see the Master Guide ndash SAP NetWeaver 70 available on SAP Service
Marketplace at httpservicesapcominstallNW70 Planning
1 Extract the SAPXICONSltSPgt_ltPLgtSCA (XI Connectivity SE 700) archive (ZIP format) to a temporary
directory
2 Save the old configuration files as described in the document Adapterpdf in directory
lttemp_directorygttech_adapterAdministrationDocumentation
3 Unpack the ZIP archive TechnicalAdapterssda to the installation directory of the XI Adapter
Engine (J2SE)
4 Restore the configuration files with restore_configuration
243 Post-Installation Steps
Procedure
Communication Channels and Queues
Restart all stopped sender channels and register all deregistered qRFC queues
XI Content
In the system with usage type PI import the XI content from the archives SAPBASISltSPgt_ltPLgtZIP
and SAPABAltSPgt_ltPLgtZIP as follows
1 Unpack the archives using a ZIP tool of your choice
2 Copy the corresponding export files (with file extension tpz) to the import directory ltINSTDIRgt
ltSAPSIDgtSYSglobalxirepository_serverimport
3 Start the Integration Builder (transaction SXMB_IFR)
4 Enter the Integration Repository by choosing Repository (Design)
5 Choose Tools Import design objects
6 Import the tpz files containing the XI content
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3260 CUSTOMER 2012-08-30
NOTE
For more information see SAP Note 836200
Role Generation on the Integration Server
On the Integration Server execute transaction SUPC (mass generation of roles) for all SAP_XI roles in
each of your clients to regenerate possibly changed roles
NOTE
Do not forget to make a user comparison for regenerated roles afterwards
Partner Connectivity Kit (Optional)
Perform the post-installation steps for PCK as described in SAP Note 746328
SAP Master Data within the SLD (Optional)
In the system where your SLD is running import the latest SLD content as described in SAP Note
669669
Receiver-Based EOIO Serialization in J2EE Adapter Engine (Optional)
The J2EE Adapter Engine can be switched to receiver-based EOIO serialization The switch can be
triggered on demand and is executed asynchronously It includes a database migration step during
which all EOIO processing in the Adapter Engine is disabled See SAP Note 973894 for details about how
to start the EOIO serialization migration
Service Metering (Optional)
Service metering gathers information about a service caller transfers it to the service provider and
counts on the service provisioning side how many times a service is called and by which service caller
Service metering is performed for the XI message protocol and the WS message protocol Service
metering is automatically enabled after applying a Support Package Stack By default only non-sensitive
data is transmitted to internal or external service providers in a compatible way
Service metering can be configured in PI in the Integration Engine on sender-side and in the Integration
Directory
Service metering can be configured in AS ABAP in transaction SOAMANAGER
Only if the service provider is allowed to receive more detailed information about the service caller set
the metering level to higher than the default
For more information see SAP Note 1239428
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3360
25 Business Intelligence
251 Planning
Procedure
Business Intelligence includes one or many of the following units that must be updated depending on
your implemented scenarios The usage types Business Intelligence (BI) and Business Intelligence Java
Components (BI-Java) must always have the same Support Package level
Business Intelligence
Software Components of Business Intelligence
Component to Be Updated SP File Name Tool Used to Apply SP
BI CONT ADDON 70x SAPK-70ltxgtltSPgtINBICONT SAINT
SAP NetWeaver Application Server ABAP (see table Software Components of Application Server ABAP [page 15])
NOTE
For information about the dependencies applying to BI Content Support Packages see SAP Note
653814 BI CONT 703 Support Packages are not part of the NetWeaver SP Stacks Updates can be
performed when applicable Alternatively BI CONT 704 Support Packages can be imported See
the BI Content release strategy in SAP Note 153967
Business Intelligence Java Components
BI Java Components
Component to Be Updated SP File NameTool Used to Apply SP
BI REPORTING AND PLANNING 702 BIREPPLANltSPgt_ltPLgtSCA JSPM
BI WEBDYNPRO ALV 702 BIWDALVltSPgt_ltPLgtSCA
BI INFORM BROADCASTING 702 BIIBCltSPgt_ltPLgtSCA
BI WEB APPLICATIONS 702 BIWEBAPPltSPgt_ltPLgtSCA
BI BASE SERVICES 702 BIBASESltSPgt_ltPLgtSCA
VISUAL COMPOSER BI KITS 702 VCKITBIltSPgt_ltPLgtSCA
Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
BI Precalculation Service
Components of the BI Precalculation Service
Component to Be Updated SP File Name Tool Used to Apply SP
BI Pre-calculation Service 700 xPreCalServerltSPgt_ltPLgtexe Installer
Search and Classification (TREX)
See table TREX Component [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3460 CUSTOMER 2012-08-30
BI Accelerator
The BI Accelerator is based on the TREX technology It is a special Linux 64-bit version of SAP NetWeaver
70 Search and Classification (TREX) which is delivered on preconfigured hardware
NOTE
You cannot use a TREX installation based on 32-bit architecture that is configured for searching
in metadata and documents for the BI Accelerator And vice versa a BI Accelerator box cannot
be used for searching in metadata and documents
If you want to use the search functionality as well as the BI Accelerator you require two separate
installations For more information see BI Accelerator [page 47]
Clients
Depending on your implemented scenarios you have to update SAP GUI Components and Business
Explorer (BI Add-OnBW Add-On)
NOTE
See SAP Note 889314 to determine when to use the BI Add-On and the BW Add-On
NOTE
As SAP GUI 640 is no longer supported BI Frontend Support Package 1800 resp patch 1801 is the
last Support Package resp patch based on SAP GUI 640 For more information see SAP Note
1231292 (Frontend Add-in Strategy 640710 GUI Version)
For more information about the new release strategy for the BI Frontend see SAP Note 1231363
(Changed Delivery Strategy for BI Frontend)
252 Preparation
Procedure
For the Support Packages of the most important Business Intelligence units so called SAPBINews
(SAPBWNews) Notes are created Read these Notes before updating Business Intelligence For SAP
NetWeaver 70 including enhancement package 2 SPS 12 these are the following
Business Intelligence ABAP SAP Note 1680996
Business Intelligence Java Components SAP Note 1726461
BI 70 Frontend Add-On for SAP GUI 710 SAP Note 1413032
BI 70 Frontend Add-On for SAP GUI 720 SAP Note 1630112
BI 70 Frontend Add-On for SAP GUI 730 SAP Note 1726739
For more information about BI Support Packages see SAP Community Network at http
scnsapcomcommunitydata-warehousingnetweaver-bw Related Resources SAP NW BW Support
Packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
2012-08-30 CUSTOMER 3560
253 Updating Units of Business Intelligence
Procedure
Business Intelligence
1 Update the SAP NetWeaver Application Server ABAP (with BI CONT 70x if necessary) with the
appropriate Support Packages
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
NOTE
When applying the component SAP BW 702 some generation errors might occur When
you start importing the BI Support Packages in transaction SPAM choose the menu path
Extras Ignore generation errors For more information see SAP Note 114134
2 Apply the Support Package Stack to the system with the usage type BI-Java
For more information see Application Server Java and Java-Based Software Components [page 19]
3 Update the BI Precalculation Service that is used in your scenario
4 Update the standalone engine Search and Classification (TREX) that is used in your scenario For more
information see Standalone Engine Search and Classification (TREX) [page 44]
NOTE
You have to update TREX to the newest version if you use search capabilities within Business
Intelligence
5 Update the BI Accelerator to the newest available version For more information see BI
Accelerator [page 47]
6 Update the SAP GUI and Business Explorer (BI Add-On BW Add-On) on all remote client hosts
that are involved in the scenario
For more information see SAP GUI Family [page 51] and Business Explorer (BI Add-On BW Add-On)
[page 51]
BI Precalculation Service
1 Log on to the host as a user with administration rights
2 Install the Support Package of the BI Precalculation Service by executing the
xPreCalServerexe file
The welcome screen of the BI Precalculation Server setup wizard appears
The setup now checks the system for the prerequisites
3 Choose the option Update for updating the BI Precalculation service to the current patch level and
then Finish
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3660 CUSTOMER 2012-08-30
26 EP Core
261 Planning
Procedure
The following installable software units must be updated
EP Core
Software Components of EP Core
Component to Be Updated SP File Name Tool Used to Apply SP
PORTAL CORE SERVICES 702 EPBCltSPgt_ltPLgtSCA JSPM
PORTAL FRAMEWORK 702 EPBC2ltSPgt_ltPLgtSCA
PORTAL 702 EPPSERVltSPgt_ltPLgtSCA
PORTAL WEB DYNPRO 702 EPWDCltSPgt_ltPLgtSCA
UWL COLL PROCESS ENGINE 702 UWLJWFltSPgt_ltPLgtSCA
CAF EU 702 SAPEUltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
262 Preparation
Procedure
Backing Up the Portal Runtime Configuration
If you have made changes to the standard Portal Runtime configuration you have to make a backup
of the configuration before the update process For more information see SAP Note 1064468
263 Updating EP Core
Procedure
Apply the Support Package Stack to a system with usage type EP Core
For more information see Application Server Java and Java-Based Software Components [page 19]
264 Post-Installation Steps for EP Core
Procedure
Restoring the Portal Runtime Configuration
To make your changes to the standard Portal Runtime Configuration effective you have to restore
the backup of the configuration done before the update process For more information see SAP Note
1064468
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
26 EP Core
2012-08-30 CUSTOMER 3760
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
Table of Contents
Chapter 1 Overview 9
11 Before You Start 9
12 Types of Support Packages 11
13 Downloading Support Package Stacks 12
Chapter 2 Applying Support Packages to Installable Software Units of SAP
NetWeaver 70 Including Enhancement Package 2 15
21 Application Server ABAP and ABAP-Based Software Components 15
211 Planning 15
212 Preparation 16
213 Updating the Application Server ABAP and ABAP-Based Software
Components 16
214 Post-Installation Steps 19
22 Application Server Java and Java-Based Software Components 19
221 Planning 20
222 Preparation for Applying a Support Package Stack 21
223 Updating the Application Server Java and Java-Based
Components 23
224 Post-Installation Steps 28
23 Parallel Update of Dual-Stack Systems 28
24 Process Integration 29
241 Planning 29
242 Updating Units of Process Integration 31
243 Post-Installation Steps 32
25 Business Intelligence 34
251 Planning 34
252 Preparation 35
253 Updating Units of Business Intelligence 36
26 EP Core 37
261 Planning 37
262 Preparation 37
660 CUSTOMER 2012-08-30
263 Updating EP Core 37
264 Post-Installation Steps for EP Core 37
27 Enterprise Portal 38
271 Planning 38
272 Updating Enterprise Portal 38
273 Post-Installation Steps for Enterprise Portal 39
28 Development Infrastructure 40
281 Planning 40
282 Updating Development Infrastructure 41
29 Mobile Infrastructure 43
291 Planning 43
292 Preparation 43
293 Updating Mobile Infrastructure 43
210 Standalone Engines 44
2101 Search and Classification (TREX) 44
21011 Planning 44
21012 Preparation 44
21013 Updating TREX 45
2102 BI Accelerator 47
21021 Planning 47
21022 Preparation 48
21023 Updating BI Accelerator 48
21024 Post-Installation Steps 49
2103 Gateway 50
2104 SAP Web Dispatcher 50
2105 Other Standalone Engines 50
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2 51
2111 SAP GUI Family 51
2112 Business Explorer (BI Add-On BW Add-On) 51
2113 Other Clients 52
212 SAP Library 52
Chapter A Appendix 55
A1 Determining the Current Component Versions 55
A2 Tools Used During the System Update 56
A21 SAPCAR 56
A22 ABAP Support Package Manager and Add-On Installation Tool 57
A23 Java Support Package Manager 58
2012-08-30 CUSTOMER 760
A3 System Profile Parameters 58
860 CUSTOMER 2012-08-30
1 Overview
This document describes how to install Support Package Stacks (SP Stacks) for SAP NetWeaver 70
including enhancement package 2 You can find all information related to the SP Stacks on SAP Service
Marketplace at httpservicesapcomsp-stacks
11 Before You Start
CAUTION
If you intend to update your system to the latest SP Stack level and plan to upgrade it within the
next 6 months first check the availability of the equivalent SP Stack for the target release The
delivery dates of the equivalent SP Stacks for your source and target release might be several
months apart
Be aware that you cannot upgrade to a target release that does not include the equivalent SP Stack
level
To avoid a deadlock situation we recommend that you check SAP Service Marketplace at
httpservicesapcomsp-stacks SP Stack Information and consider not applying the
latest SP Stack on your source release system
Updated Document Versions
The Support Package Stack Guide is regularly updated on SAP Service Marketplace at http
servicesapcommaintenanceNW70
NOTE
Make sure you have the latest version of the Support Package Stack Guide by checking SAP Service
Marketplace immediately before you start to apply or import Support Packages
SAP Notes
You must read SAP Note 1460321 before you read this document as it may contain corrections and
further information about the Support Package Stack installation
SAP Library
You must inform yourself about enhancements and changes to the Support Package Stack to be applied
from SAP Library under SAP Library SAP NetWeaver Whatrsquos New in SAP NetWeaver 70 ndash Release
Notes You can access the SAP Library in one of the following ways
SAP Help Portal at httphelpsapcomnw702 Application Help SAP Library ltLanguagegt
1 Overview
11 Before You Start
2012-08-30 CUSTOMER 960
NOTE
The SAP Help Portal always provides the up-to-date version of the SAP Library Therefore
we recommend that you use this channel to access the SAP Library
Local installation of the SAP Library from the online documentation DVD
CAUTION
In order to inform yourself about the current Support Package Stack you first have to update
your local installation of the SAP Library to the corresponding SPS level Follow the
instructions in section SAP Library [page 52]
Naming Conventions
In this document the following naming conventions apply
Variables
Variables Description
ltSAPSIDgt
ltsapsidgt
ltSIDgt
SAP system ID
ltINSTDIRgt Installation directory for the SAP system
lthostgt Host name
ltinstance_nogt Instance number of a system instance
ltdatabasegt Name of database
ltsapinst_directorygt Installation directory for the SAP installation tool SAPinst
ltsp_directorygt Temporary directory which the archives of a Support Package are downloaded or copied to
ltOSgt Operating system
ltOS_DIRgt OS-dependent directory consisting of a folder for the platform and a subfolder of your OS versionFor example if you operating system is Sun OS 64bit ltOS_DIRgt stands for UNIXSUNOS64
ltSP_Stackgt Number of Support Package Stack
ltSPgt Support Package level
ltPLgt Support Package patch level
ltRELgt Release number
ltLOCALEgt Language definitionFor example the German locale is _de
ltkrnl_directorygt Kernel directory which the profile parameter DIR_CT_RUN usually refers to
ltsdm_homegt Program file location of the Software Deployment Manager (SDM)
ltSAPGLOBALHOSTgt SAP global host the host where the global directories of an SAP system reside
ltSAPLOCALHOSTgt SAP local host the host where a particular instance of an SAP system is running
1 Overview
11 Before You Start
1060 CUSTOMER 2012-08-30
12 Types of Support Packages
The following table explains the terms used in the correction process as part of the software maintenance
process for SAP NetWeaver
Correction Process Description
Standard correction process
Support Package Stack Description
A Support Package Stack is a set of Support Packages and patches for the respective product version that must be used in the given combination
Version numbersSupport Package Stacks have a release number and a stack number for example SAP NetWeaver 70 Support Package Stack 05
DeliveryThere is no dedicated delivery format for the Support Package Stacks The included Support Package files have their delivery formats and must be applied using the tools as described below
Kernel Patches Version numbers
SAP Kernel patches have a release number and a patch number The patch number is increased with each correction
DeliverySAP Kernel patches are delivered as SAR files They are installed by extracting the SAR files to the kernel directory using SAPCAR Separate SAR files are shipped for the different kernel types depending on UNICODENON-UNICODE and the platform
ABAP Support Packages Description
ABAP Support Packages contain corrections and adjustments for the ABAP-based Software Components of the SAP system
DependenciesIn contrast to Java Support Packages ABAP Support Packages are non-cumulative Therefore ABAP Support Packages must be installed in the correct sequence one after the other You cannot skip any intermediate Support Packages
DeliveryABAP Support Packages are delivered as SAR files They are installed using the Support Package Manager (SPAM)
Java Support Packages Description
Java Support Packages contain corrections for the Java-based Software Components of the SAP system
DependenciesJava Support Packages always contain a full delivery of the Software Components Therefore you only need to apply the latest Support Package to update the software If there are dependencies with other Java Support Packages these are specified in an SAP Note
DeliveryJava Support Packages are delivered as Software Component Archives (SCAs) They are applied using the Java Support Package Manager (JSPM)
1 Overview
12 Types of Support Packages
2012-08-30 CUSTOMER 1160
Correction Process Description
Emergency correction process
SAP Note Correction (ABAP) Description
SAP Note corrections contain single ABAP fixes Delivery
SAP Note corrections are delivered with SAP Notes If required you apply them using the SAP Note Assistant
Java Support Package Patch Description
A Java Support Package patch contains corrections for the Java Software Components Java Support Package patches are created and released on demand A Java Support Package patch corresponds to an SAP Note that describes the same correction
DependenciesA Java Support Package patch always contains a full package of the corresponding Software Component and is applied using JSPM
13 Downloading Support Package Stacks
The Maintenance Optimizer in SAP Solution Manager is the only source from which you can receive
maintenance updates for SAP NetWeaver 70 and higher releases as well as for all applications running
on top of SAP NetWeaver The Maintenance Optimizer supports you in selecting and downloading all
required maintenance files In addition the Maintenance Optimizer generates a stack XML file and
saves it to the EPS inbox directory of SAP Solution Manager
Prerequisites
You have configured the Maintenance Optimizer in SAP Solution Manager as described on SAP Help
Portal at httphelpsapcom SAP Solutions SAP Solution Manager SAP Solution Manager ltReleasegt
ltLanguagegt Change Management Maintenance Optimizer Planning and Monitoring Product Maintenance and
also in section Automatically Calculating Product Maintenance Files
Procedure
To download a Support Package Stack proceed as follows
1 Start SAP Solution Manager using the transaction solution_manager To start the Maintenance
Optimizer choose Operations Change Management Maintenance Optimizer
2 In the Maintenance Optimizer choose the solution for which you want to download SP Stack files
3 Choose Create New Maintenance Transaction
4 Select the product version for which you want to apply a Support Package Stack
The Maintenance Optimizer displays all the systems assigned to the selected product version
5 Select the checkbox for the system that you want to update and choose Continue
6 On the subsequent screen select the Maintenance option and then choose Find Download Files
1 Overview
13 Downloading Support Package Stacks
1260 CUSTOMER 2012-08-30
7 Select the target SP Stack level and the relevant usage types according to the IT scenario to be
updated
8 Choose Find Download Files for the Stack Version
The Maintenance Optimizer displays the product maintenance files in three successive lists
9 Select the required files from the displayed lists
The first list shows all files that are dependent on the type of your operating system and
database
Select the files that correspond to the combination of your operating system and database and
the database-independent files
If your system is distributed on several hosts make sure to select all operating systems used
by the NetWeaver instances You can see all the kernels detected on your system on the Deployed
Components tab page on JSPM user interface (under the SAP KERNEL node) All detected kernels
must be updated to the same version
You get to the second list by choosing Continue This list displays all Support Package files that
are not assigned to the selected Support Package Stack Before you continue with the selection
you must check whether the Support Package files listed here are suitable for your product
maintenance procedure
You get to the third list by choosing Continue The list displays all product maintenance files
that are part of the selected Support Package Stack
Ensure that all files that are assigned to the Support Package Stack are selected here Files that
are not selected will not be included later in the download
10 Choose Continue Use the Download Basket to download the maintenance files
11 Choose Continue once the files have been put in your Download Basket and then Confirm Files in
Download Basket
A dialog window appears and displays all files
12 Confirm the download for all files
13 Open your Download Manager and download the files
NOTE
The stack XML file is generated by the Maintenance Optimizer and automatically saved to
the EPS inbox directory of SAP Solution Manager
More Information
For more information about the Maintenance Optimizer see SAP Support Portal at http
servicesapcomsolman-mopz
1 Overview
13 Downloading Support Package Stacks
2012-08-30 CUSTOMER 1360
This page is left blank for documents that are printed on both sides
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
This chapter describes how to apply Support Packages to installable software units of SAP NetWeaver
70 including enhancement package 2 SAP NetWeaver distinguishes three types of installable software
units
Systems with one or multiple usage types
Standalone engines
Clients
A scenario implementation usually involves several installed software units
RECOMMENDATION
We strongly recommend that you always update all software units belonging to one scenario
together in order to retain a consistent system state Due to the fact that some installable software
units can be commonly shared in different scenarios you must consequently update all scenarios
using the common software units at the same time
21 Application Server ABAP and ABAP-Based Software Components
211 Planning
Procedure
The following components belong to the usage type SAP NetWeaver Application Server ABAP
Software Components of Application Server ABAP
Component to Be Updated SP File Name Tool Used to Apply SP
SAP KERNEL 720 32-64-BIT Non-UNICODEUNICODE SAPEXESAR
SAPEXEDBSAR
JSPMmanually
SAP IGS 700 igsexesar
SAP ABA 702 SAPKA702ltSPgt SPAMSAINT
SAP BASIS 702 SAPKB702ltSPgt
SAP BW 702 SAPKW702ltSPgt
PI_BASIS 702 SAPK-702ltSPgtINPIBASIS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
2012-08-30 CUSTOMER 1560
NOTE
This table contains only software components that belong to the usage type AS ABAP Software
components of other usage types and application units are listed in the corresponding sections
NOTE
SAP delivers intermediate Support Packages for the component SAP BW 702 between two
subsequent SP levels besides the Support Packages delivered along with the Support Package
Stacks Therefore the highest SP level of SAP BW 702 does not necessarily match the target SP
Stack level
CAUTION
When applying a Support Package Stack to a dual-stack system (ABAP+Java) the Java Support
Package Manager (JSPM) will necessarily restart the system several times to make the changes
effective The ABAP part will only be restarted when JSPM is updating the SAP kernel and IGS
212 Preparation
Procedure
Read SAP Note 822379 and all related SAP Notes that the first one refers to
213 Updating the Application Server ABAP and ABAP-Based Software Components
Procedure
Applying Support Packages to SAP NetWeaver Application Server ABAP and ABAP-Based Components
You can update the SAP NetWeaver Application Server ABAP and all ABAP-based software components
running on it using the Support Package Manager (transaction SPAM)
NOTE
If a particular Support Package Stack requires the installation or upgrade of some add-on
components you must use the ABAP Add-on Installation Tool (transaction SAINT) instead of the
Support Package Manager In this case SAINT is able to import both the add-on components and
the related Support Packages of ordinary SAP components
Proceed as follows
1 Log on to the SAP NetWeaver AS system with client 000
2 Start the Support Package Manager by calling transaction SPAM or
start the Add-On Installation Tool by calling transaction SAINT
3 Load the relevant Support Packages or add-on installation packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
1660 CUSTOMER 2012-08-30
4 Define an import queue
5 Perform the import of the defined queue
NOTE
If you have modified SAP objects in your system and these objects are included in the Support
Packages you must perform modification adjustment during the import using the
transactions SPDD (for ABAP Dictionary objects) and SPAU (for Repository objects)
To import the queue you use the standard scenario You can choose between the conventional
import mode and downtime-minimized import mode
Conventional Import Mode
This option comprises the following steps
1 Update the SAP kernel and SAP IGS as described in section Updating SAP Kernel and SAP IGS below
Start the system after the kernel update
2 Import the ABAP Support Packages with the Support Package Manager (SPAM)
Import Mode Downtime-Minimized
This option can be used to reduce system downtime during the update It comprises the following
steps
1 In transaction SPAM enable the downtime-minimized import mode by choosing Extras
Settings then on the Import queue tab page choose Standard and activate the option Import Mode
Downtime-Minimized
2 Import the ABAP Support Packages into the system in an inactive state in the downtime-minimized
mode during system uptime
3 Update the SAP kernel and SAP IGS as described in section Updating SAP Kernel and SAP IGS below
Start the system after the kernel update
4 Complete the ABAP Support Packages import
CAUTION
During this step the system cannot carry out any business transactions (business downtime)
NOTE
In rare cases due to the dependencies of some Support Packages on a particular kernel patch level
the downtime-minimized update does not work In such cases the Support Package Manager
informs you that you must update the SAP kernel before importing ABAP Support Packages You
must proceed with the conventional import procedure
Updating SAP Kernel and SAP IGS
In general the SAP kernel and IGS binaries are located in the global kernel directory DIR_CT_RUN on
the host indicated by the profile parameter SAPGLOBALHOST Once the files in this directory have been
updated to a new patch level a system restart distributes them by means of the program SAPCPE to the
local directories DIR_EXECUTABLE on the hosts where the instances of the SAP system are running
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
2012-08-30 CUSTOMER 1760
CAUTION
The automatic distribution by means of SAPCPE depends on the settings of the profile parameters
DIR_CT_RUN for the global kernel directory and DIR_EXECUTABLE for the local directory of the
executables Before you continue check the instance profiles for the settings of these parameters
in systems that are not installed using SAPinst (for example systems upgraded from older releases
copied or migrated systems)
CAUTION
If your system is a dual-stack system (ABAP+Java) and the ABAP stack has a non-Unicode kernel
be aware that the SCS instance has a Unicode kernel You have to update both kernels (together
with SAP IGS) prior to updating the ABAP and Java Support Package stacks This ensures
compatibility and reduces system downtime
RECOMMENDATION
If you perform an update of a dual-stack system (ABAP+Java) we recommend that prior to
applying ABAP and Java Support Package stacks you use the Single Support Packages option in JSPM
and select for update only the components SAP KERNEL and BC-FES-IGS
For more information about updating a dual-stack system see Parallel Update of Dual-Stack Systems
[page 28]
If you perform an update of an ABAP system the following procedure applies for updating the SAP
kernel and IGS manually
1 Log on as user ltsapsidgtadm to the instance host to be updated
2 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory using
SAPCAR [page 56]
3 Stop the ABAP system that you want to update
NOTE
If the system is running in a high availability (HA) environment make sure that the HA
software does not restart the system automatically during the update
4 Back up the kernel directory ltkrnl_directorygt
5 Copy or move the extracted programs from the temporary directory to the SAP kernel directory
6 Only valid for UNIX |
Execute the following command sequence on UNIX platforms
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
1860 CUSTOMER 2012-08-30
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
7 Restart the SAP system
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS) runs
on a dedicated host You need to perform the kernel update for the ASCS instance manually but
excluding the IGS update because the IGS is not required in an ASCS instance
In rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of such instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances manually Proceed as described
in section Manually Updating Instances with Kernel Directory Located on Separate Hosts below in this document
214 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the ABAP system
22 Application Server Java and Java-Based Software Components
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system which includes
JSPM itself
SAP Kernel and SAP IGS
All Java-based usage types installed in the system
Software Deployment Manager (SDM) - the deployment service of the system
RECOMMENDATION
We strongly recommend that you apply the target Support Package Stack to your system as a
whole This ensures consistency on both the system and the application levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 1960
221 Planning
Procedure
Java Support Package files (SCAs) contain all software objects of the corresponding software
components Thus it is sufficient to apply the Java Support Package files of the intended Support Package
Stack directly to the Java system to be updated It is not necessary to apply the Support Package Stacks
between the start SP Stack level and the target SP Stack level successively
CAUTION
When applying a Support Package Stack to a Java system the Java Support Package Manager (JSPM)
will necessarily restart the system several times to make the changes effective With a dual-stack
system (ABAP+Java) the ABAP part will only be restarted when JSPM is updating the SAP kernel
and IGS
The following components belong to the usage type SAP NetWeaver Application Server Java (AS Java)
Software Components of Application Server Java
Component to Be Updated SP File Name Tool Used to Apply SP
SAP Kernel 720 32-64-BIT UNICODE SAPEXESAR
SAPEXEDBSAR
JSPM
SAP IGS 700 igsexesar
BI META MODEL REPOSITORY 702 BIMMRltSPgt_ltPLgtSCA
J2EE ENGINE CORE TOOLS 702 CORETOOLSltSPgt_ltPLgtSCA
J2EE ENGINE BASE TABLES 702 BASETABLESltSPgt_ltPLgtSCA
BI UDI 702 BIUDIltSPgt_ltPLgtSCA
DI BUILD TOOL 702 SAPBUILDTltSPgt_ltPLgtSCA
SAP CAF 702 CAFltSPgt_ltPLgtSCA
SAP IKS 702 KMKWJIKSltSPgt_ltPLgtSCA
JAVA LOG VIEWER 702 JLOGVIEWltSPgt_ltPLgtSCA
SAP J2EE ENGINE CORE 702 SAPJEECORltSPgt_ltPLgtSCA
SAP JAVA TECH SERVICES 702 SAPJTECHSltSPgt_ltPLgtSCA
SAP TECH S OFFLINE 702 SAPJTECHFltSPgt_ltPLgtSCA
SAP J2EE ENGINE 702 SAPJEEltSPgt_ltPLgtSCA
JAVA SP MANAGER 702 JSPMltSPgt_ltPLgtSCA
ADOBE DOCUMENT SERVICES 702 ADSSAPltSPgt_ltPLgtSCA
UME ADMINISTRATION 702 UMEADMINltSPgt_ltPLgtSCA
LIFECYCLE MGMT TOOLS 702 LMTOOLSltSPgt_ltPLgtSCA
SAP CAF-UM 702 CAFUMltSPgt_ltPLgtSCA
SAP SOFTW DELIV MANAGER 702 SDMKITltSPgt_ltPLgtJAR
SOFTWARE LIFECYCLE MANAGER 702 SWLIFECYCLltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2060 CUSTOMER 2012-08-30
NOTE
This table contains only software components that belong to the usage type AS Java Software
components of other usage types and Java application units are listed in the corresponding
sections
NOTE
As of Support Package 09 you can update your system with SAP Kernel 720 instead of SAP Kernel
701
222 Preparation for Applying a Support Package Stack
Procedure
1 Download the Support Package Stack with all usage types to be updated and the stack definition
XML file as described in Downloading Support Package Stacks [page 12]
NOTE
You can find the activated usage types in an existing Java system on the Deployed Components tab
page on the JSPM user interface
NOTE
You do not need to download the SP Stacks between the source SP Stack level and target SP
Stack level By default the target SP Stack level is the latest available SP Stack
2 Make sure the following requirements are met prior to applying the Support Package Stack
You have familiarized yourself with SAP Note 891983 before you start the Java Support Package
Manager
The system to be updated is fully functional
The Support Package Stack you want to apply and the corresponding stack definition XML
file are available in the EPS inbox directory usrsaptransEPSin By default this location
can be also referred to as ldquoJSPM inboxrdquo
The SAP NetWeaver Application Server Java (AS Java) and the database have been backed up
You have not deleted renamed or created any directories and files in the following directories
and their subdirectories usrsapltSAPSIDgtSYSexe and usrsapltSAPSIDgtSYS
profile
Otherwise JSPM cannot detect the kernel and the system profiles and cannot be started If a
backup of the kernel and the system profiles has been required it has been created in a different
directory
The ltsapsidgtadm user has Read permissions for the EPS inbox directory usrsaptransEPS
in
If your database is SAP MaxDB the overwrite mode for the log area has been activated
The database and the SDM repository have been synchronized
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2160
For more information see the online documentation for JSPM on SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70 Library
(including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library Administrators Guide
Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems AS Java
(Application Server for Java) Software Logistics Software Maintenance Java Support Package Manager
Then choose Troubleshooting JSPM Does Not Update the Versions of the Deployed Components
There is enough disk space
For more information see SAP Note 891895
Your current SAPCAR tool is able to extract the Support Packages for the SAP kernel and
other OS level binaries delivered as SAR files
RECOMMENDATION
You can download the latest version of SAPCAR from SAP Service Marketplace at
httpservicesapcompatches Entry by Application Group Additional Components
SAPCAR
Put the downloaded version in the same directory in the JSPM inbox in which the kernel
SAR files reside so that JSPM can use this version for extracting the SAR files
3 Only valid for Linux |
For RHEL 4 and SLES 9 you need to install additional operating system packages For more
information see SAP Note 1021236End of Linux |
4 Only valid for Windows |
For Windows you need to install additional operating system packages For more information see
SAP Note 684106End of Windows |
5 To prevent the Software Deployment Manager (SDM) from temporarily exceeding the available
disk space during the update process you can change the file transfer directory of SDM in a system
of SPS09 or higher using the following command sequence
Only valid for Windows |
cd ltsdm_homegt
StopServerbat
sdmbat jstartup mode=standalone
sdmbat filetransferdir dir=ltnew_dirgt
sdmbat jstartup mode=integrated
StartServerbat
End of Windows |
Only valid for IBM i5OSUNIX |
cd ltsdm_homegt
StopServersh
sdmsh jstartup mode=standalone
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2260 CUSTOMER 2012-08-30
sdmsh filetransferdir dir=ltnew_dirgt
sdmsh jstartup mode=integrated
StartServersh
End of IBM i5OSUNIX |
6 To prevent deployment errors during the update process proceed as follows
1 Log on to the Central Instance host
2 Start the ConfigTool and in the navigation area choose Cluster-data Global server configuration
Managers ServiceManager
3 In the Global properties panel set the Custom value of the EventTimeout property to 120
4 Choose Save
5 Restart the Central Instance
7 Check whether the used JDK version and the Java VM settings of the Java runtime system comply
with the requirements in SAP Note 723909 Update the JDK and adjust the settings if necessary
NOTE
An update of the used JDK version possibly changes the JVM path In this case you must
make the new path available to all Dialog Instances of the J2EE engine by implementing option
1 of SAP Note 718901
8 Make sure that the J2EE administrator password stored in the secure store for offline usage is
identical with the one stored in the User Management Engine (UME) You can change the password
in the secure store as described in SAP Note 870445
9 If you are running a high availability system on Windows you might need to prepare your system
as described in the online documentation for JSPM see section Preparing Systems That Run in High
Availability Environment
223 Updating the Application Server Java and Java-Based Components
Procedure
Applying a Support Package Stack to SAP NetWeaver Application Server Java and Java-Based Components
NOTE
The JSPM GUI might not work properly on some UNIX systems For more information and the
solution see SAP Note 1013976
1 Log on as user ltsapsidgtadm to the Central Instance host
NOTE
If your operating system is IBM i log on as user ltSIDgtADM or ltSIDgtOFR
2 Close the SAP Management Console (SAP MMC) and the SDM remote GUI client
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2360
3 For UNIX and Windows To start the JSPM navigate to the directory ltINSTDIRgtltSIDgt
ltCentral_Instance_Namegtj2eeJSPM and run the go script file
NOTE
If your system is running on IBM i to start the JSPM proceed as follows
1 To prevent JSPM from automatically starting its GUI in the file usrsapltSIDgt
ltCentral_Instance_Namegtj2eeJSPMparamjspm_configtxt change the
property dialogSDTServerConnectionSDTGuilaunch from true to false
2 On the IBM i host run the go script file using the following command
QSH CMD(usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPMgo)
3 In the mounted directory usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPM run
the StartGui script file The JSPM GUI appears
4 In the Host field enter the target IBM i host
NOTE
Depending on the system type ltCentral_Instance_Namegt has the following syntax
Standalone Java system JCltinstance_nogt
Add-On system DVEBMGSltinstance_nogt
4 Enter your SDM password to log on to the SDM
5 On the Deployment tab page select the Java Support Package Manager option and update the software
component sapcomJSPM to the target SPS level
6 Restart the JSPM and log on with the SDM password
RECOMMENDATION
We strongly recommend that you use the Support and Enhancement Package Stack option when
applying a Support Package Stack Other options can lead to unintended consistency issues
NOTE
If you need to include the latest patches for a particular component during the update process
with the Support and Enhancement Package Stack option stop the JSPM after restart and apply SAP
Note 1080821 Then start the JSPM again
7 On the Deployment tab page select the Support and Enhancement Package Stack option and choose Next
The Support Package Stacks that are available for deployment in the global EPS inbox directory
are displayed
8 In the Target SP Stack Level dropdown box select the Support Package Stack to be applied and choose
Next
In this step JSPM performs various status validations and displays the result of each software
component included in the stack definition XML file on the subsequent screen which includes
the following possible statuses
OK Indicates that the SPS level of the corresponding software component is applicable
WARNING We recommend that you view the details about the component by choosing Show
Details
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2460 CUSTOMER 2012-08-30
This status may indicate that the corresponding software component comprises custom
modifications in an NWDI-controlled system
If your system is used for NWDI development and it is either a DEV or a CONS system
you will be informed that JSPM will not deploy the modified software components but
only transport them to the CMS transport directory JSPM will deploy only the software
components that are not modified
If your system is not used for NWDI development or if your system is used for NWDI
development and it is either a TEST or a PROD system you will be informed that JSPM
has found newer versions of modified software components and will automatically replace
the original versions with the newer versions JSPM will deploy all software components
that are not modified together with the replaced versions of the modified software
components
CAUTION
You may get a warning telling you that there are patches installed in your system
containing fixes which might not be included in the target SP Stack This is possible if
you have applied patches of the start SP Stack level that were delivered later than the
target SP Stack delivery date In order not to lose these fixes you need to download and
apply the corresponding patches of the target SP Stack level
If you are performing an update from SAP NetWeaver 70 including enhancement
package 1 SPS00 and you have not applied any patches for the software component with
status WARNING before the update then you can ignore warnings such as the following
example
The new version of the development component sapcomcomsapnetweaver
bcrfmoni is 70100200806121227180000 and is lower than the already
deployed version 70100200807090143420000
REVISE Indicates inconsistencies with the corresponding software component
The deployment cannot be performed until all problems have been resolved You can view
the problems by choosing Show Details
9 If the status of the selected SP Stack is OK or WARNING you can start the system update by choosing
Start JSPM then changes the status to SCHEDULED
If the SP Stack to be applied includes a kernel update and the current kernel is not already of the
corresponding patch level JSPM arranges the kernel update as the very first Support Package to
be applied JSPM updates the kernel binaries of all instances (including Dialog Instances and SCS
instances in a HA environment) whose kernel directories DIR_CT_RUN effectively reside on the host
indicated by the profile parameter SAPGLOBALHOST
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2560
CAUTION
Kernel binaries of instances whose kernel directories DIR_CT_RUN are not effectively linked
to the host SAPGLOBALHOST must be updated individually as described in section Manually
Updating Instances with Kernel Directory Located on Separate Hosts below
The kernel update (includes update of SAP Kernel and SAP IGS) using JSPM consists of the following
steps
1 JSPM stops the Central Instance automatically and prompts you to stop the remote SCS and
Dialog Instances manually
2 After you have stopped all the instances choose the Next button in the dialog box
The kernel update starts
NOTE
If the system is running in a high availability environment make sure that the HA
software does not restart the instance automatically during the update
NOTE
If kernel binaries of the SCS instance need to be updated manually (see Manually Updating
Instances with Kernel Directory Located on Separate Hosts below) you must perform this at the
time when JSPM is updating the kernel binaries of the Central Instance In any case the
SCS kernel must be up-to-date before the next restart
When the kernel update is finished a dialog box appears in which you are prompted to restart
the SCS instance manually
3 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries
before you can proceed with the next step For more information see Adjusting the Ownership and
Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
4 Choose Next in the dialog box when the SCS instance is running again
After the kernel update JSPM restarts the system for further deployment of the remaining Support
Packages in the stack
RECOMMENDATION
If you need to update the kernel binaries of any Dialog Instances manually (see Manually
Updating Instances with Kernel Directory Located on Separate Hosts below) perform the update when
JSPM is updating the remaining Support Packages in the stack in order to save time
The deployment of each Support Package can end with one of the following statuses
DEPLOYED
The Support Package has been successfully deployed
DEPLOYED WITH WARNING
The Support Package has been deployed but it possibly may not work properly with other
deployed components
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2660 CUSTOMER 2012-08-30
You can view the details by choosing Show Details or examining the log files You can also view
the details about the component by choosing the Deployed Components tab page
ERROR
An error has occurred during the deployment You can view the details by choosing Show
Details or examining the log files
You must correct the error to be able to continue with the SP Stack update
You can proceed as described for a deployment that finished with status DEPLOYED WITH
WARNING
If the error correction does not change the contents in the JSPM inbox you can continue
the deployment by choosing Resume
If the error correction changes the contents in the JSPM inbox you can choose New
Deployment to redeploy the SP Stack
NOT DEPLOYED
JSPM has not attempted to deploy the software component for certain reasons
If your system is not used for NWDI development you can proceed as described for a
deployment that finished with status ERROR
If your system is used for NWDI development and it is either a DEV or a CONS system
the status of the modified software components is always NOT DEPLOYED JSPM has
transported the software components of the Support Package Stack both modified and
not modified to the CMS transport directory The deployment of the modified software
components is handled by NWDI
Manually Updating Instances with Kernel Directory Located on Separate Hosts
JSPM performs kernel update for all instances (including Dialog Instances and SCS instances in a HA
environment) whose kernel directories DIR_CT_RUN effectively reside on the host indicated by the profile
parameter SAPGLOBALHOST (by using folder sharing on Windows or file system mounting on UNIX) In
rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of those sort of instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances individually
To update the kernel of an instance manually proceed as follows
1 Log on as user ltsapsidgtadm to the host of the instance to be updated
2 Back up the kernel directory which is specified by the profile parameter DIR_CT_RUN
3 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory with
SAPCAR [page 56]
4 Stop the instance being updated
NOTE
If the system is running in a HA environment make sure that the HA software does not
restart the instance automatically during the update
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2760
5 Copy or move the extracted programs from the temporary directory to the local kernel directory
6 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries as
described in section Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
7 Restart the instance after JSPM has finished the deployment of all packages on the Central Instance
Only valid for UNIX |
Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms
On UNIX platforms you must adjust the ownership and execution permissions of the kernel binaries
after the update regardless whether you performed the update manually or by using JSPM because
both update procedures are performed with the ltsapsidgtadm user Enter the following command
sequence
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
224 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the Java system
23 Parallel Update of Dual-Stack Systems
If you perform an update of a dual-stack system (ABAP+Java) we recommend that you follow the
procedure described below The procedure has been validated to update the ABAP stack and the Java
stack of a NetWeaver system in parallel thus reducing the overall system downtime by half
Procedure
1 Before applying ABAP and Java Support Packages use the Single Support Packages option in JSPM and
select for update only the components SAP KERNEL and BC-FES-IGS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
23 Parallel Update of Dual-Stack Systems
2860 CUSTOMER 2012-08-30
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS)
runs on a dedicated host In this case JSPM does not support update of kernel binaries and
you need to update them manually Perform the update manually as described under Updating
SAP Kernel and SAP IGS in section Updating the Application Server ABAP and ABAP-Based Software
Components [page 16]
2 Import the Support Packages for the component SAP_BASIS into the ABAP stack using the ABAP
Support Package Manager (SPAM)
3 Import the remaining ABAP Support Packages with SPAM and in parallel apply the Java Support
Package Stack with JSPM
Proceed as described in Updating the Application Server ABAP and ABAP-Based Software Components [page
16] and Updating the Application Server Java and Java-Based Software Components [page 23]
24 Process Integration
241 Planning
Procedure
This section covers all the units of Process Integration that should be updated Particularly the following
units must always have the same Support Package level (the patch level can be different)
Integration Server
XI Adapter Engine
Partner Connectivity Kit
System with the Usage Type Process Integration
Software components of Integration Server
Components to Be Updated SP File Name Tool Used to Apply SP
Java stack
XI TOOLS 702 SAPXITOOLltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
ABAP stack
XI CONTENT SAP_BASIS 702 SAPBASISltSPgt_ltPLgtZIP File upload
XI CONTENT SAP_ABA 702 SAPABAltSPgt_ltPLgtZIP
SAP NetWeaver Application Server ABAP (see table Software components of Application Server ABAP [page 15])Note that update of the following software components of the ABAP system is not required SAP ABA 702 SAP BW 702 PI_BASIS 702
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 2960
J2EE Adapter Engine
If your implemented scenario includes a J2EE Adapter Engine then it must always be of the same
Support Package level as the Integration Server
Components of the J2EE Adapter Engine
Component to Be Updated SP File NameTool Used to Apply SP
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
J2SE Adapter Engine
The installation of the J2SE Adapter Engine depends on the implemented scenario
Components of the J2SE Adapter Engine
Component to Be Updated SP File Name Tool Used to Apply SP
XI CONNECTIVITY SE 702 SAPXICONSltSPgt_ltPLgtSCA ZIP tool (for example WinZip)
Partner Connectivity Kit
If your implemented scenario includes a Partner Connectivity Kit (PCK) then it must always be of the
same Support Package level as the Integration Server
Software components of Partner Connectivity Kit
Components to Be Updated SP File NameTool Used to Apply SP
XI PCK 702 SAPXIPCKltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of the Application Server Java [page 20])
System Landscape Directory (SLD)
The System Landscape Directory is required for the PI operations Although updating the SLD is not
necessarily required it is advisable to update the SLD server and the SAP Master Data Content within
it from time to time The update of the SLD includes
1 The system where the SLD is running
2 The SAP Master Data Content within this SLD
SAP GUI
See table Compatible SAP GUI Versions [page 51]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3060 CUSTOMER 2012-08-30
242 Updating Units of Process Integration
Procedure
Before you start the update perform the following steps
In the Runtime Workbench use Communication Channel Monitoring to stop all sender channels
for all adapter types on all your Adapter Engines
On the Integration Server use transaction SMQR and deregister all qRFC queues
System with the Usage Type Process Integration
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the XI instance is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system where the XI instance is running
For more information see Application Server Java and Java-Based Software Components [page 19]
System Landscape Directory (Optional)
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the SLD is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the entire Support Package Stack to the system where the SLD is running
For more information see Application Server Java and Java-Based Software Components [page 19]
J2EE Adapter Engine
Apply the Support Package Stack to the system where the Adapter Engine is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Partner Connectivity Kit
Apply the Support Package Stack to the system where the PCK is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Front End GUIs
Update the SAP GUI components if necessary
For more information see SAP GUI Family [page 51]
ABAP 700 Business System (Optional)
Apply the Support Packages for SAP NetWeaver Application Server ABAP (including SAP kernel and
the Support Package for SAP BASIS 700)
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 640 Business System (Optional)
Apply the Support Packages for SAP Web Application Server ABAP 640 (including SAP kernel and the
Support Package for SAP BASIS 640)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3160
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 620 Business System (Optional)
1 Update the SAP Kernel 620
2 Import the released Basis Support Packages for SAP Web AS 620 as well as the most recent Add-
On Support Package for APPINT 200_620 in the order described in SAP Note 439915
J2SE Adapter Engine (Optional)
NOTE
The XI Adapter Engine (J2SE) and all its adapters are provided for compatibility reasons only and
are not developed any further You have to use the XI Adapter Engine running on SAP NetWeaver
AS Java For more information see the Master Guide ndash SAP NetWeaver 70 available on SAP Service
Marketplace at httpservicesapcominstallNW70 Planning
1 Extract the SAPXICONSltSPgt_ltPLgtSCA (XI Connectivity SE 700) archive (ZIP format) to a temporary
directory
2 Save the old configuration files as described in the document Adapterpdf in directory
lttemp_directorygttech_adapterAdministrationDocumentation
3 Unpack the ZIP archive TechnicalAdapterssda to the installation directory of the XI Adapter
Engine (J2SE)
4 Restore the configuration files with restore_configuration
243 Post-Installation Steps
Procedure
Communication Channels and Queues
Restart all stopped sender channels and register all deregistered qRFC queues
XI Content
In the system with usage type PI import the XI content from the archives SAPBASISltSPgt_ltPLgtZIP
and SAPABAltSPgt_ltPLgtZIP as follows
1 Unpack the archives using a ZIP tool of your choice
2 Copy the corresponding export files (with file extension tpz) to the import directory ltINSTDIRgt
ltSAPSIDgtSYSglobalxirepository_serverimport
3 Start the Integration Builder (transaction SXMB_IFR)
4 Enter the Integration Repository by choosing Repository (Design)
5 Choose Tools Import design objects
6 Import the tpz files containing the XI content
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3260 CUSTOMER 2012-08-30
NOTE
For more information see SAP Note 836200
Role Generation on the Integration Server
On the Integration Server execute transaction SUPC (mass generation of roles) for all SAP_XI roles in
each of your clients to regenerate possibly changed roles
NOTE
Do not forget to make a user comparison for regenerated roles afterwards
Partner Connectivity Kit (Optional)
Perform the post-installation steps for PCK as described in SAP Note 746328
SAP Master Data within the SLD (Optional)
In the system where your SLD is running import the latest SLD content as described in SAP Note
669669
Receiver-Based EOIO Serialization in J2EE Adapter Engine (Optional)
The J2EE Adapter Engine can be switched to receiver-based EOIO serialization The switch can be
triggered on demand and is executed asynchronously It includes a database migration step during
which all EOIO processing in the Adapter Engine is disabled See SAP Note 973894 for details about how
to start the EOIO serialization migration
Service Metering (Optional)
Service metering gathers information about a service caller transfers it to the service provider and
counts on the service provisioning side how many times a service is called and by which service caller
Service metering is performed for the XI message protocol and the WS message protocol Service
metering is automatically enabled after applying a Support Package Stack By default only non-sensitive
data is transmitted to internal or external service providers in a compatible way
Service metering can be configured in PI in the Integration Engine on sender-side and in the Integration
Directory
Service metering can be configured in AS ABAP in transaction SOAMANAGER
Only if the service provider is allowed to receive more detailed information about the service caller set
the metering level to higher than the default
For more information see SAP Note 1239428
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3360
25 Business Intelligence
251 Planning
Procedure
Business Intelligence includes one or many of the following units that must be updated depending on
your implemented scenarios The usage types Business Intelligence (BI) and Business Intelligence Java
Components (BI-Java) must always have the same Support Package level
Business Intelligence
Software Components of Business Intelligence
Component to Be Updated SP File Name Tool Used to Apply SP
BI CONT ADDON 70x SAPK-70ltxgtltSPgtINBICONT SAINT
SAP NetWeaver Application Server ABAP (see table Software Components of Application Server ABAP [page 15])
NOTE
For information about the dependencies applying to BI Content Support Packages see SAP Note
653814 BI CONT 703 Support Packages are not part of the NetWeaver SP Stacks Updates can be
performed when applicable Alternatively BI CONT 704 Support Packages can be imported See
the BI Content release strategy in SAP Note 153967
Business Intelligence Java Components
BI Java Components
Component to Be Updated SP File NameTool Used to Apply SP
BI REPORTING AND PLANNING 702 BIREPPLANltSPgt_ltPLgtSCA JSPM
BI WEBDYNPRO ALV 702 BIWDALVltSPgt_ltPLgtSCA
BI INFORM BROADCASTING 702 BIIBCltSPgt_ltPLgtSCA
BI WEB APPLICATIONS 702 BIWEBAPPltSPgt_ltPLgtSCA
BI BASE SERVICES 702 BIBASESltSPgt_ltPLgtSCA
VISUAL COMPOSER BI KITS 702 VCKITBIltSPgt_ltPLgtSCA
Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
BI Precalculation Service
Components of the BI Precalculation Service
Component to Be Updated SP File Name Tool Used to Apply SP
BI Pre-calculation Service 700 xPreCalServerltSPgt_ltPLgtexe Installer
Search and Classification (TREX)
See table TREX Component [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3460 CUSTOMER 2012-08-30
BI Accelerator
The BI Accelerator is based on the TREX technology It is a special Linux 64-bit version of SAP NetWeaver
70 Search and Classification (TREX) which is delivered on preconfigured hardware
NOTE
You cannot use a TREX installation based on 32-bit architecture that is configured for searching
in metadata and documents for the BI Accelerator And vice versa a BI Accelerator box cannot
be used for searching in metadata and documents
If you want to use the search functionality as well as the BI Accelerator you require two separate
installations For more information see BI Accelerator [page 47]
Clients
Depending on your implemented scenarios you have to update SAP GUI Components and Business
Explorer (BI Add-OnBW Add-On)
NOTE
See SAP Note 889314 to determine when to use the BI Add-On and the BW Add-On
NOTE
As SAP GUI 640 is no longer supported BI Frontend Support Package 1800 resp patch 1801 is the
last Support Package resp patch based on SAP GUI 640 For more information see SAP Note
1231292 (Frontend Add-in Strategy 640710 GUI Version)
For more information about the new release strategy for the BI Frontend see SAP Note 1231363
(Changed Delivery Strategy for BI Frontend)
252 Preparation
Procedure
For the Support Packages of the most important Business Intelligence units so called SAPBINews
(SAPBWNews) Notes are created Read these Notes before updating Business Intelligence For SAP
NetWeaver 70 including enhancement package 2 SPS 12 these are the following
Business Intelligence ABAP SAP Note 1680996
Business Intelligence Java Components SAP Note 1726461
BI 70 Frontend Add-On for SAP GUI 710 SAP Note 1413032
BI 70 Frontend Add-On for SAP GUI 720 SAP Note 1630112
BI 70 Frontend Add-On for SAP GUI 730 SAP Note 1726739
For more information about BI Support Packages see SAP Community Network at http
scnsapcomcommunitydata-warehousingnetweaver-bw Related Resources SAP NW BW Support
Packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
2012-08-30 CUSTOMER 3560
253 Updating Units of Business Intelligence
Procedure
Business Intelligence
1 Update the SAP NetWeaver Application Server ABAP (with BI CONT 70x if necessary) with the
appropriate Support Packages
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
NOTE
When applying the component SAP BW 702 some generation errors might occur When
you start importing the BI Support Packages in transaction SPAM choose the menu path
Extras Ignore generation errors For more information see SAP Note 114134
2 Apply the Support Package Stack to the system with the usage type BI-Java
For more information see Application Server Java and Java-Based Software Components [page 19]
3 Update the BI Precalculation Service that is used in your scenario
4 Update the standalone engine Search and Classification (TREX) that is used in your scenario For more
information see Standalone Engine Search and Classification (TREX) [page 44]
NOTE
You have to update TREX to the newest version if you use search capabilities within Business
Intelligence
5 Update the BI Accelerator to the newest available version For more information see BI
Accelerator [page 47]
6 Update the SAP GUI and Business Explorer (BI Add-On BW Add-On) on all remote client hosts
that are involved in the scenario
For more information see SAP GUI Family [page 51] and Business Explorer (BI Add-On BW Add-On)
[page 51]
BI Precalculation Service
1 Log on to the host as a user with administration rights
2 Install the Support Package of the BI Precalculation Service by executing the
xPreCalServerexe file
The welcome screen of the BI Precalculation Server setup wizard appears
The setup now checks the system for the prerequisites
3 Choose the option Update for updating the BI Precalculation service to the current patch level and
then Finish
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3660 CUSTOMER 2012-08-30
26 EP Core
261 Planning
Procedure
The following installable software units must be updated
EP Core
Software Components of EP Core
Component to Be Updated SP File Name Tool Used to Apply SP
PORTAL CORE SERVICES 702 EPBCltSPgt_ltPLgtSCA JSPM
PORTAL FRAMEWORK 702 EPBC2ltSPgt_ltPLgtSCA
PORTAL 702 EPPSERVltSPgt_ltPLgtSCA
PORTAL WEB DYNPRO 702 EPWDCltSPgt_ltPLgtSCA
UWL COLL PROCESS ENGINE 702 UWLJWFltSPgt_ltPLgtSCA
CAF EU 702 SAPEUltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
262 Preparation
Procedure
Backing Up the Portal Runtime Configuration
If you have made changes to the standard Portal Runtime configuration you have to make a backup
of the configuration before the update process For more information see SAP Note 1064468
263 Updating EP Core
Procedure
Apply the Support Package Stack to a system with usage type EP Core
For more information see Application Server Java and Java-Based Software Components [page 19]
264 Post-Installation Steps for EP Core
Procedure
Restoring the Portal Runtime Configuration
To make your changes to the standard Portal Runtime Configuration effective you have to restore
the backup of the configuration done before the update process For more information see SAP Note
1064468
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
26 EP Core
2012-08-30 CUSTOMER 3760
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
263 Updating EP Core 37
264 Post-Installation Steps for EP Core 37
27 Enterprise Portal 38
271 Planning 38
272 Updating Enterprise Portal 38
273 Post-Installation Steps for Enterprise Portal 39
28 Development Infrastructure 40
281 Planning 40
282 Updating Development Infrastructure 41
29 Mobile Infrastructure 43
291 Planning 43
292 Preparation 43
293 Updating Mobile Infrastructure 43
210 Standalone Engines 44
2101 Search and Classification (TREX) 44
21011 Planning 44
21012 Preparation 44
21013 Updating TREX 45
2102 BI Accelerator 47
21021 Planning 47
21022 Preparation 48
21023 Updating BI Accelerator 48
21024 Post-Installation Steps 49
2103 Gateway 50
2104 SAP Web Dispatcher 50
2105 Other Standalone Engines 50
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2 51
2111 SAP GUI Family 51
2112 Business Explorer (BI Add-On BW Add-On) 51
2113 Other Clients 52
212 SAP Library 52
Chapter A Appendix 55
A1 Determining the Current Component Versions 55
A2 Tools Used During the System Update 56
A21 SAPCAR 56
A22 ABAP Support Package Manager and Add-On Installation Tool 57
A23 Java Support Package Manager 58
2012-08-30 CUSTOMER 760
A3 System Profile Parameters 58
860 CUSTOMER 2012-08-30
1 Overview
This document describes how to install Support Package Stacks (SP Stacks) for SAP NetWeaver 70
including enhancement package 2 You can find all information related to the SP Stacks on SAP Service
Marketplace at httpservicesapcomsp-stacks
11 Before You Start
CAUTION
If you intend to update your system to the latest SP Stack level and plan to upgrade it within the
next 6 months first check the availability of the equivalent SP Stack for the target release The
delivery dates of the equivalent SP Stacks for your source and target release might be several
months apart
Be aware that you cannot upgrade to a target release that does not include the equivalent SP Stack
level
To avoid a deadlock situation we recommend that you check SAP Service Marketplace at
httpservicesapcomsp-stacks SP Stack Information and consider not applying the
latest SP Stack on your source release system
Updated Document Versions
The Support Package Stack Guide is regularly updated on SAP Service Marketplace at http
servicesapcommaintenanceNW70
NOTE
Make sure you have the latest version of the Support Package Stack Guide by checking SAP Service
Marketplace immediately before you start to apply or import Support Packages
SAP Notes
You must read SAP Note 1460321 before you read this document as it may contain corrections and
further information about the Support Package Stack installation
SAP Library
You must inform yourself about enhancements and changes to the Support Package Stack to be applied
from SAP Library under SAP Library SAP NetWeaver Whatrsquos New in SAP NetWeaver 70 ndash Release
Notes You can access the SAP Library in one of the following ways
SAP Help Portal at httphelpsapcomnw702 Application Help SAP Library ltLanguagegt
1 Overview
11 Before You Start
2012-08-30 CUSTOMER 960
NOTE
The SAP Help Portal always provides the up-to-date version of the SAP Library Therefore
we recommend that you use this channel to access the SAP Library
Local installation of the SAP Library from the online documentation DVD
CAUTION
In order to inform yourself about the current Support Package Stack you first have to update
your local installation of the SAP Library to the corresponding SPS level Follow the
instructions in section SAP Library [page 52]
Naming Conventions
In this document the following naming conventions apply
Variables
Variables Description
ltSAPSIDgt
ltsapsidgt
ltSIDgt
SAP system ID
ltINSTDIRgt Installation directory for the SAP system
lthostgt Host name
ltinstance_nogt Instance number of a system instance
ltdatabasegt Name of database
ltsapinst_directorygt Installation directory for the SAP installation tool SAPinst
ltsp_directorygt Temporary directory which the archives of a Support Package are downloaded or copied to
ltOSgt Operating system
ltOS_DIRgt OS-dependent directory consisting of a folder for the platform and a subfolder of your OS versionFor example if you operating system is Sun OS 64bit ltOS_DIRgt stands for UNIXSUNOS64
ltSP_Stackgt Number of Support Package Stack
ltSPgt Support Package level
ltPLgt Support Package patch level
ltRELgt Release number
ltLOCALEgt Language definitionFor example the German locale is _de
ltkrnl_directorygt Kernel directory which the profile parameter DIR_CT_RUN usually refers to
ltsdm_homegt Program file location of the Software Deployment Manager (SDM)
ltSAPGLOBALHOSTgt SAP global host the host where the global directories of an SAP system reside
ltSAPLOCALHOSTgt SAP local host the host where a particular instance of an SAP system is running
1 Overview
11 Before You Start
1060 CUSTOMER 2012-08-30
12 Types of Support Packages
The following table explains the terms used in the correction process as part of the software maintenance
process for SAP NetWeaver
Correction Process Description
Standard correction process
Support Package Stack Description
A Support Package Stack is a set of Support Packages and patches for the respective product version that must be used in the given combination
Version numbersSupport Package Stacks have a release number and a stack number for example SAP NetWeaver 70 Support Package Stack 05
DeliveryThere is no dedicated delivery format for the Support Package Stacks The included Support Package files have their delivery formats and must be applied using the tools as described below
Kernel Patches Version numbers
SAP Kernel patches have a release number and a patch number The patch number is increased with each correction
DeliverySAP Kernel patches are delivered as SAR files They are installed by extracting the SAR files to the kernel directory using SAPCAR Separate SAR files are shipped for the different kernel types depending on UNICODENON-UNICODE and the platform
ABAP Support Packages Description
ABAP Support Packages contain corrections and adjustments for the ABAP-based Software Components of the SAP system
DependenciesIn contrast to Java Support Packages ABAP Support Packages are non-cumulative Therefore ABAP Support Packages must be installed in the correct sequence one after the other You cannot skip any intermediate Support Packages
DeliveryABAP Support Packages are delivered as SAR files They are installed using the Support Package Manager (SPAM)
Java Support Packages Description
Java Support Packages contain corrections for the Java-based Software Components of the SAP system
DependenciesJava Support Packages always contain a full delivery of the Software Components Therefore you only need to apply the latest Support Package to update the software If there are dependencies with other Java Support Packages these are specified in an SAP Note
DeliveryJava Support Packages are delivered as Software Component Archives (SCAs) They are applied using the Java Support Package Manager (JSPM)
1 Overview
12 Types of Support Packages
2012-08-30 CUSTOMER 1160
Correction Process Description
Emergency correction process
SAP Note Correction (ABAP) Description
SAP Note corrections contain single ABAP fixes Delivery
SAP Note corrections are delivered with SAP Notes If required you apply them using the SAP Note Assistant
Java Support Package Patch Description
A Java Support Package patch contains corrections for the Java Software Components Java Support Package patches are created and released on demand A Java Support Package patch corresponds to an SAP Note that describes the same correction
DependenciesA Java Support Package patch always contains a full package of the corresponding Software Component and is applied using JSPM
13 Downloading Support Package Stacks
The Maintenance Optimizer in SAP Solution Manager is the only source from which you can receive
maintenance updates for SAP NetWeaver 70 and higher releases as well as for all applications running
on top of SAP NetWeaver The Maintenance Optimizer supports you in selecting and downloading all
required maintenance files In addition the Maintenance Optimizer generates a stack XML file and
saves it to the EPS inbox directory of SAP Solution Manager
Prerequisites
You have configured the Maintenance Optimizer in SAP Solution Manager as described on SAP Help
Portal at httphelpsapcom SAP Solutions SAP Solution Manager SAP Solution Manager ltReleasegt
ltLanguagegt Change Management Maintenance Optimizer Planning and Monitoring Product Maintenance and
also in section Automatically Calculating Product Maintenance Files
Procedure
To download a Support Package Stack proceed as follows
1 Start SAP Solution Manager using the transaction solution_manager To start the Maintenance
Optimizer choose Operations Change Management Maintenance Optimizer
2 In the Maintenance Optimizer choose the solution for which you want to download SP Stack files
3 Choose Create New Maintenance Transaction
4 Select the product version for which you want to apply a Support Package Stack
The Maintenance Optimizer displays all the systems assigned to the selected product version
5 Select the checkbox for the system that you want to update and choose Continue
6 On the subsequent screen select the Maintenance option and then choose Find Download Files
1 Overview
13 Downloading Support Package Stacks
1260 CUSTOMER 2012-08-30
7 Select the target SP Stack level and the relevant usage types according to the IT scenario to be
updated
8 Choose Find Download Files for the Stack Version
The Maintenance Optimizer displays the product maintenance files in three successive lists
9 Select the required files from the displayed lists
The first list shows all files that are dependent on the type of your operating system and
database
Select the files that correspond to the combination of your operating system and database and
the database-independent files
If your system is distributed on several hosts make sure to select all operating systems used
by the NetWeaver instances You can see all the kernels detected on your system on the Deployed
Components tab page on JSPM user interface (under the SAP KERNEL node) All detected kernels
must be updated to the same version
You get to the second list by choosing Continue This list displays all Support Package files that
are not assigned to the selected Support Package Stack Before you continue with the selection
you must check whether the Support Package files listed here are suitable for your product
maintenance procedure
You get to the third list by choosing Continue The list displays all product maintenance files
that are part of the selected Support Package Stack
Ensure that all files that are assigned to the Support Package Stack are selected here Files that
are not selected will not be included later in the download
10 Choose Continue Use the Download Basket to download the maintenance files
11 Choose Continue once the files have been put in your Download Basket and then Confirm Files in
Download Basket
A dialog window appears and displays all files
12 Confirm the download for all files
13 Open your Download Manager and download the files
NOTE
The stack XML file is generated by the Maintenance Optimizer and automatically saved to
the EPS inbox directory of SAP Solution Manager
More Information
For more information about the Maintenance Optimizer see SAP Support Portal at http
servicesapcomsolman-mopz
1 Overview
13 Downloading Support Package Stacks
2012-08-30 CUSTOMER 1360
This page is left blank for documents that are printed on both sides
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
This chapter describes how to apply Support Packages to installable software units of SAP NetWeaver
70 including enhancement package 2 SAP NetWeaver distinguishes three types of installable software
units
Systems with one or multiple usage types
Standalone engines
Clients
A scenario implementation usually involves several installed software units
RECOMMENDATION
We strongly recommend that you always update all software units belonging to one scenario
together in order to retain a consistent system state Due to the fact that some installable software
units can be commonly shared in different scenarios you must consequently update all scenarios
using the common software units at the same time
21 Application Server ABAP and ABAP-Based Software Components
211 Planning
Procedure
The following components belong to the usage type SAP NetWeaver Application Server ABAP
Software Components of Application Server ABAP
Component to Be Updated SP File Name Tool Used to Apply SP
SAP KERNEL 720 32-64-BIT Non-UNICODEUNICODE SAPEXESAR
SAPEXEDBSAR
JSPMmanually
SAP IGS 700 igsexesar
SAP ABA 702 SAPKA702ltSPgt SPAMSAINT
SAP BASIS 702 SAPKB702ltSPgt
SAP BW 702 SAPKW702ltSPgt
PI_BASIS 702 SAPK-702ltSPgtINPIBASIS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
2012-08-30 CUSTOMER 1560
NOTE
This table contains only software components that belong to the usage type AS ABAP Software
components of other usage types and application units are listed in the corresponding sections
NOTE
SAP delivers intermediate Support Packages for the component SAP BW 702 between two
subsequent SP levels besides the Support Packages delivered along with the Support Package
Stacks Therefore the highest SP level of SAP BW 702 does not necessarily match the target SP
Stack level
CAUTION
When applying a Support Package Stack to a dual-stack system (ABAP+Java) the Java Support
Package Manager (JSPM) will necessarily restart the system several times to make the changes
effective The ABAP part will only be restarted when JSPM is updating the SAP kernel and IGS
212 Preparation
Procedure
Read SAP Note 822379 and all related SAP Notes that the first one refers to
213 Updating the Application Server ABAP and ABAP-Based Software Components
Procedure
Applying Support Packages to SAP NetWeaver Application Server ABAP and ABAP-Based Components
You can update the SAP NetWeaver Application Server ABAP and all ABAP-based software components
running on it using the Support Package Manager (transaction SPAM)
NOTE
If a particular Support Package Stack requires the installation or upgrade of some add-on
components you must use the ABAP Add-on Installation Tool (transaction SAINT) instead of the
Support Package Manager In this case SAINT is able to import both the add-on components and
the related Support Packages of ordinary SAP components
Proceed as follows
1 Log on to the SAP NetWeaver AS system with client 000
2 Start the Support Package Manager by calling transaction SPAM or
start the Add-On Installation Tool by calling transaction SAINT
3 Load the relevant Support Packages or add-on installation packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
1660 CUSTOMER 2012-08-30
4 Define an import queue
5 Perform the import of the defined queue
NOTE
If you have modified SAP objects in your system and these objects are included in the Support
Packages you must perform modification adjustment during the import using the
transactions SPDD (for ABAP Dictionary objects) and SPAU (for Repository objects)
To import the queue you use the standard scenario You can choose between the conventional
import mode and downtime-minimized import mode
Conventional Import Mode
This option comprises the following steps
1 Update the SAP kernel and SAP IGS as described in section Updating SAP Kernel and SAP IGS below
Start the system after the kernel update
2 Import the ABAP Support Packages with the Support Package Manager (SPAM)
Import Mode Downtime-Minimized
This option can be used to reduce system downtime during the update It comprises the following
steps
1 In transaction SPAM enable the downtime-minimized import mode by choosing Extras
Settings then on the Import queue tab page choose Standard and activate the option Import Mode
Downtime-Minimized
2 Import the ABAP Support Packages into the system in an inactive state in the downtime-minimized
mode during system uptime
3 Update the SAP kernel and SAP IGS as described in section Updating SAP Kernel and SAP IGS below
Start the system after the kernel update
4 Complete the ABAP Support Packages import
CAUTION
During this step the system cannot carry out any business transactions (business downtime)
NOTE
In rare cases due to the dependencies of some Support Packages on a particular kernel patch level
the downtime-minimized update does not work In such cases the Support Package Manager
informs you that you must update the SAP kernel before importing ABAP Support Packages You
must proceed with the conventional import procedure
Updating SAP Kernel and SAP IGS
In general the SAP kernel and IGS binaries are located in the global kernel directory DIR_CT_RUN on
the host indicated by the profile parameter SAPGLOBALHOST Once the files in this directory have been
updated to a new patch level a system restart distributes them by means of the program SAPCPE to the
local directories DIR_EXECUTABLE on the hosts where the instances of the SAP system are running
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
2012-08-30 CUSTOMER 1760
CAUTION
The automatic distribution by means of SAPCPE depends on the settings of the profile parameters
DIR_CT_RUN for the global kernel directory and DIR_EXECUTABLE for the local directory of the
executables Before you continue check the instance profiles for the settings of these parameters
in systems that are not installed using SAPinst (for example systems upgraded from older releases
copied or migrated systems)
CAUTION
If your system is a dual-stack system (ABAP+Java) and the ABAP stack has a non-Unicode kernel
be aware that the SCS instance has a Unicode kernel You have to update both kernels (together
with SAP IGS) prior to updating the ABAP and Java Support Package stacks This ensures
compatibility and reduces system downtime
RECOMMENDATION
If you perform an update of a dual-stack system (ABAP+Java) we recommend that prior to
applying ABAP and Java Support Package stacks you use the Single Support Packages option in JSPM
and select for update only the components SAP KERNEL and BC-FES-IGS
For more information about updating a dual-stack system see Parallel Update of Dual-Stack Systems
[page 28]
If you perform an update of an ABAP system the following procedure applies for updating the SAP
kernel and IGS manually
1 Log on as user ltsapsidgtadm to the instance host to be updated
2 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory using
SAPCAR [page 56]
3 Stop the ABAP system that you want to update
NOTE
If the system is running in a high availability (HA) environment make sure that the HA
software does not restart the system automatically during the update
4 Back up the kernel directory ltkrnl_directorygt
5 Copy or move the extracted programs from the temporary directory to the SAP kernel directory
6 Only valid for UNIX |
Execute the following command sequence on UNIX platforms
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
1860 CUSTOMER 2012-08-30
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
7 Restart the SAP system
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS) runs
on a dedicated host You need to perform the kernel update for the ASCS instance manually but
excluding the IGS update because the IGS is not required in an ASCS instance
In rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of such instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances manually Proceed as described
in section Manually Updating Instances with Kernel Directory Located on Separate Hosts below in this document
214 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the ABAP system
22 Application Server Java and Java-Based Software Components
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system which includes
JSPM itself
SAP Kernel and SAP IGS
All Java-based usage types installed in the system
Software Deployment Manager (SDM) - the deployment service of the system
RECOMMENDATION
We strongly recommend that you apply the target Support Package Stack to your system as a
whole This ensures consistency on both the system and the application levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 1960
221 Planning
Procedure
Java Support Package files (SCAs) contain all software objects of the corresponding software
components Thus it is sufficient to apply the Java Support Package files of the intended Support Package
Stack directly to the Java system to be updated It is not necessary to apply the Support Package Stacks
between the start SP Stack level and the target SP Stack level successively
CAUTION
When applying a Support Package Stack to a Java system the Java Support Package Manager (JSPM)
will necessarily restart the system several times to make the changes effective With a dual-stack
system (ABAP+Java) the ABAP part will only be restarted when JSPM is updating the SAP kernel
and IGS
The following components belong to the usage type SAP NetWeaver Application Server Java (AS Java)
Software Components of Application Server Java
Component to Be Updated SP File Name Tool Used to Apply SP
SAP Kernel 720 32-64-BIT UNICODE SAPEXESAR
SAPEXEDBSAR
JSPM
SAP IGS 700 igsexesar
BI META MODEL REPOSITORY 702 BIMMRltSPgt_ltPLgtSCA
J2EE ENGINE CORE TOOLS 702 CORETOOLSltSPgt_ltPLgtSCA
J2EE ENGINE BASE TABLES 702 BASETABLESltSPgt_ltPLgtSCA
BI UDI 702 BIUDIltSPgt_ltPLgtSCA
DI BUILD TOOL 702 SAPBUILDTltSPgt_ltPLgtSCA
SAP CAF 702 CAFltSPgt_ltPLgtSCA
SAP IKS 702 KMKWJIKSltSPgt_ltPLgtSCA
JAVA LOG VIEWER 702 JLOGVIEWltSPgt_ltPLgtSCA
SAP J2EE ENGINE CORE 702 SAPJEECORltSPgt_ltPLgtSCA
SAP JAVA TECH SERVICES 702 SAPJTECHSltSPgt_ltPLgtSCA
SAP TECH S OFFLINE 702 SAPJTECHFltSPgt_ltPLgtSCA
SAP J2EE ENGINE 702 SAPJEEltSPgt_ltPLgtSCA
JAVA SP MANAGER 702 JSPMltSPgt_ltPLgtSCA
ADOBE DOCUMENT SERVICES 702 ADSSAPltSPgt_ltPLgtSCA
UME ADMINISTRATION 702 UMEADMINltSPgt_ltPLgtSCA
LIFECYCLE MGMT TOOLS 702 LMTOOLSltSPgt_ltPLgtSCA
SAP CAF-UM 702 CAFUMltSPgt_ltPLgtSCA
SAP SOFTW DELIV MANAGER 702 SDMKITltSPgt_ltPLgtJAR
SOFTWARE LIFECYCLE MANAGER 702 SWLIFECYCLltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2060 CUSTOMER 2012-08-30
NOTE
This table contains only software components that belong to the usage type AS Java Software
components of other usage types and Java application units are listed in the corresponding
sections
NOTE
As of Support Package 09 you can update your system with SAP Kernel 720 instead of SAP Kernel
701
222 Preparation for Applying a Support Package Stack
Procedure
1 Download the Support Package Stack with all usage types to be updated and the stack definition
XML file as described in Downloading Support Package Stacks [page 12]
NOTE
You can find the activated usage types in an existing Java system on the Deployed Components tab
page on the JSPM user interface
NOTE
You do not need to download the SP Stacks between the source SP Stack level and target SP
Stack level By default the target SP Stack level is the latest available SP Stack
2 Make sure the following requirements are met prior to applying the Support Package Stack
You have familiarized yourself with SAP Note 891983 before you start the Java Support Package
Manager
The system to be updated is fully functional
The Support Package Stack you want to apply and the corresponding stack definition XML
file are available in the EPS inbox directory usrsaptransEPSin By default this location
can be also referred to as ldquoJSPM inboxrdquo
The SAP NetWeaver Application Server Java (AS Java) and the database have been backed up
You have not deleted renamed or created any directories and files in the following directories
and their subdirectories usrsapltSAPSIDgtSYSexe and usrsapltSAPSIDgtSYS
profile
Otherwise JSPM cannot detect the kernel and the system profiles and cannot be started If a
backup of the kernel and the system profiles has been required it has been created in a different
directory
The ltsapsidgtadm user has Read permissions for the EPS inbox directory usrsaptransEPS
in
If your database is SAP MaxDB the overwrite mode for the log area has been activated
The database and the SDM repository have been synchronized
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2160
For more information see the online documentation for JSPM on SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70 Library
(including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library Administrators Guide
Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems AS Java
(Application Server for Java) Software Logistics Software Maintenance Java Support Package Manager
Then choose Troubleshooting JSPM Does Not Update the Versions of the Deployed Components
There is enough disk space
For more information see SAP Note 891895
Your current SAPCAR tool is able to extract the Support Packages for the SAP kernel and
other OS level binaries delivered as SAR files
RECOMMENDATION
You can download the latest version of SAPCAR from SAP Service Marketplace at
httpservicesapcompatches Entry by Application Group Additional Components
SAPCAR
Put the downloaded version in the same directory in the JSPM inbox in which the kernel
SAR files reside so that JSPM can use this version for extracting the SAR files
3 Only valid for Linux |
For RHEL 4 and SLES 9 you need to install additional operating system packages For more
information see SAP Note 1021236End of Linux |
4 Only valid for Windows |
For Windows you need to install additional operating system packages For more information see
SAP Note 684106End of Windows |
5 To prevent the Software Deployment Manager (SDM) from temporarily exceeding the available
disk space during the update process you can change the file transfer directory of SDM in a system
of SPS09 or higher using the following command sequence
Only valid for Windows |
cd ltsdm_homegt
StopServerbat
sdmbat jstartup mode=standalone
sdmbat filetransferdir dir=ltnew_dirgt
sdmbat jstartup mode=integrated
StartServerbat
End of Windows |
Only valid for IBM i5OSUNIX |
cd ltsdm_homegt
StopServersh
sdmsh jstartup mode=standalone
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2260 CUSTOMER 2012-08-30
sdmsh filetransferdir dir=ltnew_dirgt
sdmsh jstartup mode=integrated
StartServersh
End of IBM i5OSUNIX |
6 To prevent deployment errors during the update process proceed as follows
1 Log on to the Central Instance host
2 Start the ConfigTool and in the navigation area choose Cluster-data Global server configuration
Managers ServiceManager
3 In the Global properties panel set the Custom value of the EventTimeout property to 120
4 Choose Save
5 Restart the Central Instance
7 Check whether the used JDK version and the Java VM settings of the Java runtime system comply
with the requirements in SAP Note 723909 Update the JDK and adjust the settings if necessary
NOTE
An update of the used JDK version possibly changes the JVM path In this case you must
make the new path available to all Dialog Instances of the J2EE engine by implementing option
1 of SAP Note 718901
8 Make sure that the J2EE administrator password stored in the secure store for offline usage is
identical with the one stored in the User Management Engine (UME) You can change the password
in the secure store as described in SAP Note 870445
9 If you are running a high availability system on Windows you might need to prepare your system
as described in the online documentation for JSPM see section Preparing Systems That Run in High
Availability Environment
223 Updating the Application Server Java and Java-Based Components
Procedure
Applying a Support Package Stack to SAP NetWeaver Application Server Java and Java-Based Components
NOTE
The JSPM GUI might not work properly on some UNIX systems For more information and the
solution see SAP Note 1013976
1 Log on as user ltsapsidgtadm to the Central Instance host
NOTE
If your operating system is IBM i log on as user ltSIDgtADM or ltSIDgtOFR
2 Close the SAP Management Console (SAP MMC) and the SDM remote GUI client
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2360
3 For UNIX and Windows To start the JSPM navigate to the directory ltINSTDIRgtltSIDgt
ltCentral_Instance_Namegtj2eeJSPM and run the go script file
NOTE
If your system is running on IBM i to start the JSPM proceed as follows
1 To prevent JSPM from automatically starting its GUI in the file usrsapltSIDgt
ltCentral_Instance_Namegtj2eeJSPMparamjspm_configtxt change the
property dialogSDTServerConnectionSDTGuilaunch from true to false
2 On the IBM i host run the go script file using the following command
QSH CMD(usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPMgo)
3 In the mounted directory usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPM run
the StartGui script file The JSPM GUI appears
4 In the Host field enter the target IBM i host
NOTE
Depending on the system type ltCentral_Instance_Namegt has the following syntax
Standalone Java system JCltinstance_nogt
Add-On system DVEBMGSltinstance_nogt
4 Enter your SDM password to log on to the SDM
5 On the Deployment tab page select the Java Support Package Manager option and update the software
component sapcomJSPM to the target SPS level
6 Restart the JSPM and log on with the SDM password
RECOMMENDATION
We strongly recommend that you use the Support and Enhancement Package Stack option when
applying a Support Package Stack Other options can lead to unintended consistency issues
NOTE
If you need to include the latest patches for a particular component during the update process
with the Support and Enhancement Package Stack option stop the JSPM after restart and apply SAP
Note 1080821 Then start the JSPM again
7 On the Deployment tab page select the Support and Enhancement Package Stack option and choose Next
The Support Package Stacks that are available for deployment in the global EPS inbox directory
are displayed
8 In the Target SP Stack Level dropdown box select the Support Package Stack to be applied and choose
Next
In this step JSPM performs various status validations and displays the result of each software
component included in the stack definition XML file on the subsequent screen which includes
the following possible statuses
OK Indicates that the SPS level of the corresponding software component is applicable
WARNING We recommend that you view the details about the component by choosing Show
Details
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2460 CUSTOMER 2012-08-30
This status may indicate that the corresponding software component comprises custom
modifications in an NWDI-controlled system
If your system is used for NWDI development and it is either a DEV or a CONS system
you will be informed that JSPM will not deploy the modified software components but
only transport them to the CMS transport directory JSPM will deploy only the software
components that are not modified
If your system is not used for NWDI development or if your system is used for NWDI
development and it is either a TEST or a PROD system you will be informed that JSPM
has found newer versions of modified software components and will automatically replace
the original versions with the newer versions JSPM will deploy all software components
that are not modified together with the replaced versions of the modified software
components
CAUTION
You may get a warning telling you that there are patches installed in your system
containing fixes which might not be included in the target SP Stack This is possible if
you have applied patches of the start SP Stack level that were delivered later than the
target SP Stack delivery date In order not to lose these fixes you need to download and
apply the corresponding patches of the target SP Stack level
If you are performing an update from SAP NetWeaver 70 including enhancement
package 1 SPS00 and you have not applied any patches for the software component with
status WARNING before the update then you can ignore warnings such as the following
example
The new version of the development component sapcomcomsapnetweaver
bcrfmoni is 70100200806121227180000 and is lower than the already
deployed version 70100200807090143420000
REVISE Indicates inconsistencies with the corresponding software component
The deployment cannot be performed until all problems have been resolved You can view
the problems by choosing Show Details
9 If the status of the selected SP Stack is OK or WARNING you can start the system update by choosing
Start JSPM then changes the status to SCHEDULED
If the SP Stack to be applied includes a kernel update and the current kernel is not already of the
corresponding patch level JSPM arranges the kernel update as the very first Support Package to
be applied JSPM updates the kernel binaries of all instances (including Dialog Instances and SCS
instances in a HA environment) whose kernel directories DIR_CT_RUN effectively reside on the host
indicated by the profile parameter SAPGLOBALHOST
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2560
CAUTION
Kernel binaries of instances whose kernel directories DIR_CT_RUN are not effectively linked
to the host SAPGLOBALHOST must be updated individually as described in section Manually
Updating Instances with Kernel Directory Located on Separate Hosts below
The kernel update (includes update of SAP Kernel and SAP IGS) using JSPM consists of the following
steps
1 JSPM stops the Central Instance automatically and prompts you to stop the remote SCS and
Dialog Instances manually
2 After you have stopped all the instances choose the Next button in the dialog box
The kernel update starts
NOTE
If the system is running in a high availability environment make sure that the HA
software does not restart the instance automatically during the update
NOTE
If kernel binaries of the SCS instance need to be updated manually (see Manually Updating
Instances with Kernel Directory Located on Separate Hosts below) you must perform this at the
time when JSPM is updating the kernel binaries of the Central Instance In any case the
SCS kernel must be up-to-date before the next restart
When the kernel update is finished a dialog box appears in which you are prompted to restart
the SCS instance manually
3 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries
before you can proceed with the next step For more information see Adjusting the Ownership and
Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
4 Choose Next in the dialog box when the SCS instance is running again
After the kernel update JSPM restarts the system for further deployment of the remaining Support
Packages in the stack
RECOMMENDATION
If you need to update the kernel binaries of any Dialog Instances manually (see Manually
Updating Instances with Kernel Directory Located on Separate Hosts below) perform the update when
JSPM is updating the remaining Support Packages in the stack in order to save time
The deployment of each Support Package can end with one of the following statuses
DEPLOYED
The Support Package has been successfully deployed
DEPLOYED WITH WARNING
The Support Package has been deployed but it possibly may not work properly with other
deployed components
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2660 CUSTOMER 2012-08-30
You can view the details by choosing Show Details or examining the log files You can also view
the details about the component by choosing the Deployed Components tab page
ERROR
An error has occurred during the deployment You can view the details by choosing Show
Details or examining the log files
You must correct the error to be able to continue with the SP Stack update
You can proceed as described for a deployment that finished with status DEPLOYED WITH
WARNING
If the error correction does not change the contents in the JSPM inbox you can continue
the deployment by choosing Resume
If the error correction changes the contents in the JSPM inbox you can choose New
Deployment to redeploy the SP Stack
NOT DEPLOYED
JSPM has not attempted to deploy the software component for certain reasons
If your system is not used for NWDI development you can proceed as described for a
deployment that finished with status ERROR
If your system is used for NWDI development and it is either a DEV or a CONS system
the status of the modified software components is always NOT DEPLOYED JSPM has
transported the software components of the Support Package Stack both modified and
not modified to the CMS transport directory The deployment of the modified software
components is handled by NWDI
Manually Updating Instances with Kernel Directory Located on Separate Hosts
JSPM performs kernel update for all instances (including Dialog Instances and SCS instances in a HA
environment) whose kernel directories DIR_CT_RUN effectively reside on the host indicated by the profile
parameter SAPGLOBALHOST (by using folder sharing on Windows or file system mounting on UNIX) In
rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of those sort of instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances individually
To update the kernel of an instance manually proceed as follows
1 Log on as user ltsapsidgtadm to the host of the instance to be updated
2 Back up the kernel directory which is specified by the profile parameter DIR_CT_RUN
3 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory with
SAPCAR [page 56]
4 Stop the instance being updated
NOTE
If the system is running in a HA environment make sure that the HA software does not
restart the instance automatically during the update
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2760
5 Copy or move the extracted programs from the temporary directory to the local kernel directory
6 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries as
described in section Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
7 Restart the instance after JSPM has finished the deployment of all packages on the Central Instance
Only valid for UNIX |
Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms
On UNIX platforms you must adjust the ownership and execution permissions of the kernel binaries
after the update regardless whether you performed the update manually or by using JSPM because
both update procedures are performed with the ltsapsidgtadm user Enter the following command
sequence
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
224 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the Java system
23 Parallel Update of Dual-Stack Systems
If you perform an update of a dual-stack system (ABAP+Java) we recommend that you follow the
procedure described below The procedure has been validated to update the ABAP stack and the Java
stack of a NetWeaver system in parallel thus reducing the overall system downtime by half
Procedure
1 Before applying ABAP and Java Support Packages use the Single Support Packages option in JSPM and
select for update only the components SAP KERNEL and BC-FES-IGS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
23 Parallel Update of Dual-Stack Systems
2860 CUSTOMER 2012-08-30
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS)
runs on a dedicated host In this case JSPM does not support update of kernel binaries and
you need to update them manually Perform the update manually as described under Updating
SAP Kernel and SAP IGS in section Updating the Application Server ABAP and ABAP-Based Software
Components [page 16]
2 Import the Support Packages for the component SAP_BASIS into the ABAP stack using the ABAP
Support Package Manager (SPAM)
3 Import the remaining ABAP Support Packages with SPAM and in parallel apply the Java Support
Package Stack with JSPM
Proceed as described in Updating the Application Server ABAP and ABAP-Based Software Components [page
16] and Updating the Application Server Java and Java-Based Software Components [page 23]
24 Process Integration
241 Planning
Procedure
This section covers all the units of Process Integration that should be updated Particularly the following
units must always have the same Support Package level (the patch level can be different)
Integration Server
XI Adapter Engine
Partner Connectivity Kit
System with the Usage Type Process Integration
Software components of Integration Server
Components to Be Updated SP File Name Tool Used to Apply SP
Java stack
XI TOOLS 702 SAPXITOOLltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
ABAP stack
XI CONTENT SAP_BASIS 702 SAPBASISltSPgt_ltPLgtZIP File upload
XI CONTENT SAP_ABA 702 SAPABAltSPgt_ltPLgtZIP
SAP NetWeaver Application Server ABAP (see table Software components of Application Server ABAP [page 15])Note that update of the following software components of the ABAP system is not required SAP ABA 702 SAP BW 702 PI_BASIS 702
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 2960
J2EE Adapter Engine
If your implemented scenario includes a J2EE Adapter Engine then it must always be of the same
Support Package level as the Integration Server
Components of the J2EE Adapter Engine
Component to Be Updated SP File NameTool Used to Apply SP
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
J2SE Adapter Engine
The installation of the J2SE Adapter Engine depends on the implemented scenario
Components of the J2SE Adapter Engine
Component to Be Updated SP File Name Tool Used to Apply SP
XI CONNECTIVITY SE 702 SAPXICONSltSPgt_ltPLgtSCA ZIP tool (for example WinZip)
Partner Connectivity Kit
If your implemented scenario includes a Partner Connectivity Kit (PCK) then it must always be of the
same Support Package level as the Integration Server
Software components of Partner Connectivity Kit
Components to Be Updated SP File NameTool Used to Apply SP
XI PCK 702 SAPXIPCKltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of the Application Server Java [page 20])
System Landscape Directory (SLD)
The System Landscape Directory is required for the PI operations Although updating the SLD is not
necessarily required it is advisable to update the SLD server and the SAP Master Data Content within
it from time to time The update of the SLD includes
1 The system where the SLD is running
2 The SAP Master Data Content within this SLD
SAP GUI
See table Compatible SAP GUI Versions [page 51]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3060 CUSTOMER 2012-08-30
242 Updating Units of Process Integration
Procedure
Before you start the update perform the following steps
In the Runtime Workbench use Communication Channel Monitoring to stop all sender channels
for all adapter types on all your Adapter Engines
On the Integration Server use transaction SMQR and deregister all qRFC queues
System with the Usage Type Process Integration
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the XI instance is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system where the XI instance is running
For more information see Application Server Java and Java-Based Software Components [page 19]
System Landscape Directory (Optional)
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the SLD is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the entire Support Package Stack to the system where the SLD is running
For more information see Application Server Java and Java-Based Software Components [page 19]
J2EE Adapter Engine
Apply the Support Package Stack to the system where the Adapter Engine is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Partner Connectivity Kit
Apply the Support Package Stack to the system where the PCK is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Front End GUIs
Update the SAP GUI components if necessary
For more information see SAP GUI Family [page 51]
ABAP 700 Business System (Optional)
Apply the Support Packages for SAP NetWeaver Application Server ABAP (including SAP kernel and
the Support Package for SAP BASIS 700)
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 640 Business System (Optional)
Apply the Support Packages for SAP Web Application Server ABAP 640 (including SAP kernel and the
Support Package for SAP BASIS 640)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3160
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 620 Business System (Optional)
1 Update the SAP Kernel 620
2 Import the released Basis Support Packages for SAP Web AS 620 as well as the most recent Add-
On Support Package for APPINT 200_620 in the order described in SAP Note 439915
J2SE Adapter Engine (Optional)
NOTE
The XI Adapter Engine (J2SE) and all its adapters are provided for compatibility reasons only and
are not developed any further You have to use the XI Adapter Engine running on SAP NetWeaver
AS Java For more information see the Master Guide ndash SAP NetWeaver 70 available on SAP Service
Marketplace at httpservicesapcominstallNW70 Planning
1 Extract the SAPXICONSltSPgt_ltPLgtSCA (XI Connectivity SE 700) archive (ZIP format) to a temporary
directory
2 Save the old configuration files as described in the document Adapterpdf in directory
lttemp_directorygttech_adapterAdministrationDocumentation
3 Unpack the ZIP archive TechnicalAdapterssda to the installation directory of the XI Adapter
Engine (J2SE)
4 Restore the configuration files with restore_configuration
243 Post-Installation Steps
Procedure
Communication Channels and Queues
Restart all stopped sender channels and register all deregistered qRFC queues
XI Content
In the system with usage type PI import the XI content from the archives SAPBASISltSPgt_ltPLgtZIP
and SAPABAltSPgt_ltPLgtZIP as follows
1 Unpack the archives using a ZIP tool of your choice
2 Copy the corresponding export files (with file extension tpz) to the import directory ltINSTDIRgt
ltSAPSIDgtSYSglobalxirepository_serverimport
3 Start the Integration Builder (transaction SXMB_IFR)
4 Enter the Integration Repository by choosing Repository (Design)
5 Choose Tools Import design objects
6 Import the tpz files containing the XI content
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3260 CUSTOMER 2012-08-30
NOTE
For more information see SAP Note 836200
Role Generation on the Integration Server
On the Integration Server execute transaction SUPC (mass generation of roles) for all SAP_XI roles in
each of your clients to regenerate possibly changed roles
NOTE
Do not forget to make a user comparison for regenerated roles afterwards
Partner Connectivity Kit (Optional)
Perform the post-installation steps for PCK as described in SAP Note 746328
SAP Master Data within the SLD (Optional)
In the system where your SLD is running import the latest SLD content as described in SAP Note
669669
Receiver-Based EOIO Serialization in J2EE Adapter Engine (Optional)
The J2EE Adapter Engine can be switched to receiver-based EOIO serialization The switch can be
triggered on demand and is executed asynchronously It includes a database migration step during
which all EOIO processing in the Adapter Engine is disabled See SAP Note 973894 for details about how
to start the EOIO serialization migration
Service Metering (Optional)
Service metering gathers information about a service caller transfers it to the service provider and
counts on the service provisioning side how many times a service is called and by which service caller
Service metering is performed for the XI message protocol and the WS message protocol Service
metering is automatically enabled after applying a Support Package Stack By default only non-sensitive
data is transmitted to internal or external service providers in a compatible way
Service metering can be configured in PI in the Integration Engine on sender-side and in the Integration
Directory
Service metering can be configured in AS ABAP in transaction SOAMANAGER
Only if the service provider is allowed to receive more detailed information about the service caller set
the metering level to higher than the default
For more information see SAP Note 1239428
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3360
25 Business Intelligence
251 Planning
Procedure
Business Intelligence includes one or many of the following units that must be updated depending on
your implemented scenarios The usage types Business Intelligence (BI) and Business Intelligence Java
Components (BI-Java) must always have the same Support Package level
Business Intelligence
Software Components of Business Intelligence
Component to Be Updated SP File Name Tool Used to Apply SP
BI CONT ADDON 70x SAPK-70ltxgtltSPgtINBICONT SAINT
SAP NetWeaver Application Server ABAP (see table Software Components of Application Server ABAP [page 15])
NOTE
For information about the dependencies applying to BI Content Support Packages see SAP Note
653814 BI CONT 703 Support Packages are not part of the NetWeaver SP Stacks Updates can be
performed when applicable Alternatively BI CONT 704 Support Packages can be imported See
the BI Content release strategy in SAP Note 153967
Business Intelligence Java Components
BI Java Components
Component to Be Updated SP File NameTool Used to Apply SP
BI REPORTING AND PLANNING 702 BIREPPLANltSPgt_ltPLgtSCA JSPM
BI WEBDYNPRO ALV 702 BIWDALVltSPgt_ltPLgtSCA
BI INFORM BROADCASTING 702 BIIBCltSPgt_ltPLgtSCA
BI WEB APPLICATIONS 702 BIWEBAPPltSPgt_ltPLgtSCA
BI BASE SERVICES 702 BIBASESltSPgt_ltPLgtSCA
VISUAL COMPOSER BI KITS 702 VCKITBIltSPgt_ltPLgtSCA
Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
BI Precalculation Service
Components of the BI Precalculation Service
Component to Be Updated SP File Name Tool Used to Apply SP
BI Pre-calculation Service 700 xPreCalServerltSPgt_ltPLgtexe Installer
Search and Classification (TREX)
See table TREX Component [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3460 CUSTOMER 2012-08-30
BI Accelerator
The BI Accelerator is based on the TREX technology It is a special Linux 64-bit version of SAP NetWeaver
70 Search and Classification (TREX) which is delivered on preconfigured hardware
NOTE
You cannot use a TREX installation based on 32-bit architecture that is configured for searching
in metadata and documents for the BI Accelerator And vice versa a BI Accelerator box cannot
be used for searching in metadata and documents
If you want to use the search functionality as well as the BI Accelerator you require two separate
installations For more information see BI Accelerator [page 47]
Clients
Depending on your implemented scenarios you have to update SAP GUI Components and Business
Explorer (BI Add-OnBW Add-On)
NOTE
See SAP Note 889314 to determine when to use the BI Add-On and the BW Add-On
NOTE
As SAP GUI 640 is no longer supported BI Frontend Support Package 1800 resp patch 1801 is the
last Support Package resp patch based on SAP GUI 640 For more information see SAP Note
1231292 (Frontend Add-in Strategy 640710 GUI Version)
For more information about the new release strategy for the BI Frontend see SAP Note 1231363
(Changed Delivery Strategy for BI Frontend)
252 Preparation
Procedure
For the Support Packages of the most important Business Intelligence units so called SAPBINews
(SAPBWNews) Notes are created Read these Notes before updating Business Intelligence For SAP
NetWeaver 70 including enhancement package 2 SPS 12 these are the following
Business Intelligence ABAP SAP Note 1680996
Business Intelligence Java Components SAP Note 1726461
BI 70 Frontend Add-On for SAP GUI 710 SAP Note 1413032
BI 70 Frontend Add-On for SAP GUI 720 SAP Note 1630112
BI 70 Frontend Add-On for SAP GUI 730 SAP Note 1726739
For more information about BI Support Packages see SAP Community Network at http
scnsapcomcommunitydata-warehousingnetweaver-bw Related Resources SAP NW BW Support
Packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
2012-08-30 CUSTOMER 3560
253 Updating Units of Business Intelligence
Procedure
Business Intelligence
1 Update the SAP NetWeaver Application Server ABAP (with BI CONT 70x if necessary) with the
appropriate Support Packages
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
NOTE
When applying the component SAP BW 702 some generation errors might occur When
you start importing the BI Support Packages in transaction SPAM choose the menu path
Extras Ignore generation errors For more information see SAP Note 114134
2 Apply the Support Package Stack to the system with the usage type BI-Java
For more information see Application Server Java and Java-Based Software Components [page 19]
3 Update the BI Precalculation Service that is used in your scenario
4 Update the standalone engine Search and Classification (TREX) that is used in your scenario For more
information see Standalone Engine Search and Classification (TREX) [page 44]
NOTE
You have to update TREX to the newest version if you use search capabilities within Business
Intelligence
5 Update the BI Accelerator to the newest available version For more information see BI
Accelerator [page 47]
6 Update the SAP GUI and Business Explorer (BI Add-On BW Add-On) on all remote client hosts
that are involved in the scenario
For more information see SAP GUI Family [page 51] and Business Explorer (BI Add-On BW Add-On)
[page 51]
BI Precalculation Service
1 Log on to the host as a user with administration rights
2 Install the Support Package of the BI Precalculation Service by executing the
xPreCalServerexe file
The welcome screen of the BI Precalculation Server setup wizard appears
The setup now checks the system for the prerequisites
3 Choose the option Update for updating the BI Precalculation service to the current patch level and
then Finish
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3660 CUSTOMER 2012-08-30
26 EP Core
261 Planning
Procedure
The following installable software units must be updated
EP Core
Software Components of EP Core
Component to Be Updated SP File Name Tool Used to Apply SP
PORTAL CORE SERVICES 702 EPBCltSPgt_ltPLgtSCA JSPM
PORTAL FRAMEWORK 702 EPBC2ltSPgt_ltPLgtSCA
PORTAL 702 EPPSERVltSPgt_ltPLgtSCA
PORTAL WEB DYNPRO 702 EPWDCltSPgt_ltPLgtSCA
UWL COLL PROCESS ENGINE 702 UWLJWFltSPgt_ltPLgtSCA
CAF EU 702 SAPEUltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
262 Preparation
Procedure
Backing Up the Portal Runtime Configuration
If you have made changes to the standard Portal Runtime configuration you have to make a backup
of the configuration before the update process For more information see SAP Note 1064468
263 Updating EP Core
Procedure
Apply the Support Package Stack to a system with usage type EP Core
For more information see Application Server Java and Java-Based Software Components [page 19]
264 Post-Installation Steps for EP Core
Procedure
Restoring the Portal Runtime Configuration
To make your changes to the standard Portal Runtime Configuration effective you have to restore
the backup of the configuration done before the update process For more information see SAP Note
1064468
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
26 EP Core
2012-08-30 CUSTOMER 3760
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
A3 System Profile Parameters 58
860 CUSTOMER 2012-08-30
1 Overview
This document describes how to install Support Package Stacks (SP Stacks) for SAP NetWeaver 70
including enhancement package 2 You can find all information related to the SP Stacks on SAP Service
Marketplace at httpservicesapcomsp-stacks
11 Before You Start
CAUTION
If you intend to update your system to the latest SP Stack level and plan to upgrade it within the
next 6 months first check the availability of the equivalent SP Stack for the target release The
delivery dates of the equivalent SP Stacks for your source and target release might be several
months apart
Be aware that you cannot upgrade to a target release that does not include the equivalent SP Stack
level
To avoid a deadlock situation we recommend that you check SAP Service Marketplace at
httpservicesapcomsp-stacks SP Stack Information and consider not applying the
latest SP Stack on your source release system
Updated Document Versions
The Support Package Stack Guide is regularly updated on SAP Service Marketplace at http
servicesapcommaintenanceNW70
NOTE
Make sure you have the latest version of the Support Package Stack Guide by checking SAP Service
Marketplace immediately before you start to apply or import Support Packages
SAP Notes
You must read SAP Note 1460321 before you read this document as it may contain corrections and
further information about the Support Package Stack installation
SAP Library
You must inform yourself about enhancements and changes to the Support Package Stack to be applied
from SAP Library under SAP Library SAP NetWeaver Whatrsquos New in SAP NetWeaver 70 ndash Release
Notes You can access the SAP Library in one of the following ways
SAP Help Portal at httphelpsapcomnw702 Application Help SAP Library ltLanguagegt
1 Overview
11 Before You Start
2012-08-30 CUSTOMER 960
NOTE
The SAP Help Portal always provides the up-to-date version of the SAP Library Therefore
we recommend that you use this channel to access the SAP Library
Local installation of the SAP Library from the online documentation DVD
CAUTION
In order to inform yourself about the current Support Package Stack you first have to update
your local installation of the SAP Library to the corresponding SPS level Follow the
instructions in section SAP Library [page 52]
Naming Conventions
In this document the following naming conventions apply
Variables
Variables Description
ltSAPSIDgt
ltsapsidgt
ltSIDgt
SAP system ID
ltINSTDIRgt Installation directory for the SAP system
lthostgt Host name
ltinstance_nogt Instance number of a system instance
ltdatabasegt Name of database
ltsapinst_directorygt Installation directory for the SAP installation tool SAPinst
ltsp_directorygt Temporary directory which the archives of a Support Package are downloaded or copied to
ltOSgt Operating system
ltOS_DIRgt OS-dependent directory consisting of a folder for the platform and a subfolder of your OS versionFor example if you operating system is Sun OS 64bit ltOS_DIRgt stands for UNIXSUNOS64
ltSP_Stackgt Number of Support Package Stack
ltSPgt Support Package level
ltPLgt Support Package patch level
ltRELgt Release number
ltLOCALEgt Language definitionFor example the German locale is _de
ltkrnl_directorygt Kernel directory which the profile parameter DIR_CT_RUN usually refers to
ltsdm_homegt Program file location of the Software Deployment Manager (SDM)
ltSAPGLOBALHOSTgt SAP global host the host where the global directories of an SAP system reside
ltSAPLOCALHOSTgt SAP local host the host where a particular instance of an SAP system is running
1 Overview
11 Before You Start
1060 CUSTOMER 2012-08-30
12 Types of Support Packages
The following table explains the terms used in the correction process as part of the software maintenance
process for SAP NetWeaver
Correction Process Description
Standard correction process
Support Package Stack Description
A Support Package Stack is a set of Support Packages and patches for the respective product version that must be used in the given combination
Version numbersSupport Package Stacks have a release number and a stack number for example SAP NetWeaver 70 Support Package Stack 05
DeliveryThere is no dedicated delivery format for the Support Package Stacks The included Support Package files have their delivery formats and must be applied using the tools as described below
Kernel Patches Version numbers
SAP Kernel patches have a release number and a patch number The patch number is increased with each correction
DeliverySAP Kernel patches are delivered as SAR files They are installed by extracting the SAR files to the kernel directory using SAPCAR Separate SAR files are shipped for the different kernel types depending on UNICODENON-UNICODE and the platform
ABAP Support Packages Description
ABAP Support Packages contain corrections and adjustments for the ABAP-based Software Components of the SAP system
DependenciesIn contrast to Java Support Packages ABAP Support Packages are non-cumulative Therefore ABAP Support Packages must be installed in the correct sequence one after the other You cannot skip any intermediate Support Packages
DeliveryABAP Support Packages are delivered as SAR files They are installed using the Support Package Manager (SPAM)
Java Support Packages Description
Java Support Packages contain corrections for the Java-based Software Components of the SAP system
DependenciesJava Support Packages always contain a full delivery of the Software Components Therefore you only need to apply the latest Support Package to update the software If there are dependencies with other Java Support Packages these are specified in an SAP Note
DeliveryJava Support Packages are delivered as Software Component Archives (SCAs) They are applied using the Java Support Package Manager (JSPM)
1 Overview
12 Types of Support Packages
2012-08-30 CUSTOMER 1160
Correction Process Description
Emergency correction process
SAP Note Correction (ABAP) Description
SAP Note corrections contain single ABAP fixes Delivery
SAP Note corrections are delivered with SAP Notes If required you apply them using the SAP Note Assistant
Java Support Package Patch Description
A Java Support Package patch contains corrections for the Java Software Components Java Support Package patches are created and released on demand A Java Support Package patch corresponds to an SAP Note that describes the same correction
DependenciesA Java Support Package patch always contains a full package of the corresponding Software Component and is applied using JSPM
13 Downloading Support Package Stacks
The Maintenance Optimizer in SAP Solution Manager is the only source from which you can receive
maintenance updates for SAP NetWeaver 70 and higher releases as well as for all applications running
on top of SAP NetWeaver The Maintenance Optimizer supports you in selecting and downloading all
required maintenance files In addition the Maintenance Optimizer generates a stack XML file and
saves it to the EPS inbox directory of SAP Solution Manager
Prerequisites
You have configured the Maintenance Optimizer in SAP Solution Manager as described on SAP Help
Portal at httphelpsapcom SAP Solutions SAP Solution Manager SAP Solution Manager ltReleasegt
ltLanguagegt Change Management Maintenance Optimizer Planning and Monitoring Product Maintenance and
also in section Automatically Calculating Product Maintenance Files
Procedure
To download a Support Package Stack proceed as follows
1 Start SAP Solution Manager using the transaction solution_manager To start the Maintenance
Optimizer choose Operations Change Management Maintenance Optimizer
2 In the Maintenance Optimizer choose the solution for which you want to download SP Stack files
3 Choose Create New Maintenance Transaction
4 Select the product version for which you want to apply a Support Package Stack
The Maintenance Optimizer displays all the systems assigned to the selected product version
5 Select the checkbox for the system that you want to update and choose Continue
6 On the subsequent screen select the Maintenance option and then choose Find Download Files
1 Overview
13 Downloading Support Package Stacks
1260 CUSTOMER 2012-08-30
7 Select the target SP Stack level and the relevant usage types according to the IT scenario to be
updated
8 Choose Find Download Files for the Stack Version
The Maintenance Optimizer displays the product maintenance files in three successive lists
9 Select the required files from the displayed lists
The first list shows all files that are dependent on the type of your operating system and
database
Select the files that correspond to the combination of your operating system and database and
the database-independent files
If your system is distributed on several hosts make sure to select all operating systems used
by the NetWeaver instances You can see all the kernels detected on your system on the Deployed
Components tab page on JSPM user interface (under the SAP KERNEL node) All detected kernels
must be updated to the same version
You get to the second list by choosing Continue This list displays all Support Package files that
are not assigned to the selected Support Package Stack Before you continue with the selection
you must check whether the Support Package files listed here are suitable for your product
maintenance procedure
You get to the third list by choosing Continue The list displays all product maintenance files
that are part of the selected Support Package Stack
Ensure that all files that are assigned to the Support Package Stack are selected here Files that
are not selected will not be included later in the download
10 Choose Continue Use the Download Basket to download the maintenance files
11 Choose Continue once the files have been put in your Download Basket and then Confirm Files in
Download Basket
A dialog window appears and displays all files
12 Confirm the download for all files
13 Open your Download Manager and download the files
NOTE
The stack XML file is generated by the Maintenance Optimizer and automatically saved to
the EPS inbox directory of SAP Solution Manager
More Information
For more information about the Maintenance Optimizer see SAP Support Portal at http
servicesapcomsolman-mopz
1 Overview
13 Downloading Support Package Stacks
2012-08-30 CUSTOMER 1360
This page is left blank for documents that are printed on both sides
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
This chapter describes how to apply Support Packages to installable software units of SAP NetWeaver
70 including enhancement package 2 SAP NetWeaver distinguishes three types of installable software
units
Systems with one or multiple usage types
Standalone engines
Clients
A scenario implementation usually involves several installed software units
RECOMMENDATION
We strongly recommend that you always update all software units belonging to one scenario
together in order to retain a consistent system state Due to the fact that some installable software
units can be commonly shared in different scenarios you must consequently update all scenarios
using the common software units at the same time
21 Application Server ABAP and ABAP-Based Software Components
211 Planning
Procedure
The following components belong to the usage type SAP NetWeaver Application Server ABAP
Software Components of Application Server ABAP
Component to Be Updated SP File Name Tool Used to Apply SP
SAP KERNEL 720 32-64-BIT Non-UNICODEUNICODE SAPEXESAR
SAPEXEDBSAR
JSPMmanually
SAP IGS 700 igsexesar
SAP ABA 702 SAPKA702ltSPgt SPAMSAINT
SAP BASIS 702 SAPKB702ltSPgt
SAP BW 702 SAPKW702ltSPgt
PI_BASIS 702 SAPK-702ltSPgtINPIBASIS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
2012-08-30 CUSTOMER 1560
NOTE
This table contains only software components that belong to the usage type AS ABAP Software
components of other usage types and application units are listed in the corresponding sections
NOTE
SAP delivers intermediate Support Packages for the component SAP BW 702 between two
subsequent SP levels besides the Support Packages delivered along with the Support Package
Stacks Therefore the highest SP level of SAP BW 702 does not necessarily match the target SP
Stack level
CAUTION
When applying a Support Package Stack to a dual-stack system (ABAP+Java) the Java Support
Package Manager (JSPM) will necessarily restart the system several times to make the changes
effective The ABAP part will only be restarted when JSPM is updating the SAP kernel and IGS
212 Preparation
Procedure
Read SAP Note 822379 and all related SAP Notes that the first one refers to
213 Updating the Application Server ABAP and ABAP-Based Software Components
Procedure
Applying Support Packages to SAP NetWeaver Application Server ABAP and ABAP-Based Components
You can update the SAP NetWeaver Application Server ABAP and all ABAP-based software components
running on it using the Support Package Manager (transaction SPAM)
NOTE
If a particular Support Package Stack requires the installation or upgrade of some add-on
components you must use the ABAP Add-on Installation Tool (transaction SAINT) instead of the
Support Package Manager In this case SAINT is able to import both the add-on components and
the related Support Packages of ordinary SAP components
Proceed as follows
1 Log on to the SAP NetWeaver AS system with client 000
2 Start the Support Package Manager by calling transaction SPAM or
start the Add-On Installation Tool by calling transaction SAINT
3 Load the relevant Support Packages or add-on installation packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
1660 CUSTOMER 2012-08-30
4 Define an import queue
5 Perform the import of the defined queue
NOTE
If you have modified SAP objects in your system and these objects are included in the Support
Packages you must perform modification adjustment during the import using the
transactions SPDD (for ABAP Dictionary objects) and SPAU (for Repository objects)
To import the queue you use the standard scenario You can choose between the conventional
import mode and downtime-minimized import mode
Conventional Import Mode
This option comprises the following steps
1 Update the SAP kernel and SAP IGS as described in section Updating SAP Kernel and SAP IGS below
Start the system after the kernel update
2 Import the ABAP Support Packages with the Support Package Manager (SPAM)
Import Mode Downtime-Minimized
This option can be used to reduce system downtime during the update It comprises the following
steps
1 In transaction SPAM enable the downtime-minimized import mode by choosing Extras
Settings then on the Import queue tab page choose Standard and activate the option Import Mode
Downtime-Minimized
2 Import the ABAP Support Packages into the system in an inactive state in the downtime-minimized
mode during system uptime
3 Update the SAP kernel and SAP IGS as described in section Updating SAP Kernel and SAP IGS below
Start the system after the kernel update
4 Complete the ABAP Support Packages import
CAUTION
During this step the system cannot carry out any business transactions (business downtime)
NOTE
In rare cases due to the dependencies of some Support Packages on a particular kernel patch level
the downtime-minimized update does not work In such cases the Support Package Manager
informs you that you must update the SAP kernel before importing ABAP Support Packages You
must proceed with the conventional import procedure
Updating SAP Kernel and SAP IGS
In general the SAP kernel and IGS binaries are located in the global kernel directory DIR_CT_RUN on
the host indicated by the profile parameter SAPGLOBALHOST Once the files in this directory have been
updated to a new patch level a system restart distributes them by means of the program SAPCPE to the
local directories DIR_EXECUTABLE on the hosts where the instances of the SAP system are running
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
2012-08-30 CUSTOMER 1760
CAUTION
The automatic distribution by means of SAPCPE depends on the settings of the profile parameters
DIR_CT_RUN for the global kernel directory and DIR_EXECUTABLE for the local directory of the
executables Before you continue check the instance profiles for the settings of these parameters
in systems that are not installed using SAPinst (for example systems upgraded from older releases
copied or migrated systems)
CAUTION
If your system is a dual-stack system (ABAP+Java) and the ABAP stack has a non-Unicode kernel
be aware that the SCS instance has a Unicode kernel You have to update both kernels (together
with SAP IGS) prior to updating the ABAP and Java Support Package stacks This ensures
compatibility and reduces system downtime
RECOMMENDATION
If you perform an update of a dual-stack system (ABAP+Java) we recommend that prior to
applying ABAP and Java Support Package stacks you use the Single Support Packages option in JSPM
and select for update only the components SAP KERNEL and BC-FES-IGS
For more information about updating a dual-stack system see Parallel Update of Dual-Stack Systems
[page 28]
If you perform an update of an ABAP system the following procedure applies for updating the SAP
kernel and IGS manually
1 Log on as user ltsapsidgtadm to the instance host to be updated
2 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory using
SAPCAR [page 56]
3 Stop the ABAP system that you want to update
NOTE
If the system is running in a high availability (HA) environment make sure that the HA
software does not restart the system automatically during the update
4 Back up the kernel directory ltkrnl_directorygt
5 Copy or move the extracted programs from the temporary directory to the SAP kernel directory
6 Only valid for UNIX |
Execute the following command sequence on UNIX platforms
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
1860 CUSTOMER 2012-08-30
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
7 Restart the SAP system
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS) runs
on a dedicated host You need to perform the kernel update for the ASCS instance manually but
excluding the IGS update because the IGS is not required in an ASCS instance
In rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of such instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances manually Proceed as described
in section Manually Updating Instances with Kernel Directory Located on Separate Hosts below in this document
214 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the ABAP system
22 Application Server Java and Java-Based Software Components
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system which includes
JSPM itself
SAP Kernel and SAP IGS
All Java-based usage types installed in the system
Software Deployment Manager (SDM) - the deployment service of the system
RECOMMENDATION
We strongly recommend that you apply the target Support Package Stack to your system as a
whole This ensures consistency on both the system and the application levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 1960
221 Planning
Procedure
Java Support Package files (SCAs) contain all software objects of the corresponding software
components Thus it is sufficient to apply the Java Support Package files of the intended Support Package
Stack directly to the Java system to be updated It is not necessary to apply the Support Package Stacks
between the start SP Stack level and the target SP Stack level successively
CAUTION
When applying a Support Package Stack to a Java system the Java Support Package Manager (JSPM)
will necessarily restart the system several times to make the changes effective With a dual-stack
system (ABAP+Java) the ABAP part will only be restarted when JSPM is updating the SAP kernel
and IGS
The following components belong to the usage type SAP NetWeaver Application Server Java (AS Java)
Software Components of Application Server Java
Component to Be Updated SP File Name Tool Used to Apply SP
SAP Kernel 720 32-64-BIT UNICODE SAPEXESAR
SAPEXEDBSAR
JSPM
SAP IGS 700 igsexesar
BI META MODEL REPOSITORY 702 BIMMRltSPgt_ltPLgtSCA
J2EE ENGINE CORE TOOLS 702 CORETOOLSltSPgt_ltPLgtSCA
J2EE ENGINE BASE TABLES 702 BASETABLESltSPgt_ltPLgtSCA
BI UDI 702 BIUDIltSPgt_ltPLgtSCA
DI BUILD TOOL 702 SAPBUILDTltSPgt_ltPLgtSCA
SAP CAF 702 CAFltSPgt_ltPLgtSCA
SAP IKS 702 KMKWJIKSltSPgt_ltPLgtSCA
JAVA LOG VIEWER 702 JLOGVIEWltSPgt_ltPLgtSCA
SAP J2EE ENGINE CORE 702 SAPJEECORltSPgt_ltPLgtSCA
SAP JAVA TECH SERVICES 702 SAPJTECHSltSPgt_ltPLgtSCA
SAP TECH S OFFLINE 702 SAPJTECHFltSPgt_ltPLgtSCA
SAP J2EE ENGINE 702 SAPJEEltSPgt_ltPLgtSCA
JAVA SP MANAGER 702 JSPMltSPgt_ltPLgtSCA
ADOBE DOCUMENT SERVICES 702 ADSSAPltSPgt_ltPLgtSCA
UME ADMINISTRATION 702 UMEADMINltSPgt_ltPLgtSCA
LIFECYCLE MGMT TOOLS 702 LMTOOLSltSPgt_ltPLgtSCA
SAP CAF-UM 702 CAFUMltSPgt_ltPLgtSCA
SAP SOFTW DELIV MANAGER 702 SDMKITltSPgt_ltPLgtJAR
SOFTWARE LIFECYCLE MANAGER 702 SWLIFECYCLltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2060 CUSTOMER 2012-08-30
NOTE
This table contains only software components that belong to the usage type AS Java Software
components of other usage types and Java application units are listed in the corresponding
sections
NOTE
As of Support Package 09 you can update your system with SAP Kernel 720 instead of SAP Kernel
701
222 Preparation for Applying a Support Package Stack
Procedure
1 Download the Support Package Stack with all usage types to be updated and the stack definition
XML file as described in Downloading Support Package Stacks [page 12]
NOTE
You can find the activated usage types in an existing Java system on the Deployed Components tab
page on the JSPM user interface
NOTE
You do not need to download the SP Stacks between the source SP Stack level and target SP
Stack level By default the target SP Stack level is the latest available SP Stack
2 Make sure the following requirements are met prior to applying the Support Package Stack
You have familiarized yourself with SAP Note 891983 before you start the Java Support Package
Manager
The system to be updated is fully functional
The Support Package Stack you want to apply and the corresponding stack definition XML
file are available in the EPS inbox directory usrsaptransEPSin By default this location
can be also referred to as ldquoJSPM inboxrdquo
The SAP NetWeaver Application Server Java (AS Java) and the database have been backed up
You have not deleted renamed or created any directories and files in the following directories
and their subdirectories usrsapltSAPSIDgtSYSexe and usrsapltSAPSIDgtSYS
profile
Otherwise JSPM cannot detect the kernel and the system profiles and cannot be started If a
backup of the kernel and the system profiles has been required it has been created in a different
directory
The ltsapsidgtadm user has Read permissions for the EPS inbox directory usrsaptransEPS
in
If your database is SAP MaxDB the overwrite mode for the log area has been activated
The database and the SDM repository have been synchronized
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2160
For more information see the online documentation for JSPM on SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70 Library
(including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library Administrators Guide
Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems AS Java
(Application Server for Java) Software Logistics Software Maintenance Java Support Package Manager
Then choose Troubleshooting JSPM Does Not Update the Versions of the Deployed Components
There is enough disk space
For more information see SAP Note 891895
Your current SAPCAR tool is able to extract the Support Packages for the SAP kernel and
other OS level binaries delivered as SAR files
RECOMMENDATION
You can download the latest version of SAPCAR from SAP Service Marketplace at
httpservicesapcompatches Entry by Application Group Additional Components
SAPCAR
Put the downloaded version in the same directory in the JSPM inbox in which the kernel
SAR files reside so that JSPM can use this version for extracting the SAR files
3 Only valid for Linux |
For RHEL 4 and SLES 9 you need to install additional operating system packages For more
information see SAP Note 1021236End of Linux |
4 Only valid for Windows |
For Windows you need to install additional operating system packages For more information see
SAP Note 684106End of Windows |
5 To prevent the Software Deployment Manager (SDM) from temporarily exceeding the available
disk space during the update process you can change the file transfer directory of SDM in a system
of SPS09 or higher using the following command sequence
Only valid for Windows |
cd ltsdm_homegt
StopServerbat
sdmbat jstartup mode=standalone
sdmbat filetransferdir dir=ltnew_dirgt
sdmbat jstartup mode=integrated
StartServerbat
End of Windows |
Only valid for IBM i5OSUNIX |
cd ltsdm_homegt
StopServersh
sdmsh jstartup mode=standalone
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2260 CUSTOMER 2012-08-30
sdmsh filetransferdir dir=ltnew_dirgt
sdmsh jstartup mode=integrated
StartServersh
End of IBM i5OSUNIX |
6 To prevent deployment errors during the update process proceed as follows
1 Log on to the Central Instance host
2 Start the ConfigTool and in the navigation area choose Cluster-data Global server configuration
Managers ServiceManager
3 In the Global properties panel set the Custom value of the EventTimeout property to 120
4 Choose Save
5 Restart the Central Instance
7 Check whether the used JDK version and the Java VM settings of the Java runtime system comply
with the requirements in SAP Note 723909 Update the JDK and adjust the settings if necessary
NOTE
An update of the used JDK version possibly changes the JVM path In this case you must
make the new path available to all Dialog Instances of the J2EE engine by implementing option
1 of SAP Note 718901
8 Make sure that the J2EE administrator password stored in the secure store for offline usage is
identical with the one stored in the User Management Engine (UME) You can change the password
in the secure store as described in SAP Note 870445
9 If you are running a high availability system on Windows you might need to prepare your system
as described in the online documentation for JSPM see section Preparing Systems That Run in High
Availability Environment
223 Updating the Application Server Java and Java-Based Components
Procedure
Applying a Support Package Stack to SAP NetWeaver Application Server Java and Java-Based Components
NOTE
The JSPM GUI might not work properly on some UNIX systems For more information and the
solution see SAP Note 1013976
1 Log on as user ltsapsidgtadm to the Central Instance host
NOTE
If your operating system is IBM i log on as user ltSIDgtADM or ltSIDgtOFR
2 Close the SAP Management Console (SAP MMC) and the SDM remote GUI client
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2360
3 For UNIX and Windows To start the JSPM navigate to the directory ltINSTDIRgtltSIDgt
ltCentral_Instance_Namegtj2eeJSPM and run the go script file
NOTE
If your system is running on IBM i to start the JSPM proceed as follows
1 To prevent JSPM from automatically starting its GUI in the file usrsapltSIDgt
ltCentral_Instance_Namegtj2eeJSPMparamjspm_configtxt change the
property dialogSDTServerConnectionSDTGuilaunch from true to false
2 On the IBM i host run the go script file using the following command
QSH CMD(usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPMgo)
3 In the mounted directory usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPM run
the StartGui script file The JSPM GUI appears
4 In the Host field enter the target IBM i host
NOTE
Depending on the system type ltCentral_Instance_Namegt has the following syntax
Standalone Java system JCltinstance_nogt
Add-On system DVEBMGSltinstance_nogt
4 Enter your SDM password to log on to the SDM
5 On the Deployment tab page select the Java Support Package Manager option and update the software
component sapcomJSPM to the target SPS level
6 Restart the JSPM and log on with the SDM password
RECOMMENDATION
We strongly recommend that you use the Support and Enhancement Package Stack option when
applying a Support Package Stack Other options can lead to unintended consistency issues
NOTE
If you need to include the latest patches for a particular component during the update process
with the Support and Enhancement Package Stack option stop the JSPM after restart and apply SAP
Note 1080821 Then start the JSPM again
7 On the Deployment tab page select the Support and Enhancement Package Stack option and choose Next
The Support Package Stacks that are available for deployment in the global EPS inbox directory
are displayed
8 In the Target SP Stack Level dropdown box select the Support Package Stack to be applied and choose
Next
In this step JSPM performs various status validations and displays the result of each software
component included in the stack definition XML file on the subsequent screen which includes
the following possible statuses
OK Indicates that the SPS level of the corresponding software component is applicable
WARNING We recommend that you view the details about the component by choosing Show
Details
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2460 CUSTOMER 2012-08-30
This status may indicate that the corresponding software component comprises custom
modifications in an NWDI-controlled system
If your system is used for NWDI development and it is either a DEV or a CONS system
you will be informed that JSPM will not deploy the modified software components but
only transport them to the CMS transport directory JSPM will deploy only the software
components that are not modified
If your system is not used for NWDI development or if your system is used for NWDI
development and it is either a TEST or a PROD system you will be informed that JSPM
has found newer versions of modified software components and will automatically replace
the original versions with the newer versions JSPM will deploy all software components
that are not modified together with the replaced versions of the modified software
components
CAUTION
You may get a warning telling you that there are patches installed in your system
containing fixes which might not be included in the target SP Stack This is possible if
you have applied patches of the start SP Stack level that were delivered later than the
target SP Stack delivery date In order not to lose these fixes you need to download and
apply the corresponding patches of the target SP Stack level
If you are performing an update from SAP NetWeaver 70 including enhancement
package 1 SPS00 and you have not applied any patches for the software component with
status WARNING before the update then you can ignore warnings such as the following
example
The new version of the development component sapcomcomsapnetweaver
bcrfmoni is 70100200806121227180000 and is lower than the already
deployed version 70100200807090143420000
REVISE Indicates inconsistencies with the corresponding software component
The deployment cannot be performed until all problems have been resolved You can view
the problems by choosing Show Details
9 If the status of the selected SP Stack is OK or WARNING you can start the system update by choosing
Start JSPM then changes the status to SCHEDULED
If the SP Stack to be applied includes a kernel update and the current kernel is not already of the
corresponding patch level JSPM arranges the kernel update as the very first Support Package to
be applied JSPM updates the kernel binaries of all instances (including Dialog Instances and SCS
instances in a HA environment) whose kernel directories DIR_CT_RUN effectively reside on the host
indicated by the profile parameter SAPGLOBALHOST
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2560
CAUTION
Kernel binaries of instances whose kernel directories DIR_CT_RUN are not effectively linked
to the host SAPGLOBALHOST must be updated individually as described in section Manually
Updating Instances with Kernel Directory Located on Separate Hosts below
The kernel update (includes update of SAP Kernel and SAP IGS) using JSPM consists of the following
steps
1 JSPM stops the Central Instance automatically and prompts you to stop the remote SCS and
Dialog Instances manually
2 After you have stopped all the instances choose the Next button in the dialog box
The kernel update starts
NOTE
If the system is running in a high availability environment make sure that the HA
software does not restart the instance automatically during the update
NOTE
If kernel binaries of the SCS instance need to be updated manually (see Manually Updating
Instances with Kernel Directory Located on Separate Hosts below) you must perform this at the
time when JSPM is updating the kernel binaries of the Central Instance In any case the
SCS kernel must be up-to-date before the next restart
When the kernel update is finished a dialog box appears in which you are prompted to restart
the SCS instance manually
3 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries
before you can proceed with the next step For more information see Adjusting the Ownership and
Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
4 Choose Next in the dialog box when the SCS instance is running again
After the kernel update JSPM restarts the system for further deployment of the remaining Support
Packages in the stack
RECOMMENDATION
If you need to update the kernel binaries of any Dialog Instances manually (see Manually
Updating Instances with Kernel Directory Located on Separate Hosts below) perform the update when
JSPM is updating the remaining Support Packages in the stack in order to save time
The deployment of each Support Package can end with one of the following statuses
DEPLOYED
The Support Package has been successfully deployed
DEPLOYED WITH WARNING
The Support Package has been deployed but it possibly may not work properly with other
deployed components
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2660 CUSTOMER 2012-08-30
You can view the details by choosing Show Details or examining the log files You can also view
the details about the component by choosing the Deployed Components tab page
ERROR
An error has occurred during the deployment You can view the details by choosing Show
Details or examining the log files
You must correct the error to be able to continue with the SP Stack update
You can proceed as described for a deployment that finished with status DEPLOYED WITH
WARNING
If the error correction does not change the contents in the JSPM inbox you can continue
the deployment by choosing Resume
If the error correction changes the contents in the JSPM inbox you can choose New
Deployment to redeploy the SP Stack
NOT DEPLOYED
JSPM has not attempted to deploy the software component for certain reasons
If your system is not used for NWDI development you can proceed as described for a
deployment that finished with status ERROR
If your system is used for NWDI development and it is either a DEV or a CONS system
the status of the modified software components is always NOT DEPLOYED JSPM has
transported the software components of the Support Package Stack both modified and
not modified to the CMS transport directory The deployment of the modified software
components is handled by NWDI
Manually Updating Instances with Kernel Directory Located on Separate Hosts
JSPM performs kernel update for all instances (including Dialog Instances and SCS instances in a HA
environment) whose kernel directories DIR_CT_RUN effectively reside on the host indicated by the profile
parameter SAPGLOBALHOST (by using folder sharing on Windows or file system mounting on UNIX) In
rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of those sort of instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances individually
To update the kernel of an instance manually proceed as follows
1 Log on as user ltsapsidgtadm to the host of the instance to be updated
2 Back up the kernel directory which is specified by the profile parameter DIR_CT_RUN
3 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory with
SAPCAR [page 56]
4 Stop the instance being updated
NOTE
If the system is running in a HA environment make sure that the HA software does not
restart the instance automatically during the update
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2760
5 Copy or move the extracted programs from the temporary directory to the local kernel directory
6 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries as
described in section Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
7 Restart the instance after JSPM has finished the deployment of all packages on the Central Instance
Only valid for UNIX |
Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms
On UNIX platforms you must adjust the ownership and execution permissions of the kernel binaries
after the update regardless whether you performed the update manually or by using JSPM because
both update procedures are performed with the ltsapsidgtadm user Enter the following command
sequence
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
224 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the Java system
23 Parallel Update of Dual-Stack Systems
If you perform an update of a dual-stack system (ABAP+Java) we recommend that you follow the
procedure described below The procedure has been validated to update the ABAP stack and the Java
stack of a NetWeaver system in parallel thus reducing the overall system downtime by half
Procedure
1 Before applying ABAP and Java Support Packages use the Single Support Packages option in JSPM and
select for update only the components SAP KERNEL and BC-FES-IGS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
23 Parallel Update of Dual-Stack Systems
2860 CUSTOMER 2012-08-30
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS)
runs on a dedicated host In this case JSPM does not support update of kernel binaries and
you need to update them manually Perform the update manually as described under Updating
SAP Kernel and SAP IGS in section Updating the Application Server ABAP and ABAP-Based Software
Components [page 16]
2 Import the Support Packages for the component SAP_BASIS into the ABAP stack using the ABAP
Support Package Manager (SPAM)
3 Import the remaining ABAP Support Packages with SPAM and in parallel apply the Java Support
Package Stack with JSPM
Proceed as described in Updating the Application Server ABAP and ABAP-Based Software Components [page
16] and Updating the Application Server Java and Java-Based Software Components [page 23]
24 Process Integration
241 Planning
Procedure
This section covers all the units of Process Integration that should be updated Particularly the following
units must always have the same Support Package level (the patch level can be different)
Integration Server
XI Adapter Engine
Partner Connectivity Kit
System with the Usage Type Process Integration
Software components of Integration Server
Components to Be Updated SP File Name Tool Used to Apply SP
Java stack
XI TOOLS 702 SAPXITOOLltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
ABAP stack
XI CONTENT SAP_BASIS 702 SAPBASISltSPgt_ltPLgtZIP File upload
XI CONTENT SAP_ABA 702 SAPABAltSPgt_ltPLgtZIP
SAP NetWeaver Application Server ABAP (see table Software components of Application Server ABAP [page 15])Note that update of the following software components of the ABAP system is not required SAP ABA 702 SAP BW 702 PI_BASIS 702
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 2960
J2EE Adapter Engine
If your implemented scenario includes a J2EE Adapter Engine then it must always be of the same
Support Package level as the Integration Server
Components of the J2EE Adapter Engine
Component to Be Updated SP File NameTool Used to Apply SP
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
J2SE Adapter Engine
The installation of the J2SE Adapter Engine depends on the implemented scenario
Components of the J2SE Adapter Engine
Component to Be Updated SP File Name Tool Used to Apply SP
XI CONNECTIVITY SE 702 SAPXICONSltSPgt_ltPLgtSCA ZIP tool (for example WinZip)
Partner Connectivity Kit
If your implemented scenario includes a Partner Connectivity Kit (PCK) then it must always be of the
same Support Package level as the Integration Server
Software components of Partner Connectivity Kit
Components to Be Updated SP File NameTool Used to Apply SP
XI PCK 702 SAPXIPCKltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of the Application Server Java [page 20])
System Landscape Directory (SLD)
The System Landscape Directory is required for the PI operations Although updating the SLD is not
necessarily required it is advisable to update the SLD server and the SAP Master Data Content within
it from time to time The update of the SLD includes
1 The system where the SLD is running
2 The SAP Master Data Content within this SLD
SAP GUI
See table Compatible SAP GUI Versions [page 51]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3060 CUSTOMER 2012-08-30
242 Updating Units of Process Integration
Procedure
Before you start the update perform the following steps
In the Runtime Workbench use Communication Channel Monitoring to stop all sender channels
for all adapter types on all your Adapter Engines
On the Integration Server use transaction SMQR and deregister all qRFC queues
System with the Usage Type Process Integration
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the XI instance is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system where the XI instance is running
For more information see Application Server Java and Java-Based Software Components [page 19]
System Landscape Directory (Optional)
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the SLD is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the entire Support Package Stack to the system where the SLD is running
For more information see Application Server Java and Java-Based Software Components [page 19]
J2EE Adapter Engine
Apply the Support Package Stack to the system where the Adapter Engine is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Partner Connectivity Kit
Apply the Support Package Stack to the system where the PCK is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Front End GUIs
Update the SAP GUI components if necessary
For more information see SAP GUI Family [page 51]
ABAP 700 Business System (Optional)
Apply the Support Packages for SAP NetWeaver Application Server ABAP (including SAP kernel and
the Support Package for SAP BASIS 700)
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 640 Business System (Optional)
Apply the Support Packages for SAP Web Application Server ABAP 640 (including SAP kernel and the
Support Package for SAP BASIS 640)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3160
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 620 Business System (Optional)
1 Update the SAP Kernel 620
2 Import the released Basis Support Packages for SAP Web AS 620 as well as the most recent Add-
On Support Package for APPINT 200_620 in the order described in SAP Note 439915
J2SE Adapter Engine (Optional)
NOTE
The XI Adapter Engine (J2SE) and all its adapters are provided for compatibility reasons only and
are not developed any further You have to use the XI Adapter Engine running on SAP NetWeaver
AS Java For more information see the Master Guide ndash SAP NetWeaver 70 available on SAP Service
Marketplace at httpservicesapcominstallNW70 Planning
1 Extract the SAPXICONSltSPgt_ltPLgtSCA (XI Connectivity SE 700) archive (ZIP format) to a temporary
directory
2 Save the old configuration files as described in the document Adapterpdf in directory
lttemp_directorygttech_adapterAdministrationDocumentation
3 Unpack the ZIP archive TechnicalAdapterssda to the installation directory of the XI Adapter
Engine (J2SE)
4 Restore the configuration files with restore_configuration
243 Post-Installation Steps
Procedure
Communication Channels and Queues
Restart all stopped sender channels and register all deregistered qRFC queues
XI Content
In the system with usage type PI import the XI content from the archives SAPBASISltSPgt_ltPLgtZIP
and SAPABAltSPgt_ltPLgtZIP as follows
1 Unpack the archives using a ZIP tool of your choice
2 Copy the corresponding export files (with file extension tpz) to the import directory ltINSTDIRgt
ltSAPSIDgtSYSglobalxirepository_serverimport
3 Start the Integration Builder (transaction SXMB_IFR)
4 Enter the Integration Repository by choosing Repository (Design)
5 Choose Tools Import design objects
6 Import the tpz files containing the XI content
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3260 CUSTOMER 2012-08-30
NOTE
For more information see SAP Note 836200
Role Generation on the Integration Server
On the Integration Server execute transaction SUPC (mass generation of roles) for all SAP_XI roles in
each of your clients to regenerate possibly changed roles
NOTE
Do not forget to make a user comparison for regenerated roles afterwards
Partner Connectivity Kit (Optional)
Perform the post-installation steps for PCK as described in SAP Note 746328
SAP Master Data within the SLD (Optional)
In the system where your SLD is running import the latest SLD content as described in SAP Note
669669
Receiver-Based EOIO Serialization in J2EE Adapter Engine (Optional)
The J2EE Adapter Engine can be switched to receiver-based EOIO serialization The switch can be
triggered on demand and is executed asynchronously It includes a database migration step during
which all EOIO processing in the Adapter Engine is disabled See SAP Note 973894 for details about how
to start the EOIO serialization migration
Service Metering (Optional)
Service metering gathers information about a service caller transfers it to the service provider and
counts on the service provisioning side how many times a service is called and by which service caller
Service metering is performed for the XI message protocol and the WS message protocol Service
metering is automatically enabled after applying a Support Package Stack By default only non-sensitive
data is transmitted to internal or external service providers in a compatible way
Service metering can be configured in PI in the Integration Engine on sender-side and in the Integration
Directory
Service metering can be configured in AS ABAP in transaction SOAMANAGER
Only if the service provider is allowed to receive more detailed information about the service caller set
the metering level to higher than the default
For more information see SAP Note 1239428
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3360
25 Business Intelligence
251 Planning
Procedure
Business Intelligence includes one or many of the following units that must be updated depending on
your implemented scenarios The usage types Business Intelligence (BI) and Business Intelligence Java
Components (BI-Java) must always have the same Support Package level
Business Intelligence
Software Components of Business Intelligence
Component to Be Updated SP File Name Tool Used to Apply SP
BI CONT ADDON 70x SAPK-70ltxgtltSPgtINBICONT SAINT
SAP NetWeaver Application Server ABAP (see table Software Components of Application Server ABAP [page 15])
NOTE
For information about the dependencies applying to BI Content Support Packages see SAP Note
653814 BI CONT 703 Support Packages are not part of the NetWeaver SP Stacks Updates can be
performed when applicable Alternatively BI CONT 704 Support Packages can be imported See
the BI Content release strategy in SAP Note 153967
Business Intelligence Java Components
BI Java Components
Component to Be Updated SP File NameTool Used to Apply SP
BI REPORTING AND PLANNING 702 BIREPPLANltSPgt_ltPLgtSCA JSPM
BI WEBDYNPRO ALV 702 BIWDALVltSPgt_ltPLgtSCA
BI INFORM BROADCASTING 702 BIIBCltSPgt_ltPLgtSCA
BI WEB APPLICATIONS 702 BIWEBAPPltSPgt_ltPLgtSCA
BI BASE SERVICES 702 BIBASESltSPgt_ltPLgtSCA
VISUAL COMPOSER BI KITS 702 VCKITBIltSPgt_ltPLgtSCA
Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
BI Precalculation Service
Components of the BI Precalculation Service
Component to Be Updated SP File Name Tool Used to Apply SP
BI Pre-calculation Service 700 xPreCalServerltSPgt_ltPLgtexe Installer
Search and Classification (TREX)
See table TREX Component [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3460 CUSTOMER 2012-08-30
BI Accelerator
The BI Accelerator is based on the TREX technology It is a special Linux 64-bit version of SAP NetWeaver
70 Search and Classification (TREX) which is delivered on preconfigured hardware
NOTE
You cannot use a TREX installation based on 32-bit architecture that is configured for searching
in metadata and documents for the BI Accelerator And vice versa a BI Accelerator box cannot
be used for searching in metadata and documents
If you want to use the search functionality as well as the BI Accelerator you require two separate
installations For more information see BI Accelerator [page 47]
Clients
Depending on your implemented scenarios you have to update SAP GUI Components and Business
Explorer (BI Add-OnBW Add-On)
NOTE
See SAP Note 889314 to determine when to use the BI Add-On and the BW Add-On
NOTE
As SAP GUI 640 is no longer supported BI Frontend Support Package 1800 resp patch 1801 is the
last Support Package resp patch based on SAP GUI 640 For more information see SAP Note
1231292 (Frontend Add-in Strategy 640710 GUI Version)
For more information about the new release strategy for the BI Frontend see SAP Note 1231363
(Changed Delivery Strategy for BI Frontend)
252 Preparation
Procedure
For the Support Packages of the most important Business Intelligence units so called SAPBINews
(SAPBWNews) Notes are created Read these Notes before updating Business Intelligence For SAP
NetWeaver 70 including enhancement package 2 SPS 12 these are the following
Business Intelligence ABAP SAP Note 1680996
Business Intelligence Java Components SAP Note 1726461
BI 70 Frontend Add-On for SAP GUI 710 SAP Note 1413032
BI 70 Frontend Add-On for SAP GUI 720 SAP Note 1630112
BI 70 Frontend Add-On for SAP GUI 730 SAP Note 1726739
For more information about BI Support Packages see SAP Community Network at http
scnsapcomcommunitydata-warehousingnetweaver-bw Related Resources SAP NW BW Support
Packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
2012-08-30 CUSTOMER 3560
253 Updating Units of Business Intelligence
Procedure
Business Intelligence
1 Update the SAP NetWeaver Application Server ABAP (with BI CONT 70x if necessary) with the
appropriate Support Packages
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
NOTE
When applying the component SAP BW 702 some generation errors might occur When
you start importing the BI Support Packages in transaction SPAM choose the menu path
Extras Ignore generation errors For more information see SAP Note 114134
2 Apply the Support Package Stack to the system with the usage type BI-Java
For more information see Application Server Java and Java-Based Software Components [page 19]
3 Update the BI Precalculation Service that is used in your scenario
4 Update the standalone engine Search and Classification (TREX) that is used in your scenario For more
information see Standalone Engine Search and Classification (TREX) [page 44]
NOTE
You have to update TREX to the newest version if you use search capabilities within Business
Intelligence
5 Update the BI Accelerator to the newest available version For more information see BI
Accelerator [page 47]
6 Update the SAP GUI and Business Explorer (BI Add-On BW Add-On) on all remote client hosts
that are involved in the scenario
For more information see SAP GUI Family [page 51] and Business Explorer (BI Add-On BW Add-On)
[page 51]
BI Precalculation Service
1 Log on to the host as a user with administration rights
2 Install the Support Package of the BI Precalculation Service by executing the
xPreCalServerexe file
The welcome screen of the BI Precalculation Server setup wizard appears
The setup now checks the system for the prerequisites
3 Choose the option Update for updating the BI Precalculation service to the current patch level and
then Finish
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3660 CUSTOMER 2012-08-30
26 EP Core
261 Planning
Procedure
The following installable software units must be updated
EP Core
Software Components of EP Core
Component to Be Updated SP File Name Tool Used to Apply SP
PORTAL CORE SERVICES 702 EPBCltSPgt_ltPLgtSCA JSPM
PORTAL FRAMEWORK 702 EPBC2ltSPgt_ltPLgtSCA
PORTAL 702 EPPSERVltSPgt_ltPLgtSCA
PORTAL WEB DYNPRO 702 EPWDCltSPgt_ltPLgtSCA
UWL COLL PROCESS ENGINE 702 UWLJWFltSPgt_ltPLgtSCA
CAF EU 702 SAPEUltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
262 Preparation
Procedure
Backing Up the Portal Runtime Configuration
If you have made changes to the standard Portal Runtime configuration you have to make a backup
of the configuration before the update process For more information see SAP Note 1064468
263 Updating EP Core
Procedure
Apply the Support Package Stack to a system with usage type EP Core
For more information see Application Server Java and Java-Based Software Components [page 19]
264 Post-Installation Steps for EP Core
Procedure
Restoring the Portal Runtime Configuration
To make your changes to the standard Portal Runtime Configuration effective you have to restore
the backup of the configuration done before the update process For more information see SAP Note
1064468
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
26 EP Core
2012-08-30 CUSTOMER 3760
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
1 Overview
This document describes how to install Support Package Stacks (SP Stacks) for SAP NetWeaver 70
including enhancement package 2 You can find all information related to the SP Stacks on SAP Service
Marketplace at httpservicesapcomsp-stacks
11 Before You Start
CAUTION
If you intend to update your system to the latest SP Stack level and plan to upgrade it within the
next 6 months first check the availability of the equivalent SP Stack for the target release The
delivery dates of the equivalent SP Stacks for your source and target release might be several
months apart
Be aware that you cannot upgrade to a target release that does not include the equivalent SP Stack
level
To avoid a deadlock situation we recommend that you check SAP Service Marketplace at
httpservicesapcomsp-stacks SP Stack Information and consider not applying the
latest SP Stack on your source release system
Updated Document Versions
The Support Package Stack Guide is regularly updated on SAP Service Marketplace at http
servicesapcommaintenanceNW70
NOTE
Make sure you have the latest version of the Support Package Stack Guide by checking SAP Service
Marketplace immediately before you start to apply or import Support Packages
SAP Notes
You must read SAP Note 1460321 before you read this document as it may contain corrections and
further information about the Support Package Stack installation
SAP Library
You must inform yourself about enhancements and changes to the Support Package Stack to be applied
from SAP Library under SAP Library SAP NetWeaver Whatrsquos New in SAP NetWeaver 70 ndash Release
Notes You can access the SAP Library in one of the following ways
SAP Help Portal at httphelpsapcomnw702 Application Help SAP Library ltLanguagegt
1 Overview
11 Before You Start
2012-08-30 CUSTOMER 960
NOTE
The SAP Help Portal always provides the up-to-date version of the SAP Library Therefore
we recommend that you use this channel to access the SAP Library
Local installation of the SAP Library from the online documentation DVD
CAUTION
In order to inform yourself about the current Support Package Stack you first have to update
your local installation of the SAP Library to the corresponding SPS level Follow the
instructions in section SAP Library [page 52]
Naming Conventions
In this document the following naming conventions apply
Variables
Variables Description
ltSAPSIDgt
ltsapsidgt
ltSIDgt
SAP system ID
ltINSTDIRgt Installation directory for the SAP system
lthostgt Host name
ltinstance_nogt Instance number of a system instance
ltdatabasegt Name of database
ltsapinst_directorygt Installation directory for the SAP installation tool SAPinst
ltsp_directorygt Temporary directory which the archives of a Support Package are downloaded or copied to
ltOSgt Operating system
ltOS_DIRgt OS-dependent directory consisting of a folder for the platform and a subfolder of your OS versionFor example if you operating system is Sun OS 64bit ltOS_DIRgt stands for UNIXSUNOS64
ltSP_Stackgt Number of Support Package Stack
ltSPgt Support Package level
ltPLgt Support Package patch level
ltRELgt Release number
ltLOCALEgt Language definitionFor example the German locale is _de
ltkrnl_directorygt Kernel directory which the profile parameter DIR_CT_RUN usually refers to
ltsdm_homegt Program file location of the Software Deployment Manager (SDM)
ltSAPGLOBALHOSTgt SAP global host the host where the global directories of an SAP system reside
ltSAPLOCALHOSTgt SAP local host the host where a particular instance of an SAP system is running
1 Overview
11 Before You Start
1060 CUSTOMER 2012-08-30
12 Types of Support Packages
The following table explains the terms used in the correction process as part of the software maintenance
process for SAP NetWeaver
Correction Process Description
Standard correction process
Support Package Stack Description
A Support Package Stack is a set of Support Packages and patches for the respective product version that must be used in the given combination
Version numbersSupport Package Stacks have a release number and a stack number for example SAP NetWeaver 70 Support Package Stack 05
DeliveryThere is no dedicated delivery format for the Support Package Stacks The included Support Package files have their delivery formats and must be applied using the tools as described below
Kernel Patches Version numbers
SAP Kernel patches have a release number and a patch number The patch number is increased with each correction
DeliverySAP Kernel patches are delivered as SAR files They are installed by extracting the SAR files to the kernel directory using SAPCAR Separate SAR files are shipped for the different kernel types depending on UNICODENON-UNICODE and the platform
ABAP Support Packages Description
ABAP Support Packages contain corrections and adjustments for the ABAP-based Software Components of the SAP system
DependenciesIn contrast to Java Support Packages ABAP Support Packages are non-cumulative Therefore ABAP Support Packages must be installed in the correct sequence one after the other You cannot skip any intermediate Support Packages
DeliveryABAP Support Packages are delivered as SAR files They are installed using the Support Package Manager (SPAM)
Java Support Packages Description
Java Support Packages contain corrections for the Java-based Software Components of the SAP system
DependenciesJava Support Packages always contain a full delivery of the Software Components Therefore you only need to apply the latest Support Package to update the software If there are dependencies with other Java Support Packages these are specified in an SAP Note
DeliveryJava Support Packages are delivered as Software Component Archives (SCAs) They are applied using the Java Support Package Manager (JSPM)
1 Overview
12 Types of Support Packages
2012-08-30 CUSTOMER 1160
Correction Process Description
Emergency correction process
SAP Note Correction (ABAP) Description
SAP Note corrections contain single ABAP fixes Delivery
SAP Note corrections are delivered with SAP Notes If required you apply them using the SAP Note Assistant
Java Support Package Patch Description
A Java Support Package patch contains corrections for the Java Software Components Java Support Package patches are created and released on demand A Java Support Package patch corresponds to an SAP Note that describes the same correction
DependenciesA Java Support Package patch always contains a full package of the corresponding Software Component and is applied using JSPM
13 Downloading Support Package Stacks
The Maintenance Optimizer in SAP Solution Manager is the only source from which you can receive
maintenance updates for SAP NetWeaver 70 and higher releases as well as for all applications running
on top of SAP NetWeaver The Maintenance Optimizer supports you in selecting and downloading all
required maintenance files In addition the Maintenance Optimizer generates a stack XML file and
saves it to the EPS inbox directory of SAP Solution Manager
Prerequisites
You have configured the Maintenance Optimizer in SAP Solution Manager as described on SAP Help
Portal at httphelpsapcom SAP Solutions SAP Solution Manager SAP Solution Manager ltReleasegt
ltLanguagegt Change Management Maintenance Optimizer Planning and Monitoring Product Maintenance and
also in section Automatically Calculating Product Maintenance Files
Procedure
To download a Support Package Stack proceed as follows
1 Start SAP Solution Manager using the transaction solution_manager To start the Maintenance
Optimizer choose Operations Change Management Maintenance Optimizer
2 In the Maintenance Optimizer choose the solution for which you want to download SP Stack files
3 Choose Create New Maintenance Transaction
4 Select the product version for which you want to apply a Support Package Stack
The Maintenance Optimizer displays all the systems assigned to the selected product version
5 Select the checkbox for the system that you want to update and choose Continue
6 On the subsequent screen select the Maintenance option and then choose Find Download Files
1 Overview
13 Downloading Support Package Stacks
1260 CUSTOMER 2012-08-30
7 Select the target SP Stack level and the relevant usage types according to the IT scenario to be
updated
8 Choose Find Download Files for the Stack Version
The Maintenance Optimizer displays the product maintenance files in three successive lists
9 Select the required files from the displayed lists
The first list shows all files that are dependent on the type of your operating system and
database
Select the files that correspond to the combination of your operating system and database and
the database-independent files
If your system is distributed on several hosts make sure to select all operating systems used
by the NetWeaver instances You can see all the kernels detected on your system on the Deployed
Components tab page on JSPM user interface (under the SAP KERNEL node) All detected kernels
must be updated to the same version
You get to the second list by choosing Continue This list displays all Support Package files that
are not assigned to the selected Support Package Stack Before you continue with the selection
you must check whether the Support Package files listed here are suitable for your product
maintenance procedure
You get to the third list by choosing Continue The list displays all product maintenance files
that are part of the selected Support Package Stack
Ensure that all files that are assigned to the Support Package Stack are selected here Files that
are not selected will not be included later in the download
10 Choose Continue Use the Download Basket to download the maintenance files
11 Choose Continue once the files have been put in your Download Basket and then Confirm Files in
Download Basket
A dialog window appears and displays all files
12 Confirm the download for all files
13 Open your Download Manager and download the files
NOTE
The stack XML file is generated by the Maintenance Optimizer and automatically saved to
the EPS inbox directory of SAP Solution Manager
More Information
For more information about the Maintenance Optimizer see SAP Support Portal at http
servicesapcomsolman-mopz
1 Overview
13 Downloading Support Package Stacks
2012-08-30 CUSTOMER 1360
This page is left blank for documents that are printed on both sides
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
This chapter describes how to apply Support Packages to installable software units of SAP NetWeaver
70 including enhancement package 2 SAP NetWeaver distinguishes three types of installable software
units
Systems with one or multiple usage types
Standalone engines
Clients
A scenario implementation usually involves several installed software units
RECOMMENDATION
We strongly recommend that you always update all software units belonging to one scenario
together in order to retain a consistent system state Due to the fact that some installable software
units can be commonly shared in different scenarios you must consequently update all scenarios
using the common software units at the same time
21 Application Server ABAP and ABAP-Based Software Components
211 Planning
Procedure
The following components belong to the usage type SAP NetWeaver Application Server ABAP
Software Components of Application Server ABAP
Component to Be Updated SP File Name Tool Used to Apply SP
SAP KERNEL 720 32-64-BIT Non-UNICODEUNICODE SAPEXESAR
SAPEXEDBSAR
JSPMmanually
SAP IGS 700 igsexesar
SAP ABA 702 SAPKA702ltSPgt SPAMSAINT
SAP BASIS 702 SAPKB702ltSPgt
SAP BW 702 SAPKW702ltSPgt
PI_BASIS 702 SAPK-702ltSPgtINPIBASIS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
2012-08-30 CUSTOMER 1560
NOTE
This table contains only software components that belong to the usage type AS ABAP Software
components of other usage types and application units are listed in the corresponding sections
NOTE
SAP delivers intermediate Support Packages for the component SAP BW 702 between two
subsequent SP levels besides the Support Packages delivered along with the Support Package
Stacks Therefore the highest SP level of SAP BW 702 does not necessarily match the target SP
Stack level
CAUTION
When applying a Support Package Stack to a dual-stack system (ABAP+Java) the Java Support
Package Manager (JSPM) will necessarily restart the system several times to make the changes
effective The ABAP part will only be restarted when JSPM is updating the SAP kernel and IGS
212 Preparation
Procedure
Read SAP Note 822379 and all related SAP Notes that the first one refers to
213 Updating the Application Server ABAP and ABAP-Based Software Components
Procedure
Applying Support Packages to SAP NetWeaver Application Server ABAP and ABAP-Based Components
You can update the SAP NetWeaver Application Server ABAP and all ABAP-based software components
running on it using the Support Package Manager (transaction SPAM)
NOTE
If a particular Support Package Stack requires the installation or upgrade of some add-on
components you must use the ABAP Add-on Installation Tool (transaction SAINT) instead of the
Support Package Manager In this case SAINT is able to import both the add-on components and
the related Support Packages of ordinary SAP components
Proceed as follows
1 Log on to the SAP NetWeaver AS system with client 000
2 Start the Support Package Manager by calling transaction SPAM or
start the Add-On Installation Tool by calling transaction SAINT
3 Load the relevant Support Packages or add-on installation packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
1660 CUSTOMER 2012-08-30
4 Define an import queue
5 Perform the import of the defined queue
NOTE
If you have modified SAP objects in your system and these objects are included in the Support
Packages you must perform modification adjustment during the import using the
transactions SPDD (for ABAP Dictionary objects) and SPAU (for Repository objects)
To import the queue you use the standard scenario You can choose between the conventional
import mode and downtime-minimized import mode
Conventional Import Mode
This option comprises the following steps
1 Update the SAP kernel and SAP IGS as described in section Updating SAP Kernel and SAP IGS below
Start the system after the kernel update
2 Import the ABAP Support Packages with the Support Package Manager (SPAM)
Import Mode Downtime-Minimized
This option can be used to reduce system downtime during the update It comprises the following
steps
1 In transaction SPAM enable the downtime-minimized import mode by choosing Extras
Settings then on the Import queue tab page choose Standard and activate the option Import Mode
Downtime-Minimized
2 Import the ABAP Support Packages into the system in an inactive state in the downtime-minimized
mode during system uptime
3 Update the SAP kernel and SAP IGS as described in section Updating SAP Kernel and SAP IGS below
Start the system after the kernel update
4 Complete the ABAP Support Packages import
CAUTION
During this step the system cannot carry out any business transactions (business downtime)
NOTE
In rare cases due to the dependencies of some Support Packages on a particular kernel patch level
the downtime-minimized update does not work In such cases the Support Package Manager
informs you that you must update the SAP kernel before importing ABAP Support Packages You
must proceed with the conventional import procedure
Updating SAP Kernel and SAP IGS
In general the SAP kernel and IGS binaries are located in the global kernel directory DIR_CT_RUN on
the host indicated by the profile parameter SAPGLOBALHOST Once the files in this directory have been
updated to a new patch level a system restart distributes them by means of the program SAPCPE to the
local directories DIR_EXECUTABLE on the hosts where the instances of the SAP system are running
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
2012-08-30 CUSTOMER 1760
CAUTION
The automatic distribution by means of SAPCPE depends on the settings of the profile parameters
DIR_CT_RUN for the global kernel directory and DIR_EXECUTABLE for the local directory of the
executables Before you continue check the instance profiles for the settings of these parameters
in systems that are not installed using SAPinst (for example systems upgraded from older releases
copied or migrated systems)
CAUTION
If your system is a dual-stack system (ABAP+Java) and the ABAP stack has a non-Unicode kernel
be aware that the SCS instance has a Unicode kernel You have to update both kernels (together
with SAP IGS) prior to updating the ABAP and Java Support Package stacks This ensures
compatibility and reduces system downtime
RECOMMENDATION
If you perform an update of a dual-stack system (ABAP+Java) we recommend that prior to
applying ABAP and Java Support Package stacks you use the Single Support Packages option in JSPM
and select for update only the components SAP KERNEL and BC-FES-IGS
For more information about updating a dual-stack system see Parallel Update of Dual-Stack Systems
[page 28]
If you perform an update of an ABAP system the following procedure applies for updating the SAP
kernel and IGS manually
1 Log on as user ltsapsidgtadm to the instance host to be updated
2 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory using
SAPCAR [page 56]
3 Stop the ABAP system that you want to update
NOTE
If the system is running in a high availability (HA) environment make sure that the HA
software does not restart the system automatically during the update
4 Back up the kernel directory ltkrnl_directorygt
5 Copy or move the extracted programs from the temporary directory to the SAP kernel directory
6 Only valid for UNIX |
Execute the following command sequence on UNIX platforms
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
1860 CUSTOMER 2012-08-30
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
7 Restart the SAP system
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS) runs
on a dedicated host You need to perform the kernel update for the ASCS instance manually but
excluding the IGS update because the IGS is not required in an ASCS instance
In rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of such instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances manually Proceed as described
in section Manually Updating Instances with Kernel Directory Located on Separate Hosts below in this document
214 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the ABAP system
22 Application Server Java and Java-Based Software Components
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system which includes
JSPM itself
SAP Kernel and SAP IGS
All Java-based usage types installed in the system
Software Deployment Manager (SDM) - the deployment service of the system
RECOMMENDATION
We strongly recommend that you apply the target Support Package Stack to your system as a
whole This ensures consistency on both the system and the application levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 1960
221 Planning
Procedure
Java Support Package files (SCAs) contain all software objects of the corresponding software
components Thus it is sufficient to apply the Java Support Package files of the intended Support Package
Stack directly to the Java system to be updated It is not necessary to apply the Support Package Stacks
between the start SP Stack level and the target SP Stack level successively
CAUTION
When applying a Support Package Stack to a Java system the Java Support Package Manager (JSPM)
will necessarily restart the system several times to make the changes effective With a dual-stack
system (ABAP+Java) the ABAP part will only be restarted when JSPM is updating the SAP kernel
and IGS
The following components belong to the usage type SAP NetWeaver Application Server Java (AS Java)
Software Components of Application Server Java
Component to Be Updated SP File Name Tool Used to Apply SP
SAP Kernel 720 32-64-BIT UNICODE SAPEXESAR
SAPEXEDBSAR
JSPM
SAP IGS 700 igsexesar
BI META MODEL REPOSITORY 702 BIMMRltSPgt_ltPLgtSCA
J2EE ENGINE CORE TOOLS 702 CORETOOLSltSPgt_ltPLgtSCA
J2EE ENGINE BASE TABLES 702 BASETABLESltSPgt_ltPLgtSCA
BI UDI 702 BIUDIltSPgt_ltPLgtSCA
DI BUILD TOOL 702 SAPBUILDTltSPgt_ltPLgtSCA
SAP CAF 702 CAFltSPgt_ltPLgtSCA
SAP IKS 702 KMKWJIKSltSPgt_ltPLgtSCA
JAVA LOG VIEWER 702 JLOGVIEWltSPgt_ltPLgtSCA
SAP J2EE ENGINE CORE 702 SAPJEECORltSPgt_ltPLgtSCA
SAP JAVA TECH SERVICES 702 SAPJTECHSltSPgt_ltPLgtSCA
SAP TECH S OFFLINE 702 SAPJTECHFltSPgt_ltPLgtSCA
SAP J2EE ENGINE 702 SAPJEEltSPgt_ltPLgtSCA
JAVA SP MANAGER 702 JSPMltSPgt_ltPLgtSCA
ADOBE DOCUMENT SERVICES 702 ADSSAPltSPgt_ltPLgtSCA
UME ADMINISTRATION 702 UMEADMINltSPgt_ltPLgtSCA
LIFECYCLE MGMT TOOLS 702 LMTOOLSltSPgt_ltPLgtSCA
SAP CAF-UM 702 CAFUMltSPgt_ltPLgtSCA
SAP SOFTW DELIV MANAGER 702 SDMKITltSPgt_ltPLgtJAR
SOFTWARE LIFECYCLE MANAGER 702 SWLIFECYCLltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2060 CUSTOMER 2012-08-30
NOTE
This table contains only software components that belong to the usage type AS Java Software
components of other usage types and Java application units are listed in the corresponding
sections
NOTE
As of Support Package 09 you can update your system with SAP Kernel 720 instead of SAP Kernel
701
222 Preparation for Applying a Support Package Stack
Procedure
1 Download the Support Package Stack with all usage types to be updated and the stack definition
XML file as described in Downloading Support Package Stacks [page 12]
NOTE
You can find the activated usage types in an existing Java system on the Deployed Components tab
page on the JSPM user interface
NOTE
You do not need to download the SP Stacks between the source SP Stack level and target SP
Stack level By default the target SP Stack level is the latest available SP Stack
2 Make sure the following requirements are met prior to applying the Support Package Stack
You have familiarized yourself with SAP Note 891983 before you start the Java Support Package
Manager
The system to be updated is fully functional
The Support Package Stack you want to apply and the corresponding stack definition XML
file are available in the EPS inbox directory usrsaptransEPSin By default this location
can be also referred to as ldquoJSPM inboxrdquo
The SAP NetWeaver Application Server Java (AS Java) and the database have been backed up
You have not deleted renamed or created any directories and files in the following directories
and their subdirectories usrsapltSAPSIDgtSYSexe and usrsapltSAPSIDgtSYS
profile
Otherwise JSPM cannot detect the kernel and the system profiles and cannot be started If a
backup of the kernel and the system profiles has been required it has been created in a different
directory
The ltsapsidgtadm user has Read permissions for the EPS inbox directory usrsaptransEPS
in
If your database is SAP MaxDB the overwrite mode for the log area has been activated
The database and the SDM repository have been synchronized
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2160
For more information see the online documentation for JSPM on SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70 Library
(including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library Administrators Guide
Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems AS Java
(Application Server for Java) Software Logistics Software Maintenance Java Support Package Manager
Then choose Troubleshooting JSPM Does Not Update the Versions of the Deployed Components
There is enough disk space
For more information see SAP Note 891895
Your current SAPCAR tool is able to extract the Support Packages for the SAP kernel and
other OS level binaries delivered as SAR files
RECOMMENDATION
You can download the latest version of SAPCAR from SAP Service Marketplace at
httpservicesapcompatches Entry by Application Group Additional Components
SAPCAR
Put the downloaded version in the same directory in the JSPM inbox in which the kernel
SAR files reside so that JSPM can use this version for extracting the SAR files
3 Only valid for Linux |
For RHEL 4 and SLES 9 you need to install additional operating system packages For more
information see SAP Note 1021236End of Linux |
4 Only valid for Windows |
For Windows you need to install additional operating system packages For more information see
SAP Note 684106End of Windows |
5 To prevent the Software Deployment Manager (SDM) from temporarily exceeding the available
disk space during the update process you can change the file transfer directory of SDM in a system
of SPS09 or higher using the following command sequence
Only valid for Windows |
cd ltsdm_homegt
StopServerbat
sdmbat jstartup mode=standalone
sdmbat filetransferdir dir=ltnew_dirgt
sdmbat jstartup mode=integrated
StartServerbat
End of Windows |
Only valid for IBM i5OSUNIX |
cd ltsdm_homegt
StopServersh
sdmsh jstartup mode=standalone
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2260 CUSTOMER 2012-08-30
sdmsh filetransferdir dir=ltnew_dirgt
sdmsh jstartup mode=integrated
StartServersh
End of IBM i5OSUNIX |
6 To prevent deployment errors during the update process proceed as follows
1 Log on to the Central Instance host
2 Start the ConfigTool and in the navigation area choose Cluster-data Global server configuration
Managers ServiceManager
3 In the Global properties panel set the Custom value of the EventTimeout property to 120
4 Choose Save
5 Restart the Central Instance
7 Check whether the used JDK version and the Java VM settings of the Java runtime system comply
with the requirements in SAP Note 723909 Update the JDK and adjust the settings if necessary
NOTE
An update of the used JDK version possibly changes the JVM path In this case you must
make the new path available to all Dialog Instances of the J2EE engine by implementing option
1 of SAP Note 718901
8 Make sure that the J2EE administrator password stored in the secure store for offline usage is
identical with the one stored in the User Management Engine (UME) You can change the password
in the secure store as described in SAP Note 870445
9 If you are running a high availability system on Windows you might need to prepare your system
as described in the online documentation for JSPM see section Preparing Systems That Run in High
Availability Environment
223 Updating the Application Server Java and Java-Based Components
Procedure
Applying a Support Package Stack to SAP NetWeaver Application Server Java and Java-Based Components
NOTE
The JSPM GUI might not work properly on some UNIX systems For more information and the
solution see SAP Note 1013976
1 Log on as user ltsapsidgtadm to the Central Instance host
NOTE
If your operating system is IBM i log on as user ltSIDgtADM or ltSIDgtOFR
2 Close the SAP Management Console (SAP MMC) and the SDM remote GUI client
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2360
3 For UNIX and Windows To start the JSPM navigate to the directory ltINSTDIRgtltSIDgt
ltCentral_Instance_Namegtj2eeJSPM and run the go script file
NOTE
If your system is running on IBM i to start the JSPM proceed as follows
1 To prevent JSPM from automatically starting its GUI in the file usrsapltSIDgt
ltCentral_Instance_Namegtj2eeJSPMparamjspm_configtxt change the
property dialogSDTServerConnectionSDTGuilaunch from true to false
2 On the IBM i host run the go script file using the following command
QSH CMD(usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPMgo)
3 In the mounted directory usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPM run
the StartGui script file The JSPM GUI appears
4 In the Host field enter the target IBM i host
NOTE
Depending on the system type ltCentral_Instance_Namegt has the following syntax
Standalone Java system JCltinstance_nogt
Add-On system DVEBMGSltinstance_nogt
4 Enter your SDM password to log on to the SDM
5 On the Deployment tab page select the Java Support Package Manager option and update the software
component sapcomJSPM to the target SPS level
6 Restart the JSPM and log on with the SDM password
RECOMMENDATION
We strongly recommend that you use the Support and Enhancement Package Stack option when
applying a Support Package Stack Other options can lead to unintended consistency issues
NOTE
If you need to include the latest patches for a particular component during the update process
with the Support and Enhancement Package Stack option stop the JSPM after restart and apply SAP
Note 1080821 Then start the JSPM again
7 On the Deployment tab page select the Support and Enhancement Package Stack option and choose Next
The Support Package Stacks that are available for deployment in the global EPS inbox directory
are displayed
8 In the Target SP Stack Level dropdown box select the Support Package Stack to be applied and choose
Next
In this step JSPM performs various status validations and displays the result of each software
component included in the stack definition XML file on the subsequent screen which includes
the following possible statuses
OK Indicates that the SPS level of the corresponding software component is applicable
WARNING We recommend that you view the details about the component by choosing Show
Details
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2460 CUSTOMER 2012-08-30
This status may indicate that the corresponding software component comprises custom
modifications in an NWDI-controlled system
If your system is used for NWDI development and it is either a DEV or a CONS system
you will be informed that JSPM will not deploy the modified software components but
only transport them to the CMS transport directory JSPM will deploy only the software
components that are not modified
If your system is not used for NWDI development or if your system is used for NWDI
development and it is either a TEST or a PROD system you will be informed that JSPM
has found newer versions of modified software components and will automatically replace
the original versions with the newer versions JSPM will deploy all software components
that are not modified together with the replaced versions of the modified software
components
CAUTION
You may get a warning telling you that there are patches installed in your system
containing fixes which might not be included in the target SP Stack This is possible if
you have applied patches of the start SP Stack level that were delivered later than the
target SP Stack delivery date In order not to lose these fixes you need to download and
apply the corresponding patches of the target SP Stack level
If you are performing an update from SAP NetWeaver 70 including enhancement
package 1 SPS00 and you have not applied any patches for the software component with
status WARNING before the update then you can ignore warnings such as the following
example
The new version of the development component sapcomcomsapnetweaver
bcrfmoni is 70100200806121227180000 and is lower than the already
deployed version 70100200807090143420000
REVISE Indicates inconsistencies with the corresponding software component
The deployment cannot be performed until all problems have been resolved You can view
the problems by choosing Show Details
9 If the status of the selected SP Stack is OK or WARNING you can start the system update by choosing
Start JSPM then changes the status to SCHEDULED
If the SP Stack to be applied includes a kernel update and the current kernel is not already of the
corresponding patch level JSPM arranges the kernel update as the very first Support Package to
be applied JSPM updates the kernel binaries of all instances (including Dialog Instances and SCS
instances in a HA environment) whose kernel directories DIR_CT_RUN effectively reside on the host
indicated by the profile parameter SAPGLOBALHOST
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2560
CAUTION
Kernel binaries of instances whose kernel directories DIR_CT_RUN are not effectively linked
to the host SAPGLOBALHOST must be updated individually as described in section Manually
Updating Instances with Kernel Directory Located on Separate Hosts below
The kernel update (includes update of SAP Kernel and SAP IGS) using JSPM consists of the following
steps
1 JSPM stops the Central Instance automatically and prompts you to stop the remote SCS and
Dialog Instances manually
2 After you have stopped all the instances choose the Next button in the dialog box
The kernel update starts
NOTE
If the system is running in a high availability environment make sure that the HA
software does not restart the instance automatically during the update
NOTE
If kernel binaries of the SCS instance need to be updated manually (see Manually Updating
Instances with Kernel Directory Located on Separate Hosts below) you must perform this at the
time when JSPM is updating the kernel binaries of the Central Instance In any case the
SCS kernel must be up-to-date before the next restart
When the kernel update is finished a dialog box appears in which you are prompted to restart
the SCS instance manually
3 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries
before you can proceed with the next step For more information see Adjusting the Ownership and
Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
4 Choose Next in the dialog box when the SCS instance is running again
After the kernel update JSPM restarts the system for further deployment of the remaining Support
Packages in the stack
RECOMMENDATION
If you need to update the kernel binaries of any Dialog Instances manually (see Manually
Updating Instances with Kernel Directory Located on Separate Hosts below) perform the update when
JSPM is updating the remaining Support Packages in the stack in order to save time
The deployment of each Support Package can end with one of the following statuses
DEPLOYED
The Support Package has been successfully deployed
DEPLOYED WITH WARNING
The Support Package has been deployed but it possibly may not work properly with other
deployed components
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2660 CUSTOMER 2012-08-30
You can view the details by choosing Show Details or examining the log files You can also view
the details about the component by choosing the Deployed Components tab page
ERROR
An error has occurred during the deployment You can view the details by choosing Show
Details or examining the log files
You must correct the error to be able to continue with the SP Stack update
You can proceed as described for a deployment that finished with status DEPLOYED WITH
WARNING
If the error correction does not change the contents in the JSPM inbox you can continue
the deployment by choosing Resume
If the error correction changes the contents in the JSPM inbox you can choose New
Deployment to redeploy the SP Stack
NOT DEPLOYED
JSPM has not attempted to deploy the software component for certain reasons
If your system is not used for NWDI development you can proceed as described for a
deployment that finished with status ERROR
If your system is used for NWDI development and it is either a DEV or a CONS system
the status of the modified software components is always NOT DEPLOYED JSPM has
transported the software components of the Support Package Stack both modified and
not modified to the CMS transport directory The deployment of the modified software
components is handled by NWDI
Manually Updating Instances with Kernel Directory Located on Separate Hosts
JSPM performs kernel update for all instances (including Dialog Instances and SCS instances in a HA
environment) whose kernel directories DIR_CT_RUN effectively reside on the host indicated by the profile
parameter SAPGLOBALHOST (by using folder sharing on Windows or file system mounting on UNIX) In
rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of those sort of instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances individually
To update the kernel of an instance manually proceed as follows
1 Log on as user ltsapsidgtadm to the host of the instance to be updated
2 Back up the kernel directory which is specified by the profile parameter DIR_CT_RUN
3 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory with
SAPCAR [page 56]
4 Stop the instance being updated
NOTE
If the system is running in a HA environment make sure that the HA software does not
restart the instance automatically during the update
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2760
5 Copy or move the extracted programs from the temporary directory to the local kernel directory
6 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries as
described in section Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
7 Restart the instance after JSPM has finished the deployment of all packages on the Central Instance
Only valid for UNIX |
Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms
On UNIX platforms you must adjust the ownership and execution permissions of the kernel binaries
after the update regardless whether you performed the update manually or by using JSPM because
both update procedures are performed with the ltsapsidgtadm user Enter the following command
sequence
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
224 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the Java system
23 Parallel Update of Dual-Stack Systems
If you perform an update of a dual-stack system (ABAP+Java) we recommend that you follow the
procedure described below The procedure has been validated to update the ABAP stack and the Java
stack of a NetWeaver system in parallel thus reducing the overall system downtime by half
Procedure
1 Before applying ABAP and Java Support Packages use the Single Support Packages option in JSPM and
select for update only the components SAP KERNEL and BC-FES-IGS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
23 Parallel Update of Dual-Stack Systems
2860 CUSTOMER 2012-08-30
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS)
runs on a dedicated host In this case JSPM does not support update of kernel binaries and
you need to update them manually Perform the update manually as described under Updating
SAP Kernel and SAP IGS in section Updating the Application Server ABAP and ABAP-Based Software
Components [page 16]
2 Import the Support Packages for the component SAP_BASIS into the ABAP stack using the ABAP
Support Package Manager (SPAM)
3 Import the remaining ABAP Support Packages with SPAM and in parallel apply the Java Support
Package Stack with JSPM
Proceed as described in Updating the Application Server ABAP and ABAP-Based Software Components [page
16] and Updating the Application Server Java and Java-Based Software Components [page 23]
24 Process Integration
241 Planning
Procedure
This section covers all the units of Process Integration that should be updated Particularly the following
units must always have the same Support Package level (the patch level can be different)
Integration Server
XI Adapter Engine
Partner Connectivity Kit
System with the Usage Type Process Integration
Software components of Integration Server
Components to Be Updated SP File Name Tool Used to Apply SP
Java stack
XI TOOLS 702 SAPXITOOLltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
ABAP stack
XI CONTENT SAP_BASIS 702 SAPBASISltSPgt_ltPLgtZIP File upload
XI CONTENT SAP_ABA 702 SAPABAltSPgt_ltPLgtZIP
SAP NetWeaver Application Server ABAP (see table Software components of Application Server ABAP [page 15])Note that update of the following software components of the ABAP system is not required SAP ABA 702 SAP BW 702 PI_BASIS 702
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 2960
J2EE Adapter Engine
If your implemented scenario includes a J2EE Adapter Engine then it must always be of the same
Support Package level as the Integration Server
Components of the J2EE Adapter Engine
Component to Be Updated SP File NameTool Used to Apply SP
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
J2SE Adapter Engine
The installation of the J2SE Adapter Engine depends on the implemented scenario
Components of the J2SE Adapter Engine
Component to Be Updated SP File Name Tool Used to Apply SP
XI CONNECTIVITY SE 702 SAPXICONSltSPgt_ltPLgtSCA ZIP tool (for example WinZip)
Partner Connectivity Kit
If your implemented scenario includes a Partner Connectivity Kit (PCK) then it must always be of the
same Support Package level as the Integration Server
Software components of Partner Connectivity Kit
Components to Be Updated SP File NameTool Used to Apply SP
XI PCK 702 SAPXIPCKltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of the Application Server Java [page 20])
System Landscape Directory (SLD)
The System Landscape Directory is required for the PI operations Although updating the SLD is not
necessarily required it is advisable to update the SLD server and the SAP Master Data Content within
it from time to time The update of the SLD includes
1 The system where the SLD is running
2 The SAP Master Data Content within this SLD
SAP GUI
See table Compatible SAP GUI Versions [page 51]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3060 CUSTOMER 2012-08-30
242 Updating Units of Process Integration
Procedure
Before you start the update perform the following steps
In the Runtime Workbench use Communication Channel Monitoring to stop all sender channels
for all adapter types on all your Adapter Engines
On the Integration Server use transaction SMQR and deregister all qRFC queues
System with the Usage Type Process Integration
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the XI instance is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system where the XI instance is running
For more information see Application Server Java and Java-Based Software Components [page 19]
System Landscape Directory (Optional)
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the SLD is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the entire Support Package Stack to the system where the SLD is running
For more information see Application Server Java and Java-Based Software Components [page 19]
J2EE Adapter Engine
Apply the Support Package Stack to the system where the Adapter Engine is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Partner Connectivity Kit
Apply the Support Package Stack to the system where the PCK is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Front End GUIs
Update the SAP GUI components if necessary
For more information see SAP GUI Family [page 51]
ABAP 700 Business System (Optional)
Apply the Support Packages for SAP NetWeaver Application Server ABAP (including SAP kernel and
the Support Package for SAP BASIS 700)
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 640 Business System (Optional)
Apply the Support Packages for SAP Web Application Server ABAP 640 (including SAP kernel and the
Support Package for SAP BASIS 640)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3160
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 620 Business System (Optional)
1 Update the SAP Kernel 620
2 Import the released Basis Support Packages for SAP Web AS 620 as well as the most recent Add-
On Support Package for APPINT 200_620 in the order described in SAP Note 439915
J2SE Adapter Engine (Optional)
NOTE
The XI Adapter Engine (J2SE) and all its adapters are provided for compatibility reasons only and
are not developed any further You have to use the XI Adapter Engine running on SAP NetWeaver
AS Java For more information see the Master Guide ndash SAP NetWeaver 70 available on SAP Service
Marketplace at httpservicesapcominstallNW70 Planning
1 Extract the SAPXICONSltSPgt_ltPLgtSCA (XI Connectivity SE 700) archive (ZIP format) to a temporary
directory
2 Save the old configuration files as described in the document Adapterpdf in directory
lttemp_directorygttech_adapterAdministrationDocumentation
3 Unpack the ZIP archive TechnicalAdapterssda to the installation directory of the XI Adapter
Engine (J2SE)
4 Restore the configuration files with restore_configuration
243 Post-Installation Steps
Procedure
Communication Channels and Queues
Restart all stopped sender channels and register all deregistered qRFC queues
XI Content
In the system with usage type PI import the XI content from the archives SAPBASISltSPgt_ltPLgtZIP
and SAPABAltSPgt_ltPLgtZIP as follows
1 Unpack the archives using a ZIP tool of your choice
2 Copy the corresponding export files (with file extension tpz) to the import directory ltINSTDIRgt
ltSAPSIDgtSYSglobalxirepository_serverimport
3 Start the Integration Builder (transaction SXMB_IFR)
4 Enter the Integration Repository by choosing Repository (Design)
5 Choose Tools Import design objects
6 Import the tpz files containing the XI content
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3260 CUSTOMER 2012-08-30
NOTE
For more information see SAP Note 836200
Role Generation on the Integration Server
On the Integration Server execute transaction SUPC (mass generation of roles) for all SAP_XI roles in
each of your clients to regenerate possibly changed roles
NOTE
Do not forget to make a user comparison for regenerated roles afterwards
Partner Connectivity Kit (Optional)
Perform the post-installation steps for PCK as described in SAP Note 746328
SAP Master Data within the SLD (Optional)
In the system where your SLD is running import the latest SLD content as described in SAP Note
669669
Receiver-Based EOIO Serialization in J2EE Adapter Engine (Optional)
The J2EE Adapter Engine can be switched to receiver-based EOIO serialization The switch can be
triggered on demand and is executed asynchronously It includes a database migration step during
which all EOIO processing in the Adapter Engine is disabled See SAP Note 973894 for details about how
to start the EOIO serialization migration
Service Metering (Optional)
Service metering gathers information about a service caller transfers it to the service provider and
counts on the service provisioning side how many times a service is called and by which service caller
Service metering is performed for the XI message protocol and the WS message protocol Service
metering is automatically enabled after applying a Support Package Stack By default only non-sensitive
data is transmitted to internal or external service providers in a compatible way
Service metering can be configured in PI in the Integration Engine on sender-side and in the Integration
Directory
Service metering can be configured in AS ABAP in transaction SOAMANAGER
Only if the service provider is allowed to receive more detailed information about the service caller set
the metering level to higher than the default
For more information see SAP Note 1239428
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3360
25 Business Intelligence
251 Planning
Procedure
Business Intelligence includes one or many of the following units that must be updated depending on
your implemented scenarios The usage types Business Intelligence (BI) and Business Intelligence Java
Components (BI-Java) must always have the same Support Package level
Business Intelligence
Software Components of Business Intelligence
Component to Be Updated SP File Name Tool Used to Apply SP
BI CONT ADDON 70x SAPK-70ltxgtltSPgtINBICONT SAINT
SAP NetWeaver Application Server ABAP (see table Software Components of Application Server ABAP [page 15])
NOTE
For information about the dependencies applying to BI Content Support Packages see SAP Note
653814 BI CONT 703 Support Packages are not part of the NetWeaver SP Stacks Updates can be
performed when applicable Alternatively BI CONT 704 Support Packages can be imported See
the BI Content release strategy in SAP Note 153967
Business Intelligence Java Components
BI Java Components
Component to Be Updated SP File NameTool Used to Apply SP
BI REPORTING AND PLANNING 702 BIREPPLANltSPgt_ltPLgtSCA JSPM
BI WEBDYNPRO ALV 702 BIWDALVltSPgt_ltPLgtSCA
BI INFORM BROADCASTING 702 BIIBCltSPgt_ltPLgtSCA
BI WEB APPLICATIONS 702 BIWEBAPPltSPgt_ltPLgtSCA
BI BASE SERVICES 702 BIBASESltSPgt_ltPLgtSCA
VISUAL COMPOSER BI KITS 702 VCKITBIltSPgt_ltPLgtSCA
Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
BI Precalculation Service
Components of the BI Precalculation Service
Component to Be Updated SP File Name Tool Used to Apply SP
BI Pre-calculation Service 700 xPreCalServerltSPgt_ltPLgtexe Installer
Search and Classification (TREX)
See table TREX Component [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3460 CUSTOMER 2012-08-30
BI Accelerator
The BI Accelerator is based on the TREX technology It is a special Linux 64-bit version of SAP NetWeaver
70 Search and Classification (TREX) which is delivered on preconfigured hardware
NOTE
You cannot use a TREX installation based on 32-bit architecture that is configured for searching
in metadata and documents for the BI Accelerator And vice versa a BI Accelerator box cannot
be used for searching in metadata and documents
If you want to use the search functionality as well as the BI Accelerator you require two separate
installations For more information see BI Accelerator [page 47]
Clients
Depending on your implemented scenarios you have to update SAP GUI Components and Business
Explorer (BI Add-OnBW Add-On)
NOTE
See SAP Note 889314 to determine when to use the BI Add-On and the BW Add-On
NOTE
As SAP GUI 640 is no longer supported BI Frontend Support Package 1800 resp patch 1801 is the
last Support Package resp patch based on SAP GUI 640 For more information see SAP Note
1231292 (Frontend Add-in Strategy 640710 GUI Version)
For more information about the new release strategy for the BI Frontend see SAP Note 1231363
(Changed Delivery Strategy for BI Frontend)
252 Preparation
Procedure
For the Support Packages of the most important Business Intelligence units so called SAPBINews
(SAPBWNews) Notes are created Read these Notes before updating Business Intelligence For SAP
NetWeaver 70 including enhancement package 2 SPS 12 these are the following
Business Intelligence ABAP SAP Note 1680996
Business Intelligence Java Components SAP Note 1726461
BI 70 Frontend Add-On for SAP GUI 710 SAP Note 1413032
BI 70 Frontend Add-On for SAP GUI 720 SAP Note 1630112
BI 70 Frontend Add-On for SAP GUI 730 SAP Note 1726739
For more information about BI Support Packages see SAP Community Network at http
scnsapcomcommunitydata-warehousingnetweaver-bw Related Resources SAP NW BW Support
Packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
2012-08-30 CUSTOMER 3560
253 Updating Units of Business Intelligence
Procedure
Business Intelligence
1 Update the SAP NetWeaver Application Server ABAP (with BI CONT 70x if necessary) with the
appropriate Support Packages
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
NOTE
When applying the component SAP BW 702 some generation errors might occur When
you start importing the BI Support Packages in transaction SPAM choose the menu path
Extras Ignore generation errors For more information see SAP Note 114134
2 Apply the Support Package Stack to the system with the usage type BI-Java
For more information see Application Server Java and Java-Based Software Components [page 19]
3 Update the BI Precalculation Service that is used in your scenario
4 Update the standalone engine Search and Classification (TREX) that is used in your scenario For more
information see Standalone Engine Search and Classification (TREX) [page 44]
NOTE
You have to update TREX to the newest version if you use search capabilities within Business
Intelligence
5 Update the BI Accelerator to the newest available version For more information see BI
Accelerator [page 47]
6 Update the SAP GUI and Business Explorer (BI Add-On BW Add-On) on all remote client hosts
that are involved in the scenario
For more information see SAP GUI Family [page 51] and Business Explorer (BI Add-On BW Add-On)
[page 51]
BI Precalculation Service
1 Log on to the host as a user with administration rights
2 Install the Support Package of the BI Precalculation Service by executing the
xPreCalServerexe file
The welcome screen of the BI Precalculation Server setup wizard appears
The setup now checks the system for the prerequisites
3 Choose the option Update for updating the BI Precalculation service to the current patch level and
then Finish
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3660 CUSTOMER 2012-08-30
26 EP Core
261 Planning
Procedure
The following installable software units must be updated
EP Core
Software Components of EP Core
Component to Be Updated SP File Name Tool Used to Apply SP
PORTAL CORE SERVICES 702 EPBCltSPgt_ltPLgtSCA JSPM
PORTAL FRAMEWORK 702 EPBC2ltSPgt_ltPLgtSCA
PORTAL 702 EPPSERVltSPgt_ltPLgtSCA
PORTAL WEB DYNPRO 702 EPWDCltSPgt_ltPLgtSCA
UWL COLL PROCESS ENGINE 702 UWLJWFltSPgt_ltPLgtSCA
CAF EU 702 SAPEUltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
262 Preparation
Procedure
Backing Up the Portal Runtime Configuration
If you have made changes to the standard Portal Runtime configuration you have to make a backup
of the configuration before the update process For more information see SAP Note 1064468
263 Updating EP Core
Procedure
Apply the Support Package Stack to a system with usage type EP Core
For more information see Application Server Java and Java-Based Software Components [page 19]
264 Post-Installation Steps for EP Core
Procedure
Restoring the Portal Runtime Configuration
To make your changes to the standard Portal Runtime Configuration effective you have to restore
the backup of the configuration done before the update process For more information see SAP Note
1064468
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
26 EP Core
2012-08-30 CUSTOMER 3760
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
NOTE
The SAP Help Portal always provides the up-to-date version of the SAP Library Therefore
we recommend that you use this channel to access the SAP Library
Local installation of the SAP Library from the online documentation DVD
CAUTION
In order to inform yourself about the current Support Package Stack you first have to update
your local installation of the SAP Library to the corresponding SPS level Follow the
instructions in section SAP Library [page 52]
Naming Conventions
In this document the following naming conventions apply
Variables
Variables Description
ltSAPSIDgt
ltsapsidgt
ltSIDgt
SAP system ID
ltINSTDIRgt Installation directory for the SAP system
lthostgt Host name
ltinstance_nogt Instance number of a system instance
ltdatabasegt Name of database
ltsapinst_directorygt Installation directory for the SAP installation tool SAPinst
ltsp_directorygt Temporary directory which the archives of a Support Package are downloaded or copied to
ltOSgt Operating system
ltOS_DIRgt OS-dependent directory consisting of a folder for the platform and a subfolder of your OS versionFor example if you operating system is Sun OS 64bit ltOS_DIRgt stands for UNIXSUNOS64
ltSP_Stackgt Number of Support Package Stack
ltSPgt Support Package level
ltPLgt Support Package patch level
ltRELgt Release number
ltLOCALEgt Language definitionFor example the German locale is _de
ltkrnl_directorygt Kernel directory which the profile parameter DIR_CT_RUN usually refers to
ltsdm_homegt Program file location of the Software Deployment Manager (SDM)
ltSAPGLOBALHOSTgt SAP global host the host where the global directories of an SAP system reside
ltSAPLOCALHOSTgt SAP local host the host where a particular instance of an SAP system is running
1 Overview
11 Before You Start
1060 CUSTOMER 2012-08-30
12 Types of Support Packages
The following table explains the terms used in the correction process as part of the software maintenance
process for SAP NetWeaver
Correction Process Description
Standard correction process
Support Package Stack Description
A Support Package Stack is a set of Support Packages and patches for the respective product version that must be used in the given combination
Version numbersSupport Package Stacks have a release number and a stack number for example SAP NetWeaver 70 Support Package Stack 05
DeliveryThere is no dedicated delivery format for the Support Package Stacks The included Support Package files have their delivery formats and must be applied using the tools as described below
Kernel Patches Version numbers
SAP Kernel patches have a release number and a patch number The patch number is increased with each correction
DeliverySAP Kernel patches are delivered as SAR files They are installed by extracting the SAR files to the kernel directory using SAPCAR Separate SAR files are shipped for the different kernel types depending on UNICODENON-UNICODE and the platform
ABAP Support Packages Description
ABAP Support Packages contain corrections and adjustments for the ABAP-based Software Components of the SAP system
DependenciesIn contrast to Java Support Packages ABAP Support Packages are non-cumulative Therefore ABAP Support Packages must be installed in the correct sequence one after the other You cannot skip any intermediate Support Packages
DeliveryABAP Support Packages are delivered as SAR files They are installed using the Support Package Manager (SPAM)
Java Support Packages Description
Java Support Packages contain corrections for the Java-based Software Components of the SAP system
DependenciesJava Support Packages always contain a full delivery of the Software Components Therefore you only need to apply the latest Support Package to update the software If there are dependencies with other Java Support Packages these are specified in an SAP Note
DeliveryJava Support Packages are delivered as Software Component Archives (SCAs) They are applied using the Java Support Package Manager (JSPM)
1 Overview
12 Types of Support Packages
2012-08-30 CUSTOMER 1160
Correction Process Description
Emergency correction process
SAP Note Correction (ABAP) Description
SAP Note corrections contain single ABAP fixes Delivery
SAP Note corrections are delivered with SAP Notes If required you apply them using the SAP Note Assistant
Java Support Package Patch Description
A Java Support Package patch contains corrections for the Java Software Components Java Support Package patches are created and released on demand A Java Support Package patch corresponds to an SAP Note that describes the same correction
DependenciesA Java Support Package patch always contains a full package of the corresponding Software Component and is applied using JSPM
13 Downloading Support Package Stacks
The Maintenance Optimizer in SAP Solution Manager is the only source from which you can receive
maintenance updates for SAP NetWeaver 70 and higher releases as well as for all applications running
on top of SAP NetWeaver The Maintenance Optimizer supports you in selecting and downloading all
required maintenance files In addition the Maintenance Optimizer generates a stack XML file and
saves it to the EPS inbox directory of SAP Solution Manager
Prerequisites
You have configured the Maintenance Optimizer in SAP Solution Manager as described on SAP Help
Portal at httphelpsapcom SAP Solutions SAP Solution Manager SAP Solution Manager ltReleasegt
ltLanguagegt Change Management Maintenance Optimizer Planning and Monitoring Product Maintenance and
also in section Automatically Calculating Product Maintenance Files
Procedure
To download a Support Package Stack proceed as follows
1 Start SAP Solution Manager using the transaction solution_manager To start the Maintenance
Optimizer choose Operations Change Management Maintenance Optimizer
2 In the Maintenance Optimizer choose the solution for which you want to download SP Stack files
3 Choose Create New Maintenance Transaction
4 Select the product version for which you want to apply a Support Package Stack
The Maintenance Optimizer displays all the systems assigned to the selected product version
5 Select the checkbox for the system that you want to update and choose Continue
6 On the subsequent screen select the Maintenance option and then choose Find Download Files
1 Overview
13 Downloading Support Package Stacks
1260 CUSTOMER 2012-08-30
7 Select the target SP Stack level and the relevant usage types according to the IT scenario to be
updated
8 Choose Find Download Files for the Stack Version
The Maintenance Optimizer displays the product maintenance files in three successive lists
9 Select the required files from the displayed lists
The first list shows all files that are dependent on the type of your operating system and
database
Select the files that correspond to the combination of your operating system and database and
the database-independent files
If your system is distributed on several hosts make sure to select all operating systems used
by the NetWeaver instances You can see all the kernels detected on your system on the Deployed
Components tab page on JSPM user interface (under the SAP KERNEL node) All detected kernels
must be updated to the same version
You get to the second list by choosing Continue This list displays all Support Package files that
are not assigned to the selected Support Package Stack Before you continue with the selection
you must check whether the Support Package files listed here are suitable for your product
maintenance procedure
You get to the third list by choosing Continue The list displays all product maintenance files
that are part of the selected Support Package Stack
Ensure that all files that are assigned to the Support Package Stack are selected here Files that
are not selected will not be included later in the download
10 Choose Continue Use the Download Basket to download the maintenance files
11 Choose Continue once the files have been put in your Download Basket and then Confirm Files in
Download Basket
A dialog window appears and displays all files
12 Confirm the download for all files
13 Open your Download Manager and download the files
NOTE
The stack XML file is generated by the Maintenance Optimizer and automatically saved to
the EPS inbox directory of SAP Solution Manager
More Information
For more information about the Maintenance Optimizer see SAP Support Portal at http
servicesapcomsolman-mopz
1 Overview
13 Downloading Support Package Stacks
2012-08-30 CUSTOMER 1360
This page is left blank for documents that are printed on both sides
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
This chapter describes how to apply Support Packages to installable software units of SAP NetWeaver
70 including enhancement package 2 SAP NetWeaver distinguishes three types of installable software
units
Systems with one or multiple usage types
Standalone engines
Clients
A scenario implementation usually involves several installed software units
RECOMMENDATION
We strongly recommend that you always update all software units belonging to one scenario
together in order to retain a consistent system state Due to the fact that some installable software
units can be commonly shared in different scenarios you must consequently update all scenarios
using the common software units at the same time
21 Application Server ABAP and ABAP-Based Software Components
211 Planning
Procedure
The following components belong to the usage type SAP NetWeaver Application Server ABAP
Software Components of Application Server ABAP
Component to Be Updated SP File Name Tool Used to Apply SP
SAP KERNEL 720 32-64-BIT Non-UNICODEUNICODE SAPEXESAR
SAPEXEDBSAR
JSPMmanually
SAP IGS 700 igsexesar
SAP ABA 702 SAPKA702ltSPgt SPAMSAINT
SAP BASIS 702 SAPKB702ltSPgt
SAP BW 702 SAPKW702ltSPgt
PI_BASIS 702 SAPK-702ltSPgtINPIBASIS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
2012-08-30 CUSTOMER 1560
NOTE
This table contains only software components that belong to the usage type AS ABAP Software
components of other usage types and application units are listed in the corresponding sections
NOTE
SAP delivers intermediate Support Packages for the component SAP BW 702 between two
subsequent SP levels besides the Support Packages delivered along with the Support Package
Stacks Therefore the highest SP level of SAP BW 702 does not necessarily match the target SP
Stack level
CAUTION
When applying a Support Package Stack to a dual-stack system (ABAP+Java) the Java Support
Package Manager (JSPM) will necessarily restart the system several times to make the changes
effective The ABAP part will only be restarted when JSPM is updating the SAP kernel and IGS
212 Preparation
Procedure
Read SAP Note 822379 and all related SAP Notes that the first one refers to
213 Updating the Application Server ABAP and ABAP-Based Software Components
Procedure
Applying Support Packages to SAP NetWeaver Application Server ABAP and ABAP-Based Components
You can update the SAP NetWeaver Application Server ABAP and all ABAP-based software components
running on it using the Support Package Manager (transaction SPAM)
NOTE
If a particular Support Package Stack requires the installation or upgrade of some add-on
components you must use the ABAP Add-on Installation Tool (transaction SAINT) instead of the
Support Package Manager In this case SAINT is able to import both the add-on components and
the related Support Packages of ordinary SAP components
Proceed as follows
1 Log on to the SAP NetWeaver AS system with client 000
2 Start the Support Package Manager by calling transaction SPAM or
start the Add-On Installation Tool by calling transaction SAINT
3 Load the relevant Support Packages or add-on installation packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
1660 CUSTOMER 2012-08-30
4 Define an import queue
5 Perform the import of the defined queue
NOTE
If you have modified SAP objects in your system and these objects are included in the Support
Packages you must perform modification adjustment during the import using the
transactions SPDD (for ABAP Dictionary objects) and SPAU (for Repository objects)
To import the queue you use the standard scenario You can choose between the conventional
import mode and downtime-minimized import mode
Conventional Import Mode
This option comprises the following steps
1 Update the SAP kernel and SAP IGS as described in section Updating SAP Kernel and SAP IGS below
Start the system after the kernel update
2 Import the ABAP Support Packages with the Support Package Manager (SPAM)
Import Mode Downtime-Minimized
This option can be used to reduce system downtime during the update It comprises the following
steps
1 In transaction SPAM enable the downtime-minimized import mode by choosing Extras
Settings then on the Import queue tab page choose Standard and activate the option Import Mode
Downtime-Minimized
2 Import the ABAP Support Packages into the system in an inactive state in the downtime-minimized
mode during system uptime
3 Update the SAP kernel and SAP IGS as described in section Updating SAP Kernel and SAP IGS below
Start the system after the kernel update
4 Complete the ABAP Support Packages import
CAUTION
During this step the system cannot carry out any business transactions (business downtime)
NOTE
In rare cases due to the dependencies of some Support Packages on a particular kernel patch level
the downtime-minimized update does not work In such cases the Support Package Manager
informs you that you must update the SAP kernel before importing ABAP Support Packages You
must proceed with the conventional import procedure
Updating SAP Kernel and SAP IGS
In general the SAP kernel and IGS binaries are located in the global kernel directory DIR_CT_RUN on
the host indicated by the profile parameter SAPGLOBALHOST Once the files in this directory have been
updated to a new patch level a system restart distributes them by means of the program SAPCPE to the
local directories DIR_EXECUTABLE on the hosts where the instances of the SAP system are running
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
2012-08-30 CUSTOMER 1760
CAUTION
The automatic distribution by means of SAPCPE depends on the settings of the profile parameters
DIR_CT_RUN for the global kernel directory and DIR_EXECUTABLE for the local directory of the
executables Before you continue check the instance profiles for the settings of these parameters
in systems that are not installed using SAPinst (for example systems upgraded from older releases
copied or migrated systems)
CAUTION
If your system is a dual-stack system (ABAP+Java) and the ABAP stack has a non-Unicode kernel
be aware that the SCS instance has a Unicode kernel You have to update both kernels (together
with SAP IGS) prior to updating the ABAP and Java Support Package stacks This ensures
compatibility and reduces system downtime
RECOMMENDATION
If you perform an update of a dual-stack system (ABAP+Java) we recommend that prior to
applying ABAP and Java Support Package stacks you use the Single Support Packages option in JSPM
and select for update only the components SAP KERNEL and BC-FES-IGS
For more information about updating a dual-stack system see Parallel Update of Dual-Stack Systems
[page 28]
If you perform an update of an ABAP system the following procedure applies for updating the SAP
kernel and IGS manually
1 Log on as user ltsapsidgtadm to the instance host to be updated
2 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory using
SAPCAR [page 56]
3 Stop the ABAP system that you want to update
NOTE
If the system is running in a high availability (HA) environment make sure that the HA
software does not restart the system automatically during the update
4 Back up the kernel directory ltkrnl_directorygt
5 Copy or move the extracted programs from the temporary directory to the SAP kernel directory
6 Only valid for UNIX |
Execute the following command sequence on UNIX platforms
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
1860 CUSTOMER 2012-08-30
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
7 Restart the SAP system
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS) runs
on a dedicated host You need to perform the kernel update for the ASCS instance manually but
excluding the IGS update because the IGS is not required in an ASCS instance
In rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of such instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances manually Proceed as described
in section Manually Updating Instances with Kernel Directory Located on Separate Hosts below in this document
214 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the ABAP system
22 Application Server Java and Java-Based Software Components
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system which includes
JSPM itself
SAP Kernel and SAP IGS
All Java-based usage types installed in the system
Software Deployment Manager (SDM) - the deployment service of the system
RECOMMENDATION
We strongly recommend that you apply the target Support Package Stack to your system as a
whole This ensures consistency on both the system and the application levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 1960
221 Planning
Procedure
Java Support Package files (SCAs) contain all software objects of the corresponding software
components Thus it is sufficient to apply the Java Support Package files of the intended Support Package
Stack directly to the Java system to be updated It is not necessary to apply the Support Package Stacks
between the start SP Stack level and the target SP Stack level successively
CAUTION
When applying a Support Package Stack to a Java system the Java Support Package Manager (JSPM)
will necessarily restart the system several times to make the changes effective With a dual-stack
system (ABAP+Java) the ABAP part will only be restarted when JSPM is updating the SAP kernel
and IGS
The following components belong to the usage type SAP NetWeaver Application Server Java (AS Java)
Software Components of Application Server Java
Component to Be Updated SP File Name Tool Used to Apply SP
SAP Kernel 720 32-64-BIT UNICODE SAPEXESAR
SAPEXEDBSAR
JSPM
SAP IGS 700 igsexesar
BI META MODEL REPOSITORY 702 BIMMRltSPgt_ltPLgtSCA
J2EE ENGINE CORE TOOLS 702 CORETOOLSltSPgt_ltPLgtSCA
J2EE ENGINE BASE TABLES 702 BASETABLESltSPgt_ltPLgtSCA
BI UDI 702 BIUDIltSPgt_ltPLgtSCA
DI BUILD TOOL 702 SAPBUILDTltSPgt_ltPLgtSCA
SAP CAF 702 CAFltSPgt_ltPLgtSCA
SAP IKS 702 KMKWJIKSltSPgt_ltPLgtSCA
JAVA LOG VIEWER 702 JLOGVIEWltSPgt_ltPLgtSCA
SAP J2EE ENGINE CORE 702 SAPJEECORltSPgt_ltPLgtSCA
SAP JAVA TECH SERVICES 702 SAPJTECHSltSPgt_ltPLgtSCA
SAP TECH S OFFLINE 702 SAPJTECHFltSPgt_ltPLgtSCA
SAP J2EE ENGINE 702 SAPJEEltSPgt_ltPLgtSCA
JAVA SP MANAGER 702 JSPMltSPgt_ltPLgtSCA
ADOBE DOCUMENT SERVICES 702 ADSSAPltSPgt_ltPLgtSCA
UME ADMINISTRATION 702 UMEADMINltSPgt_ltPLgtSCA
LIFECYCLE MGMT TOOLS 702 LMTOOLSltSPgt_ltPLgtSCA
SAP CAF-UM 702 CAFUMltSPgt_ltPLgtSCA
SAP SOFTW DELIV MANAGER 702 SDMKITltSPgt_ltPLgtJAR
SOFTWARE LIFECYCLE MANAGER 702 SWLIFECYCLltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2060 CUSTOMER 2012-08-30
NOTE
This table contains only software components that belong to the usage type AS Java Software
components of other usage types and Java application units are listed in the corresponding
sections
NOTE
As of Support Package 09 you can update your system with SAP Kernel 720 instead of SAP Kernel
701
222 Preparation for Applying a Support Package Stack
Procedure
1 Download the Support Package Stack with all usage types to be updated and the stack definition
XML file as described in Downloading Support Package Stacks [page 12]
NOTE
You can find the activated usage types in an existing Java system on the Deployed Components tab
page on the JSPM user interface
NOTE
You do not need to download the SP Stacks between the source SP Stack level and target SP
Stack level By default the target SP Stack level is the latest available SP Stack
2 Make sure the following requirements are met prior to applying the Support Package Stack
You have familiarized yourself with SAP Note 891983 before you start the Java Support Package
Manager
The system to be updated is fully functional
The Support Package Stack you want to apply and the corresponding stack definition XML
file are available in the EPS inbox directory usrsaptransEPSin By default this location
can be also referred to as ldquoJSPM inboxrdquo
The SAP NetWeaver Application Server Java (AS Java) and the database have been backed up
You have not deleted renamed or created any directories and files in the following directories
and their subdirectories usrsapltSAPSIDgtSYSexe and usrsapltSAPSIDgtSYS
profile
Otherwise JSPM cannot detect the kernel and the system profiles and cannot be started If a
backup of the kernel and the system profiles has been required it has been created in a different
directory
The ltsapsidgtadm user has Read permissions for the EPS inbox directory usrsaptransEPS
in
If your database is SAP MaxDB the overwrite mode for the log area has been activated
The database and the SDM repository have been synchronized
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2160
For more information see the online documentation for JSPM on SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70 Library
(including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library Administrators Guide
Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems AS Java
(Application Server for Java) Software Logistics Software Maintenance Java Support Package Manager
Then choose Troubleshooting JSPM Does Not Update the Versions of the Deployed Components
There is enough disk space
For more information see SAP Note 891895
Your current SAPCAR tool is able to extract the Support Packages for the SAP kernel and
other OS level binaries delivered as SAR files
RECOMMENDATION
You can download the latest version of SAPCAR from SAP Service Marketplace at
httpservicesapcompatches Entry by Application Group Additional Components
SAPCAR
Put the downloaded version in the same directory in the JSPM inbox in which the kernel
SAR files reside so that JSPM can use this version for extracting the SAR files
3 Only valid for Linux |
For RHEL 4 and SLES 9 you need to install additional operating system packages For more
information see SAP Note 1021236End of Linux |
4 Only valid for Windows |
For Windows you need to install additional operating system packages For more information see
SAP Note 684106End of Windows |
5 To prevent the Software Deployment Manager (SDM) from temporarily exceeding the available
disk space during the update process you can change the file transfer directory of SDM in a system
of SPS09 or higher using the following command sequence
Only valid for Windows |
cd ltsdm_homegt
StopServerbat
sdmbat jstartup mode=standalone
sdmbat filetransferdir dir=ltnew_dirgt
sdmbat jstartup mode=integrated
StartServerbat
End of Windows |
Only valid for IBM i5OSUNIX |
cd ltsdm_homegt
StopServersh
sdmsh jstartup mode=standalone
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2260 CUSTOMER 2012-08-30
sdmsh filetransferdir dir=ltnew_dirgt
sdmsh jstartup mode=integrated
StartServersh
End of IBM i5OSUNIX |
6 To prevent deployment errors during the update process proceed as follows
1 Log on to the Central Instance host
2 Start the ConfigTool and in the navigation area choose Cluster-data Global server configuration
Managers ServiceManager
3 In the Global properties panel set the Custom value of the EventTimeout property to 120
4 Choose Save
5 Restart the Central Instance
7 Check whether the used JDK version and the Java VM settings of the Java runtime system comply
with the requirements in SAP Note 723909 Update the JDK and adjust the settings if necessary
NOTE
An update of the used JDK version possibly changes the JVM path In this case you must
make the new path available to all Dialog Instances of the J2EE engine by implementing option
1 of SAP Note 718901
8 Make sure that the J2EE administrator password stored in the secure store for offline usage is
identical with the one stored in the User Management Engine (UME) You can change the password
in the secure store as described in SAP Note 870445
9 If you are running a high availability system on Windows you might need to prepare your system
as described in the online documentation for JSPM see section Preparing Systems That Run in High
Availability Environment
223 Updating the Application Server Java and Java-Based Components
Procedure
Applying a Support Package Stack to SAP NetWeaver Application Server Java and Java-Based Components
NOTE
The JSPM GUI might not work properly on some UNIX systems For more information and the
solution see SAP Note 1013976
1 Log on as user ltsapsidgtadm to the Central Instance host
NOTE
If your operating system is IBM i log on as user ltSIDgtADM or ltSIDgtOFR
2 Close the SAP Management Console (SAP MMC) and the SDM remote GUI client
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2360
3 For UNIX and Windows To start the JSPM navigate to the directory ltINSTDIRgtltSIDgt
ltCentral_Instance_Namegtj2eeJSPM and run the go script file
NOTE
If your system is running on IBM i to start the JSPM proceed as follows
1 To prevent JSPM from automatically starting its GUI in the file usrsapltSIDgt
ltCentral_Instance_Namegtj2eeJSPMparamjspm_configtxt change the
property dialogSDTServerConnectionSDTGuilaunch from true to false
2 On the IBM i host run the go script file using the following command
QSH CMD(usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPMgo)
3 In the mounted directory usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPM run
the StartGui script file The JSPM GUI appears
4 In the Host field enter the target IBM i host
NOTE
Depending on the system type ltCentral_Instance_Namegt has the following syntax
Standalone Java system JCltinstance_nogt
Add-On system DVEBMGSltinstance_nogt
4 Enter your SDM password to log on to the SDM
5 On the Deployment tab page select the Java Support Package Manager option and update the software
component sapcomJSPM to the target SPS level
6 Restart the JSPM and log on with the SDM password
RECOMMENDATION
We strongly recommend that you use the Support and Enhancement Package Stack option when
applying a Support Package Stack Other options can lead to unintended consistency issues
NOTE
If you need to include the latest patches for a particular component during the update process
with the Support and Enhancement Package Stack option stop the JSPM after restart and apply SAP
Note 1080821 Then start the JSPM again
7 On the Deployment tab page select the Support and Enhancement Package Stack option and choose Next
The Support Package Stacks that are available for deployment in the global EPS inbox directory
are displayed
8 In the Target SP Stack Level dropdown box select the Support Package Stack to be applied and choose
Next
In this step JSPM performs various status validations and displays the result of each software
component included in the stack definition XML file on the subsequent screen which includes
the following possible statuses
OK Indicates that the SPS level of the corresponding software component is applicable
WARNING We recommend that you view the details about the component by choosing Show
Details
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2460 CUSTOMER 2012-08-30
This status may indicate that the corresponding software component comprises custom
modifications in an NWDI-controlled system
If your system is used for NWDI development and it is either a DEV or a CONS system
you will be informed that JSPM will not deploy the modified software components but
only transport them to the CMS transport directory JSPM will deploy only the software
components that are not modified
If your system is not used for NWDI development or if your system is used for NWDI
development and it is either a TEST or a PROD system you will be informed that JSPM
has found newer versions of modified software components and will automatically replace
the original versions with the newer versions JSPM will deploy all software components
that are not modified together with the replaced versions of the modified software
components
CAUTION
You may get a warning telling you that there are patches installed in your system
containing fixes which might not be included in the target SP Stack This is possible if
you have applied patches of the start SP Stack level that were delivered later than the
target SP Stack delivery date In order not to lose these fixes you need to download and
apply the corresponding patches of the target SP Stack level
If you are performing an update from SAP NetWeaver 70 including enhancement
package 1 SPS00 and you have not applied any patches for the software component with
status WARNING before the update then you can ignore warnings such as the following
example
The new version of the development component sapcomcomsapnetweaver
bcrfmoni is 70100200806121227180000 and is lower than the already
deployed version 70100200807090143420000
REVISE Indicates inconsistencies with the corresponding software component
The deployment cannot be performed until all problems have been resolved You can view
the problems by choosing Show Details
9 If the status of the selected SP Stack is OK or WARNING you can start the system update by choosing
Start JSPM then changes the status to SCHEDULED
If the SP Stack to be applied includes a kernel update and the current kernel is not already of the
corresponding patch level JSPM arranges the kernel update as the very first Support Package to
be applied JSPM updates the kernel binaries of all instances (including Dialog Instances and SCS
instances in a HA environment) whose kernel directories DIR_CT_RUN effectively reside on the host
indicated by the profile parameter SAPGLOBALHOST
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2560
CAUTION
Kernel binaries of instances whose kernel directories DIR_CT_RUN are not effectively linked
to the host SAPGLOBALHOST must be updated individually as described in section Manually
Updating Instances with Kernel Directory Located on Separate Hosts below
The kernel update (includes update of SAP Kernel and SAP IGS) using JSPM consists of the following
steps
1 JSPM stops the Central Instance automatically and prompts you to stop the remote SCS and
Dialog Instances manually
2 After you have stopped all the instances choose the Next button in the dialog box
The kernel update starts
NOTE
If the system is running in a high availability environment make sure that the HA
software does not restart the instance automatically during the update
NOTE
If kernel binaries of the SCS instance need to be updated manually (see Manually Updating
Instances with Kernel Directory Located on Separate Hosts below) you must perform this at the
time when JSPM is updating the kernel binaries of the Central Instance In any case the
SCS kernel must be up-to-date before the next restart
When the kernel update is finished a dialog box appears in which you are prompted to restart
the SCS instance manually
3 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries
before you can proceed with the next step For more information see Adjusting the Ownership and
Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
4 Choose Next in the dialog box when the SCS instance is running again
After the kernel update JSPM restarts the system for further deployment of the remaining Support
Packages in the stack
RECOMMENDATION
If you need to update the kernel binaries of any Dialog Instances manually (see Manually
Updating Instances with Kernel Directory Located on Separate Hosts below) perform the update when
JSPM is updating the remaining Support Packages in the stack in order to save time
The deployment of each Support Package can end with one of the following statuses
DEPLOYED
The Support Package has been successfully deployed
DEPLOYED WITH WARNING
The Support Package has been deployed but it possibly may not work properly with other
deployed components
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2660 CUSTOMER 2012-08-30
You can view the details by choosing Show Details or examining the log files You can also view
the details about the component by choosing the Deployed Components tab page
ERROR
An error has occurred during the deployment You can view the details by choosing Show
Details or examining the log files
You must correct the error to be able to continue with the SP Stack update
You can proceed as described for a deployment that finished with status DEPLOYED WITH
WARNING
If the error correction does not change the contents in the JSPM inbox you can continue
the deployment by choosing Resume
If the error correction changes the contents in the JSPM inbox you can choose New
Deployment to redeploy the SP Stack
NOT DEPLOYED
JSPM has not attempted to deploy the software component for certain reasons
If your system is not used for NWDI development you can proceed as described for a
deployment that finished with status ERROR
If your system is used for NWDI development and it is either a DEV or a CONS system
the status of the modified software components is always NOT DEPLOYED JSPM has
transported the software components of the Support Package Stack both modified and
not modified to the CMS transport directory The deployment of the modified software
components is handled by NWDI
Manually Updating Instances with Kernel Directory Located on Separate Hosts
JSPM performs kernel update for all instances (including Dialog Instances and SCS instances in a HA
environment) whose kernel directories DIR_CT_RUN effectively reside on the host indicated by the profile
parameter SAPGLOBALHOST (by using folder sharing on Windows or file system mounting on UNIX) In
rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of those sort of instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances individually
To update the kernel of an instance manually proceed as follows
1 Log on as user ltsapsidgtadm to the host of the instance to be updated
2 Back up the kernel directory which is specified by the profile parameter DIR_CT_RUN
3 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory with
SAPCAR [page 56]
4 Stop the instance being updated
NOTE
If the system is running in a HA environment make sure that the HA software does not
restart the instance automatically during the update
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2760
5 Copy or move the extracted programs from the temporary directory to the local kernel directory
6 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries as
described in section Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
7 Restart the instance after JSPM has finished the deployment of all packages on the Central Instance
Only valid for UNIX |
Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms
On UNIX platforms you must adjust the ownership and execution permissions of the kernel binaries
after the update regardless whether you performed the update manually or by using JSPM because
both update procedures are performed with the ltsapsidgtadm user Enter the following command
sequence
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
224 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the Java system
23 Parallel Update of Dual-Stack Systems
If you perform an update of a dual-stack system (ABAP+Java) we recommend that you follow the
procedure described below The procedure has been validated to update the ABAP stack and the Java
stack of a NetWeaver system in parallel thus reducing the overall system downtime by half
Procedure
1 Before applying ABAP and Java Support Packages use the Single Support Packages option in JSPM and
select for update only the components SAP KERNEL and BC-FES-IGS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
23 Parallel Update of Dual-Stack Systems
2860 CUSTOMER 2012-08-30
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS)
runs on a dedicated host In this case JSPM does not support update of kernel binaries and
you need to update them manually Perform the update manually as described under Updating
SAP Kernel and SAP IGS in section Updating the Application Server ABAP and ABAP-Based Software
Components [page 16]
2 Import the Support Packages for the component SAP_BASIS into the ABAP stack using the ABAP
Support Package Manager (SPAM)
3 Import the remaining ABAP Support Packages with SPAM and in parallel apply the Java Support
Package Stack with JSPM
Proceed as described in Updating the Application Server ABAP and ABAP-Based Software Components [page
16] and Updating the Application Server Java and Java-Based Software Components [page 23]
24 Process Integration
241 Planning
Procedure
This section covers all the units of Process Integration that should be updated Particularly the following
units must always have the same Support Package level (the patch level can be different)
Integration Server
XI Adapter Engine
Partner Connectivity Kit
System with the Usage Type Process Integration
Software components of Integration Server
Components to Be Updated SP File Name Tool Used to Apply SP
Java stack
XI TOOLS 702 SAPXITOOLltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
ABAP stack
XI CONTENT SAP_BASIS 702 SAPBASISltSPgt_ltPLgtZIP File upload
XI CONTENT SAP_ABA 702 SAPABAltSPgt_ltPLgtZIP
SAP NetWeaver Application Server ABAP (see table Software components of Application Server ABAP [page 15])Note that update of the following software components of the ABAP system is not required SAP ABA 702 SAP BW 702 PI_BASIS 702
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 2960
J2EE Adapter Engine
If your implemented scenario includes a J2EE Adapter Engine then it must always be of the same
Support Package level as the Integration Server
Components of the J2EE Adapter Engine
Component to Be Updated SP File NameTool Used to Apply SP
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
J2SE Adapter Engine
The installation of the J2SE Adapter Engine depends on the implemented scenario
Components of the J2SE Adapter Engine
Component to Be Updated SP File Name Tool Used to Apply SP
XI CONNECTIVITY SE 702 SAPXICONSltSPgt_ltPLgtSCA ZIP tool (for example WinZip)
Partner Connectivity Kit
If your implemented scenario includes a Partner Connectivity Kit (PCK) then it must always be of the
same Support Package level as the Integration Server
Software components of Partner Connectivity Kit
Components to Be Updated SP File NameTool Used to Apply SP
XI PCK 702 SAPXIPCKltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of the Application Server Java [page 20])
System Landscape Directory (SLD)
The System Landscape Directory is required for the PI operations Although updating the SLD is not
necessarily required it is advisable to update the SLD server and the SAP Master Data Content within
it from time to time The update of the SLD includes
1 The system where the SLD is running
2 The SAP Master Data Content within this SLD
SAP GUI
See table Compatible SAP GUI Versions [page 51]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3060 CUSTOMER 2012-08-30
242 Updating Units of Process Integration
Procedure
Before you start the update perform the following steps
In the Runtime Workbench use Communication Channel Monitoring to stop all sender channels
for all adapter types on all your Adapter Engines
On the Integration Server use transaction SMQR and deregister all qRFC queues
System with the Usage Type Process Integration
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the XI instance is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system where the XI instance is running
For more information see Application Server Java and Java-Based Software Components [page 19]
System Landscape Directory (Optional)
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the SLD is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the entire Support Package Stack to the system where the SLD is running
For more information see Application Server Java and Java-Based Software Components [page 19]
J2EE Adapter Engine
Apply the Support Package Stack to the system where the Adapter Engine is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Partner Connectivity Kit
Apply the Support Package Stack to the system where the PCK is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Front End GUIs
Update the SAP GUI components if necessary
For more information see SAP GUI Family [page 51]
ABAP 700 Business System (Optional)
Apply the Support Packages for SAP NetWeaver Application Server ABAP (including SAP kernel and
the Support Package for SAP BASIS 700)
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 640 Business System (Optional)
Apply the Support Packages for SAP Web Application Server ABAP 640 (including SAP kernel and the
Support Package for SAP BASIS 640)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3160
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 620 Business System (Optional)
1 Update the SAP Kernel 620
2 Import the released Basis Support Packages for SAP Web AS 620 as well as the most recent Add-
On Support Package for APPINT 200_620 in the order described in SAP Note 439915
J2SE Adapter Engine (Optional)
NOTE
The XI Adapter Engine (J2SE) and all its adapters are provided for compatibility reasons only and
are not developed any further You have to use the XI Adapter Engine running on SAP NetWeaver
AS Java For more information see the Master Guide ndash SAP NetWeaver 70 available on SAP Service
Marketplace at httpservicesapcominstallNW70 Planning
1 Extract the SAPXICONSltSPgt_ltPLgtSCA (XI Connectivity SE 700) archive (ZIP format) to a temporary
directory
2 Save the old configuration files as described in the document Adapterpdf in directory
lttemp_directorygttech_adapterAdministrationDocumentation
3 Unpack the ZIP archive TechnicalAdapterssda to the installation directory of the XI Adapter
Engine (J2SE)
4 Restore the configuration files with restore_configuration
243 Post-Installation Steps
Procedure
Communication Channels and Queues
Restart all stopped sender channels and register all deregistered qRFC queues
XI Content
In the system with usage type PI import the XI content from the archives SAPBASISltSPgt_ltPLgtZIP
and SAPABAltSPgt_ltPLgtZIP as follows
1 Unpack the archives using a ZIP tool of your choice
2 Copy the corresponding export files (with file extension tpz) to the import directory ltINSTDIRgt
ltSAPSIDgtSYSglobalxirepository_serverimport
3 Start the Integration Builder (transaction SXMB_IFR)
4 Enter the Integration Repository by choosing Repository (Design)
5 Choose Tools Import design objects
6 Import the tpz files containing the XI content
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3260 CUSTOMER 2012-08-30
NOTE
For more information see SAP Note 836200
Role Generation on the Integration Server
On the Integration Server execute transaction SUPC (mass generation of roles) for all SAP_XI roles in
each of your clients to regenerate possibly changed roles
NOTE
Do not forget to make a user comparison for regenerated roles afterwards
Partner Connectivity Kit (Optional)
Perform the post-installation steps for PCK as described in SAP Note 746328
SAP Master Data within the SLD (Optional)
In the system where your SLD is running import the latest SLD content as described in SAP Note
669669
Receiver-Based EOIO Serialization in J2EE Adapter Engine (Optional)
The J2EE Adapter Engine can be switched to receiver-based EOIO serialization The switch can be
triggered on demand and is executed asynchronously It includes a database migration step during
which all EOIO processing in the Adapter Engine is disabled See SAP Note 973894 for details about how
to start the EOIO serialization migration
Service Metering (Optional)
Service metering gathers information about a service caller transfers it to the service provider and
counts on the service provisioning side how many times a service is called and by which service caller
Service metering is performed for the XI message protocol and the WS message protocol Service
metering is automatically enabled after applying a Support Package Stack By default only non-sensitive
data is transmitted to internal or external service providers in a compatible way
Service metering can be configured in PI in the Integration Engine on sender-side and in the Integration
Directory
Service metering can be configured in AS ABAP in transaction SOAMANAGER
Only if the service provider is allowed to receive more detailed information about the service caller set
the metering level to higher than the default
For more information see SAP Note 1239428
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3360
25 Business Intelligence
251 Planning
Procedure
Business Intelligence includes one or many of the following units that must be updated depending on
your implemented scenarios The usage types Business Intelligence (BI) and Business Intelligence Java
Components (BI-Java) must always have the same Support Package level
Business Intelligence
Software Components of Business Intelligence
Component to Be Updated SP File Name Tool Used to Apply SP
BI CONT ADDON 70x SAPK-70ltxgtltSPgtINBICONT SAINT
SAP NetWeaver Application Server ABAP (see table Software Components of Application Server ABAP [page 15])
NOTE
For information about the dependencies applying to BI Content Support Packages see SAP Note
653814 BI CONT 703 Support Packages are not part of the NetWeaver SP Stacks Updates can be
performed when applicable Alternatively BI CONT 704 Support Packages can be imported See
the BI Content release strategy in SAP Note 153967
Business Intelligence Java Components
BI Java Components
Component to Be Updated SP File NameTool Used to Apply SP
BI REPORTING AND PLANNING 702 BIREPPLANltSPgt_ltPLgtSCA JSPM
BI WEBDYNPRO ALV 702 BIWDALVltSPgt_ltPLgtSCA
BI INFORM BROADCASTING 702 BIIBCltSPgt_ltPLgtSCA
BI WEB APPLICATIONS 702 BIWEBAPPltSPgt_ltPLgtSCA
BI BASE SERVICES 702 BIBASESltSPgt_ltPLgtSCA
VISUAL COMPOSER BI KITS 702 VCKITBIltSPgt_ltPLgtSCA
Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
BI Precalculation Service
Components of the BI Precalculation Service
Component to Be Updated SP File Name Tool Used to Apply SP
BI Pre-calculation Service 700 xPreCalServerltSPgt_ltPLgtexe Installer
Search and Classification (TREX)
See table TREX Component [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3460 CUSTOMER 2012-08-30
BI Accelerator
The BI Accelerator is based on the TREX technology It is a special Linux 64-bit version of SAP NetWeaver
70 Search and Classification (TREX) which is delivered on preconfigured hardware
NOTE
You cannot use a TREX installation based on 32-bit architecture that is configured for searching
in metadata and documents for the BI Accelerator And vice versa a BI Accelerator box cannot
be used for searching in metadata and documents
If you want to use the search functionality as well as the BI Accelerator you require two separate
installations For more information see BI Accelerator [page 47]
Clients
Depending on your implemented scenarios you have to update SAP GUI Components and Business
Explorer (BI Add-OnBW Add-On)
NOTE
See SAP Note 889314 to determine when to use the BI Add-On and the BW Add-On
NOTE
As SAP GUI 640 is no longer supported BI Frontend Support Package 1800 resp patch 1801 is the
last Support Package resp patch based on SAP GUI 640 For more information see SAP Note
1231292 (Frontend Add-in Strategy 640710 GUI Version)
For more information about the new release strategy for the BI Frontend see SAP Note 1231363
(Changed Delivery Strategy for BI Frontend)
252 Preparation
Procedure
For the Support Packages of the most important Business Intelligence units so called SAPBINews
(SAPBWNews) Notes are created Read these Notes before updating Business Intelligence For SAP
NetWeaver 70 including enhancement package 2 SPS 12 these are the following
Business Intelligence ABAP SAP Note 1680996
Business Intelligence Java Components SAP Note 1726461
BI 70 Frontend Add-On for SAP GUI 710 SAP Note 1413032
BI 70 Frontend Add-On for SAP GUI 720 SAP Note 1630112
BI 70 Frontend Add-On for SAP GUI 730 SAP Note 1726739
For more information about BI Support Packages see SAP Community Network at http
scnsapcomcommunitydata-warehousingnetweaver-bw Related Resources SAP NW BW Support
Packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
2012-08-30 CUSTOMER 3560
253 Updating Units of Business Intelligence
Procedure
Business Intelligence
1 Update the SAP NetWeaver Application Server ABAP (with BI CONT 70x if necessary) with the
appropriate Support Packages
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
NOTE
When applying the component SAP BW 702 some generation errors might occur When
you start importing the BI Support Packages in transaction SPAM choose the menu path
Extras Ignore generation errors For more information see SAP Note 114134
2 Apply the Support Package Stack to the system with the usage type BI-Java
For more information see Application Server Java and Java-Based Software Components [page 19]
3 Update the BI Precalculation Service that is used in your scenario
4 Update the standalone engine Search and Classification (TREX) that is used in your scenario For more
information see Standalone Engine Search and Classification (TREX) [page 44]
NOTE
You have to update TREX to the newest version if you use search capabilities within Business
Intelligence
5 Update the BI Accelerator to the newest available version For more information see BI
Accelerator [page 47]
6 Update the SAP GUI and Business Explorer (BI Add-On BW Add-On) on all remote client hosts
that are involved in the scenario
For more information see SAP GUI Family [page 51] and Business Explorer (BI Add-On BW Add-On)
[page 51]
BI Precalculation Service
1 Log on to the host as a user with administration rights
2 Install the Support Package of the BI Precalculation Service by executing the
xPreCalServerexe file
The welcome screen of the BI Precalculation Server setup wizard appears
The setup now checks the system for the prerequisites
3 Choose the option Update for updating the BI Precalculation service to the current patch level and
then Finish
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3660 CUSTOMER 2012-08-30
26 EP Core
261 Planning
Procedure
The following installable software units must be updated
EP Core
Software Components of EP Core
Component to Be Updated SP File Name Tool Used to Apply SP
PORTAL CORE SERVICES 702 EPBCltSPgt_ltPLgtSCA JSPM
PORTAL FRAMEWORK 702 EPBC2ltSPgt_ltPLgtSCA
PORTAL 702 EPPSERVltSPgt_ltPLgtSCA
PORTAL WEB DYNPRO 702 EPWDCltSPgt_ltPLgtSCA
UWL COLL PROCESS ENGINE 702 UWLJWFltSPgt_ltPLgtSCA
CAF EU 702 SAPEUltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
262 Preparation
Procedure
Backing Up the Portal Runtime Configuration
If you have made changes to the standard Portal Runtime configuration you have to make a backup
of the configuration before the update process For more information see SAP Note 1064468
263 Updating EP Core
Procedure
Apply the Support Package Stack to a system with usage type EP Core
For more information see Application Server Java and Java-Based Software Components [page 19]
264 Post-Installation Steps for EP Core
Procedure
Restoring the Portal Runtime Configuration
To make your changes to the standard Portal Runtime Configuration effective you have to restore
the backup of the configuration done before the update process For more information see SAP Note
1064468
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
26 EP Core
2012-08-30 CUSTOMER 3760
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
12 Types of Support Packages
The following table explains the terms used in the correction process as part of the software maintenance
process for SAP NetWeaver
Correction Process Description
Standard correction process
Support Package Stack Description
A Support Package Stack is a set of Support Packages and patches for the respective product version that must be used in the given combination
Version numbersSupport Package Stacks have a release number and a stack number for example SAP NetWeaver 70 Support Package Stack 05
DeliveryThere is no dedicated delivery format for the Support Package Stacks The included Support Package files have their delivery formats and must be applied using the tools as described below
Kernel Patches Version numbers
SAP Kernel patches have a release number and a patch number The patch number is increased with each correction
DeliverySAP Kernel patches are delivered as SAR files They are installed by extracting the SAR files to the kernel directory using SAPCAR Separate SAR files are shipped for the different kernel types depending on UNICODENON-UNICODE and the platform
ABAP Support Packages Description
ABAP Support Packages contain corrections and adjustments for the ABAP-based Software Components of the SAP system
DependenciesIn contrast to Java Support Packages ABAP Support Packages are non-cumulative Therefore ABAP Support Packages must be installed in the correct sequence one after the other You cannot skip any intermediate Support Packages
DeliveryABAP Support Packages are delivered as SAR files They are installed using the Support Package Manager (SPAM)
Java Support Packages Description
Java Support Packages contain corrections for the Java-based Software Components of the SAP system
DependenciesJava Support Packages always contain a full delivery of the Software Components Therefore you only need to apply the latest Support Package to update the software If there are dependencies with other Java Support Packages these are specified in an SAP Note
DeliveryJava Support Packages are delivered as Software Component Archives (SCAs) They are applied using the Java Support Package Manager (JSPM)
1 Overview
12 Types of Support Packages
2012-08-30 CUSTOMER 1160
Correction Process Description
Emergency correction process
SAP Note Correction (ABAP) Description
SAP Note corrections contain single ABAP fixes Delivery
SAP Note corrections are delivered with SAP Notes If required you apply them using the SAP Note Assistant
Java Support Package Patch Description
A Java Support Package patch contains corrections for the Java Software Components Java Support Package patches are created and released on demand A Java Support Package patch corresponds to an SAP Note that describes the same correction
DependenciesA Java Support Package patch always contains a full package of the corresponding Software Component and is applied using JSPM
13 Downloading Support Package Stacks
The Maintenance Optimizer in SAP Solution Manager is the only source from which you can receive
maintenance updates for SAP NetWeaver 70 and higher releases as well as for all applications running
on top of SAP NetWeaver The Maintenance Optimizer supports you in selecting and downloading all
required maintenance files In addition the Maintenance Optimizer generates a stack XML file and
saves it to the EPS inbox directory of SAP Solution Manager
Prerequisites
You have configured the Maintenance Optimizer in SAP Solution Manager as described on SAP Help
Portal at httphelpsapcom SAP Solutions SAP Solution Manager SAP Solution Manager ltReleasegt
ltLanguagegt Change Management Maintenance Optimizer Planning and Monitoring Product Maintenance and
also in section Automatically Calculating Product Maintenance Files
Procedure
To download a Support Package Stack proceed as follows
1 Start SAP Solution Manager using the transaction solution_manager To start the Maintenance
Optimizer choose Operations Change Management Maintenance Optimizer
2 In the Maintenance Optimizer choose the solution for which you want to download SP Stack files
3 Choose Create New Maintenance Transaction
4 Select the product version for which you want to apply a Support Package Stack
The Maintenance Optimizer displays all the systems assigned to the selected product version
5 Select the checkbox for the system that you want to update and choose Continue
6 On the subsequent screen select the Maintenance option and then choose Find Download Files
1 Overview
13 Downloading Support Package Stacks
1260 CUSTOMER 2012-08-30
7 Select the target SP Stack level and the relevant usage types according to the IT scenario to be
updated
8 Choose Find Download Files for the Stack Version
The Maintenance Optimizer displays the product maintenance files in three successive lists
9 Select the required files from the displayed lists
The first list shows all files that are dependent on the type of your operating system and
database
Select the files that correspond to the combination of your operating system and database and
the database-independent files
If your system is distributed on several hosts make sure to select all operating systems used
by the NetWeaver instances You can see all the kernels detected on your system on the Deployed
Components tab page on JSPM user interface (under the SAP KERNEL node) All detected kernels
must be updated to the same version
You get to the second list by choosing Continue This list displays all Support Package files that
are not assigned to the selected Support Package Stack Before you continue with the selection
you must check whether the Support Package files listed here are suitable for your product
maintenance procedure
You get to the third list by choosing Continue The list displays all product maintenance files
that are part of the selected Support Package Stack
Ensure that all files that are assigned to the Support Package Stack are selected here Files that
are not selected will not be included later in the download
10 Choose Continue Use the Download Basket to download the maintenance files
11 Choose Continue once the files have been put in your Download Basket and then Confirm Files in
Download Basket
A dialog window appears and displays all files
12 Confirm the download for all files
13 Open your Download Manager and download the files
NOTE
The stack XML file is generated by the Maintenance Optimizer and automatically saved to
the EPS inbox directory of SAP Solution Manager
More Information
For more information about the Maintenance Optimizer see SAP Support Portal at http
servicesapcomsolman-mopz
1 Overview
13 Downloading Support Package Stacks
2012-08-30 CUSTOMER 1360
This page is left blank for documents that are printed on both sides
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
This chapter describes how to apply Support Packages to installable software units of SAP NetWeaver
70 including enhancement package 2 SAP NetWeaver distinguishes three types of installable software
units
Systems with one or multiple usage types
Standalone engines
Clients
A scenario implementation usually involves several installed software units
RECOMMENDATION
We strongly recommend that you always update all software units belonging to one scenario
together in order to retain a consistent system state Due to the fact that some installable software
units can be commonly shared in different scenarios you must consequently update all scenarios
using the common software units at the same time
21 Application Server ABAP and ABAP-Based Software Components
211 Planning
Procedure
The following components belong to the usage type SAP NetWeaver Application Server ABAP
Software Components of Application Server ABAP
Component to Be Updated SP File Name Tool Used to Apply SP
SAP KERNEL 720 32-64-BIT Non-UNICODEUNICODE SAPEXESAR
SAPEXEDBSAR
JSPMmanually
SAP IGS 700 igsexesar
SAP ABA 702 SAPKA702ltSPgt SPAMSAINT
SAP BASIS 702 SAPKB702ltSPgt
SAP BW 702 SAPKW702ltSPgt
PI_BASIS 702 SAPK-702ltSPgtINPIBASIS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
2012-08-30 CUSTOMER 1560
NOTE
This table contains only software components that belong to the usage type AS ABAP Software
components of other usage types and application units are listed in the corresponding sections
NOTE
SAP delivers intermediate Support Packages for the component SAP BW 702 between two
subsequent SP levels besides the Support Packages delivered along with the Support Package
Stacks Therefore the highest SP level of SAP BW 702 does not necessarily match the target SP
Stack level
CAUTION
When applying a Support Package Stack to a dual-stack system (ABAP+Java) the Java Support
Package Manager (JSPM) will necessarily restart the system several times to make the changes
effective The ABAP part will only be restarted when JSPM is updating the SAP kernel and IGS
212 Preparation
Procedure
Read SAP Note 822379 and all related SAP Notes that the first one refers to
213 Updating the Application Server ABAP and ABAP-Based Software Components
Procedure
Applying Support Packages to SAP NetWeaver Application Server ABAP and ABAP-Based Components
You can update the SAP NetWeaver Application Server ABAP and all ABAP-based software components
running on it using the Support Package Manager (transaction SPAM)
NOTE
If a particular Support Package Stack requires the installation or upgrade of some add-on
components you must use the ABAP Add-on Installation Tool (transaction SAINT) instead of the
Support Package Manager In this case SAINT is able to import both the add-on components and
the related Support Packages of ordinary SAP components
Proceed as follows
1 Log on to the SAP NetWeaver AS system with client 000
2 Start the Support Package Manager by calling transaction SPAM or
start the Add-On Installation Tool by calling transaction SAINT
3 Load the relevant Support Packages or add-on installation packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
1660 CUSTOMER 2012-08-30
4 Define an import queue
5 Perform the import of the defined queue
NOTE
If you have modified SAP objects in your system and these objects are included in the Support
Packages you must perform modification adjustment during the import using the
transactions SPDD (for ABAP Dictionary objects) and SPAU (for Repository objects)
To import the queue you use the standard scenario You can choose between the conventional
import mode and downtime-minimized import mode
Conventional Import Mode
This option comprises the following steps
1 Update the SAP kernel and SAP IGS as described in section Updating SAP Kernel and SAP IGS below
Start the system after the kernel update
2 Import the ABAP Support Packages with the Support Package Manager (SPAM)
Import Mode Downtime-Minimized
This option can be used to reduce system downtime during the update It comprises the following
steps
1 In transaction SPAM enable the downtime-minimized import mode by choosing Extras
Settings then on the Import queue tab page choose Standard and activate the option Import Mode
Downtime-Minimized
2 Import the ABAP Support Packages into the system in an inactive state in the downtime-minimized
mode during system uptime
3 Update the SAP kernel and SAP IGS as described in section Updating SAP Kernel and SAP IGS below
Start the system after the kernel update
4 Complete the ABAP Support Packages import
CAUTION
During this step the system cannot carry out any business transactions (business downtime)
NOTE
In rare cases due to the dependencies of some Support Packages on a particular kernel patch level
the downtime-minimized update does not work In such cases the Support Package Manager
informs you that you must update the SAP kernel before importing ABAP Support Packages You
must proceed with the conventional import procedure
Updating SAP Kernel and SAP IGS
In general the SAP kernel and IGS binaries are located in the global kernel directory DIR_CT_RUN on
the host indicated by the profile parameter SAPGLOBALHOST Once the files in this directory have been
updated to a new patch level a system restart distributes them by means of the program SAPCPE to the
local directories DIR_EXECUTABLE on the hosts where the instances of the SAP system are running
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
2012-08-30 CUSTOMER 1760
CAUTION
The automatic distribution by means of SAPCPE depends on the settings of the profile parameters
DIR_CT_RUN for the global kernel directory and DIR_EXECUTABLE for the local directory of the
executables Before you continue check the instance profiles for the settings of these parameters
in systems that are not installed using SAPinst (for example systems upgraded from older releases
copied or migrated systems)
CAUTION
If your system is a dual-stack system (ABAP+Java) and the ABAP stack has a non-Unicode kernel
be aware that the SCS instance has a Unicode kernel You have to update both kernels (together
with SAP IGS) prior to updating the ABAP and Java Support Package stacks This ensures
compatibility and reduces system downtime
RECOMMENDATION
If you perform an update of a dual-stack system (ABAP+Java) we recommend that prior to
applying ABAP and Java Support Package stacks you use the Single Support Packages option in JSPM
and select for update only the components SAP KERNEL and BC-FES-IGS
For more information about updating a dual-stack system see Parallel Update of Dual-Stack Systems
[page 28]
If you perform an update of an ABAP system the following procedure applies for updating the SAP
kernel and IGS manually
1 Log on as user ltsapsidgtadm to the instance host to be updated
2 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory using
SAPCAR [page 56]
3 Stop the ABAP system that you want to update
NOTE
If the system is running in a high availability (HA) environment make sure that the HA
software does not restart the system automatically during the update
4 Back up the kernel directory ltkrnl_directorygt
5 Copy or move the extracted programs from the temporary directory to the SAP kernel directory
6 Only valid for UNIX |
Execute the following command sequence on UNIX platforms
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
1860 CUSTOMER 2012-08-30
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
7 Restart the SAP system
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS) runs
on a dedicated host You need to perform the kernel update for the ASCS instance manually but
excluding the IGS update because the IGS is not required in an ASCS instance
In rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of such instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances manually Proceed as described
in section Manually Updating Instances with Kernel Directory Located on Separate Hosts below in this document
214 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the ABAP system
22 Application Server Java and Java-Based Software Components
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system which includes
JSPM itself
SAP Kernel and SAP IGS
All Java-based usage types installed in the system
Software Deployment Manager (SDM) - the deployment service of the system
RECOMMENDATION
We strongly recommend that you apply the target Support Package Stack to your system as a
whole This ensures consistency on both the system and the application levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 1960
221 Planning
Procedure
Java Support Package files (SCAs) contain all software objects of the corresponding software
components Thus it is sufficient to apply the Java Support Package files of the intended Support Package
Stack directly to the Java system to be updated It is not necessary to apply the Support Package Stacks
between the start SP Stack level and the target SP Stack level successively
CAUTION
When applying a Support Package Stack to a Java system the Java Support Package Manager (JSPM)
will necessarily restart the system several times to make the changes effective With a dual-stack
system (ABAP+Java) the ABAP part will only be restarted when JSPM is updating the SAP kernel
and IGS
The following components belong to the usage type SAP NetWeaver Application Server Java (AS Java)
Software Components of Application Server Java
Component to Be Updated SP File Name Tool Used to Apply SP
SAP Kernel 720 32-64-BIT UNICODE SAPEXESAR
SAPEXEDBSAR
JSPM
SAP IGS 700 igsexesar
BI META MODEL REPOSITORY 702 BIMMRltSPgt_ltPLgtSCA
J2EE ENGINE CORE TOOLS 702 CORETOOLSltSPgt_ltPLgtSCA
J2EE ENGINE BASE TABLES 702 BASETABLESltSPgt_ltPLgtSCA
BI UDI 702 BIUDIltSPgt_ltPLgtSCA
DI BUILD TOOL 702 SAPBUILDTltSPgt_ltPLgtSCA
SAP CAF 702 CAFltSPgt_ltPLgtSCA
SAP IKS 702 KMKWJIKSltSPgt_ltPLgtSCA
JAVA LOG VIEWER 702 JLOGVIEWltSPgt_ltPLgtSCA
SAP J2EE ENGINE CORE 702 SAPJEECORltSPgt_ltPLgtSCA
SAP JAVA TECH SERVICES 702 SAPJTECHSltSPgt_ltPLgtSCA
SAP TECH S OFFLINE 702 SAPJTECHFltSPgt_ltPLgtSCA
SAP J2EE ENGINE 702 SAPJEEltSPgt_ltPLgtSCA
JAVA SP MANAGER 702 JSPMltSPgt_ltPLgtSCA
ADOBE DOCUMENT SERVICES 702 ADSSAPltSPgt_ltPLgtSCA
UME ADMINISTRATION 702 UMEADMINltSPgt_ltPLgtSCA
LIFECYCLE MGMT TOOLS 702 LMTOOLSltSPgt_ltPLgtSCA
SAP CAF-UM 702 CAFUMltSPgt_ltPLgtSCA
SAP SOFTW DELIV MANAGER 702 SDMKITltSPgt_ltPLgtJAR
SOFTWARE LIFECYCLE MANAGER 702 SWLIFECYCLltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2060 CUSTOMER 2012-08-30
NOTE
This table contains only software components that belong to the usage type AS Java Software
components of other usage types and Java application units are listed in the corresponding
sections
NOTE
As of Support Package 09 you can update your system with SAP Kernel 720 instead of SAP Kernel
701
222 Preparation for Applying a Support Package Stack
Procedure
1 Download the Support Package Stack with all usage types to be updated and the stack definition
XML file as described in Downloading Support Package Stacks [page 12]
NOTE
You can find the activated usage types in an existing Java system on the Deployed Components tab
page on the JSPM user interface
NOTE
You do not need to download the SP Stacks between the source SP Stack level and target SP
Stack level By default the target SP Stack level is the latest available SP Stack
2 Make sure the following requirements are met prior to applying the Support Package Stack
You have familiarized yourself with SAP Note 891983 before you start the Java Support Package
Manager
The system to be updated is fully functional
The Support Package Stack you want to apply and the corresponding stack definition XML
file are available in the EPS inbox directory usrsaptransEPSin By default this location
can be also referred to as ldquoJSPM inboxrdquo
The SAP NetWeaver Application Server Java (AS Java) and the database have been backed up
You have not deleted renamed or created any directories and files in the following directories
and their subdirectories usrsapltSAPSIDgtSYSexe and usrsapltSAPSIDgtSYS
profile
Otherwise JSPM cannot detect the kernel and the system profiles and cannot be started If a
backup of the kernel and the system profiles has been required it has been created in a different
directory
The ltsapsidgtadm user has Read permissions for the EPS inbox directory usrsaptransEPS
in
If your database is SAP MaxDB the overwrite mode for the log area has been activated
The database and the SDM repository have been synchronized
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2160
For more information see the online documentation for JSPM on SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70 Library
(including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library Administrators Guide
Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems AS Java
(Application Server for Java) Software Logistics Software Maintenance Java Support Package Manager
Then choose Troubleshooting JSPM Does Not Update the Versions of the Deployed Components
There is enough disk space
For more information see SAP Note 891895
Your current SAPCAR tool is able to extract the Support Packages for the SAP kernel and
other OS level binaries delivered as SAR files
RECOMMENDATION
You can download the latest version of SAPCAR from SAP Service Marketplace at
httpservicesapcompatches Entry by Application Group Additional Components
SAPCAR
Put the downloaded version in the same directory in the JSPM inbox in which the kernel
SAR files reside so that JSPM can use this version for extracting the SAR files
3 Only valid for Linux |
For RHEL 4 and SLES 9 you need to install additional operating system packages For more
information see SAP Note 1021236End of Linux |
4 Only valid for Windows |
For Windows you need to install additional operating system packages For more information see
SAP Note 684106End of Windows |
5 To prevent the Software Deployment Manager (SDM) from temporarily exceeding the available
disk space during the update process you can change the file transfer directory of SDM in a system
of SPS09 or higher using the following command sequence
Only valid for Windows |
cd ltsdm_homegt
StopServerbat
sdmbat jstartup mode=standalone
sdmbat filetransferdir dir=ltnew_dirgt
sdmbat jstartup mode=integrated
StartServerbat
End of Windows |
Only valid for IBM i5OSUNIX |
cd ltsdm_homegt
StopServersh
sdmsh jstartup mode=standalone
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2260 CUSTOMER 2012-08-30
sdmsh filetransferdir dir=ltnew_dirgt
sdmsh jstartup mode=integrated
StartServersh
End of IBM i5OSUNIX |
6 To prevent deployment errors during the update process proceed as follows
1 Log on to the Central Instance host
2 Start the ConfigTool and in the navigation area choose Cluster-data Global server configuration
Managers ServiceManager
3 In the Global properties panel set the Custom value of the EventTimeout property to 120
4 Choose Save
5 Restart the Central Instance
7 Check whether the used JDK version and the Java VM settings of the Java runtime system comply
with the requirements in SAP Note 723909 Update the JDK and adjust the settings if necessary
NOTE
An update of the used JDK version possibly changes the JVM path In this case you must
make the new path available to all Dialog Instances of the J2EE engine by implementing option
1 of SAP Note 718901
8 Make sure that the J2EE administrator password stored in the secure store for offline usage is
identical with the one stored in the User Management Engine (UME) You can change the password
in the secure store as described in SAP Note 870445
9 If you are running a high availability system on Windows you might need to prepare your system
as described in the online documentation for JSPM see section Preparing Systems That Run in High
Availability Environment
223 Updating the Application Server Java and Java-Based Components
Procedure
Applying a Support Package Stack to SAP NetWeaver Application Server Java and Java-Based Components
NOTE
The JSPM GUI might not work properly on some UNIX systems For more information and the
solution see SAP Note 1013976
1 Log on as user ltsapsidgtadm to the Central Instance host
NOTE
If your operating system is IBM i log on as user ltSIDgtADM or ltSIDgtOFR
2 Close the SAP Management Console (SAP MMC) and the SDM remote GUI client
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2360
3 For UNIX and Windows To start the JSPM navigate to the directory ltINSTDIRgtltSIDgt
ltCentral_Instance_Namegtj2eeJSPM and run the go script file
NOTE
If your system is running on IBM i to start the JSPM proceed as follows
1 To prevent JSPM from automatically starting its GUI in the file usrsapltSIDgt
ltCentral_Instance_Namegtj2eeJSPMparamjspm_configtxt change the
property dialogSDTServerConnectionSDTGuilaunch from true to false
2 On the IBM i host run the go script file using the following command
QSH CMD(usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPMgo)
3 In the mounted directory usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPM run
the StartGui script file The JSPM GUI appears
4 In the Host field enter the target IBM i host
NOTE
Depending on the system type ltCentral_Instance_Namegt has the following syntax
Standalone Java system JCltinstance_nogt
Add-On system DVEBMGSltinstance_nogt
4 Enter your SDM password to log on to the SDM
5 On the Deployment tab page select the Java Support Package Manager option and update the software
component sapcomJSPM to the target SPS level
6 Restart the JSPM and log on with the SDM password
RECOMMENDATION
We strongly recommend that you use the Support and Enhancement Package Stack option when
applying a Support Package Stack Other options can lead to unintended consistency issues
NOTE
If you need to include the latest patches for a particular component during the update process
with the Support and Enhancement Package Stack option stop the JSPM after restart and apply SAP
Note 1080821 Then start the JSPM again
7 On the Deployment tab page select the Support and Enhancement Package Stack option and choose Next
The Support Package Stacks that are available for deployment in the global EPS inbox directory
are displayed
8 In the Target SP Stack Level dropdown box select the Support Package Stack to be applied and choose
Next
In this step JSPM performs various status validations and displays the result of each software
component included in the stack definition XML file on the subsequent screen which includes
the following possible statuses
OK Indicates that the SPS level of the corresponding software component is applicable
WARNING We recommend that you view the details about the component by choosing Show
Details
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2460 CUSTOMER 2012-08-30
This status may indicate that the corresponding software component comprises custom
modifications in an NWDI-controlled system
If your system is used for NWDI development and it is either a DEV or a CONS system
you will be informed that JSPM will not deploy the modified software components but
only transport them to the CMS transport directory JSPM will deploy only the software
components that are not modified
If your system is not used for NWDI development or if your system is used for NWDI
development and it is either a TEST or a PROD system you will be informed that JSPM
has found newer versions of modified software components and will automatically replace
the original versions with the newer versions JSPM will deploy all software components
that are not modified together with the replaced versions of the modified software
components
CAUTION
You may get a warning telling you that there are patches installed in your system
containing fixes which might not be included in the target SP Stack This is possible if
you have applied patches of the start SP Stack level that were delivered later than the
target SP Stack delivery date In order not to lose these fixes you need to download and
apply the corresponding patches of the target SP Stack level
If you are performing an update from SAP NetWeaver 70 including enhancement
package 1 SPS00 and you have not applied any patches for the software component with
status WARNING before the update then you can ignore warnings such as the following
example
The new version of the development component sapcomcomsapnetweaver
bcrfmoni is 70100200806121227180000 and is lower than the already
deployed version 70100200807090143420000
REVISE Indicates inconsistencies with the corresponding software component
The deployment cannot be performed until all problems have been resolved You can view
the problems by choosing Show Details
9 If the status of the selected SP Stack is OK or WARNING you can start the system update by choosing
Start JSPM then changes the status to SCHEDULED
If the SP Stack to be applied includes a kernel update and the current kernel is not already of the
corresponding patch level JSPM arranges the kernel update as the very first Support Package to
be applied JSPM updates the kernel binaries of all instances (including Dialog Instances and SCS
instances in a HA environment) whose kernel directories DIR_CT_RUN effectively reside on the host
indicated by the profile parameter SAPGLOBALHOST
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2560
CAUTION
Kernel binaries of instances whose kernel directories DIR_CT_RUN are not effectively linked
to the host SAPGLOBALHOST must be updated individually as described in section Manually
Updating Instances with Kernel Directory Located on Separate Hosts below
The kernel update (includes update of SAP Kernel and SAP IGS) using JSPM consists of the following
steps
1 JSPM stops the Central Instance automatically and prompts you to stop the remote SCS and
Dialog Instances manually
2 After you have stopped all the instances choose the Next button in the dialog box
The kernel update starts
NOTE
If the system is running in a high availability environment make sure that the HA
software does not restart the instance automatically during the update
NOTE
If kernel binaries of the SCS instance need to be updated manually (see Manually Updating
Instances with Kernel Directory Located on Separate Hosts below) you must perform this at the
time when JSPM is updating the kernel binaries of the Central Instance In any case the
SCS kernel must be up-to-date before the next restart
When the kernel update is finished a dialog box appears in which you are prompted to restart
the SCS instance manually
3 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries
before you can proceed with the next step For more information see Adjusting the Ownership and
Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
4 Choose Next in the dialog box when the SCS instance is running again
After the kernel update JSPM restarts the system for further deployment of the remaining Support
Packages in the stack
RECOMMENDATION
If you need to update the kernel binaries of any Dialog Instances manually (see Manually
Updating Instances with Kernel Directory Located on Separate Hosts below) perform the update when
JSPM is updating the remaining Support Packages in the stack in order to save time
The deployment of each Support Package can end with one of the following statuses
DEPLOYED
The Support Package has been successfully deployed
DEPLOYED WITH WARNING
The Support Package has been deployed but it possibly may not work properly with other
deployed components
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2660 CUSTOMER 2012-08-30
You can view the details by choosing Show Details or examining the log files You can also view
the details about the component by choosing the Deployed Components tab page
ERROR
An error has occurred during the deployment You can view the details by choosing Show
Details or examining the log files
You must correct the error to be able to continue with the SP Stack update
You can proceed as described for a deployment that finished with status DEPLOYED WITH
WARNING
If the error correction does not change the contents in the JSPM inbox you can continue
the deployment by choosing Resume
If the error correction changes the contents in the JSPM inbox you can choose New
Deployment to redeploy the SP Stack
NOT DEPLOYED
JSPM has not attempted to deploy the software component for certain reasons
If your system is not used for NWDI development you can proceed as described for a
deployment that finished with status ERROR
If your system is used for NWDI development and it is either a DEV or a CONS system
the status of the modified software components is always NOT DEPLOYED JSPM has
transported the software components of the Support Package Stack both modified and
not modified to the CMS transport directory The deployment of the modified software
components is handled by NWDI
Manually Updating Instances with Kernel Directory Located on Separate Hosts
JSPM performs kernel update for all instances (including Dialog Instances and SCS instances in a HA
environment) whose kernel directories DIR_CT_RUN effectively reside on the host indicated by the profile
parameter SAPGLOBALHOST (by using folder sharing on Windows or file system mounting on UNIX) In
rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of those sort of instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances individually
To update the kernel of an instance manually proceed as follows
1 Log on as user ltsapsidgtadm to the host of the instance to be updated
2 Back up the kernel directory which is specified by the profile parameter DIR_CT_RUN
3 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory with
SAPCAR [page 56]
4 Stop the instance being updated
NOTE
If the system is running in a HA environment make sure that the HA software does not
restart the instance automatically during the update
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2760
5 Copy or move the extracted programs from the temporary directory to the local kernel directory
6 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries as
described in section Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
7 Restart the instance after JSPM has finished the deployment of all packages on the Central Instance
Only valid for UNIX |
Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms
On UNIX platforms you must adjust the ownership and execution permissions of the kernel binaries
after the update regardless whether you performed the update manually or by using JSPM because
both update procedures are performed with the ltsapsidgtadm user Enter the following command
sequence
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
224 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the Java system
23 Parallel Update of Dual-Stack Systems
If you perform an update of a dual-stack system (ABAP+Java) we recommend that you follow the
procedure described below The procedure has been validated to update the ABAP stack and the Java
stack of a NetWeaver system in parallel thus reducing the overall system downtime by half
Procedure
1 Before applying ABAP and Java Support Packages use the Single Support Packages option in JSPM and
select for update only the components SAP KERNEL and BC-FES-IGS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
23 Parallel Update of Dual-Stack Systems
2860 CUSTOMER 2012-08-30
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS)
runs on a dedicated host In this case JSPM does not support update of kernel binaries and
you need to update them manually Perform the update manually as described under Updating
SAP Kernel and SAP IGS in section Updating the Application Server ABAP and ABAP-Based Software
Components [page 16]
2 Import the Support Packages for the component SAP_BASIS into the ABAP stack using the ABAP
Support Package Manager (SPAM)
3 Import the remaining ABAP Support Packages with SPAM and in parallel apply the Java Support
Package Stack with JSPM
Proceed as described in Updating the Application Server ABAP and ABAP-Based Software Components [page
16] and Updating the Application Server Java and Java-Based Software Components [page 23]
24 Process Integration
241 Planning
Procedure
This section covers all the units of Process Integration that should be updated Particularly the following
units must always have the same Support Package level (the patch level can be different)
Integration Server
XI Adapter Engine
Partner Connectivity Kit
System with the Usage Type Process Integration
Software components of Integration Server
Components to Be Updated SP File Name Tool Used to Apply SP
Java stack
XI TOOLS 702 SAPXITOOLltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
ABAP stack
XI CONTENT SAP_BASIS 702 SAPBASISltSPgt_ltPLgtZIP File upload
XI CONTENT SAP_ABA 702 SAPABAltSPgt_ltPLgtZIP
SAP NetWeaver Application Server ABAP (see table Software components of Application Server ABAP [page 15])Note that update of the following software components of the ABAP system is not required SAP ABA 702 SAP BW 702 PI_BASIS 702
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 2960
J2EE Adapter Engine
If your implemented scenario includes a J2EE Adapter Engine then it must always be of the same
Support Package level as the Integration Server
Components of the J2EE Adapter Engine
Component to Be Updated SP File NameTool Used to Apply SP
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
J2SE Adapter Engine
The installation of the J2SE Adapter Engine depends on the implemented scenario
Components of the J2SE Adapter Engine
Component to Be Updated SP File Name Tool Used to Apply SP
XI CONNECTIVITY SE 702 SAPXICONSltSPgt_ltPLgtSCA ZIP tool (for example WinZip)
Partner Connectivity Kit
If your implemented scenario includes a Partner Connectivity Kit (PCK) then it must always be of the
same Support Package level as the Integration Server
Software components of Partner Connectivity Kit
Components to Be Updated SP File NameTool Used to Apply SP
XI PCK 702 SAPXIPCKltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of the Application Server Java [page 20])
System Landscape Directory (SLD)
The System Landscape Directory is required for the PI operations Although updating the SLD is not
necessarily required it is advisable to update the SLD server and the SAP Master Data Content within
it from time to time The update of the SLD includes
1 The system where the SLD is running
2 The SAP Master Data Content within this SLD
SAP GUI
See table Compatible SAP GUI Versions [page 51]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3060 CUSTOMER 2012-08-30
242 Updating Units of Process Integration
Procedure
Before you start the update perform the following steps
In the Runtime Workbench use Communication Channel Monitoring to stop all sender channels
for all adapter types on all your Adapter Engines
On the Integration Server use transaction SMQR and deregister all qRFC queues
System with the Usage Type Process Integration
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the XI instance is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system where the XI instance is running
For more information see Application Server Java and Java-Based Software Components [page 19]
System Landscape Directory (Optional)
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the SLD is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the entire Support Package Stack to the system where the SLD is running
For more information see Application Server Java and Java-Based Software Components [page 19]
J2EE Adapter Engine
Apply the Support Package Stack to the system where the Adapter Engine is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Partner Connectivity Kit
Apply the Support Package Stack to the system where the PCK is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Front End GUIs
Update the SAP GUI components if necessary
For more information see SAP GUI Family [page 51]
ABAP 700 Business System (Optional)
Apply the Support Packages for SAP NetWeaver Application Server ABAP (including SAP kernel and
the Support Package for SAP BASIS 700)
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 640 Business System (Optional)
Apply the Support Packages for SAP Web Application Server ABAP 640 (including SAP kernel and the
Support Package for SAP BASIS 640)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3160
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 620 Business System (Optional)
1 Update the SAP Kernel 620
2 Import the released Basis Support Packages for SAP Web AS 620 as well as the most recent Add-
On Support Package for APPINT 200_620 in the order described in SAP Note 439915
J2SE Adapter Engine (Optional)
NOTE
The XI Adapter Engine (J2SE) and all its adapters are provided for compatibility reasons only and
are not developed any further You have to use the XI Adapter Engine running on SAP NetWeaver
AS Java For more information see the Master Guide ndash SAP NetWeaver 70 available on SAP Service
Marketplace at httpservicesapcominstallNW70 Planning
1 Extract the SAPXICONSltSPgt_ltPLgtSCA (XI Connectivity SE 700) archive (ZIP format) to a temporary
directory
2 Save the old configuration files as described in the document Adapterpdf in directory
lttemp_directorygttech_adapterAdministrationDocumentation
3 Unpack the ZIP archive TechnicalAdapterssda to the installation directory of the XI Adapter
Engine (J2SE)
4 Restore the configuration files with restore_configuration
243 Post-Installation Steps
Procedure
Communication Channels and Queues
Restart all stopped sender channels and register all deregistered qRFC queues
XI Content
In the system with usage type PI import the XI content from the archives SAPBASISltSPgt_ltPLgtZIP
and SAPABAltSPgt_ltPLgtZIP as follows
1 Unpack the archives using a ZIP tool of your choice
2 Copy the corresponding export files (with file extension tpz) to the import directory ltINSTDIRgt
ltSAPSIDgtSYSglobalxirepository_serverimport
3 Start the Integration Builder (transaction SXMB_IFR)
4 Enter the Integration Repository by choosing Repository (Design)
5 Choose Tools Import design objects
6 Import the tpz files containing the XI content
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3260 CUSTOMER 2012-08-30
NOTE
For more information see SAP Note 836200
Role Generation on the Integration Server
On the Integration Server execute transaction SUPC (mass generation of roles) for all SAP_XI roles in
each of your clients to regenerate possibly changed roles
NOTE
Do not forget to make a user comparison for regenerated roles afterwards
Partner Connectivity Kit (Optional)
Perform the post-installation steps for PCK as described in SAP Note 746328
SAP Master Data within the SLD (Optional)
In the system where your SLD is running import the latest SLD content as described in SAP Note
669669
Receiver-Based EOIO Serialization in J2EE Adapter Engine (Optional)
The J2EE Adapter Engine can be switched to receiver-based EOIO serialization The switch can be
triggered on demand and is executed asynchronously It includes a database migration step during
which all EOIO processing in the Adapter Engine is disabled See SAP Note 973894 for details about how
to start the EOIO serialization migration
Service Metering (Optional)
Service metering gathers information about a service caller transfers it to the service provider and
counts on the service provisioning side how many times a service is called and by which service caller
Service metering is performed for the XI message protocol and the WS message protocol Service
metering is automatically enabled after applying a Support Package Stack By default only non-sensitive
data is transmitted to internal or external service providers in a compatible way
Service metering can be configured in PI in the Integration Engine on sender-side and in the Integration
Directory
Service metering can be configured in AS ABAP in transaction SOAMANAGER
Only if the service provider is allowed to receive more detailed information about the service caller set
the metering level to higher than the default
For more information see SAP Note 1239428
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3360
25 Business Intelligence
251 Planning
Procedure
Business Intelligence includes one or many of the following units that must be updated depending on
your implemented scenarios The usage types Business Intelligence (BI) and Business Intelligence Java
Components (BI-Java) must always have the same Support Package level
Business Intelligence
Software Components of Business Intelligence
Component to Be Updated SP File Name Tool Used to Apply SP
BI CONT ADDON 70x SAPK-70ltxgtltSPgtINBICONT SAINT
SAP NetWeaver Application Server ABAP (see table Software Components of Application Server ABAP [page 15])
NOTE
For information about the dependencies applying to BI Content Support Packages see SAP Note
653814 BI CONT 703 Support Packages are not part of the NetWeaver SP Stacks Updates can be
performed when applicable Alternatively BI CONT 704 Support Packages can be imported See
the BI Content release strategy in SAP Note 153967
Business Intelligence Java Components
BI Java Components
Component to Be Updated SP File NameTool Used to Apply SP
BI REPORTING AND PLANNING 702 BIREPPLANltSPgt_ltPLgtSCA JSPM
BI WEBDYNPRO ALV 702 BIWDALVltSPgt_ltPLgtSCA
BI INFORM BROADCASTING 702 BIIBCltSPgt_ltPLgtSCA
BI WEB APPLICATIONS 702 BIWEBAPPltSPgt_ltPLgtSCA
BI BASE SERVICES 702 BIBASESltSPgt_ltPLgtSCA
VISUAL COMPOSER BI KITS 702 VCKITBIltSPgt_ltPLgtSCA
Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
BI Precalculation Service
Components of the BI Precalculation Service
Component to Be Updated SP File Name Tool Used to Apply SP
BI Pre-calculation Service 700 xPreCalServerltSPgt_ltPLgtexe Installer
Search and Classification (TREX)
See table TREX Component [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3460 CUSTOMER 2012-08-30
BI Accelerator
The BI Accelerator is based on the TREX technology It is a special Linux 64-bit version of SAP NetWeaver
70 Search and Classification (TREX) which is delivered on preconfigured hardware
NOTE
You cannot use a TREX installation based on 32-bit architecture that is configured for searching
in metadata and documents for the BI Accelerator And vice versa a BI Accelerator box cannot
be used for searching in metadata and documents
If you want to use the search functionality as well as the BI Accelerator you require two separate
installations For more information see BI Accelerator [page 47]
Clients
Depending on your implemented scenarios you have to update SAP GUI Components and Business
Explorer (BI Add-OnBW Add-On)
NOTE
See SAP Note 889314 to determine when to use the BI Add-On and the BW Add-On
NOTE
As SAP GUI 640 is no longer supported BI Frontend Support Package 1800 resp patch 1801 is the
last Support Package resp patch based on SAP GUI 640 For more information see SAP Note
1231292 (Frontend Add-in Strategy 640710 GUI Version)
For more information about the new release strategy for the BI Frontend see SAP Note 1231363
(Changed Delivery Strategy for BI Frontend)
252 Preparation
Procedure
For the Support Packages of the most important Business Intelligence units so called SAPBINews
(SAPBWNews) Notes are created Read these Notes before updating Business Intelligence For SAP
NetWeaver 70 including enhancement package 2 SPS 12 these are the following
Business Intelligence ABAP SAP Note 1680996
Business Intelligence Java Components SAP Note 1726461
BI 70 Frontend Add-On for SAP GUI 710 SAP Note 1413032
BI 70 Frontend Add-On for SAP GUI 720 SAP Note 1630112
BI 70 Frontend Add-On for SAP GUI 730 SAP Note 1726739
For more information about BI Support Packages see SAP Community Network at http
scnsapcomcommunitydata-warehousingnetweaver-bw Related Resources SAP NW BW Support
Packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
2012-08-30 CUSTOMER 3560
253 Updating Units of Business Intelligence
Procedure
Business Intelligence
1 Update the SAP NetWeaver Application Server ABAP (with BI CONT 70x if necessary) with the
appropriate Support Packages
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
NOTE
When applying the component SAP BW 702 some generation errors might occur When
you start importing the BI Support Packages in transaction SPAM choose the menu path
Extras Ignore generation errors For more information see SAP Note 114134
2 Apply the Support Package Stack to the system with the usage type BI-Java
For more information see Application Server Java and Java-Based Software Components [page 19]
3 Update the BI Precalculation Service that is used in your scenario
4 Update the standalone engine Search and Classification (TREX) that is used in your scenario For more
information see Standalone Engine Search and Classification (TREX) [page 44]
NOTE
You have to update TREX to the newest version if you use search capabilities within Business
Intelligence
5 Update the BI Accelerator to the newest available version For more information see BI
Accelerator [page 47]
6 Update the SAP GUI and Business Explorer (BI Add-On BW Add-On) on all remote client hosts
that are involved in the scenario
For more information see SAP GUI Family [page 51] and Business Explorer (BI Add-On BW Add-On)
[page 51]
BI Precalculation Service
1 Log on to the host as a user with administration rights
2 Install the Support Package of the BI Precalculation Service by executing the
xPreCalServerexe file
The welcome screen of the BI Precalculation Server setup wizard appears
The setup now checks the system for the prerequisites
3 Choose the option Update for updating the BI Precalculation service to the current patch level and
then Finish
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3660 CUSTOMER 2012-08-30
26 EP Core
261 Planning
Procedure
The following installable software units must be updated
EP Core
Software Components of EP Core
Component to Be Updated SP File Name Tool Used to Apply SP
PORTAL CORE SERVICES 702 EPBCltSPgt_ltPLgtSCA JSPM
PORTAL FRAMEWORK 702 EPBC2ltSPgt_ltPLgtSCA
PORTAL 702 EPPSERVltSPgt_ltPLgtSCA
PORTAL WEB DYNPRO 702 EPWDCltSPgt_ltPLgtSCA
UWL COLL PROCESS ENGINE 702 UWLJWFltSPgt_ltPLgtSCA
CAF EU 702 SAPEUltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
262 Preparation
Procedure
Backing Up the Portal Runtime Configuration
If you have made changes to the standard Portal Runtime configuration you have to make a backup
of the configuration before the update process For more information see SAP Note 1064468
263 Updating EP Core
Procedure
Apply the Support Package Stack to a system with usage type EP Core
For more information see Application Server Java and Java-Based Software Components [page 19]
264 Post-Installation Steps for EP Core
Procedure
Restoring the Portal Runtime Configuration
To make your changes to the standard Portal Runtime Configuration effective you have to restore
the backup of the configuration done before the update process For more information see SAP Note
1064468
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
26 EP Core
2012-08-30 CUSTOMER 3760
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
Correction Process Description
Emergency correction process
SAP Note Correction (ABAP) Description
SAP Note corrections contain single ABAP fixes Delivery
SAP Note corrections are delivered with SAP Notes If required you apply them using the SAP Note Assistant
Java Support Package Patch Description
A Java Support Package patch contains corrections for the Java Software Components Java Support Package patches are created and released on demand A Java Support Package patch corresponds to an SAP Note that describes the same correction
DependenciesA Java Support Package patch always contains a full package of the corresponding Software Component and is applied using JSPM
13 Downloading Support Package Stacks
The Maintenance Optimizer in SAP Solution Manager is the only source from which you can receive
maintenance updates for SAP NetWeaver 70 and higher releases as well as for all applications running
on top of SAP NetWeaver The Maintenance Optimizer supports you in selecting and downloading all
required maintenance files In addition the Maintenance Optimizer generates a stack XML file and
saves it to the EPS inbox directory of SAP Solution Manager
Prerequisites
You have configured the Maintenance Optimizer in SAP Solution Manager as described on SAP Help
Portal at httphelpsapcom SAP Solutions SAP Solution Manager SAP Solution Manager ltReleasegt
ltLanguagegt Change Management Maintenance Optimizer Planning and Monitoring Product Maintenance and
also in section Automatically Calculating Product Maintenance Files
Procedure
To download a Support Package Stack proceed as follows
1 Start SAP Solution Manager using the transaction solution_manager To start the Maintenance
Optimizer choose Operations Change Management Maintenance Optimizer
2 In the Maintenance Optimizer choose the solution for which you want to download SP Stack files
3 Choose Create New Maintenance Transaction
4 Select the product version for which you want to apply a Support Package Stack
The Maintenance Optimizer displays all the systems assigned to the selected product version
5 Select the checkbox for the system that you want to update and choose Continue
6 On the subsequent screen select the Maintenance option and then choose Find Download Files
1 Overview
13 Downloading Support Package Stacks
1260 CUSTOMER 2012-08-30
7 Select the target SP Stack level and the relevant usage types according to the IT scenario to be
updated
8 Choose Find Download Files for the Stack Version
The Maintenance Optimizer displays the product maintenance files in three successive lists
9 Select the required files from the displayed lists
The first list shows all files that are dependent on the type of your operating system and
database
Select the files that correspond to the combination of your operating system and database and
the database-independent files
If your system is distributed on several hosts make sure to select all operating systems used
by the NetWeaver instances You can see all the kernels detected on your system on the Deployed
Components tab page on JSPM user interface (under the SAP KERNEL node) All detected kernels
must be updated to the same version
You get to the second list by choosing Continue This list displays all Support Package files that
are not assigned to the selected Support Package Stack Before you continue with the selection
you must check whether the Support Package files listed here are suitable for your product
maintenance procedure
You get to the third list by choosing Continue The list displays all product maintenance files
that are part of the selected Support Package Stack
Ensure that all files that are assigned to the Support Package Stack are selected here Files that
are not selected will not be included later in the download
10 Choose Continue Use the Download Basket to download the maintenance files
11 Choose Continue once the files have been put in your Download Basket and then Confirm Files in
Download Basket
A dialog window appears and displays all files
12 Confirm the download for all files
13 Open your Download Manager and download the files
NOTE
The stack XML file is generated by the Maintenance Optimizer and automatically saved to
the EPS inbox directory of SAP Solution Manager
More Information
For more information about the Maintenance Optimizer see SAP Support Portal at http
servicesapcomsolman-mopz
1 Overview
13 Downloading Support Package Stacks
2012-08-30 CUSTOMER 1360
This page is left blank for documents that are printed on both sides
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
This chapter describes how to apply Support Packages to installable software units of SAP NetWeaver
70 including enhancement package 2 SAP NetWeaver distinguishes three types of installable software
units
Systems with one or multiple usage types
Standalone engines
Clients
A scenario implementation usually involves several installed software units
RECOMMENDATION
We strongly recommend that you always update all software units belonging to one scenario
together in order to retain a consistent system state Due to the fact that some installable software
units can be commonly shared in different scenarios you must consequently update all scenarios
using the common software units at the same time
21 Application Server ABAP and ABAP-Based Software Components
211 Planning
Procedure
The following components belong to the usage type SAP NetWeaver Application Server ABAP
Software Components of Application Server ABAP
Component to Be Updated SP File Name Tool Used to Apply SP
SAP KERNEL 720 32-64-BIT Non-UNICODEUNICODE SAPEXESAR
SAPEXEDBSAR
JSPMmanually
SAP IGS 700 igsexesar
SAP ABA 702 SAPKA702ltSPgt SPAMSAINT
SAP BASIS 702 SAPKB702ltSPgt
SAP BW 702 SAPKW702ltSPgt
PI_BASIS 702 SAPK-702ltSPgtINPIBASIS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
2012-08-30 CUSTOMER 1560
NOTE
This table contains only software components that belong to the usage type AS ABAP Software
components of other usage types and application units are listed in the corresponding sections
NOTE
SAP delivers intermediate Support Packages for the component SAP BW 702 between two
subsequent SP levels besides the Support Packages delivered along with the Support Package
Stacks Therefore the highest SP level of SAP BW 702 does not necessarily match the target SP
Stack level
CAUTION
When applying a Support Package Stack to a dual-stack system (ABAP+Java) the Java Support
Package Manager (JSPM) will necessarily restart the system several times to make the changes
effective The ABAP part will only be restarted when JSPM is updating the SAP kernel and IGS
212 Preparation
Procedure
Read SAP Note 822379 and all related SAP Notes that the first one refers to
213 Updating the Application Server ABAP and ABAP-Based Software Components
Procedure
Applying Support Packages to SAP NetWeaver Application Server ABAP and ABAP-Based Components
You can update the SAP NetWeaver Application Server ABAP and all ABAP-based software components
running on it using the Support Package Manager (transaction SPAM)
NOTE
If a particular Support Package Stack requires the installation or upgrade of some add-on
components you must use the ABAP Add-on Installation Tool (transaction SAINT) instead of the
Support Package Manager In this case SAINT is able to import both the add-on components and
the related Support Packages of ordinary SAP components
Proceed as follows
1 Log on to the SAP NetWeaver AS system with client 000
2 Start the Support Package Manager by calling transaction SPAM or
start the Add-On Installation Tool by calling transaction SAINT
3 Load the relevant Support Packages or add-on installation packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
1660 CUSTOMER 2012-08-30
4 Define an import queue
5 Perform the import of the defined queue
NOTE
If you have modified SAP objects in your system and these objects are included in the Support
Packages you must perform modification adjustment during the import using the
transactions SPDD (for ABAP Dictionary objects) and SPAU (for Repository objects)
To import the queue you use the standard scenario You can choose between the conventional
import mode and downtime-minimized import mode
Conventional Import Mode
This option comprises the following steps
1 Update the SAP kernel and SAP IGS as described in section Updating SAP Kernel and SAP IGS below
Start the system after the kernel update
2 Import the ABAP Support Packages with the Support Package Manager (SPAM)
Import Mode Downtime-Minimized
This option can be used to reduce system downtime during the update It comprises the following
steps
1 In transaction SPAM enable the downtime-minimized import mode by choosing Extras
Settings then on the Import queue tab page choose Standard and activate the option Import Mode
Downtime-Minimized
2 Import the ABAP Support Packages into the system in an inactive state in the downtime-minimized
mode during system uptime
3 Update the SAP kernel and SAP IGS as described in section Updating SAP Kernel and SAP IGS below
Start the system after the kernel update
4 Complete the ABAP Support Packages import
CAUTION
During this step the system cannot carry out any business transactions (business downtime)
NOTE
In rare cases due to the dependencies of some Support Packages on a particular kernel patch level
the downtime-minimized update does not work In such cases the Support Package Manager
informs you that you must update the SAP kernel before importing ABAP Support Packages You
must proceed with the conventional import procedure
Updating SAP Kernel and SAP IGS
In general the SAP kernel and IGS binaries are located in the global kernel directory DIR_CT_RUN on
the host indicated by the profile parameter SAPGLOBALHOST Once the files in this directory have been
updated to a new patch level a system restart distributes them by means of the program SAPCPE to the
local directories DIR_EXECUTABLE on the hosts where the instances of the SAP system are running
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
2012-08-30 CUSTOMER 1760
CAUTION
The automatic distribution by means of SAPCPE depends on the settings of the profile parameters
DIR_CT_RUN for the global kernel directory and DIR_EXECUTABLE for the local directory of the
executables Before you continue check the instance profiles for the settings of these parameters
in systems that are not installed using SAPinst (for example systems upgraded from older releases
copied or migrated systems)
CAUTION
If your system is a dual-stack system (ABAP+Java) and the ABAP stack has a non-Unicode kernel
be aware that the SCS instance has a Unicode kernel You have to update both kernels (together
with SAP IGS) prior to updating the ABAP and Java Support Package stacks This ensures
compatibility and reduces system downtime
RECOMMENDATION
If you perform an update of a dual-stack system (ABAP+Java) we recommend that prior to
applying ABAP and Java Support Package stacks you use the Single Support Packages option in JSPM
and select for update only the components SAP KERNEL and BC-FES-IGS
For more information about updating a dual-stack system see Parallel Update of Dual-Stack Systems
[page 28]
If you perform an update of an ABAP system the following procedure applies for updating the SAP
kernel and IGS manually
1 Log on as user ltsapsidgtadm to the instance host to be updated
2 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory using
SAPCAR [page 56]
3 Stop the ABAP system that you want to update
NOTE
If the system is running in a high availability (HA) environment make sure that the HA
software does not restart the system automatically during the update
4 Back up the kernel directory ltkrnl_directorygt
5 Copy or move the extracted programs from the temporary directory to the SAP kernel directory
6 Only valid for UNIX |
Execute the following command sequence on UNIX platforms
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
1860 CUSTOMER 2012-08-30
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
7 Restart the SAP system
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS) runs
on a dedicated host You need to perform the kernel update for the ASCS instance manually but
excluding the IGS update because the IGS is not required in an ASCS instance
In rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of such instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances manually Proceed as described
in section Manually Updating Instances with Kernel Directory Located on Separate Hosts below in this document
214 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the ABAP system
22 Application Server Java and Java-Based Software Components
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system which includes
JSPM itself
SAP Kernel and SAP IGS
All Java-based usage types installed in the system
Software Deployment Manager (SDM) - the deployment service of the system
RECOMMENDATION
We strongly recommend that you apply the target Support Package Stack to your system as a
whole This ensures consistency on both the system and the application levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 1960
221 Planning
Procedure
Java Support Package files (SCAs) contain all software objects of the corresponding software
components Thus it is sufficient to apply the Java Support Package files of the intended Support Package
Stack directly to the Java system to be updated It is not necessary to apply the Support Package Stacks
between the start SP Stack level and the target SP Stack level successively
CAUTION
When applying a Support Package Stack to a Java system the Java Support Package Manager (JSPM)
will necessarily restart the system several times to make the changes effective With a dual-stack
system (ABAP+Java) the ABAP part will only be restarted when JSPM is updating the SAP kernel
and IGS
The following components belong to the usage type SAP NetWeaver Application Server Java (AS Java)
Software Components of Application Server Java
Component to Be Updated SP File Name Tool Used to Apply SP
SAP Kernel 720 32-64-BIT UNICODE SAPEXESAR
SAPEXEDBSAR
JSPM
SAP IGS 700 igsexesar
BI META MODEL REPOSITORY 702 BIMMRltSPgt_ltPLgtSCA
J2EE ENGINE CORE TOOLS 702 CORETOOLSltSPgt_ltPLgtSCA
J2EE ENGINE BASE TABLES 702 BASETABLESltSPgt_ltPLgtSCA
BI UDI 702 BIUDIltSPgt_ltPLgtSCA
DI BUILD TOOL 702 SAPBUILDTltSPgt_ltPLgtSCA
SAP CAF 702 CAFltSPgt_ltPLgtSCA
SAP IKS 702 KMKWJIKSltSPgt_ltPLgtSCA
JAVA LOG VIEWER 702 JLOGVIEWltSPgt_ltPLgtSCA
SAP J2EE ENGINE CORE 702 SAPJEECORltSPgt_ltPLgtSCA
SAP JAVA TECH SERVICES 702 SAPJTECHSltSPgt_ltPLgtSCA
SAP TECH S OFFLINE 702 SAPJTECHFltSPgt_ltPLgtSCA
SAP J2EE ENGINE 702 SAPJEEltSPgt_ltPLgtSCA
JAVA SP MANAGER 702 JSPMltSPgt_ltPLgtSCA
ADOBE DOCUMENT SERVICES 702 ADSSAPltSPgt_ltPLgtSCA
UME ADMINISTRATION 702 UMEADMINltSPgt_ltPLgtSCA
LIFECYCLE MGMT TOOLS 702 LMTOOLSltSPgt_ltPLgtSCA
SAP CAF-UM 702 CAFUMltSPgt_ltPLgtSCA
SAP SOFTW DELIV MANAGER 702 SDMKITltSPgt_ltPLgtJAR
SOFTWARE LIFECYCLE MANAGER 702 SWLIFECYCLltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2060 CUSTOMER 2012-08-30
NOTE
This table contains only software components that belong to the usage type AS Java Software
components of other usage types and Java application units are listed in the corresponding
sections
NOTE
As of Support Package 09 you can update your system with SAP Kernel 720 instead of SAP Kernel
701
222 Preparation for Applying a Support Package Stack
Procedure
1 Download the Support Package Stack with all usage types to be updated and the stack definition
XML file as described in Downloading Support Package Stacks [page 12]
NOTE
You can find the activated usage types in an existing Java system on the Deployed Components tab
page on the JSPM user interface
NOTE
You do not need to download the SP Stacks between the source SP Stack level and target SP
Stack level By default the target SP Stack level is the latest available SP Stack
2 Make sure the following requirements are met prior to applying the Support Package Stack
You have familiarized yourself with SAP Note 891983 before you start the Java Support Package
Manager
The system to be updated is fully functional
The Support Package Stack you want to apply and the corresponding stack definition XML
file are available in the EPS inbox directory usrsaptransEPSin By default this location
can be also referred to as ldquoJSPM inboxrdquo
The SAP NetWeaver Application Server Java (AS Java) and the database have been backed up
You have not deleted renamed or created any directories and files in the following directories
and their subdirectories usrsapltSAPSIDgtSYSexe and usrsapltSAPSIDgtSYS
profile
Otherwise JSPM cannot detect the kernel and the system profiles and cannot be started If a
backup of the kernel and the system profiles has been required it has been created in a different
directory
The ltsapsidgtadm user has Read permissions for the EPS inbox directory usrsaptransEPS
in
If your database is SAP MaxDB the overwrite mode for the log area has been activated
The database and the SDM repository have been synchronized
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2160
For more information see the online documentation for JSPM on SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70 Library
(including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library Administrators Guide
Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems AS Java
(Application Server for Java) Software Logistics Software Maintenance Java Support Package Manager
Then choose Troubleshooting JSPM Does Not Update the Versions of the Deployed Components
There is enough disk space
For more information see SAP Note 891895
Your current SAPCAR tool is able to extract the Support Packages for the SAP kernel and
other OS level binaries delivered as SAR files
RECOMMENDATION
You can download the latest version of SAPCAR from SAP Service Marketplace at
httpservicesapcompatches Entry by Application Group Additional Components
SAPCAR
Put the downloaded version in the same directory in the JSPM inbox in which the kernel
SAR files reside so that JSPM can use this version for extracting the SAR files
3 Only valid for Linux |
For RHEL 4 and SLES 9 you need to install additional operating system packages For more
information see SAP Note 1021236End of Linux |
4 Only valid for Windows |
For Windows you need to install additional operating system packages For more information see
SAP Note 684106End of Windows |
5 To prevent the Software Deployment Manager (SDM) from temporarily exceeding the available
disk space during the update process you can change the file transfer directory of SDM in a system
of SPS09 or higher using the following command sequence
Only valid for Windows |
cd ltsdm_homegt
StopServerbat
sdmbat jstartup mode=standalone
sdmbat filetransferdir dir=ltnew_dirgt
sdmbat jstartup mode=integrated
StartServerbat
End of Windows |
Only valid for IBM i5OSUNIX |
cd ltsdm_homegt
StopServersh
sdmsh jstartup mode=standalone
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2260 CUSTOMER 2012-08-30
sdmsh filetransferdir dir=ltnew_dirgt
sdmsh jstartup mode=integrated
StartServersh
End of IBM i5OSUNIX |
6 To prevent deployment errors during the update process proceed as follows
1 Log on to the Central Instance host
2 Start the ConfigTool and in the navigation area choose Cluster-data Global server configuration
Managers ServiceManager
3 In the Global properties panel set the Custom value of the EventTimeout property to 120
4 Choose Save
5 Restart the Central Instance
7 Check whether the used JDK version and the Java VM settings of the Java runtime system comply
with the requirements in SAP Note 723909 Update the JDK and adjust the settings if necessary
NOTE
An update of the used JDK version possibly changes the JVM path In this case you must
make the new path available to all Dialog Instances of the J2EE engine by implementing option
1 of SAP Note 718901
8 Make sure that the J2EE administrator password stored in the secure store for offline usage is
identical with the one stored in the User Management Engine (UME) You can change the password
in the secure store as described in SAP Note 870445
9 If you are running a high availability system on Windows you might need to prepare your system
as described in the online documentation for JSPM see section Preparing Systems That Run in High
Availability Environment
223 Updating the Application Server Java and Java-Based Components
Procedure
Applying a Support Package Stack to SAP NetWeaver Application Server Java and Java-Based Components
NOTE
The JSPM GUI might not work properly on some UNIX systems For more information and the
solution see SAP Note 1013976
1 Log on as user ltsapsidgtadm to the Central Instance host
NOTE
If your operating system is IBM i log on as user ltSIDgtADM or ltSIDgtOFR
2 Close the SAP Management Console (SAP MMC) and the SDM remote GUI client
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2360
3 For UNIX and Windows To start the JSPM navigate to the directory ltINSTDIRgtltSIDgt
ltCentral_Instance_Namegtj2eeJSPM and run the go script file
NOTE
If your system is running on IBM i to start the JSPM proceed as follows
1 To prevent JSPM from automatically starting its GUI in the file usrsapltSIDgt
ltCentral_Instance_Namegtj2eeJSPMparamjspm_configtxt change the
property dialogSDTServerConnectionSDTGuilaunch from true to false
2 On the IBM i host run the go script file using the following command
QSH CMD(usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPMgo)
3 In the mounted directory usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPM run
the StartGui script file The JSPM GUI appears
4 In the Host field enter the target IBM i host
NOTE
Depending on the system type ltCentral_Instance_Namegt has the following syntax
Standalone Java system JCltinstance_nogt
Add-On system DVEBMGSltinstance_nogt
4 Enter your SDM password to log on to the SDM
5 On the Deployment tab page select the Java Support Package Manager option and update the software
component sapcomJSPM to the target SPS level
6 Restart the JSPM and log on with the SDM password
RECOMMENDATION
We strongly recommend that you use the Support and Enhancement Package Stack option when
applying a Support Package Stack Other options can lead to unintended consistency issues
NOTE
If you need to include the latest patches for a particular component during the update process
with the Support and Enhancement Package Stack option stop the JSPM after restart and apply SAP
Note 1080821 Then start the JSPM again
7 On the Deployment tab page select the Support and Enhancement Package Stack option and choose Next
The Support Package Stacks that are available for deployment in the global EPS inbox directory
are displayed
8 In the Target SP Stack Level dropdown box select the Support Package Stack to be applied and choose
Next
In this step JSPM performs various status validations and displays the result of each software
component included in the stack definition XML file on the subsequent screen which includes
the following possible statuses
OK Indicates that the SPS level of the corresponding software component is applicable
WARNING We recommend that you view the details about the component by choosing Show
Details
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2460 CUSTOMER 2012-08-30
This status may indicate that the corresponding software component comprises custom
modifications in an NWDI-controlled system
If your system is used for NWDI development and it is either a DEV or a CONS system
you will be informed that JSPM will not deploy the modified software components but
only transport them to the CMS transport directory JSPM will deploy only the software
components that are not modified
If your system is not used for NWDI development or if your system is used for NWDI
development and it is either a TEST or a PROD system you will be informed that JSPM
has found newer versions of modified software components and will automatically replace
the original versions with the newer versions JSPM will deploy all software components
that are not modified together with the replaced versions of the modified software
components
CAUTION
You may get a warning telling you that there are patches installed in your system
containing fixes which might not be included in the target SP Stack This is possible if
you have applied patches of the start SP Stack level that were delivered later than the
target SP Stack delivery date In order not to lose these fixes you need to download and
apply the corresponding patches of the target SP Stack level
If you are performing an update from SAP NetWeaver 70 including enhancement
package 1 SPS00 and you have not applied any patches for the software component with
status WARNING before the update then you can ignore warnings such as the following
example
The new version of the development component sapcomcomsapnetweaver
bcrfmoni is 70100200806121227180000 and is lower than the already
deployed version 70100200807090143420000
REVISE Indicates inconsistencies with the corresponding software component
The deployment cannot be performed until all problems have been resolved You can view
the problems by choosing Show Details
9 If the status of the selected SP Stack is OK or WARNING you can start the system update by choosing
Start JSPM then changes the status to SCHEDULED
If the SP Stack to be applied includes a kernel update and the current kernel is not already of the
corresponding patch level JSPM arranges the kernel update as the very first Support Package to
be applied JSPM updates the kernel binaries of all instances (including Dialog Instances and SCS
instances in a HA environment) whose kernel directories DIR_CT_RUN effectively reside on the host
indicated by the profile parameter SAPGLOBALHOST
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2560
CAUTION
Kernel binaries of instances whose kernel directories DIR_CT_RUN are not effectively linked
to the host SAPGLOBALHOST must be updated individually as described in section Manually
Updating Instances with Kernel Directory Located on Separate Hosts below
The kernel update (includes update of SAP Kernel and SAP IGS) using JSPM consists of the following
steps
1 JSPM stops the Central Instance automatically and prompts you to stop the remote SCS and
Dialog Instances manually
2 After you have stopped all the instances choose the Next button in the dialog box
The kernel update starts
NOTE
If the system is running in a high availability environment make sure that the HA
software does not restart the instance automatically during the update
NOTE
If kernel binaries of the SCS instance need to be updated manually (see Manually Updating
Instances with Kernel Directory Located on Separate Hosts below) you must perform this at the
time when JSPM is updating the kernel binaries of the Central Instance In any case the
SCS kernel must be up-to-date before the next restart
When the kernel update is finished a dialog box appears in which you are prompted to restart
the SCS instance manually
3 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries
before you can proceed with the next step For more information see Adjusting the Ownership and
Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
4 Choose Next in the dialog box when the SCS instance is running again
After the kernel update JSPM restarts the system for further deployment of the remaining Support
Packages in the stack
RECOMMENDATION
If you need to update the kernel binaries of any Dialog Instances manually (see Manually
Updating Instances with Kernel Directory Located on Separate Hosts below) perform the update when
JSPM is updating the remaining Support Packages in the stack in order to save time
The deployment of each Support Package can end with one of the following statuses
DEPLOYED
The Support Package has been successfully deployed
DEPLOYED WITH WARNING
The Support Package has been deployed but it possibly may not work properly with other
deployed components
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2660 CUSTOMER 2012-08-30
You can view the details by choosing Show Details or examining the log files You can also view
the details about the component by choosing the Deployed Components tab page
ERROR
An error has occurred during the deployment You can view the details by choosing Show
Details or examining the log files
You must correct the error to be able to continue with the SP Stack update
You can proceed as described for a deployment that finished with status DEPLOYED WITH
WARNING
If the error correction does not change the contents in the JSPM inbox you can continue
the deployment by choosing Resume
If the error correction changes the contents in the JSPM inbox you can choose New
Deployment to redeploy the SP Stack
NOT DEPLOYED
JSPM has not attempted to deploy the software component for certain reasons
If your system is not used for NWDI development you can proceed as described for a
deployment that finished with status ERROR
If your system is used for NWDI development and it is either a DEV or a CONS system
the status of the modified software components is always NOT DEPLOYED JSPM has
transported the software components of the Support Package Stack both modified and
not modified to the CMS transport directory The deployment of the modified software
components is handled by NWDI
Manually Updating Instances with Kernel Directory Located on Separate Hosts
JSPM performs kernel update for all instances (including Dialog Instances and SCS instances in a HA
environment) whose kernel directories DIR_CT_RUN effectively reside on the host indicated by the profile
parameter SAPGLOBALHOST (by using folder sharing on Windows or file system mounting on UNIX) In
rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of those sort of instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances individually
To update the kernel of an instance manually proceed as follows
1 Log on as user ltsapsidgtadm to the host of the instance to be updated
2 Back up the kernel directory which is specified by the profile parameter DIR_CT_RUN
3 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory with
SAPCAR [page 56]
4 Stop the instance being updated
NOTE
If the system is running in a HA environment make sure that the HA software does not
restart the instance automatically during the update
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2760
5 Copy or move the extracted programs from the temporary directory to the local kernel directory
6 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries as
described in section Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
7 Restart the instance after JSPM has finished the deployment of all packages on the Central Instance
Only valid for UNIX |
Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms
On UNIX platforms you must adjust the ownership and execution permissions of the kernel binaries
after the update regardless whether you performed the update manually or by using JSPM because
both update procedures are performed with the ltsapsidgtadm user Enter the following command
sequence
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
224 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the Java system
23 Parallel Update of Dual-Stack Systems
If you perform an update of a dual-stack system (ABAP+Java) we recommend that you follow the
procedure described below The procedure has been validated to update the ABAP stack and the Java
stack of a NetWeaver system in parallel thus reducing the overall system downtime by half
Procedure
1 Before applying ABAP and Java Support Packages use the Single Support Packages option in JSPM and
select for update only the components SAP KERNEL and BC-FES-IGS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
23 Parallel Update of Dual-Stack Systems
2860 CUSTOMER 2012-08-30
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS)
runs on a dedicated host In this case JSPM does not support update of kernel binaries and
you need to update them manually Perform the update manually as described under Updating
SAP Kernel and SAP IGS in section Updating the Application Server ABAP and ABAP-Based Software
Components [page 16]
2 Import the Support Packages for the component SAP_BASIS into the ABAP stack using the ABAP
Support Package Manager (SPAM)
3 Import the remaining ABAP Support Packages with SPAM and in parallel apply the Java Support
Package Stack with JSPM
Proceed as described in Updating the Application Server ABAP and ABAP-Based Software Components [page
16] and Updating the Application Server Java and Java-Based Software Components [page 23]
24 Process Integration
241 Planning
Procedure
This section covers all the units of Process Integration that should be updated Particularly the following
units must always have the same Support Package level (the patch level can be different)
Integration Server
XI Adapter Engine
Partner Connectivity Kit
System with the Usage Type Process Integration
Software components of Integration Server
Components to Be Updated SP File Name Tool Used to Apply SP
Java stack
XI TOOLS 702 SAPXITOOLltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
ABAP stack
XI CONTENT SAP_BASIS 702 SAPBASISltSPgt_ltPLgtZIP File upload
XI CONTENT SAP_ABA 702 SAPABAltSPgt_ltPLgtZIP
SAP NetWeaver Application Server ABAP (see table Software components of Application Server ABAP [page 15])Note that update of the following software components of the ABAP system is not required SAP ABA 702 SAP BW 702 PI_BASIS 702
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 2960
J2EE Adapter Engine
If your implemented scenario includes a J2EE Adapter Engine then it must always be of the same
Support Package level as the Integration Server
Components of the J2EE Adapter Engine
Component to Be Updated SP File NameTool Used to Apply SP
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
J2SE Adapter Engine
The installation of the J2SE Adapter Engine depends on the implemented scenario
Components of the J2SE Adapter Engine
Component to Be Updated SP File Name Tool Used to Apply SP
XI CONNECTIVITY SE 702 SAPXICONSltSPgt_ltPLgtSCA ZIP tool (for example WinZip)
Partner Connectivity Kit
If your implemented scenario includes a Partner Connectivity Kit (PCK) then it must always be of the
same Support Package level as the Integration Server
Software components of Partner Connectivity Kit
Components to Be Updated SP File NameTool Used to Apply SP
XI PCK 702 SAPXIPCKltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of the Application Server Java [page 20])
System Landscape Directory (SLD)
The System Landscape Directory is required for the PI operations Although updating the SLD is not
necessarily required it is advisable to update the SLD server and the SAP Master Data Content within
it from time to time The update of the SLD includes
1 The system where the SLD is running
2 The SAP Master Data Content within this SLD
SAP GUI
See table Compatible SAP GUI Versions [page 51]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3060 CUSTOMER 2012-08-30
242 Updating Units of Process Integration
Procedure
Before you start the update perform the following steps
In the Runtime Workbench use Communication Channel Monitoring to stop all sender channels
for all adapter types on all your Adapter Engines
On the Integration Server use transaction SMQR and deregister all qRFC queues
System with the Usage Type Process Integration
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the XI instance is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system where the XI instance is running
For more information see Application Server Java and Java-Based Software Components [page 19]
System Landscape Directory (Optional)
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the SLD is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the entire Support Package Stack to the system where the SLD is running
For more information see Application Server Java and Java-Based Software Components [page 19]
J2EE Adapter Engine
Apply the Support Package Stack to the system where the Adapter Engine is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Partner Connectivity Kit
Apply the Support Package Stack to the system where the PCK is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Front End GUIs
Update the SAP GUI components if necessary
For more information see SAP GUI Family [page 51]
ABAP 700 Business System (Optional)
Apply the Support Packages for SAP NetWeaver Application Server ABAP (including SAP kernel and
the Support Package for SAP BASIS 700)
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 640 Business System (Optional)
Apply the Support Packages for SAP Web Application Server ABAP 640 (including SAP kernel and the
Support Package for SAP BASIS 640)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3160
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 620 Business System (Optional)
1 Update the SAP Kernel 620
2 Import the released Basis Support Packages for SAP Web AS 620 as well as the most recent Add-
On Support Package for APPINT 200_620 in the order described in SAP Note 439915
J2SE Adapter Engine (Optional)
NOTE
The XI Adapter Engine (J2SE) and all its adapters are provided for compatibility reasons only and
are not developed any further You have to use the XI Adapter Engine running on SAP NetWeaver
AS Java For more information see the Master Guide ndash SAP NetWeaver 70 available on SAP Service
Marketplace at httpservicesapcominstallNW70 Planning
1 Extract the SAPXICONSltSPgt_ltPLgtSCA (XI Connectivity SE 700) archive (ZIP format) to a temporary
directory
2 Save the old configuration files as described in the document Adapterpdf in directory
lttemp_directorygttech_adapterAdministrationDocumentation
3 Unpack the ZIP archive TechnicalAdapterssda to the installation directory of the XI Adapter
Engine (J2SE)
4 Restore the configuration files with restore_configuration
243 Post-Installation Steps
Procedure
Communication Channels and Queues
Restart all stopped sender channels and register all deregistered qRFC queues
XI Content
In the system with usage type PI import the XI content from the archives SAPBASISltSPgt_ltPLgtZIP
and SAPABAltSPgt_ltPLgtZIP as follows
1 Unpack the archives using a ZIP tool of your choice
2 Copy the corresponding export files (with file extension tpz) to the import directory ltINSTDIRgt
ltSAPSIDgtSYSglobalxirepository_serverimport
3 Start the Integration Builder (transaction SXMB_IFR)
4 Enter the Integration Repository by choosing Repository (Design)
5 Choose Tools Import design objects
6 Import the tpz files containing the XI content
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3260 CUSTOMER 2012-08-30
NOTE
For more information see SAP Note 836200
Role Generation on the Integration Server
On the Integration Server execute transaction SUPC (mass generation of roles) for all SAP_XI roles in
each of your clients to regenerate possibly changed roles
NOTE
Do not forget to make a user comparison for regenerated roles afterwards
Partner Connectivity Kit (Optional)
Perform the post-installation steps for PCK as described in SAP Note 746328
SAP Master Data within the SLD (Optional)
In the system where your SLD is running import the latest SLD content as described in SAP Note
669669
Receiver-Based EOIO Serialization in J2EE Adapter Engine (Optional)
The J2EE Adapter Engine can be switched to receiver-based EOIO serialization The switch can be
triggered on demand and is executed asynchronously It includes a database migration step during
which all EOIO processing in the Adapter Engine is disabled See SAP Note 973894 for details about how
to start the EOIO serialization migration
Service Metering (Optional)
Service metering gathers information about a service caller transfers it to the service provider and
counts on the service provisioning side how many times a service is called and by which service caller
Service metering is performed for the XI message protocol and the WS message protocol Service
metering is automatically enabled after applying a Support Package Stack By default only non-sensitive
data is transmitted to internal or external service providers in a compatible way
Service metering can be configured in PI in the Integration Engine on sender-side and in the Integration
Directory
Service metering can be configured in AS ABAP in transaction SOAMANAGER
Only if the service provider is allowed to receive more detailed information about the service caller set
the metering level to higher than the default
For more information see SAP Note 1239428
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3360
25 Business Intelligence
251 Planning
Procedure
Business Intelligence includes one or many of the following units that must be updated depending on
your implemented scenarios The usage types Business Intelligence (BI) and Business Intelligence Java
Components (BI-Java) must always have the same Support Package level
Business Intelligence
Software Components of Business Intelligence
Component to Be Updated SP File Name Tool Used to Apply SP
BI CONT ADDON 70x SAPK-70ltxgtltSPgtINBICONT SAINT
SAP NetWeaver Application Server ABAP (see table Software Components of Application Server ABAP [page 15])
NOTE
For information about the dependencies applying to BI Content Support Packages see SAP Note
653814 BI CONT 703 Support Packages are not part of the NetWeaver SP Stacks Updates can be
performed when applicable Alternatively BI CONT 704 Support Packages can be imported See
the BI Content release strategy in SAP Note 153967
Business Intelligence Java Components
BI Java Components
Component to Be Updated SP File NameTool Used to Apply SP
BI REPORTING AND PLANNING 702 BIREPPLANltSPgt_ltPLgtSCA JSPM
BI WEBDYNPRO ALV 702 BIWDALVltSPgt_ltPLgtSCA
BI INFORM BROADCASTING 702 BIIBCltSPgt_ltPLgtSCA
BI WEB APPLICATIONS 702 BIWEBAPPltSPgt_ltPLgtSCA
BI BASE SERVICES 702 BIBASESltSPgt_ltPLgtSCA
VISUAL COMPOSER BI KITS 702 VCKITBIltSPgt_ltPLgtSCA
Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
BI Precalculation Service
Components of the BI Precalculation Service
Component to Be Updated SP File Name Tool Used to Apply SP
BI Pre-calculation Service 700 xPreCalServerltSPgt_ltPLgtexe Installer
Search and Classification (TREX)
See table TREX Component [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3460 CUSTOMER 2012-08-30
BI Accelerator
The BI Accelerator is based on the TREX technology It is a special Linux 64-bit version of SAP NetWeaver
70 Search and Classification (TREX) which is delivered on preconfigured hardware
NOTE
You cannot use a TREX installation based on 32-bit architecture that is configured for searching
in metadata and documents for the BI Accelerator And vice versa a BI Accelerator box cannot
be used for searching in metadata and documents
If you want to use the search functionality as well as the BI Accelerator you require two separate
installations For more information see BI Accelerator [page 47]
Clients
Depending on your implemented scenarios you have to update SAP GUI Components and Business
Explorer (BI Add-OnBW Add-On)
NOTE
See SAP Note 889314 to determine when to use the BI Add-On and the BW Add-On
NOTE
As SAP GUI 640 is no longer supported BI Frontend Support Package 1800 resp patch 1801 is the
last Support Package resp patch based on SAP GUI 640 For more information see SAP Note
1231292 (Frontend Add-in Strategy 640710 GUI Version)
For more information about the new release strategy for the BI Frontend see SAP Note 1231363
(Changed Delivery Strategy for BI Frontend)
252 Preparation
Procedure
For the Support Packages of the most important Business Intelligence units so called SAPBINews
(SAPBWNews) Notes are created Read these Notes before updating Business Intelligence For SAP
NetWeaver 70 including enhancement package 2 SPS 12 these are the following
Business Intelligence ABAP SAP Note 1680996
Business Intelligence Java Components SAP Note 1726461
BI 70 Frontend Add-On for SAP GUI 710 SAP Note 1413032
BI 70 Frontend Add-On for SAP GUI 720 SAP Note 1630112
BI 70 Frontend Add-On for SAP GUI 730 SAP Note 1726739
For more information about BI Support Packages see SAP Community Network at http
scnsapcomcommunitydata-warehousingnetweaver-bw Related Resources SAP NW BW Support
Packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
2012-08-30 CUSTOMER 3560
253 Updating Units of Business Intelligence
Procedure
Business Intelligence
1 Update the SAP NetWeaver Application Server ABAP (with BI CONT 70x if necessary) with the
appropriate Support Packages
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
NOTE
When applying the component SAP BW 702 some generation errors might occur When
you start importing the BI Support Packages in transaction SPAM choose the menu path
Extras Ignore generation errors For more information see SAP Note 114134
2 Apply the Support Package Stack to the system with the usage type BI-Java
For more information see Application Server Java and Java-Based Software Components [page 19]
3 Update the BI Precalculation Service that is used in your scenario
4 Update the standalone engine Search and Classification (TREX) that is used in your scenario For more
information see Standalone Engine Search and Classification (TREX) [page 44]
NOTE
You have to update TREX to the newest version if you use search capabilities within Business
Intelligence
5 Update the BI Accelerator to the newest available version For more information see BI
Accelerator [page 47]
6 Update the SAP GUI and Business Explorer (BI Add-On BW Add-On) on all remote client hosts
that are involved in the scenario
For more information see SAP GUI Family [page 51] and Business Explorer (BI Add-On BW Add-On)
[page 51]
BI Precalculation Service
1 Log on to the host as a user with administration rights
2 Install the Support Package of the BI Precalculation Service by executing the
xPreCalServerexe file
The welcome screen of the BI Precalculation Server setup wizard appears
The setup now checks the system for the prerequisites
3 Choose the option Update for updating the BI Precalculation service to the current patch level and
then Finish
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3660 CUSTOMER 2012-08-30
26 EP Core
261 Planning
Procedure
The following installable software units must be updated
EP Core
Software Components of EP Core
Component to Be Updated SP File Name Tool Used to Apply SP
PORTAL CORE SERVICES 702 EPBCltSPgt_ltPLgtSCA JSPM
PORTAL FRAMEWORK 702 EPBC2ltSPgt_ltPLgtSCA
PORTAL 702 EPPSERVltSPgt_ltPLgtSCA
PORTAL WEB DYNPRO 702 EPWDCltSPgt_ltPLgtSCA
UWL COLL PROCESS ENGINE 702 UWLJWFltSPgt_ltPLgtSCA
CAF EU 702 SAPEUltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
262 Preparation
Procedure
Backing Up the Portal Runtime Configuration
If you have made changes to the standard Portal Runtime configuration you have to make a backup
of the configuration before the update process For more information see SAP Note 1064468
263 Updating EP Core
Procedure
Apply the Support Package Stack to a system with usage type EP Core
For more information see Application Server Java and Java-Based Software Components [page 19]
264 Post-Installation Steps for EP Core
Procedure
Restoring the Portal Runtime Configuration
To make your changes to the standard Portal Runtime Configuration effective you have to restore
the backup of the configuration done before the update process For more information see SAP Note
1064468
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
26 EP Core
2012-08-30 CUSTOMER 3760
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
7 Select the target SP Stack level and the relevant usage types according to the IT scenario to be
updated
8 Choose Find Download Files for the Stack Version
The Maintenance Optimizer displays the product maintenance files in three successive lists
9 Select the required files from the displayed lists
The first list shows all files that are dependent on the type of your operating system and
database
Select the files that correspond to the combination of your operating system and database and
the database-independent files
If your system is distributed on several hosts make sure to select all operating systems used
by the NetWeaver instances You can see all the kernels detected on your system on the Deployed
Components tab page on JSPM user interface (under the SAP KERNEL node) All detected kernels
must be updated to the same version
You get to the second list by choosing Continue This list displays all Support Package files that
are not assigned to the selected Support Package Stack Before you continue with the selection
you must check whether the Support Package files listed here are suitable for your product
maintenance procedure
You get to the third list by choosing Continue The list displays all product maintenance files
that are part of the selected Support Package Stack
Ensure that all files that are assigned to the Support Package Stack are selected here Files that
are not selected will not be included later in the download
10 Choose Continue Use the Download Basket to download the maintenance files
11 Choose Continue once the files have been put in your Download Basket and then Confirm Files in
Download Basket
A dialog window appears and displays all files
12 Confirm the download for all files
13 Open your Download Manager and download the files
NOTE
The stack XML file is generated by the Maintenance Optimizer and automatically saved to
the EPS inbox directory of SAP Solution Manager
More Information
For more information about the Maintenance Optimizer see SAP Support Portal at http
servicesapcomsolman-mopz
1 Overview
13 Downloading Support Package Stacks
2012-08-30 CUSTOMER 1360
This page is left blank for documents that are printed on both sides
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
This chapter describes how to apply Support Packages to installable software units of SAP NetWeaver
70 including enhancement package 2 SAP NetWeaver distinguishes three types of installable software
units
Systems with one or multiple usage types
Standalone engines
Clients
A scenario implementation usually involves several installed software units
RECOMMENDATION
We strongly recommend that you always update all software units belonging to one scenario
together in order to retain a consistent system state Due to the fact that some installable software
units can be commonly shared in different scenarios you must consequently update all scenarios
using the common software units at the same time
21 Application Server ABAP and ABAP-Based Software Components
211 Planning
Procedure
The following components belong to the usage type SAP NetWeaver Application Server ABAP
Software Components of Application Server ABAP
Component to Be Updated SP File Name Tool Used to Apply SP
SAP KERNEL 720 32-64-BIT Non-UNICODEUNICODE SAPEXESAR
SAPEXEDBSAR
JSPMmanually
SAP IGS 700 igsexesar
SAP ABA 702 SAPKA702ltSPgt SPAMSAINT
SAP BASIS 702 SAPKB702ltSPgt
SAP BW 702 SAPKW702ltSPgt
PI_BASIS 702 SAPK-702ltSPgtINPIBASIS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
2012-08-30 CUSTOMER 1560
NOTE
This table contains only software components that belong to the usage type AS ABAP Software
components of other usage types and application units are listed in the corresponding sections
NOTE
SAP delivers intermediate Support Packages for the component SAP BW 702 between two
subsequent SP levels besides the Support Packages delivered along with the Support Package
Stacks Therefore the highest SP level of SAP BW 702 does not necessarily match the target SP
Stack level
CAUTION
When applying a Support Package Stack to a dual-stack system (ABAP+Java) the Java Support
Package Manager (JSPM) will necessarily restart the system several times to make the changes
effective The ABAP part will only be restarted when JSPM is updating the SAP kernel and IGS
212 Preparation
Procedure
Read SAP Note 822379 and all related SAP Notes that the first one refers to
213 Updating the Application Server ABAP and ABAP-Based Software Components
Procedure
Applying Support Packages to SAP NetWeaver Application Server ABAP and ABAP-Based Components
You can update the SAP NetWeaver Application Server ABAP and all ABAP-based software components
running on it using the Support Package Manager (transaction SPAM)
NOTE
If a particular Support Package Stack requires the installation or upgrade of some add-on
components you must use the ABAP Add-on Installation Tool (transaction SAINT) instead of the
Support Package Manager In this case SAINT is able to import both the add-on components and
the related Support Packages of ordinary SAP components
Proceed as follows
1 Log on to the SAP NetWeaver AS system with client 000
2 Start the Support Package Manager by calling transaction SPAM or
start the Add-On Installation Tool by calling transaction SAINT
3 Load the relevant Support Packages or add-on installation packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
1660 CUSTOMER 2012-08-30
4 Define an import queue
5 Perform the import of the defined queue
NOTE
If you have modified SAP objects in your system and these objects are included in the Support
Packages you must perform modification adjustment during the import using the
transactions SPDD (for ABAP Dictionary objects) and SPAU (for Repository objects)
To import the queue you use the standard scenario You can choose between the conventional
import mode and downtime-minimized import mode
Conventional Import Mode
This option comprises the following steps
1 Update the SAP kernel and SAP IGS as described in section Updating SAP Kernel and SAP IGS below
Start the system after the kernel update
2 Import the ABAP Support Packages with the Support Package Manager (SPAM)
Import Mode Downtime-Minimized
This option can be used to reduce system downtime during the update It comprises the following
steps
1 In transaction SPAM enable the downtime-minimized import mode by choosing Extras
Settings then on the Import queue tab page choose Standard and activate the option Import Mode
Downtime-Minimized
2 Import the ABAP Support Packages into the system in an inactive state in the downtime-minimized
mode during system uptime
3 Update the SAP kernel and SAP IGS as described in section Updating SAP Kernel and SAP IGS below
Start the system after the kernel update
4 Complete the ABAP Support Packages import
CAUTION
During this step the system cannot carry out any business transactions (business downtime)
NOTE
In rare cases due to the dependencies of some Support Packages on a particular kernel patch level
the downtime-minimized update does not work In such cases the Support Package Manager
informs you that you must update the SAP kernel before importing ABAP Support Packages You
must proceed with the conventional import procedure
Updating SAP Kernel and SAP IGS
In general the SAP kernel and IGS binaries are located in the global kernel directory DIR_CT_RUN on
the host indicated by the profile parameter SAPGLOBALHOST Once the files in this directory have been
updated to a new patch level a system restart distributes them by means of the program SAPCPE to the
local directories DIR_EXECUTABLE on the hosts where the instances of the SAP system are running
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
2012-08-30 CUSTOMER 1760
CAUTION
The automatic distribution by means of SAPCPE depends on the settings of the profile parameters
DIR_CT_RUN for the global kernel directory and DIR_EXECUTABLE for the local directory of the
executables Before you continue check the instance profiles for the settings of these parameters
in systems that are not installed using SAPinst (for example systems upgraded from older releases
copied or migrated systems)
CAUTION
If your system is a dual-stack system (ABAP+Java) and the ABAP stack has a non-Unicode kernel
be aware that the SCS instance has a Unicode kernel You have to update both kernels (together
with SAP IGS) prior to updating the ABAP and Java Support Package stacks This ensures
compatibility and reduces system downtime
RECOMMENDATION
If you perform an update of a dual-stack system (ABAP+Java) we recommend that prior to
applying ABAP and Java Support Package stacks you use the Single Support Packages option in JSPM
and select for update only the components SAP KERNEL and BC-FES-IGS
For more information about updating a dual-stack system see Parallel Update of Dual-Stack Systems
[page 28]
If you perform an update of an ABAP system the following procedure applies for updating the SAP
kernel and IGS manually
1 Log on as user ltsapsidgtadm to the instance host to be updated
2 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory using
SAPCAR [page 56]
3 Stop the ABAP system that you want to update
NOTE
If the system is running in a high availability (HA) environment make sure that the HA
software does not restart the system automatically during the update
4 Back up the kernel directory ltkrnl_directorygt
5 Copy or move the extracted programs from the temporary directory to the SAP kernel directory
6 Only valid for UNIX |
Execute the following command sequence on UNIX platforms
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
1860 CUSTOMER 2012-08-30
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
7 Restart the SAP system
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS) runs
on a dedicated host You need to perform the kernel update for the ASCS instance manually but
excluding the IGS update because the IGS is not required in an ASCS instance
In rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of such instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances manually Proceed as described
in section Manually Updating Instances with Kernel Directory Located on Separate Hosts below in this document
214 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the ABAP system
22 Application Server Java and Java-Based Software Components
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system which includes
JSPM itself
SAP Kernel and SAP IGS
All Java-based usage types installed in the system
Software Deployment Manager (SDM) - the deployment service of the system
RECOMMENDATION
We strongly recommend that you apply the target Support Package Stack to your system as a
whole This ensures consistency on both the system and the application levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 1960
221 Planning
Procedure
Java Support Package files (SCAs) contain all software objects of the corresponding software
components Thus it is sufficient to apply the Java Support Package files of the intended Support Package
Stack directly to the Java system to be updated It is not necessary to apply the Support Package Stacks
between the start SP Stack level and the target SP Stack level successively
CAUTION
When applying a Support Package Stack to a Java system the Java Support Package Manager (JSPM)
will necessarily restart the system several times to make the changes effective With a dual-stack
system (ABAP+Java) the ABAP part will only be restarted when JSPM is updating the SAP kernel
and IGS
The following components belong to the usage type SAP NetWeaver Application Server Java (AS Java)
Software Components of Application Server Java
Component to Be Updated SP File Name Tool Used to Apply SP
SAP Kernel 720 32-64-BIT UNICODE SAPEXESAR
SAPEXEDBSAR
JSPM
SAP IGS 700 igsexesar
BI META MODEL REPOSITORY 702 BIMMRltSPgt_ltPLgtSCA
J2EE ENGINE CORE TOOLS 702 CORETOOLSltSPgt_ltPLgtSCA
J2EE ENGINE BASE TABLES 702 BASETABLESltSPgt_ltPLgtSCA
BI UDI 702 BIUDIltSPgt_ltPLgtSCA
DI BUILD TOOL 702 SAPBUILDTltSPgt_ltPLgtSCA
SAP CAF 702 CAFltSPgt_ltPLgtSCA
SAP IKS 702 KMKWJIKSltSPgt_ltPLgtSCA
JAVA LOG VIEWER 702 JLOGVIEWltSPgt_ltPLgtSCA
SAP J2EE ENGINE CORE 702 SAPJEECORltSPgt_ltPLgtSCA
SAP JAVA TECH SERVICES 702 SAPJTECHSltSPgt_ltPLgtSCA
SAP TECH S OFFLINE 702 SAPJTECHFltSPgt_ltPLgtSCA
SAP J2EE ENGINE 702 SAPJEEltSPgt_ltPLgtSCA
JAVA SP MANAGER 702 JSPMltSPgt_ltPLgtSCA
ADOBE DOCUMENT SERVICES 702 ADSSAPltSPgt_ltPLgtSCA
UME ADMINISTRATION 702 UMEADMINltSPgt_ltPLgtSCA
LIFECYCLE MGMT TOOLS 702 LMTOOLSltSPgt_ltPLgtSCA
SAP CAF-UM 702 CAFUMltSPgt_ltPLgtSCA
SAP SOFTW DELIV MANAGER 702 SDMKITltSPgt_ltPLgtJAR
SOFTWARE LIFECYCLE MANAGER 702 SWLIFECYCLltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2060 CUSTOMER 2012-08-30
NOTE
This table contains only software components that belong to the usage type AS Java Software
components of other usage types and Java application units are listed in the corresponding
sections
NOTE
As of Support Package 09 you can update your system with SAP Kernel 720 instead of SAP Kernel
701
222 Preparation for Applying a Support Package Stack
Procedure
1 Download the Support Package Stack with all usage types to be updated and the stack definition
XML file as described in Downloading Support Package Stacks [page 12]
NOTE
You can find the activated usage types in an existing Java system on the Deployed Components tab
page on the JSPM user interface
NOTE
You do not need to download the SP Stacks between the source SP Stack level and target SP
Stack level By default the target SP Stack level is the latest available SP Stack
2 Make sure the following requirements are met prior to applying the Support Package Stack
You have familiarized yourself with SAP Note 891983 before you start the Java Support Package
Manager
The system to be updated is fully functional
The Support Package Stack you want to apply and the corresponding stack definition XML
file are available in the EPS inbox directory usrsaptransEPSin By default this location
can be also referred to as ldquoJSPM inboxrdquo
The SAP NetWeaver Application Server Java (AS Java) and the database have been backed up
You have not deleted renamed or created any directories and files in the following directories
and their subdirectories usrsapltSAPSIDgtSYSexe and usrsapltSAPSIDgtSYS
profile
Otherwise JSPM cannot detect the kernel and the system profiles and cannot be started If a
backup of the kernel and the system profiles has been required it has been created in a different
directory
The ltsapsidgtadm user has Read permissions for the EPS inbox directory usrsaptransEPS
in
If your database is SAP MaxDB the overwrite mode for the log area has been activated
The database and the SDM repository have been synchronized
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2160
For more information see the online documentation for JSPM on SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70 Library
(including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library Administrators Guide
Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems AS Java
(Application Server for Java) Software Logistics Software Maintenance Java Support Package Manager
Then choose Troubleshooting JSPM Does Not Update the Versions of the Deployed Components
There is enough disk space
For more information see SAP Note 891895
Your current SAPCAR tool is able to extract the Support Packages for the SAP kernel and
other OS level binaries delivered as SAR files
RECOMMENDATION
You can download the latest version of SAPCAR from SAP Service Marketplace at
httpservicesapcompatches Entry by Application Group Additional Components
SAPCAR
Put the downloaded version in the same directory in the JSPM inbox in which the kernel
SAR files reside so that JSPM can use this version for extracting the SAR files
3 Only valid for Linux |
For RHEL 4 and SLES 9 you need to install additional operating system packages For more
information see SAP Note 1021236End of Linux |
4 Only valid for Windows |
For Windows you need to install additional operating system packages For more information see
SAP Note 684106End of Windows |
5 To prevent the Software Deployment Manager (SDM) from temporarily exceeding the available
disk space during the update process you can change the file transfer directory of SDM in a system
of SPS09 or higher using the following command sequence
Only valid for Windows |
cd ltsdm_homegt
StopServerbat
sdmbat jstartup mode=standalone
sdmbat filetransferdir dir=ltnew_dirgt
sdmbat jstartup mode=integrated
StartServerbat
End of Windows |
Only valid for IBM i5OSUNIX |
cd ltsdm_homegt
StopServersh
sdmsh jstartup mode=standalone
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2260 CUSTOMER 2012-08-30
sdmsh filetransferdir dir=ltnew_dirgt
sdmsh jstartup mode=integrated
StartServersh
End of IBM i5OSUNIX |
6 To prevent deployment errors during the update process proceed as follows
1 Log on to the Central Instance host
2 Start the ConfigTool and in the navigation area choose Cluster-data Global server configuration
Managers ServiceManager
3 In the Global properties panel set the Custom value of the EventTimeout property to 120
4 Choose Save
5 Restart the Central Instance
7 Check whether the used JDK version and the Java VM settings of the Java runtime system comply
with the requirements in SAP Note 723909 Update the JDK and adjust the settings if necessary
NOTE
An update of the used JDK version possibly changes the JVM path In this case you must
make the new path available to all Dialog Instances of the J2EE engine by implementing option
1 of SAP Note 718901
8 Make sure that the J2EE administrator password stored in the secure store for offline usage is
identical with the one stored in the User Management Engine (UME) You can change the password
in the secure store as described in SAP Note 870445
9 If you are running a high availability system on Windows you might need to prepare your system
as described in the online documentation for JSPM see section Preparing Systems That Run in High
Availability Environment
223 Updating the Application Server Java and Java-Based Components
Procedure
Applying a Support Package Stack to SAP NetWeaver Application Server Java and Java-Based Components
NOTE
The JSPM GUI might not work properly on some UNIX systems For more information and the
solution see SAP Note 1013976
1 Log on as user ltsapsidgtadm to the Central Instance host
NOTE
If your operating system is IBM i log on as user ltSIDgtADM or ltSIDgtOFR
2 Close the SAP Management Console (SAP MMC) and the SDM remote GUI client
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2360
3 For UNIX and Windows To start the JSPM navigate to the directory ltINSTDIRgtltSIDgt
ltCentral_Instance_Namegtj2eeJSPM and run the go script file
NOTE
If your system is running on IBM i to start the JSPM proceed as follows
1 To prevent JSPM from automatically starting its GUI in the file usrsapltSIDgt
ltCentral_Instance_Namegtj2eeJSPMparamjspm_configtxt change the
property dialogSDTServerConnectionSDTGuilaunch from true to false
2 On the IBM i host run the go script file using the following command
QSH CMD(usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPMgo)
3 In the mounted directory usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPM run
the StartGui script file The JSPM GUI appears
4 In the Host field enter the target IBM i host
NOTE
Depending on the system type ltCentral_Instance_Namegt has the following syntax
Standalone Java system JCltinstance_nogt
Add-On system DVEBMGSltinstance_nogt
4 Enter your SDM password to log on to the SDM
5 On the Deployment tab page select the Java Support Package Manager option and update the software
component sapcomJSPM to the target SPS level
6 Restart the JSPM and log on with the SDM password
RECOMMENDATION
We strongly recommend that you use the Support and Enhancement Package Stack option when
applying a Support Package Stack Other options can lead to unintended consistency issues
NOTE
If you need to include the latest patches for a particular component during the update process
with the Support and Enhancement Package Stack option stop the JSPM after restart and apply SAP
Note 1080821 Then start the JSPM again
7 On the Deployment tab page select the Support and Enhancement Package Stack option and choose Next
The Support Package Stacks that are available for deployment in the global EPS inbox directory
are displayed
8 In the Target SP Stack Level dropdown box select the Support Package Stack to be applied and choose
Next
In this step JSPM performs various status validations and displays the result of each software
component included in the stack definition XML file on the subsequent screen which includes
the following possible statuses
OK Indicates that the SPS level of the corresponding software component is applicable
WARNING We recommend that you view the details about the component by choosing Show
Details
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2460 CUSTOMER 2012-08-30
This status may indicate that the corresponding software component comprises custom
modifications in an NWDI-controlled system
If your system is used for NWDI development and it is either a DEV or a CONS system
you will be informed that JSPM will not deploy the modified software components but
only transport them to the CMS transport directory JSPM will deploy only the software
components that are not modified
If your system is not used for NWDI development or if your system is used for NWDI
development and it is either a TEST or a PROD system you will be informed that JSPM
has found newer versions of modified software components and will automatically replace
the original versions with the newer versions JSPM will deploy all software components
that are not modified together with the replaced versions of the modified software
components
CAUTION
You may get a warning telling you that there are patches installed in your system
containing fixes which might not be included in the target SP Stack This is possible if
you have applied patches of the start SP Stack level that were delivered later than the
target SP Stack delivery date In order not to lose these fixes you need to download and
apply the corresponding patches of the target SP Stack level
If you are performing an update from SAP NetWeaver 70 including enhancement
package 1 SPS00 and you have not applied any patches for the software component with
status WARNING before the update then you can ignore warnings such as the following
example
The new version of the development component sapcomcomsapnetweaver
bcrfmoni is 70100200806121227180000 and is lower than the already
deployed version 70100200807090143420000
REVISE Indicates inconsistencies with the corresponding software component
The deployment cannot be performed until all problems have been resolved You can view
the problems by choosing Show Details
9 If the status of the selected SP Stack is OK or WARNING you can start the system update by choosing
Start JSPM then changes the status to SCHEDULED
If the SP Stack to be applied includes a kernel update and the current kernel is not already of the
corresponding patch level JSPM arranges the kernel update as the very first Support Package to
be applied JSPM updates the kernel binaries of all instances (including Dialog Instances and SCS
instances in a HA environment) whose kernel directories DIR_CT_RUN effectively reside on the host
indicated by the profile parameter SAPGLOBALHOST
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2560
CAUTION
Kernel binaries of instances whose kernel directories DIR_CT_RUN are not effectively linked
to the host SAPGLOBALHOST must be updated individually as described in section Manually
Updating Instances with Kernel Directory Located on Separate Hosts below
The kernel update (includes update of SAP Kernel and SAP IGS) using JSPM consists of the following
steps
1 JSPM stops the Central Instance automatically and prompts you to stop the remote SCS and
Dialog Instances manually
2 After you have stopped all the instances choose the Next button in the dialog box
The kernel update starts
NOTE
If the system is running in a high availability environment make sure that the HA
software does not restart the instance automatically during the update
NOTE
If kernel binaries of the SCS instance need to be updated manually (see Manually Updating
Instances with Kernel Directory Located on Separate Hosts below) you must perform this at the
time when JSPM is updating the kernel binaries of the Central Instance In any case the
SCS kernel must be up-to-date before the next restart
When the kernel update is finished a dialog box appears in which you are prompted to restart
the SCS instance manually
3 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries
before you can proceed with the next step For more information see Adjusting the Ownership and
Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
4 Choose Next in the dialog box when the SCS instance is running again
After the kernel update JSPM restarts the system for further deployment of the remaining Support
Packages in the stack
RECOMMENDATION
If you need to update the kernel binaries of any Dialog Instances manually (see Manually
Updating Instances with Kernel Directory Located on Separate Hosts below) perform the update when
JSPM is updating the remaining Support Packages in the stack in order to save time
The deployment of each Support Package can end with one of the following statuses
DEPLOYED
The Support Package has been successfully deployed
DEPLOYED WITH WARNING
The Support Package has been deployed but it possibly may not work properly with other
deployed components
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2660 CUSTOMER 2012-08-30
You can view the details by choosing Show Details or examining the log files You can also view
the details about the component by choosing the Deployed Components tab page
ERROR
An error has occurred during the deployment You can view the details by choosing Show
Details or examining the log files
You must correct the error to be able to continue with the SP Stack update
You can proceed as described for a deployment that finished with status DEPLOYED WITH
WARNING
If the error correction does not change the contents in the JSPM inbox you can continue
the deployment by choosing Resume
If the error correction changes the contents in the JSPM inbox you can choose New
Deployment to redeploy the SP Stack
NOT DEPLOYED
JSPM has not attempted to deploy the software component for certain reasons
If your system is not used for NWDI development you can proceed as described for a
deployment that finished with status ERROR
If your system is used for NWDI development and it is either a DEV or a CONS system
the status of the modified software components is always NOT DEPLOYED JSPM has
transported the software components of the Support Package Stack both modified and
not modified to the CMS transport directory The deployment of the modified software
components is handled by NWDI
Manually Updating Instances with Kernel Directory Located on Separate Hosts
JSPM performs kernel update for all instances (including Dialog Instances and SCS instances in a HA
environment) whose kernel directories DIR_CT_RUN effectively reside on the host indicated by the profile
parameter SAPGLOBALHOST (by using folder sharing on Windows or file system mounting on UNIX) In
rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of those sort of instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances individually
To update the kernel of an instance manually proceed as follows
1 Log on as user ltsapsidgtadm to the host of the instance to be updated
2 Back up the kernel directory which is specified by the profile parameter DIR_CT_RUN
3 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory with
SAPCAR [page 56]
4 Stop the instance being updated
NOTE
If the system is running in a HA environment make sure that the HA software does not
restart the instance automatically during the update
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2760
5 Copy or move the extracted programs from the temporary directory to the local kernel directory
6 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries as
described in section Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
7 Restart the instance after JSPM has finished the deployment of all packages on the Central Instance
Only valid for UNIX |
Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms
On UNIX platforms you must adjust the ownership and execution permissions of the kernel binaries
after the update regardless whether you performed the update manually or by using JSPM because
both update procedures are performed with the ltsapsidgtadm user Enter the following command
sequence
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
224 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the Java system
23 Parallel Update of Dual-Stack Systems
If you perform an update of a dual-stack system (ABAP+Java) we recommend that you follow the
procedure described below The procedure has been validated to update the ABAP stack and the Java
stack of a NetWeaver system in parallel thus reducing the overall system downtime by half
Procedure
1 Before applying ABAP and Java Support Packages use the Single Support Packages option in JSPM and
select for update only the components SAP KERNEL and BC-FES-IGS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
23 Parallel Update of Dual-Stack Systems
2860 CUSTOMER 2012-08-30
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS)
runs on a dedicated host In this case JSPM does not support update of kernel binaries and
you need to update them manually Perform the update manually as described under Updating
SAP Kernel and SAP IGS in section Updating the Application Server ABAP and ABAP-Based Software
Components [page 16]
2 Import the Support Packages for the component SAP_BASIS into the ABAP stack using the ABAP
Support Package Manager (SPAM)
3 Import the remaining ABAP Support Packages with SPAM and in parallel apply the Java Support
Package Stack with JSPM
Proceed as described in Updating the Application Server ABAP and ABAP-Based Software Components [page
16] and Updating the Application Server Java and Java-Based Software Components [page 23]
24 Process Integration
241 Planning
Procedure
This section covers all the units of Process Integration that should be updated Particularly the following
units must always have the same Support Package level (the patch level can be different)
Integration Server
XI Adapter Engine
Partner Connectivity Kit
System with the Usage Type Process Integration
Software components of Integration Server
Components to Be Updated SP File Name Tool Used to Apply SP
Java stack
XI TOOLS 702 SAPXITOOLltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
ABAP stack
XI CONTENT SAP_BASIS 702 SAPBASISltSPgt_ltPLgtZIP File upload
XI CONTENT SAP_ABA 702 SAPABAltSPgt_ltPLgtZIP
SAP NetWeaver Application Server ABAP (see table Software components of Application Server ABAP [page 15])Note that update of the following software components of the ABAP system is not required SAP ABA 702 SAP BW 702 PI_BASIS 702
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 2960
J2EE Adapter Engine
If your implemented scenario includes a J2EE Adapter Engine then it must always be of the same
Support Package level as the Integration Server
Components of the J2EE Adapter Engine
Component to Be Updated SP File NameTool Used to Apply SP
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
J2SE Adapter Engine
The installation of the J2SE Adapter Engine depends on the implemented scenario
Components of the J2SE Adapter Engine
Component to Be Updated SP File Name Tool Used to Apply SP
XI CONNECTIVITY SE 702 SAPXICONSltSPgt_ltPLgtSCA ZIP tool (for example WinZip)
Partner Connectivity Kit
If your implemented scenario includes a Partner Connectivity Kit (PCK) then it must always be of the
same Support Package level as the Integration Server
Software components of Partner Connectivity Kit
Components to Be Updated SP File NameTool Used to Apply SP
XI PCK 702 SAPXIPCKltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of the Application Server Java [page 20])
System Landscape Directory (SLD)
The System Landscape Directory is required for the PI operations Although updating the SLD is not
necessarily required it is advisable to update the SLD server and the SAP Master Data Content within
it from time to time The update of the SLD includes
1 The system where the SLD is running
2 The SAP Master Data Content within this SLD
SAP GUI
See table Compatible SAP GUI Versions [page 51]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3060 CUSTOMER 2012-08-30
242 Updating Units of Process Integration
Procedure
Before you start the update perform the following steps
In the Runtime Workbench use Communication Channel Monitoring to stop all sender channels
for all adapter types on all your Adapter Engines
On the Integration Server use transaction SMQR and deregister all qRFC queues
System with the Usage Type Process Integration
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the XI instance is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system where the XI instance is running
For more information see Application Server Java and Java-Based Software Components [page 19]
System Landscape Directory (Optional)
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the SLD is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the entire Support Package Stack to the system where the SLD is running
For more information see Application Server Java and Java-Based Software Components [page 19]
J2EE Adapter Engine
Apply the Support Package Stack to the system where the Adapter Engine is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Partner Connectivity Kit
Apply the Support Package Stack to the system where the PCK is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Front End GUIs
Update the SAP GUI components if necessary
For more information see SAP GUI Family [page 51]
ABAP 700 Business System (Optional)
Apply the Support Packages for SAP NetWeaver Application Server ABAP (including SAP kernel and
the Support Package for SAP BASIS 700)
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 640 Business System (Optional)
Apply the Support Packages for SAP Web Application Server ABAP 640 (including SAP kernel and the
Support Package for SAP BASIS 640)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3160
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 620 Business System (Optional)
1 Update the SAP Kernel 620
2 Import the released Basis Support Packages for SAP Web AS 620 as well as the most recent Add-
On Support Package for APPINT 200_620 in the order described in SAP Note 439915
J2SE Adapter Engine (Optional)
NOTE
The XI Adapter Engine (J2SE) and all its adapters are provided for compatibility reasons only and
are not developed any further You have to use the XI Adapter Engine running on SAP NetWeaver
AS Java For more information see the Master Guide ndash SAP NetWeaver 70 available on SAP Service
Marketplace at httpservicesapcominstallNW70 Planning
1 Extract the SAPXICONSltSPgt_ltPLgtSCA (XI Connectivity SE 700) archive (ZIP format) to a temporary
directory
2 Save the old configuration files as described in the document Adapterpdf in directory
lttemp_directorygttech_adapterAdministrationDocumentation
3 Unpack the ZIP archive TechnicalAdapterssda to the installation directory of the XI Adapter
Engine (J2SE)
4 Restore the configuration files with restore_configuration
243 Post-Installation Steps
Procedure
Communication Channels and Queues
Restart all stopped sender channels and register all deregistered qRFC queues
XI Content
In the system with usage type PI import the XI content from the archives SAPBASISltSPgt_ltPLgtZIP
and SAPABAltSPgt_ltPLgtZIP as follows
1 Unpack the archives using a ZIP tool of your choice
2 Copy the corresponding export files (with file extension tpz) to the import directory ltINSTDIRgt
ltSAPSIDgtSYSglobalxirepository_serverimport
3 Start the Integration Builder (transaction SXMB_IFR)
4 Enter the Integration Repository by choosing Repository (Design)
5 Choose Tools Import design objects
6 Import the tpz files containing the XI content
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3260 CUSTOMER 2012-08-30
NOTE
For more information see SAP Note 836200
Role Generation on the Integration Server
On the Integration Server execute transaction SUPC (mass generation of roles) for all SAP_XI roles in
each of your clients to regenerate possibly changed roles
NOTE
Do not forget to make a user comparison for regenerated roles afterwards
Partner Connectivity Kit (Optional)
Perform the post-installation steps for PCK as described in SAP Note 746328
SAP Master Data within the SLD (Optional)
In the system where your SLD is running import the latest SLD content as described in SAP Note
669669
Receiver-Based EOIO Serialization in J2EE Adapter Engine (Optional)
The J2EE Adapter Engine can be switched to receiver-based EOIO serialization The switch can be
triggered on demand and is executed asynchronously It includes a database migration step during
which all EOIO processing in the Adapter Engine is disabled See SAP Note 973894 for details about how
to start the EOIO serialization migration
Service Metering (Optional)
Service metering gathers information about a service caller transfers it to the service provider and
counts on the service provisioning side how many times a service is called and by which service caller
Service metering is performed for the XI message protocol and the WS message protocol Service
metering is automatically enabled after applying a Support Package Stack By default only non-sensitive
data is transmitted to internal or external service providers in a compatible way
Service metering can be configured in PI in the Integration Engine on sender-side and in the Integration
Directory
Service metering can be configured in AS ABAP in transaction SOAMANAGER
Only if the service provider is allowed to receive more detailed information about the service caller set
the metering level to higher than the default
For more information see SAP Note 1239428
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3360
25 Business Intelligence
251 Planning
Procedure
Business Intelligence includes one or many of the following units that must be updated depending on
your implemented scenarios The usage types Business Intelligence (BI) and Business Intelligence Java
Components (BI-Java) must always have the same Support Package level
Business Intelligence
Software Components of Business Intelligence
Component to Be Updated SP File Name Tool Used to Apply SP
BI CONT ADDON 70x SAPK-70ltxgtltSPgtINBICONT SAINT
SAP NetWeaver Application Server ABAP (see table Software Components of Application Server ABAP [page 15])
NOTE
For information about the dependencies applying to BI Content Support Packages see SAP Note
653814 BI CONT 703 Support Packages are not part of the NetWeaver SP Stacks Updates can be
performed when applicable Alternatively BI CONT 704 Support Packages can be imported See
the BI Content release strategy in SAP Note 153967
Business Intelligence Java Components
BI Java Components
Component to Be Updated SP File NameTool Used to Apply SP
BI REPORTING AND PLANNING 702 BIREPPLANltSPgt_ltPLgtSCA JSPM
BI WEBDYNPRO ALV 702 BIWDALVltSPgt_ltPLgtSCA
BI INFORM BROADCASTING 702 BIIBCltSPgt_ltPLgtSCA
BI WEB APPLICATIONS 702 BIWEBAPPltSPgt_ltPLgtSCA
BI BASE SERVICES 702 BIBASESltSPgt_ltPLgtSCA
VISUAL COMPOSER BI KITS 702 VCKITBIltSPgt_ltPLgtSCA
Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
BI Precalculation Service
Components of the BI Precalculation Service
Component to Be Updated SP File Name Tool Used to Apply SP
BI Pre-calculation Service 700 xPreCalServerltSPgt_ltPLgtexe Installer
Search and Classification (TREX)
See table TREX Component [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3460 CUSTOMER 2012-08-30
BI Accelerator
The BI Accelerator is based on the TREX technology It is a special Linux 64-bit version of SAP NetWeaver
70 Search and Classification (TREX) which is delivered on preconfigured hardware
NOTE
You cannot use a TREX installation based on 32-bit architecture that is configured for searching
in metadata and documents for the BI Accelerator And vice versa a BI Accelerator box cannot
be used for searching in metadata and documents
If you want to use the search functionality as well as the BI Accelerator you require two separate
installations For more information see BI Accelerator [page 47]
Clients
Depending on your implemented scenarios you have to update SAP GUI Components and Business
Explorer (BI Add-OnBW Add-On)
NOTE
See SAP Note 889314 to determine when to use the BI Add-On and the BW Add-On
NOTE
As SAP GUI 640 is no longer supported BI Frontend Support Package 1800 resp patch 1801 is the
last Support Package resp patch based on SAP GUI 640 For more information see SAP Note
1231292 (Frontend Add-in Strategy 640710 GUI Version)
For more information about the new release strategy for the BI Frontend see SAP Note 1231363
(Changed Delivery Strategy for BI Frontend)
252 Preparation
Procedure
For the Support Packages of the most important Business Intelligence units so called SAPBINews
(SAPBWNews) Notes are created Read these Notes before updating Business Intelligence For SAP
NetWeaver 70 including enhancement package 2 SPS 12 these are the following
Business Intelligence ABAP SAP Note 1680996
Business Intelligence Java Components SAP Note 1726461
BI 70 Frontend Add-On for SAP GUI 710 SAP Note 1413032
BI 70 Frontend Add-On for SAP GUI 720 SAP Note 1630112
BI 70 Frontend Add-On for SAP GUI 730 SAP Note 1726739
For more information about BI Support Packages see SAP Community Network at http
scnsapcomcommunitydata-warehousingnetweaver-bw Related Resources SAP NW BW Support
Packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
2012-08-30 CUSTOMER 3560
253 Updating Units of Business Intelligence
Procedure
Business Intelligence
1 Update the SAP NetWeaver Application Server ABAP (with BI CONT 70x if necessary) with the
appropriate Support Packages
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
NOTE
When applying the component SAP BW 702 some generation errors might occur When
you start importing the BI Support Packages in transaction SPAM choose the menu path
Extras Ignore generation errors For more information see SAP Note 114134
2 Apply the Support Package Stack to the system with the usage type BI-Java
For more information see Application Server Java and Java-Based Software Components [page 19]
3 Update the BI Precalculation Service that is used in your scenario
4 Update the standalone engine Search and Classification (TREX) that is used in your scenario For more
information see Standalone Engine Search and Classification (TREX) [page 44]
NOTE
You have to update TREX to the newest version if you use search capabilities within Business
Intelligence
5 Update the BI Accelerator to the newest available version For more information see BI
Accelerator [page 47]
6 Update the SAP GUI and Business Explorer (BI Add-On BW Add-On) on all remote client hosts
that are involved in the scenario
For more information see SAP GUI Family [page 51] and Business Explorer (BI Add-On BW Add-On)
[page 51]
BI Precalculation Service
1 Log on to the host as a user with administration rights
2 Install the Support Package of the BI Precalculation Service by executing the
xPreCalServerexe file
The welcome screen of the BI Precalculation Server setup wizard appears
The setup now checks the system for the prerequisites
3 Choose the option Update for updating the BI Precalculation service to the current patch level and
then Finish
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3660 CUSTOMER 2012-08-30
26 EP Core
261 Planning
Procedure
The following installable software units must be updated
EP Core
Software Components of EP Core
Component to Be Updated SP File Name Tool Used to Apply SP
PORTAL CORE SERVICES 702 EPBCltSPgt_ltPLgtSCA JSPM
PORTAL FRAMEWORK 702 EPBC2ltSPgt_ltPLgtSCA
PORTAL 702 EPPSERVltSPgt_ltPLgtSCA
PORTAL WEB DYNPRO 702 EPWDCltSPgt_ltPLgtSCA
UWL COLL PROCESS ENGINE 702 UWLJWFltSPgt_ltPLgtSCA
CAF EU 702 SAPEUltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
262 Preparation
Procedure
Backing Up the Portal Runtime Configuration
If you have made changes to the standard Portal Runtime configuration you have to make a backup
of the configuration before the update process For more information see SAP Note 1064468
263 Updating EP Core
Procedure
Apply the Support Package Stack to a system with usage type EP Core
For more information see Application Server Java and Java-Based Software Components [page 19]
264 Post-Installation Steps for EP Core
Procedure
Restoring the Portal Runtime Configuration
To make your changes to the standard Portal Runtime Configuration effective you have to restore
the backup of the configuration done before the update process For more information see SAP Note
1064468
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
26 EP Core
2012-08-30 CUSTOMER 3760
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
This page is left blank for documents that are printed on both sides
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
This chapter describes how to apply Support Packages to installable software units of SAP NetWeaver
70 including enhancement package 2 SAP NetWeaver distinguishes three types of installable software
units
Systems with one or multiple usage types
Standalone engines
Clients
A scenario implementation usually involves several installed software units
RECOMMENDATION
We strongly recommend that you always update all software units belonging to one scenario
together in order to retain a consistent system state Due to the fact that some installable software
units can be commonly shared in different scenarios you must consequently update all scenarios
using the common software units at the same time
21 Application Server ABAP and ABAP-Based Software Components
211 Planning
Procedure
The following components belong to the usage type SAP NetWeaver Application Server ABAP
Software Components of Application Server ABAP
Component to Be Updated SP File Name Tool Used to Apply SP
SAP KERNEL 720 32-64-BIT Non-UNICODEUNICODE SAPEXESAR
SAPEXEDBSAR
JSPMmanually
SAP IGS 700 igsexesar
SAP ABA 702 SAPKA702ltSPgt SPAMSAINT
SAP BASIS 702 SAPKB702ltSPgt
SAP BW 702 SAPKW702ltSPgt
PI_BASIS 702 SAPK-702ltSPgtINPIBASIS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
2012-08-30 CUSTOMER 1560
NOTE
This table contains only software components that belong to the usage type AS ABAP Software
components of other usage types and application units are listed in the corresponding sections
NOTE
SAP delivers intermediate Support Packages for the component SAP BW 702 between two
subsequent SP levels besides the Support Packages delivered along with the Support Package
Stacks Therefore the highest SP level of SAP BW 702 does not necessarily match the target SP
Stack level
CAUTION
When applying a Support Package Stack to a dual-stack system (ABAP+Java) the Java Support
Package Manager (JSPM) will necessarily restart the system several times to make the changes
effective The ABAP part will only be restarted when JSPM is updating the SAP kernel and IGS
212 Preparation
Procedure
Read SAP Note 822379 and all related SAP Notes that the first one refers to
213 Updating the Application Server ABAP and ABAP-Based Software Components
Procedure
Applying Support Packages to SAP NetWeaver Application Server ABAP and ABAP-Based Components
You can update the SAP NetWeaver Application Server ABAP and all ABAP-based software components
running on it using the Support Package Manager (transaction SPAM)
NOTE
If a particular Support Package Stack requires the installation or upgrade of some add-on
components you must use the ABAP Add-on Installation Tool (transaction SAINT) instead of the
Support Package Manager In this case SAINT is able to import both the add-on components and
the related Support Packages of ordinary SAP components
Proceed as follows
1 Log on to the SAP NetWeaver AS system with client 000
2 Start the Support Package Manager by calling transaction SPAM or
start the Add-On Installation Tool by calling transaction SAINT
3 Load the relevant Support Packages or add-on installation packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
1660 CUSTOMER 2012-08-30
4 Define an import queue
5 Perform the import of the defined queue
NOTE
If you have modified SAP objects in your system and these objects are included in the Support
Packages you must perform modification adjustment during the import using the
transactions SPDD (for ABAP Dictionary objects) and SPAU (for Repository objects)
To import the queue you use the standard scenario You can choose between the conventional
import mode and downtime-minimized import mode
Conventional Import Mode
This option comprises the following steps
1 Update the SAP kernel and SAP IGS as described in section Updating SAP Kernel and SAP IGS below
Start the system after the kernel update
2 Import the ABAP Support Packages with the Support Package Manager (SPAM)
Import Mode Downtime-Minimized
This option can be used to reduce system downtime during the update It comprises the following
steps
1 In transaction SPAM enable the downtime-minimized import mode by choosing Extras
Settings then on the Import queue tab page choose Standard and activate the option Import Mode
Downtime-Minimized
2 Import the ABAP Support Packages into the system in an inactive state in the downtime-minimized
mode during system uptime
3 Update the SAP kernel and SAP IGS as described in section Updating SAP Kernel and SAP IGS below
Start the system after the kernel update
4 Complete the ABAP Support Packages import
CAUTION
During this step the system cannot carry out any business transactions (business downtime)
NOTE
In rare cases due to the dependencies of some Support Packages on a particular kernel patch level
the downtime-minimized update does not work In such cases the Support Package Manager
informs you that you must update the SAP kernel before importing ABAP Support Packages You
must proceed with the conventional import procedure
Updating SAP Kernel and SAP IGS
In general the SAP kernel and IGS binaries are located in the global kernel directory DIR_CT_RUN on
the host indicated by the profile parameter SAPGLOBALHOST Once the files in this directory have been
updated to a new patch level a system restart distributes them by means of the program SAPCPE to the
local directories DIR_EXECUTABLE on the hosts where the instances of the SAP system are running
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
2012-08-30 CUSTOMER 1760
CAUTION
The automatic distribution by means of SAPCPE depends on the settings of the profile parameters
DIR_CT_RUN for the global kernel directory and DIR_EXECUTABLE for the local directory of the
executables Before you continue check the instance profiles for the settings of these parameters
in systems that are not installed using SAPinst (for example systems upgraded from older releases
copied or migrated systems)
CAUTION
If your system is a dual-stack system (ABAP+Java) and the ABAP stack has a non-Unicode kernel
be aware that the SCS instance has a Unicode kernel You have to update both kernels (together
with SAP IGS) prior to updating the ABAP and Java Support Package stacks This ensures
compatibility and reduces system downtime
RECOMMENDATION
If you perform an update of a dual-stack system (ABAP+Java) we recommend that prior to
applying ABAP and Java Support Package stacks you use the Single Support Packages option in JSPM
and select for update only the components SAP KERNEL and BC-FES-IGS
For more information about updating a dual-stack system see Parallel Update of Dual-Stack Systems
[page 28]
If you perform an update of an ABAP system the following procedure applies for updating the SAP
kernel and IGS manually
1 Log on as user ltsapsidgtadm to the instance host to be updated
2 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory using
SAPCAR [page 56]
3 Stop the ABAP system that you want to update
NOTE
If the system is running in a high availability (HA) environment make sure that the HA
software does not restart the system automatically during the update
4 Back up the kernel directory ltkrnl_directorygt
5 Copy or move the extracted programs from the temporary directory to the SAP kernel directory
6 Only valid for UNIX |
Execute the following command sequence on UNIX platforms
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
1860 CUSTOMER 2012-08-30
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
7 Restart the SAP system
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS) runs
on a dedicated host You need to perform the kernel update for the ASCS instance manually but
excluding the IGS update because the IGS is not required in an ASCS instance
In rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of such instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances manually Proceed as described
in section Manually Updating Instances with Kernel Directory Located on Separate Hosts below in this document
214 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the ABAP system
22 Application Server Java and Java-Based Software Components
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system which includes
JSPM itself
SAP Kernel and SAP IGS
All Java-based usage types installed in the system
Software Deployment Manager (SDM) - the deployment service of the system
RECOMMENDATION
We strongly recommend that you apply the target Support Package Stack to your system as a
whole This ensures consistency on both the system and the application levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 1960
221 Planning
Procedure
Java Support Package files (SCAs) contain all software objects of the corresponding software
components Thus it is sufficient to apply the Java Support Package files of the intended Support Package
Stack directly to the Java system to be updated It is not necessary to apply the Support Package Stacks
between the start SP Stack level and the target SP Stack level successively
CAUTION
When applying a Support Package Stack to a Java system the Java Support Package Manager (JSPM)
will necessarily restart the system several times to make the changes effective With a dual-stack
system (ABAP+Java) the ABAP part will only be restarted when JSPM is updating the SAP kernel
and IGS
The following components belong to the usage type SAP NetWeaver Application Server Java (AS Java)
Software Components of Application Server Java
Component to Be Updated SP File Name Tool Used to Apply SP
SAP Kernel 720 32-64-BIT UNICODE SAPEXESAR
SAPEXEDBSAR
JSPM
SAP IGS 700 igsexesar
BI META MODEL REPOSITORY 702 BIMMRltSPgt_ltPLgtSCA
J2EE ENGINE CORE TOOLS 702 CORETOOLSltSPgt_ltPLgtSCA
J2EE ENGINE BASE TABLES 702 BASETABLESltSPgt_ltPLgtSCA
BI UDI 702 BIUDIltSPgt_ltPLgtSCA
DI BUILD TOOL 702 SAPBUILDTltSPgt_ltPLgtSCA
SAP CAF 702 CAFltSPgt_ltPLgtSCA
SAP IKS 702 KMKWJIKSltSPgt_ltPLgtSCA
JAVA LOG VIEWER 702 JLOGVIEWltSPgt_ltPLgtSCA
SAP J2EE ENGINE CORE 702 SAPJEECORltSPgt_ltPLgtSCA
SAP JAVA TECH SERVICES 702 SAPJTECHSltSPgt_ltPLgtSCA
SAP TECH S OFFLINE 702 SAPJTECHFltSPgt_ltPLgtSCA
SAP J2EE ENGINE 702 SAPJEEltSPgt_ltPLgtSCA
JAVA SP MANAGER 702 JSPMltSPgt_ltPLgtSCA
ADOBE DOCUMENT SERVICES 702 ADSSAPltSPgt_ltPLgtSCA
UME ADMINISTRATION 702 UMEADMINltSPgt_ltPLgtSCA
LIFECYCLE MGMT TOOLS 702 LMTOOLSltSPgt_ltPLgtSCA
SAP CAF-UM 702 CAFUMltSPgt_ltPLgtSCA
SAP SOFTW DELIV MANAGER 702 SDMKITltSPgt_ltPLgtJAR
SOFTWARE LIFECYCLE MANAGER 702 SWLIFECYCLltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2060 CUSTOMER 2012-08-30
NOTE
This table contains only software components that belong to the usage type AS Java Software
components of other usage types and Java application units are listed in the corresponding
sections
NOTE
As of Support Package 09 you can update your system with SAP Kernel 720 instead of SAP Kernel
701
222 Preparation for Applying a Support Package Stack
Procedure
1 Download the Support Package Stack with all usage types to be updated and the stack definition
XML file as described in Downloading Support Package Stacks [page 12]
NOTE
You can find the activated usage types in an existing Java system on the Deployed Components tab
page on the JSPM user interface
NOTE
You do not need to download the SP Stacks between the source SP Stack level and target SP
Stack level By default the target SP Stack level is the latest available SP Stack
2 Make sure the following requirements are met prior to applying the Support Package Stack
You have familiarized yourself with SAP Note 891983 before you start the Java Support Package
Manager
The system to be updated is fully functional
The Support Package Stack you want to apply and the corresponding stack definition XML
file are available in the EPS inbox directory usrsaptransEPSin By default this location
can be also referred to as ldquoJSPM inboxrdquo
The SAP NetWeaver Application Server Java (AS Java) and the database have been backed up
You have not deleted renamed or created any directories and files in the following directories
and their subdirectories usrsapltSAPSIDgtSYSexe and usrsapltSAPSIDgtSYS
profile
Otherwise JSPM cannot detect the kernel and the system profiles and cannot be started If a
backup of the kernel and the system profiles has been required it has been created in a different
directory
The ltsapsidgtadm user has Read permissions for the EPS inbox directory usrsaptransEPS
in
If your database is SAP MaxDB the overwrite mode for the log area has been activated
The database and the SDM repository have been synchronized
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2160
For more information see the online documentation for JSPM on SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70 Library
(including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library Administrators Guide
Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems AS Java
(Application Server for Java) Software Logistics Software Maintenance Java Support Package Manager
Then choose Troubleshooting JSPM Does Not Update the Versions of the Deployed Components
There is enough disk space
For more information see SAP Note 891895
Your current SAPCAR tool is able to extract the Support Packages for the SAP kernel and
other OS level binaries delivered as SAR files
RECOMMENDATION
You can download the latest version of SAPCAR from SAP Service Marketplace at
httpservicesapcompatches Entry by Application Group Additional Components
SAPCAR
Put the downloaded version in the same directory in the JSPM inbox in which the kernel
SAR files reside so that JSPM can use this version for extracting the SAR files
3 Only valid for Linux |
For RHEL 4 and SLES 9 you need to install additional operating system packages For more
information see SAP Note 1021236End of Linux |
4 Only valid for Windows |
For Windows you need to install additional operating system packages For more information see
SAP Note 684106End of Windows |
5 To prevent the Software Deployment Manager (SDM) from temporarily exceeding the available
disk space during the update process you can change the file transfer directory of SDM in a system
of SPS09 or higher using the following command sequence
Only valid for Windows |
cd ltsdm_homegt
StopServerbat
sdmbat jstartup mode=standalone
sdmbat filetransferdir dir=ltnew_dirgt
sdmbat jstartup mode=integrated
StartServerbat
End of Windows |
Only valid for IBM i5OSUNIX |
cd ltsdm_homegt
StopServersh
sdmsh jstartup mode=standalone
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2260 CUSTOMER 2012-08-30
sdmsh filetransferdir dir=ltnew_dirgt
sdmsh jstartup mode=integrated
StartServersh
End of IBM i5OSUNIX |
6 To prevent deployment errors during the update process proceed as follows
1 Log on to the Central Instance host
2 Start the ConfigTool and in the navigation area choose Cluster-data Global server configuration
Managers ServiceManager
3 In the Global properties panel set the Custom value of the EventTimeout property to 120
4 Choose Save
5 Restart the Central Instance
7 Check whether the used JDK version and the Java VM settings of the Java runtime system comply
with the requirements in SAP Note 723909 Update the JDK and adjust the settings if necessary
NOTE
An update of the used JDK version possibly changes the JVM path In this case you must
make the new path available to all Dialog Instances of the J2EE engine by implementing option
1 of SAP Note 718901
8 Make sure that the J2EE administrator password stored in the secure store for offline usage is
identical with the one stored in the User Management Engine (UME) You can change the password
in the secure store as described in SAP Note 870445
9 If you are running a high availability system on Windows you might need to prepare your system
as described in the online documentation for JSPM see section Preparing Systems That Run in High
Availability Environment
223 Updating the Application Server Java and Java-Based Components
Procedure
Applying a Support Package Stack to SAP NetWeaver Application Server Java and Java-Based Components
NOTE
The JSPM GUI might not work properly on some UNIX systems For more information and the
solution see SAP Note 1013976
1 Log on as user ltsapsidgtadm to the Central Instance host
NOTE
If your operating system is IBM i log on as user ltSIDgtADM or ltSIDgtOFR
2 Close the SAP Management Console (SAP MMC) and the SDM remote GUI client
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2360
3 For UNIX and Windows To start the JSPM navigate to the directory ltINSTDIRgtltSIDgt
ltCentral_Instance_Namegtj2eeJSPM and run the go script file
NOTE
If your system is running on IBM i to start the JSPM proceed as follows
1 To prevent JSPM from automatically starting its GUI in the file usrsapltSIDgt
ltCentral_Instance_Namegtj2eeJSPMparamjspm_configtxt change the
property dialogSDTServerConnectionSDTGuilaunch from true to false
2 On the IBM i host run the go script file using the following command
QSH CMD(usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPMgo)
3 In the mounted directory usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPM run
the StartGui script file The JSPM GUI appears
4 In the Host field enter the target IBM i host
NOTE
Depending on the system type ltCentral_Instance_Namegt has the following syntax
Standalone Java system JCltinstance_nogt
Add-On system DVEBMGSltinstance_nogt
4 Enter your SDM password to log on to the SDM
5 On the Deployment tab page select the Java Support Package Manager option and update the software
component sapcomJSPM to the target SPS level
6 Restart the JSPM and log on with the SDM password
RECOMMENDATION
We strongly recommend that you use the Support and Enhancement Package Stack option when
applying a Support Package Stack Other options can lead to unintended consistency issues
NOTE
If you need to include the latest patches for a particular component during the update process
with the Support and Enhancement Package Stack option stop the JSPM after restart and apply SAP
Note 1080821 Then start the JSPM again
7 On the Deployment tab page select the Support and Enhancement Package Stack option and choose Next
The Support Package Stacks that are available for deployment in the global EPS inbox directory
are displayed
8 In the Target SP Stack Level dropdown box select the Support Package Stack to be applied and choose
Next
In this step JSPM performs various status validations and displays the result of each software
component included in the stack definition XML file on the subsequent screen which includes
the following possible statuses
OK Indicates that the SPS level of the corresponding software component is applicable
WARNING We recommend that you view the details about the component by choosing Show
Details
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2460 CUSTOMER 2012-08-30
This status may indicate that the corresponding software component comprises custom
modifications in an NWDI-controlled system
If your system is used for NWDI development and it is either a DEV or a CONS system
you will be informed that JSPM will not deploy the modified software components but
only transport them to the CMS transport directory JSPM will deploy only the software
components that are not modified
If your system is not used for NWDI development or if your system is used for NWDI
development and it is either a TEST or a PROD system you will be informed that JSPM
has found newer versions of modified software components and will automatically replace
the original versions with the newer versions JSPM will deploy all software components
that are not modified together with the replaced versions of the modified software
components
CAUTION
You may get a warning telling you that there are patches installed in your system
containing fixes which might not be included in the target SP Stack This is possible if
you have applied patches of the start SP Stack level that were delivered later than the
target SP Stack delivery date In order not to lose these fixes you need to download and
apply the corresponding patches of the target SP Stack level
If you are performing an update from SAP NetWeaver 70 including enhancement
package 1 SPS00 and you have not applied any patches for the software component with
status WARNING before the update then you can ignore warnings such as the following
example
The new version of the development component sapcomcomsapnetweaver
bcrfmoni is 70100200806121227180000 and is lower than the already
deployed version 70100200807090143420000
REVISE Indicates inconsistencies with the corresponding software component
The deployment cannot be performed until all problems have been resolved You can view
the problems by choosing Show Details
9 If the status of the selected SP Stack is OK or WARNING you can start the system update by choosing
Start JSPM then changes the status to SCHEDULED
If the SP Stack to be applied includes a kernel update and the current kernel is not already of the
corresponding patch level JSPM arranges the kernel update as the very first Support Package to
be applied JSPM updates the kernel binaries of all instances (including Dialog Instances and SCS
instances in a HA environment) whose kernel directories DIR_CT_RUN effectively reside on the host
indicated by the profile parameter SAPGLOBALHOST
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2560
CAUTION
Kernel binaries of instances whose kernel directories DIR_CT_RUN are not effectively linked
to the host SAPGLOBALHOST must be updated individually as described in section Manually
Updating Instances with Kernel Directory Located on Separate Hosts below
The kernel update (includes update of SAP Kernel and SAP IGS) using JSPM consists of the following
steps
1 JSPM stops the Central Instance automatically and prompts you to stop the remote SCS and
Dialog Instances manually
2 After you have stopped all the instances choose the Next button in the dialog box
The kernel update starts
NOTE
If the system is running in a high availability environment make sure that the HA
software does not restart the instance automatically during the update
NOTE
If kernel binaries of the SCS instance need to be updated manually (see Manually Updating
Instances with Kernel Directory Located on Separate Hosts below) you must perform this at the
time when JSPM is updating the kernel binaries of the Central Instance In any case the
SCS kernel must be up-to-date before the next restart
When the kernel update is finished a dialog box appears in which you are prompted to restart
the SCS instance manually
3 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries
before you can proceed with the next step For more information see Adjusting the Ownership and
Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
4 Choose Next in the dialog box when the SCS instance is running again
After the kernel update JSPM restarts the system for further deployment of the remaining Support
Packages in the stack
RECOMMENDATION
If you need to update the kernel binaries of any Dialog Instances manually (see Manually
Updating Instances with Kernel Directory Located on Separate Hosts below) perform the update when
JSPM is updating the remaining Support Packages in the stack in order to save time
The deployment of each Support Package can end with one of the following statuses
DEPLOYED
The Support Package has been successfully deployed
DEPLOYED WITH WARNING
The Support Package has been deployed but it possibly may not work properly with other
deployed components
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2660 CUSTOMER 2012-08-30
You can view the details by choosing Show Details or examining the log files You can also view
the details about the component by choosing the Deployed Components tab page
ERROR
An error has occurred during the deployment You can view the details by choosing Show
Details or examining the log files
You must correct the error to be able to continue with the SP Stack update
You can proceed as described for a deployment that finished with status DEPLOYED WITH
WARNING
If the error correction does not change the contents in the JSPM inbox you can continue
the deployment by choosing Resume
If the error correction changes the contents in the JSPM inbox you can choose New
Deployment to redeploy the SP Stack
NOT DEPLOYED
JSPM has not attempted to deploy the software component for certain reasons
If your system is not used for NWDI development you can proceed as described for a
deployment that finished with status ERROR
If your system is used for NWDI development and it is either a DEV or a CONS system
the status of the modified software components is always NOT DEPLOYED JSPM has
transported the software components of the Support Package Stack both modified and
not modified to the CMS transport directory The deployment of the modified software
components is handled by NWDI
Manually Updating Instances with Kernel Directory Located on Separate Hosts
JSPM performs kernel update for all instances (including Dialog Instances and SCS instances in a HA
environment) whose kernel directories DIR_CT_RUN effectively reside on the host indicated by the profile
parameter SAPGLOBALHOST (by using folder sharing on Windows or file system mounting on UNIX) In
rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of those sort of instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances individually
To update the kernel of an instance manually proceed as follows
1 Log on as user ltsapsidgtadm to the host of the instance to be updated
2 Back up the kernel directory which is specified by the profile parameter DIR_CT_RUN
3 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory with
SAPCAR [page 56]
4 Stop the instance being updated
NOTE
If the system is running in a HA environment make sure that the HA software does not
restart the instance automatically during the update
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2760
5 Copy or move the extracted programs from the temporary directory to the local kernel directory
6 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries as
described in section Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
7 Restart the instance after JSPM has finished the deployment of all packages on the Central Instance
Only valid for UNIX |
Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms
On UNIX platforms you must adjust the ownership and execution permissions of the kernel binaries
after the update regardless whether you performed the update manually or by using JSPM because
both update procedures are performed with the ltsapsidgtadm user Enter the following command
sequence
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
224 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the Java system
23 Parallel Update of Dual-Stack Systems
If you perform an update of a dual-stack system (ABAP+Java) we recommend that you follow the
procedure described below The procedure has been validated to update the ABAP stack and the Java
stack of a NetWeaver system in parallel thus reducing the overall system downtime by half
Procedure
1 Before applying ABAP and Java Support Packages use the Single Support Packages option in JSPM and
select for update only the components SAP KERNEL and BC-FES-IGS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
23 Parallel Update of Dual-Stack Systems
2860 CUSTOMER 2012-08-30
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS)
runs on a dedicated host In this case JSPM does not support update of kernel binaries and
you need to update them manually Perform the update manually as described under Updating
SAP Kernel and SAP IGS in section Updating the Application Server ABAP and ABAP-Based Software
Components [page 16]
2 Import the Support Packages for the component SAP_BASIS into the ABAP stack using the ABAP
Support Package Manager (SPAM)
3 Import the remaining ABAP Support Packages with SPAM and in parallel apply the Java Support
Package Stack with JSPM
Proceed as described in Updating the Application Server ABAP and ABAP-Based Software Components [page
16] and Updating the Application Server Java and Java-Based Software Components [page 23]
24 Process Integration
241 Planning
Procedure
This section covers all the units of Process Integration that should be updated Particularly the following
units must always have the same Support Package level (the patch level can be different)
Integration Server
XI Adapter Engine
Partner Connectivity Kit
System with the Usage Type Process Integration
Software components of Integration Server
Components to Be Updated SP File Name Tool Used to Apply SP
Java stack
XI TOOLS 702 SAPXITOOLltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
ABAP stack
XI CONTENT SAP_BASIS 702 SAPBASISltSPgt_ltPLgtZIP File upload
XI CONTENT SAP_ABA 702 SAPABAltSPgt_ltPLgtZIP
SAP NetWeaver Application Server ABAP (see table Software components of Application Server ABAP [page 15])Note that update of the following software components of the ABAP system is not required SAP ABA 702 SAP BW 702 PI_BASIS 702
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 2960
J2EE Adapter Engine
If your implemented scenario includes a J2EE Adapter Engine then it must always be of the same
Support Package level as the Integration Server
Components of the J2EE Adapter Engine
Component to Be Updated SP File NameTool Used to Apply SP
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
J2SE Adapter Engine
The installation of the J2SE Adapter Engine depends on the implemented scenario
Components of the J2SE Adapter Engine
Component to Be Updated SP File Name Tool Used to Apply SP
XI CONNECTIVITY SE 702 SAPXICONSltSPgt_ltPLgtSCA ZIP tool (for example WinZip)
Partner Connectivity Kit
If your implemented scenario includes a Partner Connectivity Kit (PCK) then it must always be of the
same Support Package level as the Integration Server
Software components of Partner Connectivity Kit
Components to Be Updated SP File NameTool Used to Apply SP
XI PCK 702 SAPXIPCKltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of the Application Server Java [page 20])
System Landscape Directory (SLD)
The System Landscape Directory is required for the PI operations Although updating the SLD is not
necessarily required it is advisable to update the SLD server and the SAP Master Data Content within
it from time to time The update of the SLD includes
1 The system where the SLD is running
2 The SAP Master Data Content within this SLD
SAP GUI
See table Compatible SAP GUI Versions [page 51]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3060 CUSTOMER 2012-08-30
242 Updating Units of Process Integration
Procedure
Before you start the update perform the following steps
In the Runtime Workbench use Communication Channel Monitoring to stop all sender channels
for all adapter types on all your Adapter Engines
On the Integration Server use transaction SMQR and deregister all qRFC queues
System with the Usage Type Process Integration
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the XI instance is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system where the XI instance is running
For more information see Application Server Java and Java-Based Software Components [page 19]
System Landscape Directory (Optional)
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the SLD is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the entire Support Package Stack to the system where the SLD is running
For more information see Application Server Java and Java-Based Software Components [page 19]
J2EE Adapter Engine
Apply the Support Package Stack to the system where the Adapter Engine is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Partner Connectivity Kit
Apply the Support Package Stack to the system where the PCK is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Front End GUIs
Update the SAP GUI components if necessary
For more information see SAP GUI Family [page 51]
ABAP 700 Business System (Optional)
Apply the Support Packages for SAP NetWeaver Application Server ABAP (including SAP kernel and
the Support Package for SAP BASIS 700)
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 640 Business System (Optional)
Apply the Support Packages for SAP Web Application Server ABAP 640 (including SAP kernel and the
Support Package for SAP BASIS 640)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3160
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 620 Business System (Optional)
1 Update the SAP Kernel 620
2 Import the released Basis Support Packages for SAP Web AS 620 as well as the most recent Add-
On Support Package for APPINT 200_620 in the order described in SAP Note 439915
J2SE Adapter Engine (Optional)
NOTE
The XI Adapter Engine (J2SE) and all its adapters are provided for compatibility reasons only and
are not developed any further You have to use the XI Adapter Engine running on SAP NetWeaver
AS Java For more information see the Master Guide ndash SAP NetWeaver 70 available on SAP Service
Marketplace at httpservicesapcominstallNW70 Planning
1 Extract the SAPXICONSltSPgt_ltPLgtSCA (XI Connectivity SE 700) archive (ZIP format) to a temporary
directory
2 Save the old configuration files as described in the document Adapterpdf in directory
lttemp_directorygttech_adapterAdministrationDocumentation
3 Unpack the ZIP archive TechnicalAdapterssda to the installation directory of the XI Adapter
Engine (J2SE)
4 Restore the configuration files with restore_configuration
243 Post-Installation Steps
Procedure
Communication Channels and Queues
Restart all stopped sender channels and register all deregistered qRFC queues
XI Content
In the system with usage type PI import the XI content from the archives SAPBASISltSPgt_ltPLgtZIP
and SAPABAltSPgt_ltPLgtZIP as follows
1 Unpack the archives using a ZIP tool of your choice
2 Copy the corresponding export files (with file extension tpz) to the import directory ltINSTDIRgt
ltSAPSIDgtSYSglobalxirepository_serverimport
3 Start the Integration Builder (transaction SXMB_IFR)
4 Enter the Integration Repository by choosing Repository (Design)
5 Choose Tools Import design objects
6 Import the tpz files containing the XI content
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3260 CUSTOMER 2012-08-30
NOTE
For more information see SAP Note 836200
Role Generation on the Integration Server
On the Integration Server execute transaction SUPC (mass generation of roles) for all SAP_XI roles in
each of your clients to regenerate possibly changed roles
NOTE
Do not forget to make a user comparison for regenerated roles afterwards
Partner Connectivity Kit (Optional)
Perform the post-installation steps for PCK as described in SAP Note 746328
SAP Master Data within the SLD (Optional)
In the system where your SLD is running import the latest SLD content as described in SAP Note
669669
Receiver-Based EOIO Serialization in J2EE Adapter Engine (Optional)
The J2EE Adapter Engine can be switched to receiver-based EOIO serialization The switch can be
triggered on demand and is executed asynchronously It includes a database migration step during
which all EOIO processing in the Adapter Engine is disabled See SAP Note 973894 for details about how
to start the EOIO serialization migration
Service Metering (Optional)
Service metering gathers information about a service caller transfers it to the service provider and
counts on the service provisioning side how many times a service is called and by which service caller
Service metering is performed for the XI message protocol and the WS message protocol Service
metering is automatically enabled after applying a Support Package Stack By default only non-sensitive
data is transmitted to internal or external service providers in a compatible way
Service metering can be configured in PI in the Integration Engine on sender-side and in the Integration
Directory
Service metering can be configured in AS ABAP in transaction SOAMANAGER
Only if the service provider is allowed to receive more detailed information about the service caller set
the metering level to higher than the default
For more information see SAP Note 1239428
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3360
25 Business Intelligence
251 Planning
Procedure
Business Intelligence includes one or many of the following units that must be updated depending on
your implemented scenarios The usage types Business Intelligence (BI) and Business Intelligence Java
Components (BI-Java) must always have the same Support Package level
Business Intelligence
Software Components of Business Intelligence
Component to Be Updated SP File Name Tool Used to Apply SP
BI CONT ADDON 70x SAPK-70ltxgtltSPgtINBICONT SAINT
SAP NetWeaver Application Server ABAP (see table Software Components of Application Server ABAP [page 15])
NOTE
For information about the dependencies applying to BI Content Support Packages see SAP Note
653814 BI CONT 703 Support Packages are not part of the NetWeaver SP Stacks Updates can be
performed when applicable Alternatively BI CONT 704 Support Packages can be imported See
the BI Content release strategy in SAP Note 153967
Business Intelligence Java Components
BI Java Components
Component to Be Updated SP File NameTool Used to Apply SP
BI REPORTING AND PLANNING 702 BIREPPLANltSPgt_ltPLgtSCA JSPM
BI WEBDYNPRO ALV 702 BIWDALVltSPgt_ltPLgtSCA
BI INFORM BROADCASTING 702 BIIBCltSPgt_ltPLgtSCA
BI WEB APPLICATIONS 702 BIWEBAPPltSPgt_ltPLgtSCA
BI BASE SERVICES 702 BIBASESltSPgt_ltPLgtSCA
VISUAL COMPOSER BI KITS 702 VCKITBIltSPgt_ltPLgtSCA
Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
BI Precalculation Service
Components of the BI Precalculation Service
Component to Be Updated SP File Name Tool Used to Apply SP
BI Pre-calculation Service 700 xPreCalServerltSPgt_ltPLgtexe Installer
Search and Classification (TREX)
See table TREX Component [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3460 CUSTOMER 2012-08-30
BI Accelerator
The BI Accelerator is based on the TREX technology It is a special Linux 64-bit version of SAP NetWeaver
70 Search and Classification (TREX) which is delivered on preconfigured hardware
NOTE
You cannot use a TREX installation based on 32-bit architecture that is configured for searching
in metadata and documents for the BI Accelerator And vice versa a BI Accelerator box cannot
be used for searching in metadata and documents
If you want to use the search functionality as well as the BI Accelerator you require two separate
installations For more information see BI Accelerator [page 47]
Clients
Depending on your implemented scenarios you have to update SAP GUI Components and Business
Explorer (BI Add-OnBW Add-On)
NOTE
See SAP Note 889314 to determine when to use the BI Add-On and the BW Add-On
NOTE
As SAP GUI 640 is no longer supported BI Frontend Support Package 1800 resp patch 1801 is the
last Support Package resp patch based on SAP GUI 640 For more information see SAP Note
1231292 (Frontend Add-in Strategy 640710 GUI Version)
For more information about the new release strategy for the BI Frontend see SAP Note 1231363
(Changed Delivery Strategy for BI Frontend)
252 Preparation
Procedure
For the Support Packages of the most important Business Intelligence units so called SAPBINews
(SAPBWNews) Notes are created Read these Notes before updating Business Intelligence For SAP
NetWeaver 70 including enhancement package 2 SPS 12 these are the following
Business Intelligence ABAP SAP Note 1680996
Business Intelligence Java Components SAP Note 1726461
BI 70 Frontend Add-On for SAP GUI 710 SAP Note 1413032
BI 70 Frontend Add-On for SAP GUI 720 SAP Note 1630112
BI 70 Frontend Add-On for SAP GUI 730 SAP Note 1726739
For more information about BI Support Packages see SAP Community Network at http
scnsapcomcommunitydata-warehousingnetweaver-bw Related Resources SAP NW BW Support
Packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
2012-08-30 CUSTOMER 3560
253 Updating Units of Business Intelligence
Procedure
Business Intelligence
1 Update the SAP NetWeaver Application Server ABAP (with BI CONT 70x if necessary) with the
appropriate Support Packages
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
NOTE
When applying the component SAP BW 702 some generation errors might occur When
you start importing the BI Support Packages in transaction SPAM choose the menu path
Extras Ignore generation errors For more information see SAP Note 114134
2 Apply the Support Package Stack to the system with the usage type BI-Java
For more information see Application Server Java and Java-Based Software Components [page 19]
3 Update the BI Precalculation Service that is used in your scenario
4 Update the standalone engine Search and Classification (TREX) that is used in your scenario For more
information see Standalone Engine Search and Classification (TREX) [page 44]
NOTE
You have to update TREX to the newest version if you use search capabilities within Business
Intelligence
5 Update the BI Accelerator to the newest available version For more information see BI
Accelerator [page 47]
6 Update the SAP GUI and Business Explorer (BI Add-On BW Add-On) on all remote client hosts
that are involved in the scenario
For more information see SAP GUI Family [page 51] and Business Explorer (BI Add-On BW Add-On)
[page 51]
BI Precalculation Service
1 Log on to the host as a user with administration rights
2 Install the Support Package of the BI Precalculation Service by executing the
xPreCalServerexe file
The welcome screen of the BI Precalculation Server setup wizard appears
The setup now checks the system for the prerequisites
3 Choose the option Update for updating the BI Precalculation service to the current patch level and
then Finish
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3660 CUSTOMER 2012-08-30
26 EP Core
261 Planning
Procedure
The following installable software units must be updated
EP Core
Software Components of EP Core
Component to Be Updated SP File Name Tool Used to Apply SP
PORTAL CORE SERVICES 702 EPBCltSPgt_ltPLgtSCA JSPM
PORTAL FRAMEWORK 702 EPBC2ltSPgt_ltPLgtSCA
PORTAL 702 EPPSERVltSPgt_ltPLgtSCA
PORTAL WEB DYNPRO 702 EPWDCltSPgt_ltPLgtSCA
UWL COLL PROCESS ENGINE 702 UWLJWFltSPgt_ltPLgtSCA
CAF EU 702 SAPEUltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
262 Preparation
Procedure
Backing Up the Portal Runtime Configuration
If you have made changes to the standard Portal Runtime configuration you have to make a backup
of the configuration before the update process For more information see SAP Note 1064468
263 Updating EP Core
Procedure
Apply the Support Package Stack to a system with usage type EP Core
For more information see Application Server Java and Java-Based Software Components [page 19]
264 Post-Installation Steps for EP Core
Procedure
Restoring the Portal Runtime Configuration
To make your changes to the standard Portal Runtime Configuration effective you have to restore
the backup of the configuration done before the update process For more information see SAP Note
1064468
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
26 EP Core
2012-08-30 CUSTOMER 3760
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
This chapter describes how to apply Support Packages to installable software units of SAP NetWeaver
70 including enhancement package 2 SAP NetWeaver distinguishes three types of installable software
units
Systems with one or multiple usage types
Standalone engines
Clients
A scenario implementation usually involves several installed software units
RECOMMENDATION
We strongly recommend that you always update all software units belonging to one scenario
together in order to retain a consistent system state Due to the fact that some installable software
units can be commonly shared in different scenarios you must consequently update all scenarios
using the common software units at the same time
21 Application Server ABAP and ABAP-Based Software Components
211 Planning
Procedure
The following components belong to the usage type SAP NetWeaver Application Server ABAP
Software Components of Application Server ABAP
Component to Be Updated SP File Name Tool Used to Apply SP
SAP KERNEL 720 32-64-BIT Non-UNICODEUNICODE SAPEXESAR
SAPEXEDBSAR
JSPMmanually
SAP IGS 700 igsexesar
SAP ABA 702 SAPKA702ltSPgt SPAMSAINT
SAP BASIS 702 SAPKB702ltSPgt
SAP BW 702 SAPKW702ltSPgt
PI_BASIS 702 SAPK-702ltSPgtINPIBASIS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
2012-08-30 CUSTOMER 1560
NOTE
This table contains only software components that belong to the usage type AS ABAP Software
components of other usage types and application units are listed in the corresponding sections
NOTE
SAP delivers intermediate Support Packages for the component SAP BW 702 between two
subsequent SP levels besides the Support Packages delivered along with the Support Package
Stacks Therefore the highest SP level of SAP BW 702 does not necessarily match the target SP
Stack level
CAUTION
When applying a Support Package Stack to a dual-stack system (ABAP+Java) the Java Support
Package Manager (JSPM) will necessarily restart the system several times to make the changes
effective The ABAP part will only be restarted when JSPM is updating the SAP kernel and IGS
212 Preparation
Procedure
Read SAP Note 822379 and all related SAP Notes that the first one refers to
213 Updating the Application Server ABAP and ABAP-Based Software Components
Procedure
Applying Support Packages to SAP NetWeaver Application Server ABAP and ABAP-Based Components
You can update the SAP NetWeaver Application Server ABAP and all ABAP-based software components
running on it using the Support Package Manager (transaction SPAM)
NOTE
If a particular Support Package Stack requires the installation or upgrade of some add-on
components you must use the ABAP Add-on Installation Tool (transaction SAINT) instead of the
Support Package Manager In this case SAINT is able to import both the add-on components and
the related Support Packages of ordinary SAP components
Proceed as follows
1 Log on to the SAP NetWeaver AS system with client 000
2 Start the Support Package Manager by calling transaction SPAM or
start the Add-On Installation Tool by calling transaction SAINT
3 Load the relevant Support Packages or add-on installation packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
1660 CUSTOMER 2012-08-30
4 Define an import queue
5 Perform the import of the defined queue
NOTE
If you have modified SAP objects in your system and these objects are included in the Support
Packages you must perform modification adjustment during the import using the
transactions SPDD (for ABAP Dictionary objects) and SPAU (for Repository objects)
To import the queue you use the standard scenario You can choose between the conventional
import mode and downtime-minimized import mode
Conventional Import Mode
This option comprises the following steps
1 Update the SAP kernel and SAP IGS as described in section Updating SAP Kernel and SAP IGS below
Start the system after the kernel update
2 Import the ABAP Support Packages with the Support Package Manager (SPAM)
Import Mode Downtime-Minimized
This option can be used to reduce system downtime during the update It comprises the following
steps
1 In transaction SPAM enable the downtime-minimized import mode by choosing Extras
Settings then on the Import queue tab page choose Standard and activate the option Import Mode
Downtime-Minimized
2 Import the ABAP Support Packages into the system in an inactive state in the downtime-minimized
mode during system uptime
3 Update the SAP kernel and SAP IGS as described in section Updating SAP Kernel and SAP IGS below
Start the system after the kernel update
4 Complete the ABAP Support Packages import
CAUTION
During this step the system cannot carry out any business transactions (business downtime)
NOTE
In rare cases due to the dependencies of some Support Packages on a particular kernel patch level
the downtime-minimized update does not work In such cases the Support Package Manager
informs you that you must update the SAP kernel before importing ABAP Support Packages You
must proceed with the conventional import procedure
Updating SAP Kernel and SAP IGS
In general the SAP kernel and IGS binaries are located in the global kernel directory DIR_CT_RUN on
the host indicated by the profile parameter SAPGLOBALHOST Once the files in this directory have been
updated to a new patch level a system restart distributes them by means of the program SAPCPE to the
local directories DIR_EXECUTABLE on the hosts where the instances of the SAP system are running
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
2012-08-30 CUSTOMER 1760
CAUTION
The automatic distribution by means of SAPCPE depends on the settings of the profile parameters
DIR_CT_RUN for the global kernel directory and DIR_EXECUTABLE for the local directory of the
executables Before you continue check the instance profiles for the settings of these parameters
in systems that are not installed using SAPinst (for example systems upgraded from older releases
copied or migrated systems)
CAUTION
If your system is a dual-stack system (ABAP+Java) and the ABAP stack has a non-Unicode kernel
be aware that the SCS instance has a Unicode kernel You have to update both kernels (together
with SAP IGS) prior to updating the ABAP and Java Support Package stacks This ensures
compatibility and reduces system downtime
RECOMMENDATION
If you perform an update of a dual-stack system (ABAP+Java) we recommend that prior to
applying ABAP and Java Support Package stacks you use the Single Support Packages option in JSPM
and select for update only the components SAP KERNEL and BC-FES-IGS
For more information about updating a dual-stack system see Parallel Update of Dual-Stack Systems
[page 28]
If you perform an update of an ABAP system the following procedure applies for updating the SAP
kernel and IGS manually
1 Log on as user ltsapsidgtadm to the instance host to be updated
2 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory using
SAPCAR [page 56]
3 Stop the ABAP system that you want to update
NOTE
If the system is running in a high availability (HA) environment make sure that the HA
software does not restart the system automatically during the update
4 Back up the kernel directory ltkrnl_directorygt
5 Copy or move the extracted programs from the temporary directory to the SAP kernel directory
6 Only valid for UNIX |
Execute the following command sequence on UNIX platforms
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
1860 CUSTOMER 2012-08-30
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
7 Restart the SAP system
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS) runs
on a dedicated host You need to perform the kernel update for the ASCS instance manually but
excluding the IGS update because the IGS is not required in an ASCS instance
In rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of such instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances manually Proceed as described
in section Manually Updating Instances with Kernel Directory Located on Separate Hosts below in this document
214 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the ABAP system
22 Application Server Java and Java-Based Software Components
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system which includes
JSPM itself
SAP Kernel and SAP IGS
All Java-based usage types installed in the system
Software Deployment Manager (SDM) - the deployment service of the system
RECOMMENDATION
We strongly recommend that you apply the target Support Package Stack to your system as a
whole This ensures consistency on both the system and the application levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 1960
221 Planning
Procedure
Java Support Package files (SCAs) contain all software objects of the corresponding software
components Thus it is sufficient to apply the Java Support Package files of the intended Support Package
Stack directly to the Java system to be updated It is not necessary to apply the Support Package Stacks
between the start SP Stack level and the target SP Stack level successively
CAUTION
When applying a Support Package Stack to a Java system the Java Support Package Manager (JSPM)
will necessarily restart the system several times to make the changes effective With a dual-stack
system (ABAP+Java) the ABAP part will only be restarted when JSPM is updating the SAP kernel
and IGS
The following components belong to the usage type SAP NetWeaver Application Server Java (AS Java)
Software Components of Application Server Java
Component to Be Updated SP File Name Tool Used to Apply SP
SAP Kernel 720 32-64-BIT UNICODE SAPEXESAR
SAPEXEDBSAR
JSPM
SAP IGS 700 igsexesar
BI META MODEL REPOSITORY 702 BIMMRltSPgt_ltPLgtSCA
J2EE ENGINE CORE TOOLS 702 CORETOOLSltSPgt_ltPLgtSCA
J2EE ENGINE BASE TABLES 702 BASETABLESltSPgt_ltPLgtSCA
BI UDI 702 BIUDIltSPgt_ltPLgtSCA
DI BUILD TOOL 702 SAPBUILDTltSPgt_ltPLgtSCA
SAP CAF 702 CAFltSPgt_ltPLgtSCA
SAP IKS 702 KMKWJIKSltSPgt_ltPLgtSCA
JAVA LOG VIEWER 702 JLOGVIEWltSPgt_ltPLgtSCA
SAP J2EE ENGINE CORE 702 SAPJEECORltSPgt_ltPLgtSCA
SAP JAVA TECH SERVICES 702 SAPJTECHSltSPgt_ltPLgtSCA
SAP TECH S OFFLINE 702 SAPJTECHFltSPgt_ltPLgtSCA
SAP J2EE ENGINE 702 SAPJEEltSPgt_ltPLgtSCA
JAVA SP MANAGER 702 JSPMltSPgt_ltPLgtSCA
ADOBE DOCUMENT SERVICES 702 ADSSAPltSPgt_ltPLgtSCA
UME ADMINISTRATION 702 UMEADMINltSPgt_ltPLgtSCA
LIFECYCLE MGMT TOOLS 702 LMTOOLSltSPgt_ltPLgtSCA
SAP CAF-UM 702 CAFUMltSPgt_ltPLgtSCA
SAP SOFTW DELIV MANAGER 702 SDMKITltSPgt_ltPLgtJAR
SOFTWARE LIFECYCLE MANAGER 702 SWLIFECYCLltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2060 CUSTOMER 2012-08-30
NOTE
This table contains only software components that belong to the usage type AS Java Software
components of other usage types and Java application units are listed in the corresponding
sections
NOTE
As of Support Package 09 you can update your system with SAP Kernel 720 instead of SAP Kernel
701
222 Preparation for Applying a Support Package Stack
Procedure
1 Download the Support Package Stack with all usage types to be updated and the stack definition
XML file as described in Downloading Support Package Stacks [page 12]
NOTE
You can find the activated usage types in an existing Java system on the Deployed Components tab
page on the JSPM user interface
NOTE
You do not need to download the SP Stacks between the source SP Stack level and target SP
Stack level By default the target SP Stack level is the latest available SP Stack
2 Make sure the following requirements are met prior to applying the Support Package Stack
You have familiarized yourself with SAP Note 891983 before you start the Java Support Package
Manager
The system to be updated is fully functional
The Support Package Stack you want to apply and the corresponding stack definition XML
file are available in the EPS inbox directory usrsaptransEPSin By default this location
can be also referred to as ldquoJSPM inboxrdquo
The SAP NetWeaver Application Server Java (AS Java) and the database have been backed up
You have not deleted renamed or created any directories and files in the following directories
and their subdirectories usrsapltSAPSIDgtSYSexe and usrsapltSAPSIDgtSYS
profile
Otherwise JSPM cannot detect the kernel and the system profiles and cannot be started If a
backup of the kernel and the system profiles has been required it has been created in a different
directory
The ltsapsidgtadm user has Read permissions for the EPS inbox directory usrsaptransEPS
in
If your database is SAP MaxDB the overwrite mode for the log area has been activated
The database and the SDM repository have been synchronized
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2160
For more information see the online documentation for JSPM on SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70 Library
(including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library Administrators Guide
Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems AS Java
(Application Server for Java) Software Logistics Software Maintenance Java Support Package Manager
Then choose Troubleshooting JSPM Does Not Update the Versions of the Deployed Components
There is enough disk space
For more information see SAP Note 891895
Your current SAPCAR tool is able to extract the Support Packages for the SAP kernel and
other OS level binaries delivered as SAR files
RECOMMENDATION
You can download the latest version of SAPCAR from SAP Service Marketplace at
httpservicesapcompatches Entry by Application Group Additional Components
SAPCAR
Put the downloaded version in the same directory in the JSPM inbox in which the kernel
SAR files reside so that JSPM can use this version for extracting the SAR files
3 Only valid for Linux |
For RHEL 4 and SLES 9 you need to install additional operating system packages For more
information see SAP Note 1021236End of Linux |
4 Only valid for Windows |
For Windows you need to install additional operating system packages For more information see
SAP Note 684106End of Windows |
5 To prevent the Software Deployment Manager (SDM) from temporarily exceeding the available
disk space during the update process you can change the file transfer directory of SDM in a system
of SPS09 or higher using the following command sequence
Only valid for Windows |
cd ltsdm_homegt
StopServerbat
sdmbat jstartup mode=standalone
sdmbat filetransferdir dir=ltnew_dirgt
sdmbat jstartup mode=integrated
StartServerbat
End of Windows |
Only valid for IBM i5OSUNIX |
cd ltsdm_homegt
StopServersh
sdmsh jstartup mode=standalone
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2260 CUSTOMER 2012-08-30
sdmsh filetransferdir dir=ltnew_dirgt
sdmsh jstartup mode=integrated
StartServersh
End of IBM i5OSUNIX |
6 To prevent deployment errors during the update process proceed as follows
1 Log on to the Central Instance host
2 Start the ConfigTool and in the navigation area choose Cluster-data Global server configuration
Managers ServiceManager
3 In the Global properties panel set the Custom value of the EventTimeout property to 120
4 Choose Save
5 Restart the Central Instance
7 Check whether the used JDK version and the Java VM settings of the Java runtime system comply
with the requirements in SAP Note 723909 Update the JDK and adjust the settings if necessary
NOTE
An update of the used JDK version possibly changes the JVM path In this case you must
make the new path available to all Dialog Instances of the J2EE engine by implementing option
1 of SAP Note 718901
8 Make sure that the J2EE administrator password stored in the secure store for offline usage is
identical with the one stored in the User Management Engine (UME) You can change the password
in the secure store as described in SAP Note 870445
9 If you are running a high availability system on Windows you might need to prepare your system
as described in the online documentation for JSPM see section Preparing Systems That Run in High
Availability Environment
223 Updating the Application Server Java and Java-Based Components
Procedure
Applying a Support Package Stack to SAP NetWeaver Application Server Java and Java-Based Components
NOTE
The JSPM GUI might not work properly on some UNIX systems For more information and the
solution see SAP Note 1013976
1 Log on as user ltsapsidgtadm to the Central Instance host
NOTE
If your operating system is IBM i log on as user ltSIDgtADM or ltSIDgtOFR
2 Close the SAP Management Console (SAP MMC) and the SDM remote GUI client
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2360
3 For UNIX and Windows To start the JSPM navigate to the directory ltINSTDIRgtltSIDgt
ltCentral_Instance_Namegtj2eeJSPM and run the go script file
NOTE
If your system is running on IBM i to start the JSPM proceed as follows
1 To prevent JSPM from automatically starting its GUI in the file usrsapltSIDgt
ltCentral_Instance_Namegtj2eeJSPMparamjspm_configtxt change the
property dialogSDTServerConnectionSDTGuilaunch from true to false
2 On the IBM i host run the go script file using the following command
QSH CMD(usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPMgo)
3 In the mounted directory usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPM run
the StartGui script file The JSPM GUI appears
4 In the Host field enter the target IBM i host
NOTE
Depending on the system type ltCentral_Instance_Namegt has the following syntax
Standalone Java system JCltinstance_nogt
Add-On system DVEBMGSltinstance_nogt
4 Enter your SDM password to log on to the SDM
5 On the Deployment tab page select the Java Support Package Manager option and update the software
component sapcomJSPM to the target SPS level
6 Restart the JSPM and log on with the SDM password
RECOMMENDATION
We strongly recommend that you use the Support and Enhancement Package Stack option when
applying a Support Package Stack Other options can lead to unintended consistency issues
NOTE
If you need to include the latest patches for a particular component during the update process
with the Support and Enhancement Package Stack option stop the JSPM after restart and apply SAP
Note 1080821 Then start the JSPM again
7 On the Deployment tab page select the Support and Enhancement Package Stack option and choose Next
The Support Package Stacks that are available for deployment in the global EPS inbox directory
are displayed
8 In the Target SP Stack Level dropdown box select the Support Package Stack to be applied and choose
Next
In this step JSPM performs various status validations and displays the result of each software
component included in the stack definition XML file on the subsequent screen which includes
the following possible statuses
OK Indicates that the SPS level of the corresponding software component is applicable
WARNING We recommend that you view the details about the component by choosing Show
Details
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2460 CUSTOMER 2012-08-30
This status may indicate that the corresponding software component comprises custom
modifications in an NWDI-controlled system
If your system is used for NWDI development and it is either a DEV or a CONS system
you will be informed that JSPM will not deploy the modified software components but
only transport them to the CMS transport directory JSPM will deploy only the software
components that are not modified
If your system is not used for NWDI development or if your system is used for NWDI
development and it is either a TEST or a PROD system you will be informed that JSPM
has found newer versions of modified software components and will automatically replace
the original versions with the newer versions JSPM will deploy all software components
that are not modified together with the replaced versions of the modified software
components
CAUTION
You may get a warning telling you that there are patches installed in your system
containing fixes which might not be included in the target SP Stack This is possible if
you have applied patches of the start SP Stack level that were delivered later than the
target SP Stack delivery date In order not to lose these fixes you need to download and
apply the corresponding patches of the target SP Stack level
If you are performing an update from SAP NetWeaver 70 including enhancement
package 1 SPS00 and you have not applied any patches for the software component with
status WARNING before the update then you can ignore warnings such as the following
example
The new version of the development component sapcomcomsapnetweaver
bcrfmoni is 70100200806121227180000 and is lower than the already
deployed version 70100200807090143420000
REVISE Indicates inconsistencies with the corresponding software component
The deployment cannot be performed until all problems have been resolved You can view
the problems by choosing Show Details
9 If the status of the selected SP Stack is OK or WARNING you can start the system update by choosing
Start JSPM then changes the status to SCHEDULED
If the SP Stack to be applied includes a kernel update and the current kernel is not already of the
corresponding patch level JSPM arranges the kernel update as the very first Support Package to
be applied JSPM updates the kernel binaries of all instances (including Dialog Instances and SCS
instances in a HA environment) whose kernel directories DIR_CT_RUN effectively reside on the host
indicated by the profile parameter SAPGLOBALHOST
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2560
CAUTION
Kernel binaries of instances whose kernel directories DIR_CT_RUN are not effectively linked
to the host SAPGLOBALHOST must be updated individually as described in section Manually
Updating Instances with Kernel Directory Located on Separate Hosts below
The kernel update (includes update of SAP Kernel and SAP IGS) using JSPM consists of the following
steps
1 JSPM stops the Central Instance automatically and prompts you to stop the remote SCS and
Dialog Instances manually
2 After you have stopped all the instances choose the Next button in the dialog box
The kernel update starts
NOTE
If the system is running in a high availability environment make sure that the HA
software does not restart the instance automatically during the update
NOTE
If kernel binaries of the SCS instance need to be updated manually (see Manually Updating
Instances with Kernel Directory Located on Separate Hosts below) you must perform this at the
time when JSPM is updating the kernel binaries of the Central Instance In any case the
SCS kernel must be up-to-date before the next restart
When the kernel update is finished a dialog box appears in which you are prompted to restart
the SCS instance manually
3 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries
before you can proceed with the next step For more information see Adjusting the Ownership and
Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
4 Choose Next in the dialog box when the SCS instance is running again
After the kernel update JSPM restarts the system for further deployment of the remaining Support
Packages in the stack
RECOMMENDATION
If you need to update the kernel binaries of any Dialog Instances manually (see Manually
Updating Instances with Kernel Directory Located on Separate Hosts below) perform the update when
JSPM is updating the remaining Support Packages in the stack in order to save time
The deployment of each Support Package can end with one of the following statuses
DEPLOYED
The Support Package has been successfully deployed
DEPLOYED WITH WARNING
The Support Package has been deployed but it possibly may not work properly with other
deployed components
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2660 CUSTOMER 2012-08-30
You can view the details by choosing Show Details or examining the log files You can also view
the details about the component by choosing the Deployed Components tab page
ERROR
An error has occurred during the deployment You can view the details by choosing Show
Details or examining the log files
You must correct the error to be able to continue with the SP Stack update
You can proceed as described for a deployment that finished with status DEPLOYED WITH
WARNING
If the error correction does not change the contents in the JSPM inbox you can continue
the deployment by choosing Resume
If the error correction changes the contents in the JSPM inbox you can choose New
Deployment to redeploy the SP Stack
NOT DEPLOYED
JSPM has not attempted to deploy the software component for certain reasons
If your system is not used for NWDI development you can proceed as described for a
deployment that finished with status ERROR
If your system is used for NWDI development and it is either a DEV or a CONS system
the status of the modified software components is always NOT DEPLOYED JSPM has
transported the software components of the Support Package Stack both modified and
not modified to the CMS transport directory The deployment of the modified software
components is handled by NWDI
Manually Updating Instances with Kernel Directory Located on Separate Hosts
JSPM performs kernel update for all instances (including Dialog Instances and SCS instances in a HA
environment) whose kernel directories DIR_CT_RUN effectively reside on the host indicated by the profile
parameter SAPGLOBALHOST (by using folder sharing on Windows or file system mounting on UNIX) In
rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of those sort of instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances individually
To update the kernel of an instance manually proceed as follows
1 Log on as user ltsapsidgtadm to the host of the instance to be updated
2 Back up the kernel directory which is specified by the profile parameter DIR_CT_RUN
3 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory with
SAPCAR [page 56]
4 Stop the instance being updated
NOTE
If the system is running in a HA environment make sure that the HA software does not
restart the instance automatically during the update
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2760
5 Copy or move the extracted programs from the temporary directory to the local kernel directory
6 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries as
described in section Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
7 Restart the instance after JSPM has finished the deployment of all packages on the Central Instance
Only valid for UNIX |
Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms
On UNIX platforms you must adjust the ownership and execution permissions of the kernel binaries
after the update regardless whether you performed the update manually or by using JSPM because
both update procedures are performed with the ltsapsidgtadm user Enter the following command
sequence
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
224 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the Java system
23 Parallel Update of Dual-Stack Systems
If you perform an update of a dual-stack system (ABAP+Java) we recommend that you follow the
procedure described below The procedure has been validated to update the ABAP stack and the Java
stack of a NetWeaver system in parallel thus reducing the overall system downtime by half
Procedure
1 Before applying ABAP and Java Support Packages use the Single Support Packages option in JSPM and
select for update only the components SAP KERNEL and BC-FES-IGS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
23 Parallel Update of Dual-Stack Systems
2860 CUSTOMER 2012-08-30
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS)
runs on a dedicated host In this case JSPM does not support update of kernel binaries and
you need to update them manually Perform the update manually as described under Updating
SAP Kernel and SAP IGS in section Updating the Application Server ABAP and ABAP-Based Software
Components [page 16]
2 Import the Support Packages for the component SAP_BASIS into the ABAP stack using the ABAP
Support Package Manager (SPAM)
3 Import the remaining ABAP Support Packages with SPAM and in parallel apply the Java Support
Package Stack with JSPM
Proceed as described in Updating the Application Server ABAP and ABAP-Based Software Components [page
16] and Updating the Application Server Java and Java-Based Software Components [page 23]
24 Process Integration
241 Planning
Procedure
This section covers all the units of Process Integration that should be updated Particularly the following
units must always have the same Support Package level (the patch level can be different)
Integration Server
XI Adapter Engine
Partner Connectivity Kit
System with the Usage Type Process Integration
Software components of Integration Server
Components to Be Updated SP File Name Tool Used to Apply SP
Java stack
XI TOOLS 702 SAPXITOOLltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
ABAP stack
XI CONTENT SAP_BASIS 702 SAPBASISltSPgt_ltPLgtZIP File upload
XI CONTENT SAP_ABA 702 SAPABAltSPgt_ltPLgtZIP
SAP NetWeaver Application Server ABAP (see table Software components of Application Server ABAP [page 15])Note that update of the following software components of the ABAP system is not required SAP ABA 702 SAP BW 702 PI_BASIS 702
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 2960
J2EE Adapter Engine
If your implemented scenario includes a J2EE Adapter Engine then it must always be of the same
Support Package level as the Integration Server
Components of the J2EE Adapter Engine
Component to Be Updated SP File NameTool Used to Apply SP
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
J2SE Adapter Engine
The installation of the J2SE Adapter Engine depends on the implemented scenario
Components of the J2SE Adapter Engine
Component to Be Updated SP File Name Tool Used to Apply SP
XI CONNECTIVITY SE 702 SAPXICONSltSPgt_ltPLgtSCA ZIP tool (for example WinZip)
Partner Connectivity Kit
If your implemented scenario includes a Partner Connectivity Kit (PCK) then it must always be of the
same Support Package level as the Integration Server
Software components of Partner Connectivity Kit
Components to Be Updated SP File NameTool Used to Apply SP
XI PCK 702 SAPXIPCKltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of the Application Server Java [page 20])
System Landscape Directory (SLD)
The System Landscape Directory is required for the PI operations Although updating the SLD is not
necessarily required it is advisable to update the SLD server and the SAP Master Data Content within
it from time to time The update of the SLD includes
1 The system where the SLD is running
2 The SAP Master Data Content within this SLD
SAP GUI
See table Compatible SAP GUI Versions [page 51]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3060 CUSTOMER 2012-08-30
242 Updating Units of Process Integration
Procedure
Before you start the update perform the following steps
In the Runtime Workbench use Communication Channel Monitoring to stop all sender channels
for all adapter types on all your Adapter Engines
On the Integration Server use transaction SMQR and deregister all qRFC queues
System with the Usage Type Process Integration
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the XI instance is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system where the XI instance is running
For more information see Application Server Java and Java-Based Software Components [page 19]
System Landscape Directory (Optional)
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the SLD is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the entire Support Package Stack to the system where the SLD is running
For more information see Application Server Java and Java-Based Software Components [page 19]
J2EE Adapter Engine
Apply the Support Package Stack to the system where the Adapter Engine is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Partner Connectivity Kit
Apply the Support Package Stack to the system where the PCK is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Front End GUIs
Update the SAP GUI components if necessary
For more information see SAP GUI Family [page 51]
ABAP 700 Business System (Optional)
Apply the Support Packages for SAP NetWeaver Application Server ABAP (including SAP kernel and
the Support Package for SAP BASIS 700)
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 640 Business System (Optional)
Apply the Support Packages for SAP Web Application Server ABAP 640 (including SAP kernel and the
Support Package for SAP BASIS 640)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3160
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 620 Business System (Optional)
1 Update the SAP Kernel 620
2 Import the released Basis Support Packages for SAP Web AS 620 as well as the most recent Add-
On Support Package for APPINT 200_620 in the order described in SAP Note 439915
J2SE Adapter Engine (Optional)
NOTE
The XI Adapter Engine (J2SE) and all its adapters are provided for compatibility reasons only and
are not developed any further You have to use the XI Adapter Engine running on SAP NetWeaver
AS Java For more information see the Master Guide ndash SAP NetWeaver 70 available on SAP Service
Marketplace at httpservicesapcominstallNW70 Planning
1 Extract the SAPXICONSltSPgt_ltPLgtSCA (XI Connectivity SE 700) archive (ZIP format) to a temporary
directory
2 Save the old configuration files as described in the document Adapterpdf in directory
lttemp_directorygttech_adapterAdministrationDocumentation
3 Unpack the ZIP archive TechnicalAdapterssda to the installation directory of the XI Adapter
Engine (J2SE)
4 Restore the configuration files with restore_configuration
243 Post-Installation Steps
Procedure
Communication Channels and Queues
Restart all stopped sender channels and register all deregistered qRFC queues
XI Content
In the system with usage type PI import the XI content from the archives SAPBASISltSPgt_ltPLgtZIP
and SAPABAltSPgt_ltPLgtZIP as follows
1 Unpack the archives using a ZIP tool of your choice
2 Copy the corresponding export files (with file extension tpz) to the import directory ltINSTDIRgt
ltSAPSIDgtSYSglobalxirepository_serverimport
3 Start the Integration Builder (transaction SXMB_IFR)
4 Enter the Integration Repository by choosing Repository (Design)
5 Choose Tools Import design objects
6 Import the tpz files containing the XI content
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3260 CUSTOMER 2012-08-30
NOTE
For more information see SAP Note 836200
Role Generation on the Integration Server
On the Integration Server execute transaction SUPC (mass generation of roles) for all SAP_XI roles in
each of your clients to regenerate possibly changed roles
NOTE
Do not forget to make a user comparison for regenerated roles afterwards
Partner Connectivity Kit (Optional)
Perform the post-installation steps for PCK as described in SAP Note 746328
SAP Master Data within the SLD (Optional)
In the system where your SLD is running import the latest SLD content as described in SAP Note
669669
Receiver-Based EOIO Serialization in J2EE Adapter Engine (Optional)
The J2EE Adapter Engine can be switched to receiver-based EOIO serialization The switch can be
triggered on demand and is executed asynchronously It includes a database migration step during
which all EOIO processing in the Adapter Engine is disabled See SAP Note 973894 for details about how
to start the EOIO serialization migration
Service Metering (Optional)
Service metering gathers information about a service caller transfers it to the service provider and
counts on the service provisioning side how many times a service is called and by which service caller
Service metering is performed for the XI message protocol and the WS message protocol Service
metering is automatically enabled after applying a Support Package Stack By default only non-sensitive
data is transmitted to internal or external service providers in a compatible way
Service metering can be configured in PI in the Integration Engine on sender-side and in the Integration
Directory
Service metering can be configured in AS ABAP in transaction SOAMANAGER
Only if the service provider is allowed to receive more detailed information about the service caller set
the metering level to higher than the default
For more information see SAP Note 1239428
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3360
25 Business Intelligence
251 Planning
Procedure
Business Intelligence includes one or many of the following units that must be updated depending on
your implemented scenarios The usage types Business Intelligence (BI) and Business Intelligence Java
Components (BI-Java) must always have the same Support Package level
Business Intelligence
Software Components of Business Intelligence
Component to Be Updated SP File Name Tool Used to Apply SP
BI CONT ADDON 70x SAPK-70ltxgtltSPgtINBICONT SAINT
SAP NetWeaver Application Server ABAP (see table Software Components of Application Server ABAP [page 15])
NOTE
For information about the dependencies applying to BI Content Support Packages see SAP Note
653814 BI CONT 703 Support Packages are not part of the NetWeaver SP Stacks Updates can be
performed when applicable Alternatively BI CONT 704 Support Packages can be imported See
the BI Content release strategy in SAP Note 153967
Business Intelligence Java Components
BI Java Components
Component to Be Updated SP File NameTool Used to Apply SP
BI REPORTING AND PLANNING 702 BIREPPLANltSPgt_ltPLgtSCA JSPM
BI WEBDYNPRO ALV 702 BIWDALVltSPgt_ltPLgtSCA
BI INFORM BROADCASTING 702 BIIBCltSPgt_ltPLgtSCA
BI WEB APPLICATIONS 702 BIWEBAPPltSPgt_ltPLgtSCA
BI BASE SERVICES 702 BIBASESltSPgt_ltPLgtSCA
VISUAL COMPOSER BI KITS 702 VCKITBIltSPgt_ltPLgtSCA
Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
BI Precalculation Service
Components of the BI Precalculation Service
Component to Be Updated SP File Name Tool Used to Apply SP
BI Pre-calculation Service 700 xPreCalServerltSPgt_ltPLgtexe Installer
Search and Classification (TREX)
See table TREX Component [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3460 CUSTOMER 2012-08-30
BI Accelerator
The BI Accelerator is based on the TREX technology It is a special Linux 64-bit version of SAP NetWeaver
70 Search and Classification (TREX) which is delivered on preconfigured hardware
NOTE
You cannot use a TREX installation based on 32-bit architecture that is configured for searching
in metadata and documents for the BI Accelerator And vice versa a BI Accelerator box cannot
be used for searching in metadata and documents
If you want to use the search functionality as well as the BI Accelerator you require two separate
installations For more information see BI Accelerator [page 47]
Clients
Depending on your implemented scenarios you have to update SAP GUI Components and Business
Explorer (BI Add-OnBW Add-On)
NOTE
See SAP Note 889314 to determine when to use the BI Add-On and the BW Add-On
NOTE
As SAP GUI 640 is no longer supported BI Frontend Support Package 1800 resp patch 1801 is the
last Support Package resp patch based on SAP GUI 640 For more information see SAP Note
1231292 (Frontend Add-in Strategy 640710 GUI Version)
For more information about the new release strategy for the BI Frontend see SAP Note 1231363
(Changed Delivery Strategy for BI Frontend)
252 Preparation
Procedure
For the Support Packages of the most important Business Intelligence units so called SAPBINews
(SAPBWNews) Notes are created Read these Notes before updating Business Intelligence For SAP
NetWeaver 70 including enhancement package 2 SPS 12 these are the following
Business Intelligence ABAP SAP Note 1680996
Business Intelligence Java Components SAP Note 1726461
BI 70 Frontend Add-On for SAP GUI 710 SAP Note 1413032
BI 70 Frontend Add-On for SAP GUI 720 SAP Note 1630112
BI 70 Frontend Add-On for SAP GUI 730 SAP Note 1726739
For more information about BI Support Packages see SAP Community Network at http
scnsapcomcommunitydata-warehousingnetweaver-bw Related Resources SAP NW BW Support
Packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
2012-08-30 CUSTOMER 3560
253 Updating Units of Business Intelligence
Procedure
Business Intelligence
1 Update the SAP NetWeaver Application Server ABAP (with BI CONT 70x if necessary) with the
appropriate Support Packages
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
NOTE
When applying the component SAP BW 702 some generation errors might occur When
you start importing the BI Support Packages in transaction SPAM choose the menu path
Extras Ignore generation errors For more information see SAP Note 114134
2 Apply the Support Package Stack to the system with the usage type BI-Java
For more information see Application Server Java and Java-Based Software Components [page 19]
3 Update the BI Precalculation Service that is used in your scenario
4 Update the standalone engine Search and Classification (TREX) that is used in your scenario For more
information see Standalone Engine Search and Classification (TREX) [page 44]
NOTE
You have to update TREX to the newest version if you use search capabilities within Business
Intelligence
5 Update the BI Accelerator to the newest available version For more information see BI
Accelerator [page 47]
6 Update the SAP GUI and Business Explorer (BI Add-On BW Add-On) on all remote client hosts
that are involved in the scenario
For more information see SAP GUI Family [page 51] and Business Explorer (BI Add-On BW Add-On)
[page 51]
BI Precalculation Service
1 Log on to the host as a user with administration rights
2 Install the Support Package of the BI Precalculation Service by executing the
xPreCalServerexe file
The welcome screen of the BI Precalculation Server setup wizard appears
The setup now checks the system for the prerequisites
3 Choose the option Update for updating the BI Precalculation service to the current patch level and
then Finish
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3660 CUSTOMER 2012-08-30
26 EP Core
261 Planning
Procedure
The following installable software units must be updated
EP Core
Software Components of EP Core
Component to Be Updated SP File Name Tool Used to Apply SP
PORTAL CORE SERVICES 702 EPBCltSPgt_ltPLgtSCA JSPM
PORTAL FRAMEWORK 702 EPBC2ltSPgt_ltPLgtSCA
PORTAL 702 EPPSERVltSPgt_ltPLgtSCA
PORTAL WEB DYNPRO 702 EPWDCltSPgt_ltPLgtSCA
UWL COLL PROCESS ENGINE 702 UWLJWFltSPgt_ltPLgtSCA
CAF EU 702 SAPEUltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
262 Preparation
Procedure
Backing Up the Portal Runtime Configuration
If you have made changes to the standard Portal Runtime configuration you have to make a backup
of the configuration before the update process For more information see SAP Note 1064468
263 Updating EP Core
Procedure
Apply the Support Package Stack to a system with usage type EP Core
For more information see Application Server Java and Java-Based Software Components [page 19]
264 Post-Installation Steps for EP Core
Procedure
Restoring the Portal Runtime Configuration
To make your changes to the standard Portal Runtime Configuration effective you have to restore
the backup of the configuration done before the update process For more information see SAP Note
1064468
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
26 EP Core
2012-08-30 CUSTOMER 3760
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
NOTE
This table contains only software components that belong to the usage type AS ABAP Software
components of other usage types and application units are listed in the corresponding sections
NOTE
SAP delivers intermediate Support Packages for the component SAP BW 702 between two
subsequent SP levels besides the Support Packages delivered along with the Support Package
Stacks Therefore the highest SP level of SAP BW 702 does not necessarily match the target SP
Stack level
CAUTION
When applying a Support Package Stack to a dual-stack system (ABAP+Java) the Java Support
Package Manager (JSPM) will necessarily restart the system several times to make the changes
effective The ABAP part will only be restarted when JSPM is updating the SAP kernel and IGS
212 Preparation
Procedure
Read SAP Note 822379 and all related SAP Notes that the first one refers to
213 Updating the Application Server ABAP and ABAP-Based Software Components
Procedure
Applying Support Packages to SAP NetWeaver Application Server ABAP and ABAP-Based Components
You can update the SAP NetWeaver Application Server ABAP and all ABAP-based software components
running on it using the Support Package Manager (transaction SPAM)
NOTE
If a particular Support Package Stack requires the installation or upgrade of some add-on
components you must use the ABAP Add-on Installation Tool (transaction SAINT) instead of the
Support Package Manager In this case SAINT is able to import both the add-on components and
the related Support Packages of ordinary SAP components
Proceed as follows
1 Log on to the SAP NetWeaver AS system with client 000
2 Start the Support Package Manager by calling transaction SPAM or
start the Add-On Installation Tool by calling transaction SAINT
3 Load the relevant Support Packages or add-on installation packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
1660 CUSTOMER 2012-08-30
4 Define an import queue
5 Perform the import of the defined queue
NOTE
If you have modified SAP objects in your system and these objects are included in the Support
Packages you must perform modification adjustment during the import using the
transactions SPDD (for ABAP Dictionary objects) and SPAU (for Repository objects)
To import the queue you use the standard scenario You can choose between the conventional
import mode and downtime-minimized import mode
Conventional Import Mode
This option comprises the following steps
1 Update the SAP kernel and SAP IGS as described in section Updating SAP Kernel and SAP IGS below
Start the system after the kernel update
2 Import the ABAP Support Packages with the Support Package Manager (SPAM)
Import Mode Downtime-Minimized
This option can be used to reduce system downtime during the update It comprises the following
steps
1 In transaction SPAM enable the downtime-minimized import mode by choosing Extras
Settings then on the Import queue tab page choose Standard and activate the option Import Mode
Downtime-Minimized
2 Import the ABAP Support Packages into the system in an inactive state in the downtime-minimized
mode during system uptime
3 Update the SAP kernel and SAP IGS as described in section Updating SAP Kernel and SAP IGS below
Start the system after the kernel update
4 Complete the ABAP Support Packages import
CAUTION
During this step the system cannot carry out any business transactions (business downtime)
NOTE
In rare cases due to the dependencies of some Support Packages on a particular kernel patch level
the downtime-minimized update does not work In such cases the Support Package Manager
informs you that you must update the SAP kernel before importing ABAP Support Packages You
must proceed with the conventional import procedure
Updating SAP Kernel and SAP IGS
In general the SAP kernel and IGS binaries are located in the global kernel directory DIR_CT_RUN on
the host indicated by the profile parameter SAPGLOBALHOST Once the files in this directory have been
updated to a new patch level a system restart distributes them by means of the program SAPCPE to the
local directories DIR_EXECUTABLE on the hosts where the instances of the SAP system are running
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
2012-08-30 CUSTOMER 1760
CAUTION
The automatic distribution by means of SAPCPE depends on the settings of the profile parameters
DIR_CT_RUN for the global kernel directory and DIR_EXECUTABLE for the local directory of the
executables Before you continue check the instance profiles for the settings of these parameters
in systems that are not installed using SAPinst (for example systems upgraded from older releases
copied or migrated systems)
CAUTION
If your system is a dual-stack system (ABAP+Java) and the ABAP stack has a non-Unicode kernel
be aware that the SCS instance has a Unicode kernel You have to update both kernels (together
with SAP IGS) prior to updating the ABAP and Java Support Package stacks This ensures
compatibility and reduces system downtime
RECOMMENDATION
If you perform an update of a dual-stack system (ABAP+Java) we recommend that prior to
applying ABAP and Java Support Package stacks you use the Single Support Packages option in JSPM
and select for update only the components SAP KERNEL and BC-FES-IGS
For more information about updating a dual-stack system see Parallel Update of Dual-Stack Systems
[page 28]
If you perform an update of an ABAP system the following procedure applies for updating the SAP
kernel and IGS manually
1 Log on as user ltsapsidgtadm to the instance host to be updated
2 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory using
SAPCAR [page 56]
3 Stop the ABAP system that you want to update
NOTE
If the system is running in a high availability (HA) environment make sure that the HA
software does not restart the system automatically during the update
4 Back up the kernel directory ltkrnl_directorygt
5 Copy or move the extracted programs from the temporary directory to the SAP kernel directory
6 Only valid for UNIX |
Execute the following command sequence on UNIX platforms
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
1860 CUSTOMER 2012-08-30
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
7 Restart the SAP system
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS) runs
on a dedicated host You need to perform the kernel update for the ASCS instance manually but
excluding the IGS update because the IGS is not required in an ASCS instance
In rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of such instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances manually Proceed as described
in section Manually Updating Instances with Kernel Directory Located on Separate Hosts below in this document
214 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the ABAP system
22 Application Server Java and Java-Based Software Components
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system which includes
JSPM itself
SAP Kernel and SAP IGS
All Java-based usage types installed in the system
Software Deployment Manager (SDM) - the deployment service of the system
RECOMMENDATION
We strongly recommend that you apply the target Support Package Stack to your system as a
whole This ensures consistency on both the system and the application levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 1960
221 Planning
Procedure
Java Support Package files (SCAs) contain all software objects of the corresponding software
components Thus it is sufficient to apply the Java Support Package files of the intended Support Package
Stack directly to the Java system to be updated It is not necessary to apply the Support Package Stacks
between the start SP Stack level and the target SP Stack level successively
CAUTION
When applying a Support Package Stack to a Java system the Java Support Package Manager (JSPM)
will necessarily restart the system several times to make the changes effective With a dual-stack
system (ABAP+Java) the ABAP part will only be restarted when JSPM is updating the SAP kernel
and IGS
The following components belong to the usage type SAP NetWeaver Application Server Java (AS Java)
Software Components of Application Server Java
Component to Be Updated SP File Name Tool Used to Apply SP
SAP Kernel 720 32-64-BIT UNICODE SAPEXESAR
SAPEXEDBSAR
JSPM
SAP IGS 700 igsexesar
BI META MODEL REPOSITORY 702 BIMMRltSPgt_ltPLgtSCA
J2EE ENGINE CORE TOOLS 702 CORETOOLSltSPgt_ltPLgtSCA
J2EE ENGINE BASE TABLES 702 BASETABLESltSPgt_ltPLgtSCA
BI UDI 702 BIUDIltSPgt_ltPLgtSCA
DI BUILD TOOL 702 SAPBUILDTltSPgt_ltPLgtSCA
SAP CAF 702 CAFltSPgt_ltPLgtSCA
SAP IKS 702 KMKWJIKSltSPgt_ltPLgtSCA
JAVA LOG VIEWER 702 JLOGVIEWltSPgt_ltPLgtSCA
SAP J2EE ENGINE CORE 702 SAPJEECORltSPgt_ltPLgtSCA
SAP JAVA TECH SERVICES 702 SAPJTECHSltSPgt_ltPLgtSCA
SAP TECH S OFFLINE 702 SAPJTECHFltSPgt_ltPLgtSCA
SAP J2EE ENGINE 702 SAPJEEltSPgt_ltPLgtSCA
JAVA SP MANAGER 702 JSPMltSPgt_ltPLgtSCA
ADOBE DOCUMENT SERVICES 702 ADSSAPltSPgt_ltPLgtSCA
UME ADMINISTRATION 702 UMEADMINltSPgt_ltPLgtSCA
LIFECYCLE MGMT TOOLS 702 LMTOOLSltSPgt_ltPLgtSCA
SAP CAF-UM 702 CAFUMltSPgt_ltPLgtSCA
SAP SOFTW DELIV MANAGER 702 SDMKITltSPgt_ltPLgtJAR
SOFTWARE LIFECYCLE MANAGER 702 SWLIFECYCLltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2060 CUSTOMER 2012-08-30
NOTE
This table contains only software components that belong to the usage type AS Java Software
components of other usage types and Java application units are listed in the corresponding
sections
NOTE
As of Support Package 09 you can update your system with SAP Kernel 720 instead of SAP Kernel
701
222 Preparation for Applying a Support Package Stack
Procedure
1 Download the Support Package Stack with all usage types to be updated and the stack definition
XML file as described in Downloading Support Package Stacks [page 12]
NOTE
You can find the activated usage types in an existing Java system on the Deployed Components tab
page on the JSPM user interface
NOTE
You do not need to download the SP Stacks between the source SP Stack level and target SP
Stack level By default the target SP Stack level is the latest available SP Stack
2 Make sure the following requirements are met prior to applying the Support Package Stack
You have familiarized yourself with SAP Note 891983 before you start the Java Support Package
Manager
The system to be updated is fully functional
The Support Package Stack you want to apply and the corresponding stack definition XML
file are available in the EPS inbox directory usrsaptransEPSin By default this location
can be also referred to as ldquoJSPM inboxrdquo
The SAP NetWeaver Application Server Java (AS Java) and the database have been backed up
You have not deleted renamed or created any directories and files in the following directories
and their subdirectories usrsapltSAPSIDgtSYSexe and usrsapltSAPSIDgtSYS
profile
Otherwise JSPM cannot detect the kernel and the system profiles and cannot be started If a
backup of the kernel and the system profiles has been required it has been created in a different
directory
The ltsapsidgtadm user has Read permissions for the EPS inbox directory usrsaptransEPS
in
If your database is SAP MaxDB the overwrite mode for the log area has been activated
The database and the SDM repository have been synchronized
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2160
For more information see the online documentation for JSPM on SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70 Library
(including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library Administrators Guide
Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems AS Java
(Application Server for Java) Software Logistics Software Maintenance Java Support Package Manager
Then choose Troubleshooting JSPM Does Not Update the Versions of the Deployed Components
There is enough disk space
For more information see SAP Note 891895
Your current SAPCAR tool is able to extract the Support Packages for the SAP kernel and
other OS level binaries delivered as SAR files
RECOMMENDATION
You can download the latest version of SAPCAR from SAP Service Marketplace at
httpservicesapcompatches Entry by Application Group Additional Components
SAPCAR
Put the downloaded version in the same directory in the JSPM inbox in which the kernel
SAR files reside so that JSPM can use this version for extracting the SAR files
3 Only valid for Linux |
For RHEL 4 and SLES 9 you need to install additional operating system packages For more
information see SAP Note 1021236End of Linux |
4 Only valid for Windows |
For Windows you need to install additional operating system packages For more information see
SAP Note 684106End of Windows |
5 To prevent the Software Deployment Manager (SDM) from temporarily exceeding the available
disk space during the update process you can change the file transfer directory of SDM in a system
of SPS09 or higher using the following command sequence
Only valid for Windows |
cd ltsdm_homegt
StopServerbat
sdmbat jstartup mode=standalone
sdmbat filetransferdir dir=ltnew_dirgt
sdmbat jstartup mode=integrated
StartServerbat
End of Windows |
Only valid for IBM i5OSUNIX |
cd ltsdm_homegt
StopServersh
sdmsh jstartup mode=standalone
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2260 CUSTOMER 2012-08-30
sdmsh filetransferdir dir=ltnew_dirgt
sdmsh jstartup mode=integrated
StartServersh
End of IBM i5OSUNIX |
6 To prevent deployment errors during the update process proceed as follows
1 Log on to the Central Instance host
2 Start the ConfigTool and in the navigation area choose Cluster-data Global server configuration
Managers ServiceManager
3 In the Global properties panel set the Custom value of the EventTimeout property to 120
4 Choose Save
5 Restart the Central Instance
7 Check whether the used JDK version and the Java VM settings of the Java runtime system comply
with the requirements in SAP Note 723909 Update the JDK and adjust the settings if necessary
NOTE
An update of the used JDK version possibly changes the JVM path In this case you must
make the new path available to all Dialog Instances of the J2EE engine by implementing option
1 of SAP Note 718901
8 Make sure that the J2EE administrator password stored in the secure store for offline usage is
identical with the one stored in the User Management Engine (UME) You can change the password
in the secure store as described in SAP Note 870445
9 If you are running a high availability system on Windows you might need to prepare your system
as described in the online documentation for JSPM see section Preparing Systems That Run in High
Availability Environment
223 Updating the Application Server Java and Java-Based Components
Procedure
Applying a Support Package Stack to SAP NetWeaver Application Server Java and Java-Based Components
NOTE
The JSPM GUI might not work properly on some UNIX systems For more information and the
solution see SAP Note 1013976
1 Log on as user ltsapsidgtadm to the Central Instance host
NOTE
If your operating system is IBM i log on as user ltSIDgtADM or ltSIDgtOFR
2 Close the SAP Management Console (SAP MMC) and the SDM remote GUI client
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2360
3 For UNIX and Windows To start the JSPM navigate to the directory ltINSTDIRgtltSIDgt
ltCentral_Instance_Namegtj2eeJSPM and run the go script file
NOTE
If your system is running on IBM i to start the JSPM proceed as follows
1 To prevent JSPM from automatically starting its GUI in the file usrsapltSIDgt
ltCentral_Instance_Namegtj2eeJSPMparamjspm_configtxt change the
property dialogSDTServerConnectionSDTGuilaunch from true to false
2 On the IBM i host run the go script file using the following command
QSH CMD(usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPMgo)
3 In the mounted directory usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPM run
the StartGui script file The JSPM GUI appears
4 In the Host field enter the target IBM i host
NOTE
Depending on the system type ltCentral_Instance_Namegt has the following syntax
Standalone Java system JCltinstance_nogt
Add-On system DVEBMGSltinstance_nogt
4 Enter your SDM password to log on to the SDM
5 On the Deployment tab page select the Java Support Package Manager option and update the software
component sapcomJSPM to the target SPS level
6 Restart the JSPM and log on with the SDM password
RECOMMENDATION
We strongly recommend that you use the Support and Enhancement Package Stack option when
applying a Support Package Stack Other options can lead to unintended consistency issues
NOTE
If you need to include the latest patches for a particular component during the update process
with the Support and Enhancement Package Stack option stop the JSPM after restart and apply SAP
Note 1080821 Then start the JSPM again
7 On the Deployment tab page select the Support and Enhancement Package Stack option and choose Next
The Support Package Stacks that are available for deployment in the global EPS inbox directory
are displayed
8 In the Target SP Stack Level dropdown box select the Support Package Stack to be applied and choose
Next
In this step JSPM performs various status validations and displays the result of each software
component included in the stack definition XML file on the subsequent screen which includes
the following possible statuses
OK Indicates that the SPS level of the corresponding software component is applicable
WARNING We recommend that you view the details about the component by choosing Show
Details
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2460 CUSTOMER 2012-08-30
This status may indicate that the corresponding software component comprises custom
modifications in an NWDI-controlled system
If your system is used for NWDI development and it is either a DEV or a CONS system
you will be informed that JSPM will not deploy the modified software components but
only transport them to the CMS transport directory JSPM will deploy only the software
components that are not modified
If your system is not used for NWDI development or if your system is used for NWDI
development and it is either a TEST or a PROD system you will be informed that JSPM
has found newer versions of modified software components and will automatically replace
the original versions with the newer versions JSPM will deploy all software components
that are not modified together with the replaced versions of the modified software
components
CAUTION
You may get a warning telling you that there are patches installed in your system
containing fixes which might not be included in the target SP Stack This is possible if
you have applied patches of the start SP Stack level that were delivered later than the
target SP Stack delivery date In order not to lose these fixes you need to download and
apply the corresponding patches of the target SP Stack level
If you are performing an update from SAP NetWeaver 70 including enhancement
package 1 SPS00 and you have not applied any patches for the software component with
status WARNING before the update then you can ignore warnings such as the following
example
The new version of the development component sapcomcomsapnetweaver
bcrfmoni is 70100200806121227180000 and is lower than the already
deployed version 70100200807090143420000
REVISE Indicates inconsistencies with the corresponding software component
The deployment cannot be performed until all problems have been resolved You can view
the problems by choosing Show Details
9 If the status of the selected SP Stack is OK or WARNING you can start the system update by choosing
Start JSPM then changes the status to SCHEDULED
If the SP Stack to be applied includes a kernel update and the current kernel is not already of the
corresponding patch level JSPM arranges the kernel update as the very first Support Package to
be applied JSPM updates the kernel binaries of all instances (including Dialog Instances and SCS
instances in a HA environment) whose kernel directories DIR_CT_RUN effectively reside on the host
indicated by the profile parameter SAPGLOBALHOST
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2560
CAUTION
Kernel binaries of instances whose kernel directories DIR_CT_RUN are not effectively linked
to the host SAPGLOBALHOST must be updated individually as described in section Manually
Updating Instances with Kernel Directory Located on Separate Hosts below
The kernel update (includes update of SAP Kernel and SAP IGS) using JSPM consists of the following
steps
1 JSPM stops the Central Instance automatically and prompts you to stop the remote SCS and
Dialog Instances manually
2 After you have stopped all the instances choose the Next button in the dialog box
The kernel update starts
NOTE
If the system is running in a high availability environment make sure that the HA
software does not restart the instance automatically during the update
NOTE
If kernel binaries of the SCS instance need to be updated manually (see Manually Updating
Instances with Kernel Directory Located on Separate Hosts below) you must perform this at the
time when JSPM is updating the kernel binaries of the Central Instance In any case the
SCS kernel must be up-to-date before the next restart
When the kernel update is finished a dialog box appears in which you are prompted to restart
the SCS instance manually
3 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries
before you can proceed with the next step For more information see Adjusting the Ownership and
Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
4 Choose Next in the dialog box when the SCS instance is running again
After the kernel update JSPM restarts the system for further deployment of the remaining Support
Packages in the stack
RECOMMENDATION
If you need to update the kernel binaries of any Dialog Instances manually (see Manually
Updating Instances with Kernel Directory Located on Separate Hosts below) perform the update when
JSPM is updating the remaining Support Packages in the stack in order to save time
The deployment of each Support Package can end with one of the following statuses
DEPLOYED
The Support Package has been successfully deployed
DEPLOYED WITH WARNING
The Support Package has been deployed but it possibly may not work properly with other
deployed components
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2660 CUSTOMER 2012-08-30
You can view the details by choosing Show Details or examining the log files You can also view
the details about the component by choosing the Deployed Components tab page
ERROR
An error has occurred during the deployment You can view the details by choosing Show
Details or examining the log files
You must correct the error to be able to continue with the SP Stack update
You can proceed as described for a deployment that finished with status DEPLOYED WITH
WARNING
If the error correction does not change the contents in the JSPM inbox you can continue
the deployment by choosing Resume
If the error correction changes the contents in the JSPM inbox you can choose New
Deployment to redeploy the SP Stack
NOT DEPLOYED
JSPM has not attempted to deploy the software component for certain reasons
If your system is not used for NWDI development you can proceed as described for a
deployment that finished with status ERROR
If your system is used for NWDI development and it is either a DEV or a CONS system
the status of the modified software components is always NOT DEPLOYED JSPM has
transported the software components of the Support Package Stack both modified and
not modified to the CMS transport directory The deployment of the modified software
components is handled by NWDI
Manually Updating Instances with Kernel Directory Located on Separate Hosts
JSPM performs kernel update for all instances (including Dialog Instances and SCS instances in a HA
environment) whose kernel directories DIR_CT_RUN effectively reside on the host indicated by the profile
parameter SAPGLOBALHOST (by using folder sharing on Windows or file system mounting on UNIX) In
rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of those sort of instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances individually
To update the kernel of an instance manually proceed as follows
1 Log on as user ltsapsidgtadm to the host of the instance to be updated
2 Back up the kernel directory which is specified by the profile parameter DIR_CT_RUN
3 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory with
SAPCAR [page 56]
4 Stop the instance being updated
NOTE
If the system is running in a HA environment make sure that the HA software does not
restart the instance automatically during the update
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2760
5 Copy or move the extracted programs from the temporary directory to the local kernel directory
6 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries as
described in section Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
7 Restart the instance after JSPM has finished the deployment of all packages on the Central Instance
Only valid for UNIX |
Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms
On UNIX platforms you must adjust the ownership and execution permissions of the kernel binaries
after the update regardless whether you performed the update manually or by using JSPM because
both update procedures are performed with the ltsapsidgtadm user Enter the following command
sequence
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
224 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the Java system
23 Parallel Update of Dual-Stack Systems
If you perform an update of a dual-stack system (ABAP+Java) we recommend that you follow the
procedure described below The procedure has been validated to update the ABAP stack and the Java
stack of a NetWeaver system in parallel thus reducing the overall system downtime by half
Procedure
1 Before applying ABAP and Java Support Packages use the Single Support Packages option in JSPM and
select for update only the components SAP KERNEL and BC-FES-IGS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
23 Parallel Update of Dual-Stack Systems
2860 CUSTOMER 2012-08-30
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS)
runs on a dedicated host In this case JSPM does not support update of kernel binaries and
you need to update them manually Perform the update manually as described under Updating
SAP Kernel and SAP IGS in section Updating the Application Server ABAP and ABAP-Based Software
Components [page 16]
2 Import the Support Packages for the component SAP_BASIS into the ABAP stack using the ABAP
Support Package Manager (SPAM)
3 Import the remaining ABAP Support Packages with SPAM and in parallel apply the Java Support
Package Stack with JSPM
Proceed as described in Updating the Application Server ABAP and ABAP-Based Software Components [page
16] and Updating the Application Server Java and Java-Based Software Components [page 23]
24 Process Integration
241 Planning
Procedure
This section covers all the units of Process Integration that should be updated Particularly the following
units must always have the same Support Package level (the patch level can be different)
Integration Server
XI Adapter Engine
Partner Connectivity Kit
System with the Usage Type Process Integration
Software components of Integration Server
Components to Be Updated SP File Name Tool Used to Apply SP
Java stack
XI TOOLS 702 SAPXITOOLltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
ABAP stack
XI CONTENT SAP_BASIS 702 SAPBASISltSPgt_ltPLgtZIP File upload
XI CONTENT SAP_ABA 702 SAPABAltSPgt_ltPLgtZIP
SAP NetWeaver Application Server ABAP (see table Software components of Application Server ABAP [page 15])Note that update of the following software components of the ABAP system is not required SAP ABA 702 SAP BW 702 PI_BASIS 702
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 2960
J2EE Adapter Engine
If your implemented scenario includes a J2EE Adapter Engine then it must always be of the same
Support Package level as the Integration Server
Components of the J2EE Adapter Engine
Component to Be Updated SP File NameTool Used to Apply SP
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
J2SE Adapter Engine
The installation of the J2SE Adapter Engine depends on the implemented scenario
Components of the J2SE Adapter Engine
Component to Be Updated SP File Name Tool Used to Apply SP
XI CONNECTIVITY SE 702 SAPXICONSltSPgt_ltPLgtSCA ZIP tool (for example WinZip)
Partner Connectivity Kit
If your implemented scenario includes a Partner Connectivity Kit (PCK) then it must always be of the
same Support Package level as the Integration Server
Software components of Partner Connectivity Kit
Components to Be Updated SP File NameTool Used to Apply SP
XI PCK 702 SAPXIPCKltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of the Application Server Java [page 20])
System Landscape Directory (SLD)
The System Landscape Directory is required for the PI operations Although updating the SLD is not
necessarily required it is advisable to update the SLD server and the SAP Master Data Content within
it from time to time The update of the SLD includes
1 The system where the SLD is running
2 The SAP Master Data Content within this SLD
SAP GUI
See table Compatible SAP GUI Versions [page 51]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3060 CUSTOMER 2012-08-30
242 Updating Units of Process Integration
Procedure
Before you start the update perform the following steps
In the Runtime Workbench use Communication Channel Monitoring to stop all sender channels
for all adapter types on all your Adapter Engines
On the Integration Server use transaction SMQR and deregister all qRFC queues
System with the Usage Type Process Integration
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the XI instance is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system where the XI instance is running
For more information see Application Server Java and Java-Based Software Components [page 19]
System Landscape Directory (Optional)
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the SLD is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the entire Support Package Stack to the system where the SLD is running
For more information see Application Server Java and Java-Based Software Components [page 19]
J2EE Adapter Engine
Apply the Support Package Stack to the system where the Adapter Engine is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Partner Connectivity Kit
Apply the Support Package Stack to the system where the PCK is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Front End GUIs
Update the SAP GUI components if necessary
For more information see SAP GUI Family [page 51]
ABAP 700 Business System (Optional)
Apply the Support Packages for SAP NetWeaver Application Server ABAP (including SAP kernel and
the Support Package for SAP BASIS 700)
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 640 Business System (Optional)
Apply the Support Packages for SAP Web Application Server ABAP 640 (including SAP kernel and the
Support Package for SAP BASIS 640)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3160
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 620 Business System (Optional)
1 Update the SAP Kernel 620
2 Import the released Basis Support Packages for SAP Web AS 620 as well as the most recent Add-
On Support Package for APPINT 200_620 in the order described in SAP Note 439915
J2SE Adapter Engine (Optional)
NOTE
The XI Adapter Engine (J2SE) and all its adapters are provided for compatibility reasons only and
are not developed any further You have to use the XI Adapter Engine running on SAP NetWeaver
AS Java For more information see the Master Guide ndash SAP NetWeaver 70 available on SAP Service
Marketplace at httpservicesapcominstallNW70 Planning
1 Extract the SAPXICONSltSPgt_ltPLgtSCA (XI Connectivity SE 700) archive (ZIP format) to a temporary
directory
2 Save the old configuration files as described in the document Adapterpdf in directory
lttemp_directorygttech_adapterAdministrationDocumentation
3 Unpack the ZIP archive TechnicalAdapterssda to the installation directory of the XI Adapter
Engine (J2SE)
4 Restore the configuration files with restore_configuration
243 Post-Installation Steps
Procedure
Communication Channels and Queues
Restart all stopped sender channels and register all deregistered qRFC queues
XI Content
In the system with usage type PI import the XI content from the archives SAPBASISltSPgt_ltPLgtZIP
and SAPABAltSPgt_ltPLgtZIP as follows
1 Unpack the archives using a ZIP tool of your choice
2 Copy the corresponding export files (with file extension tpz) to the import directory ltINSTDIRgt
ltSAPSIDgtSYSglobalxirepository_serverimport
3 Start the Integration Builder (transaction SXMB_IFR)
4 Enter the Integration Repository by choosing Repository (Design)
5 Choose Tools Import design objects
6 Import the tpz files containing the XI content
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3260 CUSTOMER 2012-08-30
NOTE
For more information see SAP Note 836200
Role Generation on the Integration Server
On the Integration Server execute transaction SUPC (mass generation of roles) for all SAP_XI roles in
each of your clients to regenerate possibly changed roles
NOTE
Do not forget to make a user comparison for regenerated roles afterwards
Partner Connectivity Kit (Optional)
Perform the post-installation steps for PCK as described in SAP Note 746328
SAP Master Data within the SLD (Optional)
In the system where your SLD is running import the latest SLD content as described in SAP Note
669669
Receiver-Based EOIO Serialization in J2EE Adapter Engine (Optional)
The J2EE Adapter Engine can be switched to receiver-based EOIO serialization The switch can be
triggered on demand and is executed asynchronously It includes a database migration step during
which all EOIO processing in the Adapter Engine is disabled See SAP Note 973894 for details about how
to start the EOIO serialization migration
Service Metering (Optional)
Service metering gathers information about a service caller transfers it to the service provider and
counts on the service provisioning side how many times a service is called and by which service caller
Service metering is performed for the XI message protocol and the WS message protocol Service
metering is automatically enabled after applying a Support Package Stack By default only non-sensitive
data is transmitted to internal or external service providers in a compatible way
Service metering can be configured in PI in the Integration Engine on sender-side and in the Integration
Directory
Service metering can be configured in AS ABAP in transaction SOAMANAGER
Only if the service provider is allowed to receive more detailed information about the service caller set
the metering level to higher than the default
For more information see SAP Note 1239428
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3360
25 Business Intelligence
251 Planning
Procedure
Business Intelligence includes one or many of the following units that must be updated depending on
your implemented scenarios The usage types Business Intelligence (BI) and Business Intelligence Java
Components (BI-Java) must always have the same Support Package level
Business Intelligence
Software Components of Business Intelligence
Component to Be Updated SP File Name Tool Used to Apply SP
BI CONT ADDON 70x SAPK-70ltxgtltSPgtINBICONT SAINT
SAP NetWeaver Application Server ABAP (see table Software Components of Application Server ABAP [page 15])
NOTE
For information about the dependencies applying to BI Content Support Packages see SAP Note
653814 BI CONT 703 Support Packages are not part of the NetWeaver SP Stacks Updates can be
performed when applicable Alternatively BI CONT 704 Support Packages can be imported See
the BI Content release strategy in SAP Note 153967
Business Intelligence Java Components
BI Java Components
Component to Be Updated SP File NameTool Used to Apply SP
BI REPORTING AND PLANNING 702 BIREPPLANltSPgt_ltPLgtSCA JSPM
BI WEBDYNPRO ALV 702 BIWDALVltSPgt_ltPLgtSCA
BI INFORM BROADCASTING 702 BIIBCltSPgt_ltPLgtSCA
BI WEB APPLICATIONS 702 BIWEBAPPltSPgt_ltPLgtSCA
BI BASE SERVICES 702 BIBASESltSPgt_ltPLgtSCA
VISUAL COMPOSER BI KITS 702 VCKITBIltSPgt_ltPLgtSCA
Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
BI Precalculation Service
Components of the BI Precalculation Service
Component to Be Updated SP File Name Tool Used to Apply SP
BI Pre-calculation Service 700 xPreCalServerltSPgt_ltPLgtexe Installer
Search and Classification (TREX)
See table TREX Component [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3460 CUSTOMER 2012-08-30
BI Accelerator
The BI Accelerator is based on the TREX technology It is a special Linux 64-bit version of SAP NetWeaver
70 Search and Classification (TREX) which is delivered on preconfigured hardware
NOTE
You cannot use a TREX installation based on 32-bit architecture that is configured for searching
in metadata and documents for the BI Accelerator And vice versa a BI Accelerator box cannot
be used for searching in metadata and documents
If you want to use the search functionality as well as the BI Accelerator you require two separate
installations For more information see BI Accelerator [page 47]
Clients
Depending on your implemented scenarios you have to update SAP GUI Components and Business
Explorer (BI Add-OnBW Add-On)
NOTE
See SAP Note 889314 to determine when to use the BI Add-On and the BW Add-On
NOTE
As SAP GUI 640 is no longer supported BI Frontend Support Package 1800 resp patch 1801 is the
last Support Package resp patch based on SAP GUI 640 For more information see SAP Note
1231292 (Frontend Add-in Strategy 640710 GUI Version)
For more information about the new release strategy for the BI Frontend see SAP Note 1231363
(Changed Delivery Strategy for BI Frontend)
252 Preparation
Procedure
For the Support Packages of the most important Business Intelligence units so called SAPBINews
(SAPBWNews) Notes are created Read these Notes before updating Business Intelligence For SAP
NetWeaver 70 including enhancement package 2 SPS 12 these are the following
Business Intelligence ABAP SAP Note 1680996
Business Intelligence Java Components SAP Note 1726461
BI 70 Frontend Add-On for SAP GUI 710 SAP Note 1413032
BI 70 Frontend Add-On for SAP GUI 720 SAP Note 1630112
BI 70 Frontend Add-On for SAP GUI 730 SAP Note 1726739
For more information about BI Support Packages see SAP Community Network at http
scnsapcomcommunitydata-warehousingnetweaver-bw Related Resources SAP NW BW Support
Packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
2012-08-30 CUSTOMER 3560
253 Updating Units of Business Intelligence
Procedure
Business Intelligence
1 Update the SAP NetWeaver Application Server ABAP (with BI CONT 70x if necessary) with the
appropriate Support Packages
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
NOTE
When applying the component SAP BW 702 some generation errors might occur When
you start importing the BI Support Packages in transaction SPAM choose the menu path
Extras Ignore generation errors For more information see SAP Note 114134
2 Apply the Support Package Stack to the system with the usage type BI-Java
For more information see Application Server Java and Java-Based Software Components [page 19]
3 Update the BI Precalculation Service that is used in your scenario
4 Update the standalone engine Search and Classification (TREX) that is used in your scenario For more
information see Standalone Engine Search and Classification (TREX) [page 44]
NOTE
You have to update TREX to the newest version if you use search capabilities within Business
Intelligence
5 Update the BI Accelerator to the newest available version For more information see BI
Accelerator [page 47]
6 Update the SAP GUI and Business Explorer (BI Add-On BW Add-On) on all remote client hosts
that are involved in the scenario
For more information see SAP GUI Family [page 51] and Business Explorer (BI Add-On BW Add-On)
[page 51]
BI Precalculation Service
1 Log on to the host as a user with administration rights
2 Install the Support Package of the BI Precalculation Service by executing the
xPreCalServerexe file
The welcome screen of the BI Precalculation Server setup wizard appears
The setup now checks the system for the prerequisites
3 Choose the option Update for updating the BI Precalculation service to the current patch level and
then Finish
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3660 CUSTOMER 2012-08-30
26 EP Core
261 Planning
Procedure
The following installable software units must be updated
EP Core
Software Components of EP Core
Component to Be Updated SP File Name Tool Used to Apply SP
PORTAL CORE SERVICES 702 EPBCltSPgt_ltPLgtSCA JSPM
PORTAL FRAMEWORK 702 EPBC2ltSPgt_ltPLgtSCA
PORTAL 702 EPPSERVltSPgt_ltPLgtSCA
PORTAL WEB DYNPRO 702 EPWDCltSPgt_ltPLgtSCA
UWL COLL PROCESS ENGINE 702 UWLJWFltSPgt_ltPLgtSCA
CAF EU 702 SAPEUltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
262 Preparation
Procedure
Backing Up the Portal Runtime Configuration
If you have made changes to the standard Portal Runtime configuration you have to make a backup
of the configuration before the update process For more information see SAP Note 1064468
263 Updating EP Core
Procedure
Apply the Support Package Stack to a system with usage type EP Core
For more information see Application Server Java and Java-Based Software Components [page 19]
264 Post-Installation Steps for EP Core
Procedure
Restoring the Portal Runtime Configuration
To make your changes to the standard Portal Runtime Configuration effective you have to restore
the backup of the configuration done before the update process For more information see SAP Note
1064468
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
26 EP Core
2012-08-30 CUSTOMER 3760
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
4 Define an import queue
5 Perform the import of the defined queue
NOTE
If you have modified SAP objects in your system and these objects are included in the Support
Packages you must perform modification adjustment during the import using the
transactions SPDD (for ABAP Dictionary objects) and SPAU (for Repository objects)
To import the queue you use the standard scenario You can choose between the conventional
import mode and downtime-minimized import mode
Conventional Import Mode
This option comprises the following steps
1 Update the SAP kernel and SAP IGS as described in section Updating SAP Kernel and SAP IGS below
Start the system after the kernel update
2 Import the ABAP Support Packages with the Support Package Manager (SPAM)
Import Mode Downtime-Minimized
This option can be used to reduce system downtime during the update It comprises the following
steps
1 In transaction SPAM enable the downtime-minimized import mode by choosing Extras
Settings then on the Import queue tab page choose Standard and activate the option Import Mode
Downtime-Minimized
2 Import the ABAP Support Packages into the system in an inactive state in the downtime-minimized
mode during system uptime
3 Update the SAP kernel and SAP IGS as described in section Updating SAP Kernel and SAP IGS below
Start the system after the kernel update
4 Complete the ABAP Support Packages import
CAUTION
During this step the system cannot carry out any business transactions (business downtime)
NOTE
In rare cases due to the dependencies of some Support Packages on a particular kernel patch level
the downtime-minimized update does not work In such cases the Support Package Manager
informs you that you must update the SAP kernel before importing ABAP Support Packages You
must proceed with the conventional import procedure
Updating SAP Kernel and SAP IGS
In general the SAP kernel and IGS binaries are located in the global kernel directory DIR_CT_RUN on
the host indicated by the profile parameter SAPGLOBALHOST Once the files in this directory have been
updated to a new patch level a system restart distributes them by means of the program SAPCPE to the
local directories DIR_EXECUTABLE on the hosts where the instances of the SAP system are running
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
2012-08-30 CUSTOMER 1760
CAUTION
The automatic distribution by means of SAPCPE depends on the settings of the profile parameters
DIR_CT_RUN for the global kernel directory and DIR_EXECUTABLE for the local directory of the
executables Before you continue check the instance profiles for the settings of these parameters
in systems that are not installed using SAPinst (for example systems upgraded from older releases
copied or migrated systems)
CAUTION
If your system is a dual-stack system (ABAP+Java) and the ABAP stack has a non-Unicode kernel
be aware that the SCS instance has a Unicode kernel You have to update both kernels (together
with SAP IGS) prior to updating the ABAP and Java Support Package stacks This ensures
compatibility and reduces system downtime
RECOMMENDATION
If you perform an update of a dual-stack system (ABAP+Java) we recommend that prior to
applying ABAP and Java Support Package stacks you use the Single Support Packages option in JSPM
and select for update only the components SAP KERNEL and BC-FES-IGS
For more information about updating a dual-stack system see Parallel Update of Dual-Stack Systems
[page 28]
If you perform an update of an ABAP system the following procedure applies for updating the SAP
kernel and IGS manually
1 Log on as user ltsapsidgtadm to the instance host to be updated
2 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory using
SAPCAR [page 56]
3 Stop the ABAP system that you want to update
NOTE
If the system is running in a high availability (HA) environment make sure that the HA
software does not restart the system automatically during the update
4 Back up the kernel directory ltkrnl_directorygt
5 Copy or move the extracted programs from the temporary directory to the SAP kernel directory
6 Only valid for UNIX |
Execute the following command sequence on UNIX platforms
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
1860 CUSTOMER 2012-08-30
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
7 Restart the SAP system
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS) runs
on a dedicated host You need to perform the kernel update for the ASCS instance manually but
excluding the IGS update because the IGS is not required in an ASCS instance
In rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of such instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances manually Proceed as described
in section Manually Updating Instances with Kernel Directory Located on Separate Hosts below in this document
214 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the ABAP system
22 Application Server Java and Java-Based Software Components
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system which includes
JSPM itself
SAP Kernel and SAP IGS
All Java-based usage types installed in the system
Software Deployment Manager (SDM) - the deployment service of the system
RECOMMENDATION
We strongly recommend that you apply the target Support Package Stack to your system as a
whole This ensures consistency on both the system and the application levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 1960
221 Planning
Procedure
Java Support Package files (SCAs) contain all software objects of the corresponding software
components Thus it is sufficient to apply the Java Support Package files of the intended Support Package
Stack directly to the Java system to be updated It is not necessary to apply the Support Package Stacks
between the start SP Stack level and the target SP Stack level successively
CAUTION
When applying a Support Package Stack to a Java system the Java Support Package Manager (JSPM)
will necessarily restart the system several times to make the changes effective With a dual-stack
system (ABAP+Java) the ABAP part will only be restarted when JSPM is updating the SAP kernel
and IGS
The following components belong to the usage type SAP NetWeaver Application Server Java (AS Java)
Software Components of Application Server Java
Component to Be Updated SP File Name Tool Used to Apply SP
SAP Kernel 720 32-64-BIT UNICODE SAPEXESAR
SAPEXEDBSAR
JSPM
SAP IGS 700 igsexesar
BI META MODEL REPOSITORY 702 BIMMRltSPgt_ltPLgtSCA
J2EE ENGINE CORE TOOLS 702 CORETOOLSltSPgt_ltPLgtSCA
J2EE ENGINE BASE TABLES 702 BASETABLESltSPgt_ltPLgtSCA
BI UDI 702 BIUDIltSPgt_ltPLgtSCA
DI BUILD TOOL 702 SAPBUILDTltSPgt_ltPLgtSCA
SAP CAF 702 CAFltSPgt_ltPLgtSCA
SAP IKS 702 KMKWJIKSltSPgt_ltPLgtSCA
JAVA LOG VIEWER 702 JLOGVIEWltSPgt_ltPLgtSCA
SAP J2EE ENGINE CORE 702 SAPJEECORltSPgt_ltPLgtSCA
SAP JAVA TECH SERVICES 702 SAPJTECHSltSPgt_ltPLgtSCA
SAP TECH S OFFLINE 702 SAPJTECHFltSPgt_ltPLgtSCA
SAP J2EE ENGINE 702 SAPJEEltSPgt_ltPLgtSCA
JAVA SP MANAGER 702 JSPMltSPgt_ltPLgtSCA
ADOBE DOCUMENT SERVICES 702 ADSSAPltSPgt_ltPLgtSCA
UME ADMINISTRATION 702 UMEADMINltSPgt_ltPLgtSCA
LIFECYCLE MGMT TOOLS 702 LMTOOLSltSPgt_ltPLgtSCA
SAP CAF-UM 702 CAFUMltSPgt_ltPLgtSCA
SAP SOFTW DELIV MANAGER 702 SDMKITltSPgt_ltPLgtJAR
SOFTWARE LIFECYCLE MANAGER 702 SWLIFECYCLltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2060 CUSTOMER 2012-08-30
NOTE
This table contains only software components that belong to the usage type AS Java Software
components of other usage types and Java application units are listed in the corresponding
sections
NOTE
As of Support Package 09 you can update your system with SAP Kernel 720 instead of SAP Kernel
701
222 Preparation for Applying a Support Package Stack
Procedure
1 Download the Support Package Stack with all usage types to be updated and the stack definition
XML file as described in Downloading Support Package Stacks [page 12]
NOTE
You can find the activated usage types in an existing Java system on the Deployed Components tab
page on the JSPM user interface
NOTE
You do not need to download the SP Stacks between the source SP Stack level and target SP
Stack level By default the target SP Stack level is the latest available SP Stack
2 Make sure the following requirements are met prior to applying the Support Package Stack
You have familiarized yourself with SAP Note 891983 before you start the Java Support Package
Manager
The system to be updated is fully functional
The Support Package Stack you want to apply and the corresponding stack definition XML
file are available in the EPS inbox directory usrsaptransEPSin By default this location
can be also referred to as ldquoJSPM inboxrdquo
The SAP NetWeaver Application Server Java (AS Java) and the database have been backed up
You have not deleted renamed or created any directories and files in the following directories
and their subdirectories usrsapltSAPSIDgtSYSexe and usrsapltSAPSIDgtSYS
profile
Otherwise JSPM cannot detect the kernel and the system profiles and cannot be started If a
backup of the kernel and the system profiles has been required it has been created in a different
directory
The ltsapsidgtadm user has Read permissions for the EPS inbox directory usrsaptransEPS
in
If your database is SAP MaxDB the overwrite mode for the log area has been activated
The database and the SDM repository have been synchronized
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2160
For more information see the online documentation for JSPM on SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70 Library
(including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library Administrators Guide
Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems AS Java
(Application Server for Java) Software Logistics Software Maintenance Java Support Package Manager
Then choose Troubleshooting JSPM Does Not Update the Versions of the Deployed Components
There is enough disk space
For more information see SAP Note 891895
Your current SAPCAR tool is able to extract the Support Packages for the SAP kernel and
other OS level binaries delivered as SAR files
RECOMMENDATION
You can download the latest version of SAPCAR from SAP Service Marketplace at
httpservicesapcompatches Entry by Application Group Additional Components
SAPCAR
Put the downloaded version in the same directory in the JSPM inbox in which the kernel
SAR files reside so that JSPM can use this version for extracting the SAR files
3 Only valid for Linux |
For RHEL 4 and SLES 9 you need to install additional operating system packages For more
information see SAP Note 1021236End of Linux |
4 Only valid for Windows |
For Windows you need to install additional operating system packages For more information see
SAP Note 684106End of Windows |
5 To prevent the Software Deployment Manager (SDM) from temporarily exceeding the available
disk space during the update process you can change the file transfer directory of SDM in a system
of SPS09 or higher using the following command sequence
Only valid for Windows |
cd ltsdm_homegt
StopServerbat
sdmbat jstartup mode=standalone
sdmbat filetransferdir dir=ltnew_dirgt
sdmbat jstartup mode=integrated
StartServerbat
End of Windows |
Only valid for IBM i5OSUNIX |
cd ltsdm_homegt
StopServersh
sdmsh jstartup mode=standalone
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2260 CUSTOMER 2012-08-30
sdmsh filetransferdir dir=ltnew_dirgt
sdmsh jstartup mode=integrated
StartServersh
End of IBM i5OSUNIX |
6 To prevent deployment errors during the update process proceed as follows
1 Log on to the Central Instance host
2 Start the ConfigTool and in the navigation area choose Cluster-data Global server configuration
Managers ServiceManager
3 In the Global properties panel set the Custom value of the EventTimeout property to 120
4 Choose Save
5 Restart the Central Instance
7 Check whether the used JDK version and the Java VM settings of the Java runtime system comply
with the requirements in SAP Note 723909 Update the JDK and adjust the settings if necessary
NOTE
An update of the used JDK version possibly changes the JVM path In this case you must
make the new path available to all Dialog Instances of the J2EE engine by implementing option
1 of SAP Note 718901
8 Make sure that the J2EE administrator password stored in the secure store for offline usage is
identical with the one stored in the User Management Engine (UME) You can change the password
in the secure store as described in SAP Note 870445
9 If you are running a high availability system on Windows you might need to prepare your system
as described in the online documentation for JSPM see section Preparing Systems That Run in High
Availability Environment
223 Updating the Application Server Java and Java-Based Components
Procedure
Applying a Support Package Stack to SAP NetWeaver Application Server Java and Java-Based Components
NOTE
The JSPM GUI might not work properly on some UNIX systems For more information and the
solution see SAP Note 1013976
1 Log on as user ltsapsidgtadm to the Central Instance host
NOTE
If your operating system is IBM i log on as user ltSIDgtADM or ltSIDgtOFR
2 Close the SAP Management Console (SAP MMC) and the SDM remote GUI client
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2360
3 For UNIX and Windows To start the JSPM navigate to the directory ltINSTDIRgtltSIDgt
ltCentral_Instance_Namegtj2eeJSPM and run the go script file
NOTE
If your system is running on IBM i to start the JSPM proceed as follows
1 To prevent JSPM from automatically starting its GUI in the file usrsapltSIDgt
ltCentral_Instance_Namegtj2eeJSPMparamjspm_configtxt change the
property dialogSDTServerConnectionSDTGuilaunch from true to false
2 On the IBM i host run the go script file using the following command
QSH CMD(usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPMgo)
3 In the mounted directory usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPM run
the StartGui script file The JSPM GUI appears
4 In the Host field enter the target IBM i host
NOTE
Depending on the system type ltCentral_Instance_Namegt has the following syntax
Standalone Java system JCltinstance_nogt
Add-On system DVEBMGSltinstance_nogt
4 Enter your SDM password to log on to the SDM
5 On the Deployment tab page select the Java Support Package Manager option and update the software
component sapcomJSPM to the target SPS level
6 Restart the JSPM and log on with the SDM password
RECOMMENDATION
We strongly recommend that you use the Support and Enhancement Package Stack option when
applying a Support Package Stack Other options can lead to unintended consistency issues
NOTE
If you need to include the latest patches for a particular component during the update process
with the Support and Enhancement Package Stack option stop the JSPM after restart and apply SAP
Note 1080821 Then start the JSPM again
7 On the Deployment tab page select the Support and Enhancement Package Stack option and choose Next
The Support Package Stacks that are available for deployment in the global EPS inbox directory
are displayed
8 In the Target SP Stack Level dropdown box select the Support Package Stack to be applied and choose
Next
In this step JSPM performs various status validations and displays the result of each software
component included in the stack definition XML file on the subsequent screen which includes
the following possible statuses
OK Indicates that the SPS level of the corresponding software component is applicable
WARNING We recommend that you view the details about the component by choosing Show
Details
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2460 CUSTOMER 2012-08-30
This status may indicate that the corresponding software component comprises custom
modifications in an NWDI-controlled system
If your system is used for NWDI development and it is either a DEV or a CONS system
you will be informed that JSPM will not deploy the modified software components but
only transport them to the CMS transport directory JSPM will deploy only the software
components that are not modified
If your system is not used for NWDI development or if your system is used for NWDI
development and it is either a TEST or a PROD system you will be informed that JSPM
has found newer versions of modified software components and will automatically replace
the original versions with the newer versions JSPM will deploy all software components
that are not modified together with the replaced versions of the modified software
components
CAUTION
You may get a warning telling you that there are patches installed in your system
containing fixes which might not be included in the target SP Stack This is possible if
you have applied patches of the start SP Stack level that were delivered later than the
target SP Stack delivery date In order not to lose these fixes you need to download and
apply the corresponding patches of the target SP Stack level
If you are performing an update from SAP NetWeaver 70 including enhancement
package 1 SPS00 and you have not applied any patches for the software component with
status WARNING before the update then you can ignore warnings such as the following
example
The new version of the development component sapcomcomsapnetweaver
bcrfmoni is 70100200806121227180000 and is lower than the already
deployed version 70100200807090143420000
REVISE Indicates inconsistencies with the corresponding software component
The deployment cannot be performed until all problems have been resolved You can view
the problems by choosing Show Details
9 If the status of the selected SP Stack is OK or WARNING you can start the system update by choosing
Start JSPM then changes the status to SCHEDULED
If the SP Stack to be applied includes a kernel update and the current kernel is not already of the
corresponding patch level JSPM arranges the kernel update as the very first Support Package to
be applied JSPM updates the kernel binaries of all instances (including Dialog Instances and SCS
instances in a HA environment) whose kernel directories DIR_CT_RUN effectively reside on the host
indicated by the profile parameter SAPGLOBALHOST
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2560
CAUTION
Kernel binaries of instances whose kernel directories DIR_CT_RUN are not effectively linked
to the host SAPGLOBALHOST must be updated individually as described in section Manually
Updating Instances with Kernel Directory Located on Separate Hosts below
The kernel update (includes update of SAP Kernel and SAP IGS) using JSPM consists of the following
steps
1 JSPM stops the Central Instance automatically and prompts you to stop the remote SCS and
Dialog Instances manually
2 After you have stopped all the instances choose the Next button in the dialog box
The kernel update starts
NOTE
If the system is running in a high availability environment make sure that the HA
software does not restart the instance automatically during the update
NOTE
If kernel binaries of the SCS instance need to be updated manually (see Manually Updating
Instances with Kernel Directory Located on Separate Hosts below) you must perform this at the
time when JSPM is updating the kernel binaries of the Central Instance In any case the
SCS kernel must be up-to-date before the next restart
When the kernel update is finished a dialog box appears in which you are prompted to restart
the SCS instance manually
3 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries
before you can proceed with the next step For more information see Adjusting the Ownership and
Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
4 Choose Next in the dialog box when the SCS instance is running again
After the kernel update JSPM restarts the system for further deployment of the remaining Support
Packages in the stack
RECOMMENDATION
If you need to update the kernel binaries of any Dialog Instances manually (see Manually
Updating Instances with Kernel Directory Located on Separate Hosts below) perform the update when
JSPM is updating the remaining Support Packages in the stack in order to save time
The deployment of each Support Package can end with one of the following statuses
DEPLOYED
The Support Package has been successfully deployed
DEPLOYED WITH WARNING
The Support Package has been deployed but it possibly may not work properly with other
deployed components
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2660 CUSTOMER 2012-08-30
You can view the details by choosing Show Details or examining the log files You can also view
the details about the component by choosing the Deployed Components tab page
ERROR
An error has occurred during the deployment You can view the details by choosing Show
Details or examining the log files
You must correct the error to be able to continue with the SP Stack update
You can proceed as described for a deployment that finished with status DEPLOYED WITH
WARNING
If the error correction does not change the contents in the JSPM inbox you can continue
the deployment by choosing Resume
If the error correction changes the contents in the JSPM inbox you can choose New
Deployment to redeploy the SP Stack
NOT DEPLOYED
JSPM has not attempted to deploy the software component for certain reasons
If your system is not used for NWDI development you can proceed as described for a
deployment that finished with status ERROR
If your system is used for NWDI development and it is either a DEV or a CONS system
the status of the modified software components is always NOT DEPLOYED JSPM has
transported the software components of the Support Package Stack both modified and
not modified to the CMS transport directory The deployment of the modified software
components is handled by NWDI
Manually Updating Instances with Kernel Directory Located on Separate Hosts
JSPM performs kernel update for all instances (including Dialog Instances and SCS instances in a HA
environment) whose kernel directories DIR_CT_RUN effectively reside on the host indicated by the profile
parameter SAPGLOBALHOST (by using folder sharing on Windows or file system mounting on UNIX) In
rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of those sort of instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances individually
To update the kernel of an instance manually proceed as follows
1 Log on as user ltsapsidgtadm to the host of the instance to be updated
2 Back up the kernel directory which is specified by the profile parameter DIR_CT_RUN
3 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory with
SAPCAR [page 56]
4 Stop the instance being updated
NOTE
If the system is running in a HA environment make sure that the HA software does not
restart the instance automatically during the update
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2760
5 Copy or move the extracted programs from the temporary directory to the local kernel directory
6 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries as
described in section Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
7 Restart the instance after JSPM has finished the deployment of all packages on the Central Instance
Only valid for UNIX |
Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms
On UNIX platforms you must adjust the ownership and execution permissions of the kernel binaries
after the update regardless whether you performed the update manually or by using JSPM because
both update procedures are performed with the ltsapsidgtadm user Enter the following command
sequence
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
224 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the Java system
23 Parallel Update of Dual-Stack Systems
If you perform an update of a dual-stack system (ABAP+Java) we recommend that you follow the
procedure described below The procedure has been validated to update the ABAP stack and the Java
stack of a NetWeaver system in parallel thus reducing the overall system downtime by half
Procedure
1 Before applying ABAP and Java Support Packages use the Single Support Packages option in JSPM and
select for update only the components SAP KERNEL and BC-FES-IGS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
23 Parallel Update of Dual-Stack Systems
2860 CUSTOMER 2012-08-30
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS)
runs on a dedicated host In this case JSPM does not support update of kernel binaries and
you need to update them manually Perform the update manually as described under Updating
SAP Kernel and SAP IGS in section Updating the Application Server ABAP and ABAP-Based Software
Components [page 16]
2 Import the Support Packages for the component SAP_BASIS into the ABAP stack using the ABAP
Support Package Manager (SPAM)
3 Import the remaining ABAP Support Packages with SPAM and in parallel apply the Java Support
Package Stack with JSPM
Proceed as described in Updating the Application Server ABAP and ABAP-Based Software Components [page
16] and Updating the Application Server Java and Java-Based Software Components [page 23]
24 Process Integration
241 Planning
Procedure
This section covers all the units of Process Integration that should be updated Particularly the following
units must always have the same Support Package level (the patch level can be different)
Integration Server
XI Adapter Engine
Partner Connectivity Kit
System with the Usage Type Process Integration
Software components of Integration Server
Components to Be Updated SP File Name Tool Used to Apply SP
Java stack
XI TOOLS 702 SAPXITOOLltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
ABAP stack
XI CONTENT SAP_BASIS 702 SAPBASISltSPgt_ltPLgtZIP File upload
XI CONTENT SAP_ABA 702 SAPABAltSPgt_ltPLgtZIP
SAP NetWeaver Application Server ABAP (see table Software components of Application Server ABAP [page 15])Note that update of the following software components of the ABAP system is not required SAP ABA 702 SAP BW 702 PI_BASIS 702
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 2960
J2EE Adapter Engine
If your implemented scenario includes a J2EE Adapter Engine then it must always be of the same
Support Package level as the Integration Server
Components of the J2EE Adapter Engine
Component to Be Updated SP File NameTool Used to Apply SP
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
J2SE Adapter Engine
The installation of the J2SE Adapter Engine depends on the implemented scenario
Components of the J2SE Adapter Engine
Component to Be Updated SP File Name Tool Used to Apply SP
XI CONNECTIVITY SE 702 SAPXICONSltSPgt_ltPLgtSCA ZIP tool (for example WinZip)
Partner Connectivity Kit
If your implemented scenario includes a Partner Connectivity Kit (PCK) then it must always be of the
same Support Package level as the Integration Server
Software components of Partner Connectivity Kit
Components to Be Updated SP File NameTool Used to Apply SP
XI PCK 702 SAPXIPCKltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of the Application Server Java [page 20])
System Landscape Directory (SLD)
The System Landscape Directory is required for the PI operations Although updating the SLD is not
necessarily required it is advisable to update the SLD server and the SAP Master Data Content within
it from time to time The update of the SLD includes
1 The system where the SLD is running
2 The SAP Master Data Content within this SLD
SAP GUI
See table Compatible SAP GUI Versions [page 51]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3060 CUSTOMER 2012-08-30
242 Updating Units of Process Integration
Procedure
Before you start the update perform the following steps
In the Runtime Workbench use Communication Channel Monitoring to stop all sender channels
for all adapter types on all your Adapter Engines
On the Integration Server use transaction SMQR and deregister all qRFC queues
System with the Usage Type Process Integration
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the XI instance is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system where the XI instance is running
For more information see Application Server Java and Java-Based Software Components [page 19]
System Landscape Directory (Optional)
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the SLD is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the entire Support Package Stack to the system where the SLD is running
For more information see Application Server Java and Java-Based Software Components [page 19]
J2EE Adapter Engine
Apply the Support Package Stack to the system where the Adapter Engine is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Partner Connectivity Kit
Apply the Support Package Stack to the system where the PCK is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Front End GUIs
Update the SAP GUI components if necessary
For more information see SAP GUI Family [page 51]
ABAP 700 Business System (Optional)
Apply the Support Packages for SAP NetWeaver Application Server ABAP (including SAP kernel and
the Support Package for SAP BASIS 700)
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 640 Business System (Optional)
Apply the Support Packages for SAP Web Application Server ABAP 640 (including SAP kernel and the
Support Package for SAP BASIS 640)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3160
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 620 Business System (Optional)
1 Update the SAP Kernel 620
2 Import the released Basis Support Packages for SAP Web AS 620 as well as the most recent Add-
On Support Package for APPINT 200_620 in the order described in SAP Note 439915
J2SE Adapter Engine (Optional)
NOTE
The XI Adapter Engine (J2SE) and all its adapters are provided for compatibility reasons only and
are not developed any further You have to use the XI Adapter Engine running on SAP NetWeaver
AS Java For more information see the Master Guide ndash SAP NetWeaver 70 available on SAP Service
Marketplace at httpservicesapcominstallNW70 Planning
1 Extract the SAPXICONSltSPgt_ltPLgtSCA (XI Connectivity SE 700) archive (ZIP format) to a temporary
directory
2 Save the old configuration files as described in the document Adapterpdf in directory
lttemp_directorygttech_adapterAdministrationDocumentation
3 Unpack the ZIP archive TechnicalAdapterssda to the installation directory of the XI Adapter
Engine (J2SE)
4 Restore the configuration files with restore_configuration
243 Post-Installation Steps
Procedure
Communication Channels and Queues
Restart all stopped sender channels and register all deregistered qRFC queues
XI Content
In the system with usage type PI import the XI content from the archives SAPBASISltSPgt_ltPLgtZIP
and SAPABAltSPgt_ltPLgtZIP as follows
1 Unpack the archives using a ZIP tool of your choice
2 Copy the corresponding export files (with file extension tpz) to the import directory ltINSTDIRgt
ltSAPSIDgtSYSglobalxirepository_serverimport
3 Start the Integration Builder (transaction SXMB_IFR)
4 Enter the Integration Repository by choosing Repository (Design)
5 Choose Tools Import design objects
6 Import the tpz files containing the XI content
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3260 CUSTOMER 2012-08-30
NOTE
For more information see SAP Note 836200
Role Generation on the Integration Server
On the Integration Server execute transaction SUPC (mass generation of roles) for all SAP_XI roles in
each of your clients to regenerate possibly changed roles
NOTE
Do not forget to make a user comparison for regenerated roles afterwards
Partner Connectivity Kit (Optional)
Perform the post-installation steps for PCK as described in SAP Note 746328
SAP Master Data within the SLD (Optional)
In the system where your SLD is running import the latest SLD content as described in SAP Note
669669
Receiver-Based EOIO Serialization in J2EE Adapter Engine (Optional)
The J2EE Adapter Engine can be switched to receiver-based EOIO serialization The switch can be
triggered on demand and is executed asynchronously It includes a database migration step during
which all EOIO processing in the Adapter Engine is disabled See SAP Note 973894 for details about how
to start the EOIO serialization migration
Service Metering (Optional)
Service metering gathers information about a service caller transfers it to the service provider and
counts on the service provisioning side how many times a service is called and by which service caller
Service metering is performed for the XI message protocol and the WS message protocol Service
metering is automatically enabled after applying a Support Package Stack By default only non-sensitive
data is transmitted to internal or external service providers in a compatible way
Service metering can be configured in PI in the Integration Engine on sender-side and in the Integration
Directory
Service metering can be configured in AS ABAP in transaction SOAMANAGER
Only if the service provider is allowed to receive more detailed information about the service caller set
the metering level to higher than the default
For more information see SAP Note 1239428
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3360
25 Business Intelligence
251 Planning
Procedure
Business Intelligence includes one or many of the following units that must be updated depending on
your implemented scenarios The usage types Business Intelligence (BI) and Business Intelligence Java
Components (BI-Java) must always have the same Support Package level
Business Intelligence
Software Components of Business Intelligence
Component to Be Updated SP File Name Tool Used to Apply SP
BI CONT ADDON 70x SAPK-70ltxgtltSPgtINBICONT SAINT
SAP NetWeaver Application Server ABAP (see table Software Components of Application Server ABAP [page 15])
NOTE
For information about the dependencies applying to BI Content Support Packages see SAP Note
653814 BI CONT 703 Support Packages are not part of the NetWeaver SP Stacks Updates can be
performed when applicable Alternatively BI CONT 704 Support Packages can be imported See
the BI Content release strategy in SAP Note 153967
Business Intelligence Java Components
BI Java Components
Component to Be Updated SP File NameTool Used to Apply SP
BI REPORTING AND PLANNING 702 BIREPPLANltSPgt_ltPLgtSCA JSPM
BI WEBDYNPRO ALV 702 BIWDALVltSPgt_ltPLgtSCA
BI INFORM BROADCASTING 702 BIIBCltSPgt_ltPLgtSCA
BI WEB APPLICATIONS 702 BIWEBAPPltSPgt_ltPLgtSCA
BI BASE SERVICES 702 BIBASESltSPgt_ltPLgtSCA
VISUAL COMPOSER BI KITS 702 VCKITBIltSPgt_ltPLgtSCA
Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
BI Precalculation Service
Components of the BI Precalculation Service
Component to Be Updated SP File Name Tool Used to Apply SP
BI Pre-calculation Service 700 xPreCalServerltSPgt_ltPLgtexe Installer
Search and Classification (TREX)
See table TREX Component [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3460 CUSTOMER 2012-08-30
BI Accelerator
The BI Accelerator is based on the TREX technology It is a special Linux 64-bit version of SAP NetWeaver
70 Search and Classification (TREX) which is delivered on preconfigured hardware
NOTE
You cannot use a TREX installation based on 32-bit architecture that is configured for searching
in metadata and documents for the BI Accelerator And vice versa a BI Accelerator box cannot
be used for searching in metadata and documents
If you want to use the search functionality as well as the BI Accelerator you require two separate
installations For more information see BI Accelerator [page 47]
Clients
Depending on your implemented scenarios you have to update SAP GUI Components and Business
Explorer (BI Add-OnBW Add-On)
NOTE
See SAP Note 889314 to determine when to use the BI Add-On and the BW Add-On
NOTE
As SAP GUI 640 is no longer supported BI Frontend Support Package 1800 resp patch 1801 is the
last Support Package resp patch based on SAP GUI 640 For more information see SAP Note
1231292 (Frontend Add-in Strategy 640710 GUI Version)
For more information about the new release strategy for the BI Frontend see SAP Note 1231363
(Changed Delivery Strategy for BI Frontend)
252 Preparation
Procedure
For the Support Packages of the most important Business Intelligence units so called SAPBINews
(SAPBWNews) Notes are created Read these Notes before updating Business Intelligence For SAP
NetWeaver 70 including enhancement package 2 SPS 12 these are the following
Business Intelligence ABAP SAP Note 1680996
Business Intelligence Java Components SAP Note 1726461
BI 70 Frontend Add-On for SAP GUI 710 SAP Note 1413032
BI 70 Frontend Add-On for SAP GUI 720 SAP Note 1630112
BI 70 Frontend Add-On for SAP GUI 730 SAP Note 1726739
For more information about BI Support Packages see SAP Community Network at http
scnsapcomcommunitydata-warehousingnetweaver-bw Related Resources SAP NW BW Support
Packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
2012-08-30 CUSTOMER 3560
253 Updating Units of Business Intelligence
Procedure
Business Intelligence
1 Update the SAP NetWeaver Application Server ABAP (with BI CONT 70x if necessary) with the
appropriate Support Packages
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
NOTE
When applying the component SAP BW 702 some generation errors might occur When
you start importing the BI Support Packages in transaction SPAM choose the menu path
Extras Ignore generation errors For more information see SAP Note 114134
2 Apply the Support Package Stack to the system with the usage type BI-Java
For more information see Application Server Java and Java-Based Software Components [page 19]
3 Update the BI Precalculation Service that is used in your scenario
4 Update the standalone engine Search and Classification (TREX) that is used in your scenario For more
information see Standalone Engine Search and Classification (TREX) [page 44]
NOTE
You have to update TREX to the newest version if you use search capabilities within Business
Intelligence
5 Update the BI Accelerator to the newest available version For more information see BI
Accelerator [page 47]
6 Update the SAP GUI and Business Explorer (BI Add-On BW Add-On) on all remote client hosts
that are involved in the scenario
For more information see SAP GUI Family [page 51] and Business Explorer (BI Add-On BW Add-On)
[page 51]
BI Precalculation Service
1 Log on to the host as a user with administration rights
2 Install the Support Package of the BI Precalculation Service by executing the
xPreCalServerexe file
The welcome screen of the BI Precalculation Server setup wizard appears
The setup now checks the system for the prerequisites
3 Choose the option Update for updating the BI Precalculation service to the current patch level and
then Finish
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3660 CUSTOMER 2012-08-30
26 EP Core
261 Planning
Procedure
The following installable software units must be updated
EP Core
Software Components of EP Core
Component to Be Updated SP File Name Tool Used to Apply SP
PORTAL CORE SERVICES 702 EPBCltSPgt_ltPLgtSCA JSPM
PORTAL FRAMEWORK 702 EPBC2ltSPgt_ltPLgtSCA
PORTAL 702 EPPSERVltSPgt_ltPLgtSCA
PORTAL WEB DYNPRO 702 EPWDCltSPgt_ltPLgtSCA
UWL COLL PROCESS ENGINE 702 UWLJWFltSPgt_ltPLgtSCA
CAF EU 702 SAPEUltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
262 Preparation
Procedure
Backing Up the Portal Runtime Configuration
If you have made changes to the standard Portal Runtime configuration you have to make a backup
of the configuration before the update process For more information see SAP Note 1064468
263 Updating EP Core
Procedure
Apply the Support Package Stack to a system with usage type EP Core
For more information see Application Server Java and Java-Based Software Components [page 19]
264 Post-Installation Steps for EP Core
Procedure
Restoring the Portal Runtime Configuration
To make your changes to the standard Portal Runtime Configuration effective you have to restore
the backup of the configuration done before the update process For more information see SAP Note
1064468
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
26 EP Core
2012-08-30 CUSTOMER 3760
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
CAUTION
The automatic distribution by means of SAPCPE depends on the settings of the profile parameters
DIR_CT_RUN for the global kernel directory and DIR_EXECUTABLE for the local directory of the
executables Before you continue check the instance profiles for the settings of these parameters
in systems that are not installed using SAPinst (for example systems upgraded from older releases
copied or migrated systems)
CAUTION
If your system is a dual-stack system (ABAP+Java) and the ABAP stack has a non-Unicode kernel
be aware that the SCS instance has a Unicode kernel You have to update both kernels (together
with SAP IGS) prior to updating the ABAP and Java Support Package stacks This ensures
compatibility and reduces system downtime
RECOMMENDATION
If you perform an update of a dual-stack system (ABAP+Java) we recommend that prior to
applying ABAP and Java Support Package stacks you use the Single Support Packages option in JSPM
and select for update only the components SAP KERNEL and BC-FES-IGS
For more information about updating a dual-stack system see Parallel Update of Dual-Stack Systems
[page 28]
If you perform an update of an ABAP system the following procedure applies for updating the SAP
kernel and IGS manually
1 Log on as user ltsapsidgtadm to the instance host to be updated
2 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory using
SAPCAR [page 56]
3 Stop the ABAP system that you want to update
NOTE
If the system is running in a high availability (HA) environment make sure that the HA
software does not restart the system automatically during the update
4 Back up the kernel directory ltkrnl_directorygt
5 Copy or move the extracted programs from the temporary directory to the SAP kernel directory
6 Only valid for UNIX |
Execute the following command sequence on UNIX platforms
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
21 Application Server ABAP and ABAP-Based Software Components
1860 CUSTOMER 2012-08-30
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
7 Restart the SAP system
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS) runs
on a dedicated host You need to perform the kernel update for the ASCS instance manually but
excluding the IGS update because the IGS is not required in an ASCS instance
In rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of such instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances manually Proceed as described
in section Manually Updating Instances with Kernel Directory Located on Separate Hosts below in this document
214 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the ABAP system
22 Application Server Java and Java-Based Software Components
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system which includes
JSPM itself
SAP Kernel and SAP IGS
All Java-based usage types installed in the system
Software Deployment Manager (SDM) - the deployment service of the system
RECOMMENDATION
We strongly recommend that you apply the target Support Package Stack to your system as a
whole This ensures consistency on both the system and the application levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 1960
221 Planning
Procedure
Java Support Package files (SCAs) contain all software objects of the corresponding software
components Thus it is sufficient to apply the Java Support Package files of the intended Support Package
Stack directly to the Java system to be updated It is not necessary to apply the Support Package Stacks
between the start SP Stack level and the target SP Stack level successively
CAUTION
When applying a Support Package Stack to a Java system the Java Support Package Manager (JSPM)
will necessarily restart the system several times to make the changes effective With a dual-stack
system (ABAP+Java) the ABAP part will only be restarted when JSPM is updating the SAP kernel
and IGS
The following components belong to the usage type SAP NetWeaver Application Server Java (AS Java)
Software Components of Application Server Java
Component to Be Updated SP File Name Tool Used to Apply SP
SAP Kernel 720 32-64-BIT UNICODE SAPEXESAR
SAPEXEDBSAR
JSPM
SAP IGS 700 igsexesar
BI META MODEL REPOSITORY 702 BIMMRltSPgt_ltPLgtSCA
J2EE ENGINE CORE TOOLS 702 CORETOOLSltSPgt_ltPLgtSCA
J2EE ENGINE BASE TABLES 702 BASETABLESltSPgt_ltPLgtSCA
BI UDI 702 BIUDIltSPgt_ltPLgtSCA
DI BUILD TOOL 702 SAPBUILDTltSPgt_ltPLgtSCA
SAP CAF 702 CAFltSPgt_ltPLgtSCA
SAP IKS 702 KMKWJIKSltSPgt_ltPLgtSCA
JAVA LOG VIEWER 702 JLOGVIEWltSPgt_ltPLgtSCA
SAP J2EE ENGINE CORE 702 SAPJEECORltSPgt_ltPLgtSCA
SAP JAVA TECH SERVICES 702 SAPJTECHSltSPgt_ltPLgtSCA
SAP TECH S OFFLINE 702 SAPJTECHFltSPgt_ltPLgtSCA
SAP J2EE ENGINE 702 SAPJEEltSPgt_ltPLgtSCA
JAVA SP MANAGER 702 JSPMltSPgt_ltPLgtSCA
ADOBE DOCUMENT SERVICES 702 ADSSAPltSPgt_ltPLgtSCA
UME ADMINISTRATION 702 UMEADMINltSPgt_ltPLgtSCA
LIFECYCLE MGMT TOOLS 702 LMTOOLSltSPgt_ltPLgtSCA
SAP CAF-UM 702 CAFUMltSPgt_ltPLgtSCA
SAP SOFTW DELIV MANAGER 702 SDMKITltSPgt_ltPLgtJAR
SOFTWARE LIFECYCLE MANAGER 702 SWLIFECYCLltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2060 CUSTOMER 2012-08-30
NOTE
This table contains only software components that belong to the usage type AS Java Software
components of other usage types and Java application units are listed in the corresponding
sections
NOTE
As of Support Package 09 you can update your system with SAP Kernel 720 instead of SAP Kernel
701
222 Preparation for Applying a Support Package Stack
Procedure
1 Download the Support Package Stack with all usage types to be updated and the stack definition
XML file as described in Downloading Support Package Stacks [page 12]
NOTE
You can find the activated usage types in an existing Java system on the Deployed Components tab
page on the JSPM user interface
NOTE
You do not need to download the SP Stacks between the source SP Stack level and target SP
Stack level By default the target SP Stack level is the latest available SP Stack
2 Make sure the following requirements are met prior to applying the Support Package Stack
You have familiarized yourself with SAP Note 891983 before you start the Java Support Package
Manager
The system to be updated is fully functional
The Support Package Stack you want to apply and the corresponding stack definition XML
file are available in the EPS inbox directory usrsaptransEPSin By default this location
can be also referred to as ldquoJSPM inboxrdquo
The SAP NetWeaver Application Server Java (AS Java) and the database have been backed up
You have not deleted renamed or created any directories and files in the following directories
and their subdirectories usrsapltSAPSIDgtSYSexe and usrsapltSAPSIDgtSYS
profile
Otherwise JSPM cannot detect the kernel and the system profiles and cannot be started If a
backup of the kernel and the system profiles has been required it has been created in a different
directory
The ltsapsidgtadm user has Read permissions for the EPS inbox directory usrsaptransEPS
in
If your database is SAP MaxDB the overwrite mode for the log area has been activated
The database and the SDM repository have been synchronized
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2160
For more information see the online documentation for JSPM on SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70 Library
(including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library Administrators Guide
Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems AS Java
(Application Server for Java) Software Logistics Software Maintenance Java Support Package Manager
Then choose Troubleshooting JSPM Does Not Update the Versions of the Deployed Components
There is enough disk space
For more information see SAP Note 891895
Your current SAPCAR tool is able to extract the Support Packages for the SAP kernel and
other OS level binaries delivered as SAR files
RECOMMENDATION
You can download the latest version of SAPCAR from SAP Service Marketplace at
httpservicesapcompatches Entry by Application Group Additional Components
SAPCAR
Put the downloaded version in the same directory in the JSPM inbox in which the kernel
SAR files reside so that JSPM can use this version for extracting the SAR files
3 Only valid for Linux |
For RHEL 4 and SLES 9 you need to install additional operating system packages For more
information see SAP Note 1021236End of Linux |
4 Only valid for Windows |
For Windows you need to install additional operating system packages For more information see
SAP Note 684106End of Windows |
5 To prevent the Software Deployment Manager (SDM) from temporarily exceeding the available
disk space during the update process you can change the file transfer directory of SDM in a system
of SPS09 or higher using the following command sequence
Only valid for Windows |
cd ltsdm_homegt
StopServerbat
sdmbat jstartup mode=standalone
sdmbat filetransferdir dir=ltnew_dirgt
sdmbat jstartup mode=integrated
StartServerbat
End of Windows |
Only valid for IBM i5OSUNIX |
cd ltsdm_homegt
StopServersh
sdmsh jstartup mode=standalone
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2260 CUSTOMER 2012-08-30
sdmsh filetransferdir dir=ltnew_dirgt
sdmsh jstartup mode=integrated
StartServersh
End of IBM i5OSUNIX |
6 To prevent deployment errors during the update process proceed as follows
1 Log on to the Central Instance host
2 Start the ConfigTool and in the navigation area choose Cluster-data Global server configuration
Managers ServiceManager
3 In the Global properties panel set the Custom value of the EventTimeout property to 120
4 Choose Save
5 Restart the Central Instance
7 Check whether the used JDK version and the Java VM settings of the Java runtime system comply
with the requirements in SAP Note 723909 Update the JDK and adjust the settings if necessary
NOTE
An update of the used JDK version possibly changes the JVM path In this case you must
make the new path available to all Dialog Instances of the J2EE engine by implementing option
1 of SAP Note 718901
8 Make sure that the J2EE administrator password stored in the secure store for offline usage is
identical with the one stored in the User Management Engine (UME) You can change the password
in the secure store as described in SAP Note 870445
9 If you are running a high availability system on Windows you might need to prepare your system
as described in the online documentation for JSPM see section Preparing Systems That Run in High
Availability Environment
223 Updating the Application Server Java and Java-Based Components
Procedure
Applying a Support Package Stack to SAP NetWeaver Application Server Java and Java-Based Components
NOTE
The JSPM GUI might not work properly on some UNIX systems For more information and the
solution see SAP Note 1013976
1 Log on as user ltsapsidgtadm to the Central Instance host
NOTE
If your operating system is IBM i log on as user ltSIDgtADM or ltSIDgtOFR
2 Close the SAP Management Console (SAP MMC) and the SDM remote GUI client
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2360
3 For UNIX and Windows To start the JSPM navigate to the directory ltINSTDIRgtltSIDgt
ltCentral_Instance_Namegtj2eeJSPM and run the go script file
NOTE
If your system is running on IBM i to start the JSPM proceed as follows
1 To prevent JSPM from automatically starting its GUI in the file usrsapltSIDgt
ltCentral_Instance_Namegtj2eeJSPMparamjspm_configtxt change the
property dialogSDTServerConnectionSDTGuilaunch from true to false
2 On the IBM i host run the go script file using the following command
QSH CMD(usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPMgo)
3 In the mounted directory usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPM run
the StartGui script file The JSPM GUI appears
4 In the Host field enter the target IBM i host
NOTE
Depending on the system type ltCentral_Instance_Namegt has the following syntax
Standalone Java system JCltinstance_nogt
Add-On system DVEBMGSltinstance_nogt
4 Enter your SDM password to log on to the SDM
5 On the Deployment tab page select the Java Support Package Manager option and update the software
component sapcomJSPM to the target SPS level
6 Restart the JSPM and log on with the SDM password
RECOMMENDATION
We strongly recommend that you use the Support and Enhancement Package Stack option when
applying a Support Package Stack Other options can lead to unintended consistency issues
NOTE
If you need to include the latest patches for a particular component during the update process
with the Support and Enhancement Package Stack option stop the JSPM after restart and apply SAP
Note 1080821 Then start the JSPM again
7 On the Deployment tab page select the Support and Enhancement Package Stack option and choose Next
The Support Package Stacks that are available for deployment in the global EPS inbox directory
are displayed
8 In the Target SP Stack Level dropdown box select the Support Package Stack to be applied and choose
Next
In this step JSPM performs various status validations and displays the result of each software
component included in the stack definition XML file on the subsequent screen which includes
the following possible statuses
OK Indicates that the SPS level of the corresponding software component is applicable
WARNING We recommend that you view the details about the component by choosing Show
Details
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2460 CUSTOMER 2012-08-30
This status may indicate that the corresponding software component comprises custom
modifications in an NWDI-controlled system
If your system is used for NWDI development and it is either a DEV or a CONS system
you will be informed that JSPM will not deploy the modified software components but
only transport them to the CMS transport directory JSPM will deploy only the software
components that are not modified
If your system is not used for NWDI development or if your system is used for NWDI
development and it is either a TEST or a PROD system you will be informed that JSPM
has found newer versions of modified software components and will automatically replace
the original versions with the newer versions JSPM will deploy all software components
that are not modified together with the replaced versions of the modified software
components
CAUTION
You may get a warning telling you that there are patches installed in your system
containing fixes which might not be included in the target SP Stack This is possible if
you have applied patches of the start SP Stack level that were delivered later than the
target SP Stack delivery date In order not to lose these fixes you need to download and
apply the corresponding patches of the target SP Stack level
If you are performing an update from SAP NetWeaver 70 including enhancement
package 1 SPS00 and you have not applied any patches for the software component with
status WARNING before the update then you can ignore warnings such as the following
example
The new version of the development component sapcomcomsapnetweaver
bcrfmoni is 70100200806121227180000 and is lower than the already
deployed version 70100200807090143420000
REVISE Indicates inconsistencies with the corresponding software component
The deployment cannot be performed until all problems have been resolved You can view
the problems by choosing Show Details
9 If the status of the selected SP Stack is OK or WARNING you can start the system update by choosing
Start JSPM then changes the status to SCHEDULED
If the SP Stack to be applied includes a kernel update and the current kernel is not already of the
corresponding patch level JSPM arranges the kernel update as the very first Support Package to
be applied JSPM updates the kernel binaries of all instances (including Dialog Instances and SCS
instances in a HA environment) whose kernel directories DIR_CT_RUN effectively reside on the host
indicated by the profile parameter SAPGLOBALHOST
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2560
CAUTION
Kernel binaries of instances whose kernel directories DIR_CT_RUN are not effectively linked
to the host SAPGLOBALHOST must be updated individually as described in section Manually
Updating Instances with Kernel Directory Located on Separate Hosts below
The kernel update (includes update of SAP Kernel and SAP IGS) using JSPM consists of the following
steps
1 JSPM stops the Central Instance automatically and prompts you to stop the remote SCS and
Dialog Instances manually
2 After you have stopped all the instances choose the Next button in the dialog box
The kernel update starts
NOTE
If the system is running in a high availability environment make sure that the HA
software does not restart the instance automatically during the update
NOTE
If kernel binaries of the SCS instance need to be updated manually (see Manually Updating
Instances with Kernel Directory Located on Separate Hosts below) you must perform this at the
time when JSPM is updating the kernel binaries of the Central Instance In any case the
SCS kernel must be up-to-date before the next restart
When the kernel update is finished a dialog box appears in which you are prompted to restart
the SCS instance manually
3 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries
before you can proceed with the next step For more information see Adjusting the Ownership and
Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
4 Choose Next in the dialog box when the SCS instance is running again
After the kernel update JSPM restarts the system for further deployment of the remaining Support
Packages in the stack
RECOMMENDATION
If you need to update the kernel binaries of any Dialog Instances manually (see Manually
Updating Instances with Kernel Directory Located on Separate Hosts below) perform the update when
JSPM is updating the remaining Support Packages in the stack in order to save time
The deployment of each Support Package can end with one of the following statuses
DEPLOYED
The Support Package has been successfully deployed
DEPLOYED WITH WARNING
The Support Package has been deployed but it possibly may not work properly with other
deployed components
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2660 CUSTOMER 2012-08-30
You can view the details by choosing Show Details or examining the log files You can also view
the details about the component by choosing the Deployed Components tab page
ERROR
An error has occurred during the deployment You can view the details by choosing Show
Details or examining the log files
You must correct the error to be able to continue with the SP Stack update
You can proceed as described for a deployment that finished with status DEPLOYED WITH
WARNING
If the error correction does not change the contents in the JSPM inbox you can continue
the deployment by choosing Resume
If the error correction changes the contents in the JSPM inbox you can choose New
Deployment to redeploy the SP Stack
NOT DEPLOYED
JSPM has not attempted to deploy the software component for certain reasons
If your system is not used for NWDI development you can proceed as described for a
deployment that finished with status ERROR
If your system is used for NWDI development and it is either a DEV or a CONS system
the status of the modified software components is always NOT DEPLOYED JSPM has
transported the software components of the Support Package Stack both modified and
not modified to the CMS transport directory The deployment of the modified software
components is handled by NWDI
Manually Updating Instances with Kernel Directory Located on Separate Hosts
JSPM performs kernel update for all instances (including Dialog Instances and SCS instances in a HA
environment) whose kernel directories DIR_CT_RUN effectively reside on the host indicated by the profile
parameter SAPGLOBALHOST (by using folder sharing on Windows or file system mounting on UNIX) In
rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of those sort of instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances individually
To update the kernel of an instance manually proceed as follows
1 Log on as user ltsapsidgtadm to the host of the instance to be updated
2 Back up the kernel directory which is specified by the profile parameter DIR_CT_RUN
3 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory with
SAPCAR [page 56]
4 Stop the instance being updated
NOTE
If the system is running in a HA environment make sure that the HA software does not
restart the instance automatically during the update
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2760
5 Copy or move the extracted programs from the temporary directory to the local kernel directory
6 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries as
described in section Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
7 Restart the instance after JSPM has finished the deployment of all packages on the Central Instance
Only valid for UNIX |
Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms
On UNIX platforms you must adjust the ownership and execution permissions of the kernel binaries
after the update regardless whether you performed the update manually or by using JSPM because
both update procedures are performed with the ltsapsidgtadm user Enter the following command
sequence
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
224 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the Java system
23 Parallel Update of Dual-Stack Systems
If you perform an update of a dual-stack system (ABAP+Java) we recommend that you follow the
procedure described below The procedure has been validated to update the ABAP stack and the Java
stack of a NetWeaver system in parallel thus reducing the overall system downtime by half
Procedure
1 Before applying ABAP and Java Support Packages use the Single Support Packages option in JSPM and
select for update only the components SAP KERNEL and BC-FES-IGS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
23 Parallel Update of Dual-Stack Systems
2860 CUSTOMER 2012-08-30
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS)
runs on a dedicated host In this case JSPM does not support update of kernel binaries and
you need to update them manually Perform the update manually as described under Updating
SAP Kernel and SAP IGS in section Updating the Application Server ABAP and ABAP-Based Software
Components [page 16]
2 Import the Support Packages for the component SAP_BASIS into the ABAP stack using the ABAP
Support Package Manager (SPAM)
3 Import the remaining ABAP Support Packages with SPAM and in parallel apply the Java Support
Package Stack with JSPM
Proceed as described in Updating the Application Server ABAP and ABAP-Based Software Components [page
16] and Updating the Application Server Java and Java-Based Software Components [page 23]
24 Process Integration
241 Planning
Procedure
This section covers all the units of Process Integration that should be updated Particularly the following
units must always have the same Support Package level (the patch level can be different)
Integration Server
XI Adapter Engine
Partner Connectivity Kit
System with the Usage Type Process Integration
Software components of Integration Server
Components to Be Updated SP File Name Tool Used to Apply SP
Java stack
XI TOOLS 702 SAPXITOOLltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
ABAP stack
XI CONTENT SAP_BASIS 702 SAPBASISltSPgt_ltPLgtZIP File upload
XI CONTENT SAP_ABA 702 SAPABAltSPgt_ltPLgtZIP
SAP NetWeaver Application Server ABAP (see table Software components of Application Server ABAP [page 15])Note that update of the following software components of the ABAP system is not required SAP ABA 702 SAP BW 702 PI_BASIS 702
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 2960
J2EE Adapter Engine
If your implemented scenario includes a J2EE Adapter Engine then it must always be of the same
Support Package level as the Integration Server
Components of the J2EE Adapter Engine
Component to Be Updated SP File NameTool Used to Apply SP
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
J2SE Adapter Engine
The installation of the J2SE Adapter Engine depends on the implemented scenario
Components of the J2SE Adapter Engine
Component to Be Updated SP File Name Tool Used to Apply SP
XI CONNECTIVITY SE 702 SAPXICONSltSPgt_ltPLgtSCA ZIP tool (for example WinZip)
Partner Connectivity Kit
If your implemented scenario includes a Partner Connectivity Kit (PCK) then it must always be of the
same Support Package level as the Integration Server
Software components of Partner Connectivity Kit
Components to Be Updated SP File NameTool Used to Apply SP
XI PCK 702 SAPXIPCKltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of the Application Server Java [page 20])
System Landscape Directory (SLD)
The System Landscape Directory is required for the PI operations Although updating the SLD is not
necessarily required it is advisable to update the SLD server and the SAP Master Data Content within
it from time to time The update of the SLD includes
1 The system where the SLD is running
2 The SAP Master Data Content within this SLD
SAP GUI
See table Compatible SAP GUI Versions [page 51]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3060 CUSTOMER 2012-08-30
242 Updating Units of Process Integration
Procedure
Before you start the update perform the following steps
In the Runtime Workbench use Communication Channel Monitoring to stop all sender channels
for all adapter types on all your Adapter Engines
On the Integration Server use transaction SMQR and deregister all qRFC queues
System with the Usage Type Process Integration
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the XI instance is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system where the XI instance is running
For more information see Application Server Java and Java-Based Software Components [page 19]
System Landscape Directory (Optional)
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the SLD is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the entire Support Package Stack to the system where the SLD is running
For more information see Application Server Java and Java-Based Software Components [page 19]
J2EE Adapter Engine
Apply the Support Package Stack to the system where the Adapter Engine is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Partner Connectivity Kit
Apply the Support Package Stack to the system where the PCK is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Front End GUIs
Update the SAP GUI components if necessary
For more information see SAP GUI Family [page 51]
ABAP 700 Business System (Optional)
Apply the Support Packages for SAP NetWeaver Application Server ABAP (including SAP kernel and
the Support Package for SAP BASIS 700)
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 640 Business System (Optional)
Apply the Support Packages for SAP Web Application Server ABAP 640 (including SAP kernel and the
Support Package for SAP BASIS 640)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3160
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 620 Business System (Optional)
1 Update the SAP Kernel 620
2 Import the released Basis Support Packages for SAP Web AS 620 as well as the most recent Add-
On Support Package for APPINT 200_620 in the order described in SAP Note 439915
J2SE Adapter Engine (Optional)
NOTE
The XI Adapter Engine (J2SE) and all its adapters are provided for compatibility reasons only and
are not developed any further You have to use the XI Adapter Engine running on SAP NetWeaver
AS Java For more information see the Master Guide ndash SAP NetWeaver 70 available on SAP Service
Marketplace at httpservicesapcominstallNW70 Planning
1 Extract the SAPXICONSltSPgt_ltPLgtSCA (XI Connectivity SE 700) archive (ZIP format) to a temporary
directory
2 Save the old configuration files as described in the document Adapterpdf in directory
lttemp_directorygttech_adapterAdministrationDocumentation
3 Unpack the ZIP archive TechnicalAdapterssda to the installation directory of the XI Adapter
Engine (J2SE)
4 Restore the configuration files with restore_configuration
243 Post-Installation Steps
Procedure
Communication Channels and Queues
Restart all stopped sender channels and register all deregistered qRFC queues
XI Content
In the system with usage type PI import the XI content from the archives SAPBASISltSPgt_ltPLgtZIP
and SAPABAltSPgt_ltPLgtZIP as follows
1 Unpack the archives using a ZIP tool of your choice
2 Copy the corresponding export files (with file extension tpz) to the import directory ltINSTDIRgt
ltSAPSIDgtSYSglobalxirepository_serverimport
3 Start the Integration Builder (transaction SXMB_IFR)
4 Enter the Integration Repository by choosing Repository (Design)
5 Choose Tools Import design objects
6 Import the tpz files containing the XI content
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3260 CUSTOMER 2012-08-30
NOTE
For more information see SAP Note 836200
Role Generation on the Integration Server
On the Integration Server execute transaction SUPC (mass generation of roles) for all SAP_XI roles in
each of your clients to regenerate possibly changed roles
NOTE
Do not forget to make a user comparison for regenerated roles afterwards
Partner Connectivity Kit (Optional)
Perform the post-installation steps for PCK as described in SAP Note 746328
SAP Master Data within the SLD (Optional)
In the system where your SLD is running import the latest SLD content as described in SAP Note
669669
Receiver-Based EOIO Serialization in J2EE Adapter Engine (Optional)
The J2EE Adapter Engine can be switched to receiver-based EOIO serialization The switch can be
triggered on demand and is executed asynchronously It includes a database migration step during
which all EOIO processing in the Adapter Engine is disabled See SAP Note 973894 for details about how
to start the EOIO serialization migration
Service Metering (Optional)
Service metering gathers information about a service caller transfers it to the service provider and
counts on the service provisioning side how many times a service is called and by which service caller
Service metering is performed for the XI message protocol and the WS message protocol Service
metering is automatically enabled after applying a Support Package Stack By default only non-sensitive
data is transmitted to internal or external service providers in a compatible way
Service metering can be configured in PI in the Integration Engine on sender-side and in the Integration
Directory
Service metering can be configured in AS ABAP in transaction SOAMANAGER
Only if the service provider is allowed to receive more detailed information about the service caller set
the metering level to higher than the default
For more information see SAP Note 1239428
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3360
25 Business Intelligence
251 Planning
Procedure
Business Intelligence includes one or many of the following units that must be updated depending on
your implemented scenarios The usage types Business Intelligence (BI) and Business Intelligence Java
Components (BI-Java) must always have the same Support Package level
Business Intelligence
Software Components of Business Intelligence
Component to Be Updated SP File Name Tool Used to Apply SP
BI CONT ADDON 70x SAPK-70ltxgtltSPgtINBICONT SAINT
SAP NetWeaver Application Server ABAP (see table Software Components of Application Server ABAP [page 15])
NOTE
For information about the dependencies applying to BI Content Support Packages see SAP Note
653814 BI CONT 703 Support Packages are not part of the NetWeaver SP Stacks Updates can be
performed when applicable Alternatively BI CONT 704 Support Packages can be imported See
the BI Content release strategy in SAP Note 153967
Business Intelligence Java Components
BI Java Components
Component to Be Updated SP File NameTool Used to Apply SP
BI REPORTING AND PLANNING 702 BIREPPLANltSPgt_ltPLgtSCA JSPM
BI WEBDYNPRO ALV 702 BIWDALVltSPgt_ltPLgtSCA
BI INFORM BROADCASTING 702 BIIBCltSPgt_ltPLgtSCA
BI WEB APPLICATIONS 702 BIWEBAPPltSPgt_ltPLgtSCA
BI BASE SERVICES 702 BIBASESltSPgt_ltPLgtSCA
VISUAL COMPOSER BI KITS 702 VCKITBIltSPgt_ltPLgtSCA
Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
BI Precalculation Service
Components of the BI Precalculation Service
Component to Be Updated SP File Name Tool Used to Apply SP
BI Pre-calculation Service 700 xPreCalServerltSPgt_ltPLgtexe Installer
Search and Classification (TREX)
See table TREX Component [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3460 CUSTOMER 2012-08-30
BI Accelerator
The BI Accelerator is based on the TREX technology It is a special Linux 64-bit version of SAP NetWeaver
70 Search and Classification (TREX) which is delivered on preconfigured hardware
NOTE
You cannot use a TREX installation based on 32-bit architecture that is configured for searching
in metadata and documents for the BI Accelerator And vice versa a BI Accelerator box cannot
be used for searching in metadata and documents
If you want to use the search functionality as well as the BI Accelerator you require two separate
installations For more information see BI Accelerator [page 47]
Clients
Depending on your implemented scenarios you have to update SAP GUI Components and Business
Explorer (BI Add-OnBW Add-On)
NOTE
See SAP Note 889314 to determine when to use the BI Add-On and the BW Add-On
NOTE
As SAP GUI 640 is no longer supported BI Frontend Support Package 1800 resp patch 1801 is the
last Support Package resp patch based on SAP GUI 640 For more information see SAP Note
1231292 (Frontend Add-in Strategy 640710 GUI Version)
For more information about the new release strategy for the BI Frontend see SAP Note 1231363
(Changed Delivery Strategy for BI Frontend)
252 Preparation
Procedure
For the Support Packages of the most important Business Intelligence units so called SAPBINews
(SAPBWNews) Notes are created Read these Notes before updating Business Intelligence For SAP
NetWeaver 70 including enhancement package 2 SPS 12 these are the following
Business Intelligence ABAP SAP Note 1680996
Business Intelligence Java Components SAP Note 1726461
BI 70 Frontend Add-On for SAP GUI 710 SAP Note 1413032
BI 70 Frontend Add-On for SAP GUI 720 SAP Note 1630112
BI 70 Frontend Add-On for SAP GUI 730 SAP Note 1726739
For more information about BI Support Packages see SAP Community Network at http
scnsapcomcommunitydata-warehousingnetweaver-bw Related Resources SAP NW BW Support
Packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
2012-08-30 CUSTOMER 3560
253 Updating Units of Business Intelligence
Procedure
Business Intelligence
1 Update the SAP NetWeaver Application Server ABAP (with BI CONT 70x if necessary) with the
appropriate Support Packages
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
NOTE
When applying the component SAP BW 702 some generation errors might occur When
you start importing the BI Support Packages in transaction SPAM choose the menu path
Extras Ignore generation errors For more information see SAP Note 114134
2 Apply the Support Package Stack to the system with the usage type BI-Java
For more information see Application Server Java and Java-Based Software Components [page 19]
3 Update the BI Precalculation Service that is used in your scenario
4 Update the standalone engine Search and Classification (TREX) that is used in your scenario For more
information see Standalone Engine Search and Classification (TREX) [page 44]
NOTE
You have to update TREX to the newest version if you use search capabilities within Business
Intelligence
5 Update the BI Accelerator to the newest available version For more information see BI
Accelerator [page 47]
6 Update the SAP GUI and Business Explorer (BI Add-On BW Add-On) on all remote client hosts
that are involved in the scenario
For more information see SAP GUI Family [page 51] and Business Explorer (BI Add-On BW Add-On)
[page 51]
BI Precalculation Service
1 Log on to the host as a user with administration rights
2 Install the Support Package of the BI Precalculation Service by executing the
xPreCalServerexe file
The welcome screen of the BI Precalculation Server setup wizard appears
The setup now checks the system for the prerequisites
3 Choose the option Update for updating the BI Precalculation service to the current patch level and
then Finish
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3660 CUSTOMER 2012-08-30
26 EP Core
261 Planning
Procedure
The following installable software units must be updated
EP Core
Software Components of EP Core
Component to Be Updated SP File Name Tool Used to Apply SP
PORTAL CORE SERVICES 702 EPBCltSPgt_ltPLgtSCA JSPM
PORTAL FRAMEWORK 702 EPBC2ltSPgt_ltPLgtSCA
PORTAL 702 EPPSERVltSPgt_ltPLgtSCA
PORTAL WEB DYNPRO 702 EPWDCltSPgt_ltPLgtSCA
UWL COLL PROCESS ENGINE 702 UWLJWFltSPgt_ltPLgtSCA
CAF EU 702 SAPEUltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
262 Preparation
Procedure
Backing Up the Portal Runtime Configuration
If you have made changes to the standard Portal Runtime configuration you have to make a backup
of the configuration before the update process For more information see SAP Note 1064468
263 Updating EP Core
Procedure
Apply the Support Package Stack to a system with usage type EP Core
For more information see Application Server Java and Java-Based Software Components [page 19]
264 Post-Installation Steps for EP Core
Procedure
Restoring the Portal Runtime Configuration
To make your changes to the standard Portal Runtime Configuration effective you have to restore
the backup of the configuration done before the update process For more information see SAP Note
1064468
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
26 EP Core
2012-08-30 CUSTOMER 3760
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
7 Restart the SAP system
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS) runs
on a dedicated host You need to perform the kernel update for the ASCS instance manually but
excluding the IGS update because the IGS is not required in an ASCS instance
In rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of such instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances manually Proceed as described
in section Manually Updating Instances with Kernel Directory Located on Separate Hosts below in this document
214 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the ABAP system
22 Application Server Java and Java-Based Software Components
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system which includes
JSPM itself
SAP Kernel and SAP IGS
All Java-based usage types installed in the system
Software Deployment Manager (SDM) - the deployment service of the system
RECOMMENDATION
We strongly recommend that you apply the target Support Package Stack to your system as a
whole This ensures consistency on both the system and the application levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 1960
221 Planning
Procedure
Java Support Package files (SCAs) contain all software objects of the corresponding software
components Thus it is sufficient to apply the Java Support Package files of the intended Support Package
Stack directly to the Java system to be updated It is not necessary to apply the Support Package Stacks
between the start SP Stack level and the target SP Stack level successively
CAUTION
When applying a Support Package Stack to a Java system the Java Support Package Manager (JSPM)
will necessarily restart the system several times to make the changes effective With a dual-stack
system (ABAP+Java) the ABAP part will only be restarted when JSPM is updating the SAP kernel
and IGS
The following components belong to the usage type SAP NetWeaver Application Server Java (AS Java)
Software Components of Application Server Java
Component to Be Updated SP File Name Tool Used to Apply SP
SAP Kernel 720 32-64-BIT UNICODE SAPEXESAR
SAPEXEDBSAR
JSPM
SAP IGS 700 igsexesar
BI META MODEL REPOSITORY 702 BIMMRltSPgt_ltPLgtSCA
J2EE ENGINE CORE TOOLS 702 CORETOOLSltSPgt_ltPLgtSCA
J2EE ENGINE BASE TABLES 702 BASETABLESltSPgt_ltPLgtSCA
BI UDI 702 BIUDIltSPgt_ltPLgtSCA
DI BUILD TOOL 702 SAPBUILDTltSPgt_ltPLgtSCA
SAP CAF 702 CAFltSPgt_ltPLgtSCA
SAP IKS 702 KMKWJIKSltSPgt_ltPLgtSCA
JAVA LOG VIEWER 702 JLOGVIEWltSPgt_ltPLgtSCA
SAP J2EE ENGINE CORE 702 SAPJEECORltSPgt_ltPLgtSCA
SAP JAVA TECH SERVICES 702 SAPJTECHSltSPgt_ltPLgtSCA
SAP TECH S OFFLINE 702 SAPJTECHFltSPgt_ltPLgtSCA
SAP J2EE ENGINE 702 SAPJEEltSPgt_ltPLgtSCA
JAVA SP MANAGER 702 JSPMltSPgt_ltPLgtSCA
ADOBE DOCUMENT SERVICES 702 ADSSAPltSPgt_ltPLgtSCA
UME ADMINISTRATION 702 UMEADMINltSPgt_ltPLgtSCA
LIFECYCLE MGMT TOOLS 702 LMTOOLSltSPgt_ltPLgtSCA
SAP CAF-UM 702 CAFUMltSPgt_ltPLgtSCA
SAP SOFTW DELIV MANAGER 702 SDMKITltSPgt_ltPLgtJAR
SOFTWARE LIFECYCLE MANAGER 702 SWLIFECYCLltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2060 CUSTOMER 2012-08-30
NOTE
This table contains only software components that belong to the usage type AS Java Software
components of other usage types and Java application units are listed in the corresponding
sections
NOTE
As of Support Package 09 you can update your system with SAP Kernel 720 instead of SAP Kernel
701
222 Preparation for Applying a Support Package Stack
Procedure
1 Download the Support Package Stack with all usage types to be updated and the stack definition
XML file as described in Downloading Support Package Stacks [page 12]
NOTE
You can find the activated usage types in an existing Java system on the Deployed Components tab
page on the JSPM user interface
NOTE
You do not need to download the SP Stacks between the source SP Stack level and target SP
Stack level By default the target SP Stack level is the latest available SP Stack
2 Make sure the following requirements are met prior to applying the Support Package Stack
You have familiarized yourself with SAP Note 891983 before you start the Java Support Package
Manager
The system to be updated is fully functional
The Support Package Stack you want to apply and the corresponding stack definition XML
file are available in the EPS inbox directory usrsaptransEPSin By default this location
can be also referred to as ldquoJSPM inboxrdquo
The SAP NetWeaver Application Server Java (AS Java) and the database have been backed up
You have not deleted renamed or created any directories and files in the following directories
and their subdirectories usrsapltSAPSIDgtSYSexe and usrsapltSAPSIDgtSYS
profile
Otherwise JSPM cannot detect the kernel and the system profiles and cannot be started If a
backup of the kernel and the system profiles has been required it has been created in a different
directory
The ltsapsidgtadm user has Read permissions for the EPS inbox directory usrsaptransEPS
in
If your database is SAP MaxDB the overwrite mode for the log area has been activated
The database and the SDM repository have been synchronized
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2160
For more information see the online documentation for JSPM on SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70 Library
(including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library Administrators Guide
Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems AS Java
(Application Server for Java) Software Logistics Software Maintenance Java Support Package Manager
Then choose Troubleshooting JSPM Does Not Update the Versions of the Deployed Components
There is enough disk space
For more information see SAP Note 891895
Your current SAPCAR tool is able to extract the Support Packages for the SAP kernel and
other OS level binaries delivered as SAR files
RECOMMENDATION
You can download the latest version of SAPCAR from SAP Service Marketplace at
httpservicesapcompatches Entry by Application Group Additional Components
SAPCAR
Put the downloaded version in the same directory in the JSPM inbox in which the kernel
SAR files reside so that JSPM can use this version for extracting the SAR files
3 Only valid for Linux |
For RHEL 4 and SLES 9 you need to install additional operating system packages For more
information see SAP Note 1021236End of Linux |
4 Only valid for Windows |
For Windows you need to install additional operating system packages For more information see
SAP Note 684106End of Windows |
5 To prevent the Software Deployment Manager (SDM) from temporarily exceeding the available
disk space during the update process you can change the file transfer directory of SDM in a system
of SPS09 or higher using the following command sequence
Only valid for Windows |
cd ltsdm_homegt
StopServerbat
sdmbat jstartup mode=standalone
sdmbat filetransferdir dir=ltnew_dirgt
sdmbat jstartup mode=integrated
StartServerbat
End of Windows |
Only valid for IBM i5OSUNIX |
cd ltsdm_homegt
StopServersh
sdmsh jstartup mode=standalone
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2260 CUSTOMER 2012-08-30
sdmsh filetransferdir dir=ltnew_dirgt
sdmsh jstartup mode=integrated
StartServersh
End of IBM i5OSUNIX |
6 To prevent deployment errors during the update process proceed as follows
1 Log on to the Central Instance host
2 Start the ConfigTool and in the navigation area choose Cluster-data Global server configuration
Managers ServiceManager
3 In the Global properties panel set the Custom value of the EventTimeout property to 120
4 Choose Save
5 Restart the Central Instance
7 Check whether the used JDK version and the Java VM settings of the Java runtime system comply
with the requirements in SAP Note 723909 Update the JDK and adjust the settings if necessary
NOTE
An update of the used JDK version possibly changes the JVM path In this case you must
make the new path available to all Dialog Instances of the J2EE engine by implementing option
1 of SAP Note 718901
8 Make sure that the J2EE administrator password stored in the secure store for offline usage is
identical with the one stored in the User Management Engine (UME) You can change the password
in the secure store as described in SAP Note 870445
9 If you are running a high availability system on Windows you might need to prepare your system
as described in the online documentation for JSPM see section Preparing Systems That Run in High
Availability Environment
223 Updating the Application Server Java and Java-Based Components
Procedure
Applying a Support Package Stack to SAP NetWeaver Application Server Java and Java-Based Components
NOTE
The JSPM GUI might not work properly on some UNIX systems For more information and the
solution see SAP Note 1013976
1 Log on as user ltsapsidgtadm to the Central Instance host
NOTE
If your operating system is IBM i log on as user ltSIDgtADM or ltSIDgtOFR
2 Close the SAP Management Console (SAP MMC) and the SDM remote GUI client
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2360
3 For UNIX and Windows To start the JSPM navigate to the directory ltINSTDIRgtltSIDgt
ltCentral_Instance_Namegtj2eeJSPM and run the go script file
NOTE
If your system is running on IBM i to start the JSPM proceed as follows
1 To prevent JSPM from automatically starting its GUI in the file usrsapltSIDgt
ltCentral_Instance_Namegtj2eeJSPMparamjspm_configtxt change the
property dialogSDTServerConnectionSDTGuilaunch from true to false
2 On the IBM i host run the go script file using the following command
QSH CMD(usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPMgo)
3 In the mounted directory usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPM run
the StartGui script file The JSPM GUI appears
4 In the Host field enter the target IBM i host
NOTE
Depending on the system type ltCentral_Instance_Namegt has the following syntax
Standalone Java system JCltinstance_nogt
Add-On system DVEBMGSltinstance_nogt
4 Enter your SDM password to log on to the SDM
5 On the Deployment tab page select the Java Support Package Manager option and update the software
component sapcomJSPM to the target SPS level
6 Restart the JSPM and log on with the SDM password
RECOMMENDATION
We strongly recommend that you use the Support and Enhancement Package Stack option when
applying a Support Package Stack Other options can lead to unintended consistency issues
NOTE
If you need to include the latest patches for a particular component during the update process
with the Support and Enhancement Package Stack option stop the JSPM after restart and apply SAP
Note 1080821 Then start the JSPM again
7 On the Deployment tab page select the Support and Enhancement Package Stack option and choose Next
The Support Package Stacks that are available for deployment in the global EPS inbox directory
are displayed
8 In the Target SP Stack Level dropdown box select the Support Package Stack to be applied and choose
Next
In this step JSPM performs various status validations and displays the result of each software
component included in the stack definition XML file on the subsequent screen which includes
the following possible statuses
OK Indicates that the SPS level of the corresponding software component is applicable
WARNING We recommend that you view the details about the component by choosing Show
Details
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2460 CUSTOMER 2012-08-30
This status may indicate that the corresponding software component comprises custom
modifications in an NWDI-controlled system
If your system is used for NWDI development and it is either a DEV or a CONS system
you will be informed that JSPM will not deploy the modified software components but
only transport them to the CMS transport directory JSPM will deploy only the software
components that are not modified
If your system is not used for NWDI development or if your system is used for NWDI
development and it is either a TEST or a PROD system you will be informed that JSPM
has found newer versions of modified software components and will automatically replace
the original versions with the newer versions JSPM will deploy all software components
that are not modified together with the replaced versions of the modified software
components
CAUTION
You may get a warning telling you that there are patches installed in your system
containing fixes which might not be included in the target SP Stack This is possible if
you have applied patches of the start SP Stack level that were delivered later than the
target SP Stack delivery date In order not to lose these fixes you need to download and
apply the corresponding patches of the target SP Stack level
If you are performing an update from SAP NetWeaver 70 including enhancement
package 1 SPS00 and you have not applied any patches for the software component with
status WARNING before the update then you can ignore warnings such as the following
example
The new version of the development component sapcomcomsapnetweaver
bcrfmoni is 70100200806121227180000 and is lower than the already
deployed version 70100200807090143420000
REVISE Indicates inconsistencies with the corresponding software component
The deployment cannot be performed until all problems have been resolved You can view
the problems by choosing Show Details
9 If the status of the selected SP Stack is OK or WARNING you can start the system update by choosing
Start JSPM then changes the status to SCHEDULED
If the SP Stack to be applied includes a kernel update and the current kernel is not already of the
corresponding patch level JSPM arranges the kernel update as the very first Support Package to
be applied JSPM updates the kernel binaries of all instances (including Dialog Instances and SCS
instances in a HA environment) whose kernel directories DIR_CT_RUN effectively reside on the host
indicated by the profile parameter SAPGLOBALHOST
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2560
CAUTION
Kernel binaries of instances whose kernel directories DIR_CT_RUN are not effectively linked
to the host SAPGLOBALHOST must be updated individually as described in section Manually
Updating Instances with Kernel Directory Located on Separate Hosts below
The kernel update (includes update of SAP Kernel and SAP IGS) using JSPM consists of the following
steps
1 JSPM stops the Central Instance automatically and prompts you to stop the remote SCS and
Dialog Instances manually
2 After you have stopped all the instances choose the Next button in the dialog box
The kernel update starts
NOTE
If the system is running in a high availability environment make sure that the HA
software does not restart the instance automatically during the update
NOTE
If kernel binaries of the SCS instance need to be updated manually (see Manually Updating
Instances with Kernel Directory Located on Separate Hosts below) you must perform this at the
time when JSPM is updating the kernel binaries of the Central Instance In any case the
SCS kernel must be up-to-date before the next restart
When the kernel update is finished a dialog box appears in which you are prompted to restart
the SCS instance manually
3 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries
before you can proceed with the next step For more information see Adjusting the Ownership and
Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
4 Choose Next in the dialog box when the SCS instance is running again
After the kernel update JSPM restarts the system for further deployment of the remaining Support
Packages in the stack
RECOMMENDATION
If you need to update the kernel binaries of any Dialog Instances manually (see Manually
Updating Instances with Kernel Directory Located on Separate Hosts below) perform the update when
JSPM is updating the remaining Support Packages in the stack in order to save time
The deployment of each Support Package can end with one of the following statuses
DEPLOYED
The Support Package has been successfully deployed
DEPLOYED WITH WARNING
The Support Package has been deployed but it possibly may not work properly with other
deployed components
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2660 CUSTOMER 2012-08-30
You can view the details by choosing Show Details or examining the log files You can also view
the details about the component by choosing the Deployed Components tab page
ERROR
An error has occurred during the deployment You can view the details by choosing Show
Details or examining the log files
You must correct the error to be able to continue with the SP Stack update
You can proceed as described for a deployment that finished with status DEPLOYED WITH
WARNING
If the error correction does not change the contents in the JSPM inbox you can continue
the deployment by choosing Resume
If the error correction changes the contents in the JSPM inbox you can choose New
Deployment to redeploy the SP Stack
NOT DEPLOYED
JSPM has not attempted to deploy the software component for certain reasons
If your system is not used for NWDI development you can proceed as described for a
deployment that finished with status ERROR
If your system is used for NWDI development and it is either a DEV or a CONS system
the status of the modified software components is always NOT DEPLOYED JSPM has
transported the software components of the Support Package Stack both modified and
not modified to the CMS transport directory The deployment of the modified software
components is handled by NWDI
Manually Updating Instances with Kernel Directory Located on Separate Hosts
JSPM performs kernel update for all instances (including Dialog Instances and SCS instances in a HA
environment) whose kernel directories DIR_CT_RUN effectively reside on the host indicated by the profile
parameter SAPGLOBALHOST (by using folder sharing on Windows or file system mounting on UNIX) In
rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of those sort of instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances individually
To update the kernel of an instance manually proceed as follows
1 Log on as user ltsapsidgtadm to the host of the instance to be updated
2 Back up the kernel directory which is specified by the profile parameter DIR_CT_RUN
3 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory with
SAPCAR [page 56]
4 Stop the instance being updated
NOTE
If the system is running in a HA environment make sure that the HA software does not
restart the instance automatically during the update
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2760
5 Copy or move the extracted programs from the temporary directory to the local kernel directory
6 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries as
described in section Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
7 Restart the instance after JSPM has finished the deployment of all packages on the Central Instance
Only valid for UNIX |
Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms
On UNIX platforms you must adjust the ownership and execution permissions of the kernel binaries
after the update regardless whether you performed the update manually or by using JSPM because
both update procedures are performed with the ltsapsidgtadm user Enter the following command
sequence
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
224 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the Java system
23 Parallel Update of Dual-Stack Systems
If you perform an update of a dual-stack system (ABAP+Java) we recommend that you follow the
procedure described below The procedure has been validated to update the ABAP stack and the Java
stack of a NetWeaver system in parallel thus reducing the overall system downtime by half
Procedure
1 Before applying ABAP and Java Support Packages use the Single Support Packages option in JSPM and
select for update only the components SAP KERNEL and BC-FES-IGS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
23 Parallel Update of Dual-Stack Systems
2860 CUSTOMER 2012-08-30
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS)
runs on a dedicated host In this case JSPM does not support update of kernel binaries and
you need to update them manually Perform the update manually as described under Updating
SAP Kernel and SAP IGS in section Updating the Application Server ABAP and ABAP-Based Software
Components [page 16]
2 Import the Support Packages for the component SAP_BASIS into the ABAP stack using the ABAP
Support Package Manager (SPAM)
3 Import the remaining ABAP Support Packages with SPAM and in parallel apply the Java Support
Package Stack with JSPM
Proceed as described in Updating the Application Server ABAP and ABAP-Based Software Components [page
16] and Updating the Application Server Java and Java-Based Software Components [page 23]
24 Process Integration
241 Planning
Procedure
This section covers all the units of Process Integration that should be updated Particularly the following
units must always have the same Support Package level (the patch level can be different)
Integration Server
XI Adapter Engine
Partner Connectivity Kit
System with the Usage Type Process Integration
Software components of Integration Server
Components to Be Updated SP File Name Tool Used to Apply SP
Java stack
XI TOOLS 702 SAPXITOOLltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
ABAP stack
XI CONTENT SAP_BASIS 702 SAPBASISltSPgt_ltPLgtZIP File upload
XI CONTENT SAP_ABA 702 SAPABAltSPgt_ltPLgtZIP
SAP NetWeaver Application Server ABAP (see table Software components of Application Server ABAP [page 15])Note that update of the following software components of the ABAP system is not required SAP ABA 702 SAP BW 702 PI_BASIS 702
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 2960
J2EE Adapter Engine
If your implemented scenario includes a J2EE Adapter Engine then it must always be of the same
Support Package level as the Integration Server
Components of the J2EE Adapter Engine
Component to Be Updated SP File NameTool Used to Apply SP
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
J2SE Adapter Engine
The installation of the J2SE Adapter Engine depends on the implemented scenario
Components of the J2SE Adapter Engine
Component to Be Updated SP File Name Tool Used to Apply SP
XI CONNECTIVITY SE 702 SAPXICONSltSPgt_ltPLgtSCA ZIP tool (for example WinZip)
Partner Connectivity Kit
If your implemented scenario includes a Partner Connectivity Kit (PCK) then it must always be of the
same Support Package level as the Integration Server
Software components of Partner Connectivity Kit
Components to Be Updated SP File NameTool Used to Apply SP
XI PCK 702 SAPXIPCKltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of the Application Server Java [page 20])
System Landscape Directory (SLD)
The System Landscape Directory is required for the PI operations Although updating the SLD is not
necessarily required it is advisable to update the SLD server and the SAP Master Data Content within
it from time to time The update of the SLD includes
1 The system where the SLD is running
2 The SAP Master Data Content within this SLD
SAP GUI
See table Compatible SAP GUI Versions [page 51]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3060 CUSTOMER 2012-08-30
242 Updating Units of Process Integration
Procedure
Before you start the update perform the following steps
In the Runtime Workbench use Communication Channel Monitoring to stop all sender channels
for all adapter types on all your Adapter Engines
On the Integration Server use transaction SMQR and deregister all qRFC queues
System with the Usage Type Process Integration
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the XI instance is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system where the XI instance is running
For more information see Application Server Java and Java-Based Software Components [page 19]
System Landscape Directory (Optional)
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the SLD is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the entire Support Package Stack to the system where the SLD is running
For more information see Application Server Java and Java-Based Software Components [page 19]
J2EE Adapter Engine
Apply the Support Package Stack to the system where the Adapter Engine is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Partner Connectivity Kit
Apply the Support Package Stack to the system where the PCK is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Front End GUIs
Update the SAP GUI components if necessary
For more information see SAP GUI Family [page 51]
ABAP 700 Business System (Optional)
Apply the Support Packages for SAP NetWeaver Application Server ABAP (including SAP kernel and
the Support Package for SAP BASIS 700)
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 640 Business System (Optional)
Apply the Support Packages for SAP Web Application Server ABAP 640 (including SAP kernel and the
Support Package for SAP BASIS 640)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3160
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 620 Business System (Optional)
1 Update the SAP Kernel 620
2 Import the released Basis Support Packages for SAP Web AS 620 as well as the most recent Add-
On Support Package for APPINT 200_620 in the order described in SAP Note 439915
J2SE Adapter Engine (Optional)
NOTE
The XI Adapter Engine (J2SE) and all its adapters are provided for compatibility reasons only and
are not developed any further You have to use the XI Adapter Engine running on SAP NetWeaver
AS Java For more information see the Master Guide ndash SAP NetWeaver 70 available on SAP Service
Marketplace at httpservicesapcominstallNW70 Planning
1 Extract the SAPXICONSltSPgt_ltPLgtSCA (XI Connectivity SE 700) archive (ZIP format) to a temporary
directory
2 Save the old configuration files as described in the document Adapterpdf in directory
lttemp_directorygttech_adapterAdministrationDocumentation
3 Unpack the ZIP archive TechnicalAdapterssda to the installation directory of the XI Adapter
Engine (J2SE)
4 Restore the configuration files with restore_configuration
243 Post-Installation Steps
Procedure
Communication Channels and Queues
Restart all stopped sender channels and register all deregistered qRFC queues
XI Content
In the system with usage type PI import the XI content from the archives SAPBASISltSPgt_ltPLgtZIP
and SAPABAltSPgt_ltPLgtZIP as follows
1 Unpack the archives using a ZIP tool of your choice
2 Copy the corresponding export files (with file extension tpz) to the import directory ltINSTDIRgt
ltSAPSIDgtSYSglobalxirepository_serverimport
3 Start the Integration Builder (transaction SXMB_IFR)
4 Enter the Integration Repository by choosing Repository (Design)
5 Choose Tools Import design objects
6 Import the tpz files containing the XI content
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3260 CUSTOMER 2012-08-30
NOTE
For more information see SAP Note 836200
Role Generation on the Integration Server
On the Integration Server execute transaction SUPC (mass generation of roles) for all SAP_XI roles in
each of your clients to regenerate possibly changed roles
NOTE
Do not forget to make a user comparison for regenerated roles afterwards
Partner Connectivity Kit (Optional)
Perform the post-installation steps for PCK as described in SAP Note 746328
SAP Master Data within the SLD (Optional)
In the system where your SLD is running import the latest SLD content as described in SAP Note
669669
Receiver-Based EOIO Serialization in J2EE Adapter Engine (Optional)
The J2EE Adapter Engine can be switched to receiver-based EOIO serialization The switch can be
triggered on demand and is executed asynchronously It includes a database migration step during
which all EOIO processing in the Adapter Engine is disabled See SAP Note 973894 for details about how
to start the EOIO serialization migration
Service Metering (Optional)
Service metering gathers information about a service caller transfers it to the service provider and
counts on the service provisioning side how many times a service is called and by which service caller
Service metering is performed for the XI message protocol and the WS message protocol Service
metering is automatically enabled after applying a Support Package Stack By default only non-sensitive
data is transmitted to internal or external service providers in a compatible way
Service metering can be configured in PI in the Integration Engine on sender-side and in the Integration
Directory
Service metering can be configured in AS ABAP in transaction SOAMANAGER
Only if the service provider is allowed to receive more detailed information about the service caller set
the metering level to higher than the default
For more information see SAP Note 1239428
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3360
25 Business Intelligence
251 Planning
Procedure
Business Intelligence includes one or many of the following units that must be updated depending on
your implemented scenarios The usage types Business Intelligence (BI) and Business Intelligence Java
Components (BI-Java) must always have the same Support Package level
Business Intelligence
Software Components of Business Intelligence
Component to Be Updated SP File Name Tool Used to Apply SP
BI CONT ADDON 70x SAPK-70ltxgtltSPgtINBICONT SAINT
SAP NetWeaver Application Server ABAP (see table Software Components of Application Server ABAP [page 15])
NOTE
For information about the dependencies applying to BI Content Support Packages see SAP Note
653814 BI CONT 703 Support Packages are not part of the NetWeaver SP Stacks Updates can be
performed when applicable Alternatively BI CONT 704 Support Packages can be imported See
the BI Content release strategy in SAP Note 153967
Business Intelligence Java Components
BI Java Components
Component to Be Updated SP File NameTool Used to Apply SP
BI REPORTING AND PLANNING 702 BIREPPLANltSPgt_ltPLgtSCA JSPM
BI WEBDYNPRO ALV 702 BIWDALVltSPgt_ltPLgtSCA
BI INFORM BROADCASTING 702 BIIBCltSPgt_ltPLgtSCA
BI WEB APPLICATIONS 702 BIWEBAPPltSPgt_ltPLgtSCA
BI BASE SERVICES 702 BIBASESltSPgt_ltPLgtSCA
VISUAL COMPOSER BI KITS 702 VCKITBIltSPgt_ltPLgtSCA
Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
BI Precalculation Service
Components of the BI Precalculation Service
Component to Be Updated SP File Name Tool Used to Apply SP
BI Pre-calculation Service 700 xPreCalServerltSPgt_ltPLgtexe Installer
Search and Classification (TREX)
See table TREX Component [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3460 CUSTOMER 2012-08-30
BI Accelerator
The BI Accelerator is based on the TREX technology It is a special Linux 64-bit version of SAP NetWeaver
70 Search and Classification (TREX) which is delivered on preconfigured hardware
NOTE
You cannot use a TREX installation based on 32-bit architecture that is configured for searching
in metadata and documents for the BI Accelerator And vice versa a BI Accelerator box cannot
be used for searching in metadata and documents
If you want to use the search functionality as well as the BI Accelerator you require two separate
installations For more information see BI Accelerator [page 47]
Clients
Depending on your implemented scenarios you have to update SAP GUI Components and Business
Explorer (BI Add-OnBW Add-On)
NOTE
See SAP Note 889314 to determine when to use the BI Add-On and the BW Add-On
NOTE
As SAP GUI 640 is no longer supported BI Frontend Support Package 1800 resp patch 1801 is the
last Support Package resp patch based on SAP GUI 640 For more information see SAP Note
1231292 (Frontend Add-in Strategy 640710 GUI Version)
For more information about the new release strategy for the BI Frontend see SAP Note 1231363
(Changed Delivery Strategy for BI Frontend)
252 Preparation
Procedure
For the Support Packages of the most important Business Intelligence units so called SAPBINews
(SAPBWNews) Notes are created Read these Notes before updating Business Intelligence For SAP
NetWeaver 70 including enhancement package 2 SPS 12 these are the following
Business Intelligence ABAP SAP Note 1680996
Business Intelligence Java Components SAP Note 1726461
BI 70 Frontend Add-On for SAP GUI 710 SAP Note 1413032
BI 70 Frontend Add-On for SAP GUI 720 SAP Note 1630112
BI 70 Frontend Add-On for SAP GUI 730 SAP Note 1726739
For more information about BI Support Packages see SAP Community Network at http
scnsapcomcommunitydata-warehousingnetweaver-bw Related Resources SAP NW BW Support
Packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
2012-08-30 CUSTOMER 3560
253 Updating Units of Business Intelligence
Procedure
Business Intelligence
1 Update the SAP NetWeaver Application Server ABAP (with BI CONT 70x if necessary) with the
appropriate Support Packages
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
NOTE
When applying the component SAP BW 702 some generation errors might occur When
you start importing the BI Support Packages in transaction SPAM choose the menu path
Extras Ignore generation errors For more information see SAP Note 114134
2 Apply the Support Package Stack to the system with the usage type BI-Java
For more information see Application Server Java and Java-Based Software Components [page 19]
3 Update the BI Precalculation Service that is used in your scenario
4 Update the standalone engine Search and Classification (TREX) that is used in your scenario For more
information see Standalone Engine Search and Classification (TREX) [page 44]
NOTE
You have to update TREX to the newest version if you use search capabilities within Business
Intelligence
5 Update the BI Accelerator to the newest available version For more information see BI
Accelerator [page 47]
6 Update the SAP GUI and Business Explorer (BI Add-On BW Add-On) on all remote client hosts
that are involved in the scenario
For more information see SAP GUI Family [page 51] and Business Explorer (BI Add-On BW Add-On)
[page 51]
BI Precalculation Service
1 Log on to the host as a user with administration rights
2 Install the Support Package of the BI Precalculation Service by executing the
xPreCalServerexe file
The welcome screen of the BI Precalculation Server setup wizard appears
The setup now checks the system for the prerequisites
3 Choose the option Update for updating the BI Precalculation service to the current patch level and
then Finish
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3660 CUSTOMER 2012-08-30
26 EP Core
261 Planning
Procedure
The following installable software units must be updated
EP Core
Software Components of EP Core
Component to Be Updated SP File Name Tool Used to Apply SP
PORTAL CORE SERVICES 702 EPBCltSPgt_ltPLgtSCA JSPM
PORTAL FRAMEWORK 702 EPBC2ltSPgt_ltPLgtSCA
PORTAL 702 EPPSERVltSPgt_ltPLgtSCA
PORTAL WEB DYNPRO 702 EPWDCltSPgt_ltPLgtSCA
UWL COLL PROCESS ENGINE 702 UWLJWFltSPgt_ltPLgtSCA
CAF EU 702 SAPEUltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
262 Preparation
Procedure
Backing Up the Portal Runtime Configuration
If you have made changes to the standard Portal Runtime configuration you have to make a backup
of the configuration before the update process For more information see SAP Note 1064468
263 Updating EP Core
Procedure
Apply the Support Package Stack to a system with usage type EP Core
For more information see Application Server Java and Java-Based Software Components [page 19]
264 Post-Installation Steps for EP Core
Procedure
Restoring the Portal Runtime Configuration
To make your changes to the standard Portal Runtime Configuration effective you have to restore
the backup of the configuration done before the update process For more information see SAP Note
1064468
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
26 EP Core
2012-08-30 CUSTOMER 3760
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
221 Planning
Procedure
Java Support Package files (SCAs) contain all software objects of the corresponding software
components Thus it is sufficient to apply the Java Support Package files of the intended Support Package
Stack directly to the Java system to be updated It is not necessary to apply the Support Package Stacks
between the start SP Stack level and the target SP Stack level successively
CAUTION
When applying a Support Package Stack to a Java system the Java Support Package Manager (JSPM)
will necessarily restart the system several times to make the changes effective With a dual-stack
system (ABAP+Java) the ABAP part will only be restarted when JSPM is updating the SAP kernel
and IGS
The following components belong to the usage type SAP NetWeaver Application Server Java (AS Java)
Software Components of Application Server Java
Component to Be Updated SP File Name Tool Used to Apply SP
SAP Kernel 720 32-64-BIT UNICODE SAPEXESAR
SAPEXEDBSAR
JSPM
SAP IGS 700 igsexesar
BI META MODEL REPOSITORY 702 BIMMRltSPgt_ltPLgtSCA
J2EE ENGINE CORE TOOLS 702 CORETOOLSltSPgt_ltPLgtSCA
J2EE ENGINE BASE TABLES 702 BASETABLESltSPgt_ltPLgtSCA
BI UDI 702 BIUDIltSPgt_ltPLgtSCA
DI BUILD TOOL 702 SAPBUILDTltSPgt_ltPLgtSCA
SAP CAF 702 CAFltSPgt_ltPLgtSCA
SAP IKS 702 KMKWJIKSltSPgt_ltPLgtSCA
JAVA LOG VIEWER 702 JLOGVIEWltSPgt_ltPLgtSCA
SAP J2EE ENGINE CORE 702 SAPJEECORltSPgt_ltPLgtSCA
SAP JAVA TECH SERVICES 702 SAPJTECHSltSPgt_ltPLgtSCA
SAP TECH S OFFLINE 702 SAPJTECHFltSPgt_ltPLgtSCA
SAP J2EE ENGINE 702 SAPJEEltSPgt_ltPLgtSCA
JAVA SP MANAGER 702 JSPMltSPgt_ltPLgtSCA
ADOBE DOCUMENT SERVICES 702 ADSSAPltSPgt_ltPLgtSCA
UME ADMINISTRATION 702 UMEADMINltSPgt_ltPLgtSCA
LIFECYCLE MGMT TOOLS 702 LMTOOLSltSPgt_ltPLgtSCA
SAP CAF-UM 702 CAFUMltSPgt_ltPLgtSCA
SAP SOFTW DELIV MANAGER 702 SDMKITltSPgt_ltPLgtJAR
SOFTWARE LIFECYCLE MANAGER 702 SWLIFECYCLltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2060 CUSTOMER 2012-08-30
NOTE
This table contains only software components that belong to the usage type AS Java Software
components of other usage types and Java application units are listed in the corresponding
sections
NOTE
As of Support Package 09 you can update your system with SAP Kernel 720 instead of SAP Kernel
701
222 Preparation for Applying a Support Package Stack
Procedure
1 Download the Support Package Stack with all usage types to be updated and the stack definition
XML file as described in Downloading Support Package Stacks [page 12]
NOTE
You can find the activated usage types in an existing Java system on the Deployed Components tab
page on the JSPM user interface
NOTE
You do not need to download the SP Stacks between the source SP Stack level and target SP
Stack level By default the target SP Stack level is the latest available SP Stack
2 Make sure the following requirements are met prior to applying the Support Package Stack
You have familiarized yourself with SAP Note 891983 before you start the Java Support Package
Manager
The system to be updated is fully functional
The Support Package Stack you want to apply and the corresponding stack definition XML
file are available in the EPS inbox directory usrsaptransEPSin By default this location
can be also referred to as ldquoJSPM inboxrdquo
The SAP NetWeaver Application Server Java (AS Java) and the database have been backed up
You have not deleted renamed or created any directories and files in the following directories
and their subdirectories usrsapltSAPSIDgtSYSexe and usrsapltSAPSIDgtSYS
profile
Otherwise JSPM cannot detect the kernel and the system profiles and cannot be started If a
backup of the kernel and the system profiles has been required it has been created in a different
directory
The ltsapsidgtadm user has Read permissions for the EPS inbox directory usrsaptransEPS
in
If your database is SAP MaxDB the overwrite mode for the log area has been activated
The database and the SDM repository have been synchronized
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2160
For more information see the online documentation for JSPM on SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70 Library
(including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library Administrators Guide
Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems AS Java
(Application Server for Java) Software Logistics Software Maintenance Java Support Package Manager
Then choose Troubleshooting JSPM Does Not Update the Versions of the Deployed Components
There is enough disk space
For more information see SAP Note 891895
Your current SAPCAR tool is able to extract the Support Packages for the SAP kernel and
other OS level binaries delivered as SAR files
RECOMMENDATION
You can download the latest version of SAPCAR from SAP Service Marketplace at
httpservicesapcompatches Entry by Application Group Additional Components
SAPCAR
Put the downloaded version in the same directory in the JSPM inbox in which the kernel
SAR files reside so that JSPM can use this version for extracting the SAR files
3 Only valid for Linux |
For RHEL 4 and SLES 9 you need to install additional operating system packages For more
information see SAP Note 1021236End of Linux |
4 Only valid for Windows |
For Windows you need to install additional operating system packages For more information see
SAP Note 684106End of Windows |
5 To prevent the Software Deployment Manager (SDM) from temporarily exceeding the available
disk space during the update process you can change the file transfer directory of SDM in a system
of SPS09 or higher using the following command sequence
Only valid for Windows |
cd ltsdm_homegt
StopServerbat
sdmbat jstartup mode=standalone
sdmbat filetransferdir dir=ltnew_dirgt
sdmbat jstartup mode=integrated
StartServerbat
End of Windows |
Only valid for IBM i5OSUNIX |
cd ltsdm_homegt
StopServersh
sdmsh jstartup mode=standalone
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2260 CUSTOMER 2012-08-30
sdmsh filetransferdir dir=ltnew_dirgt
sdmsh jstartup mode=integrated
StartServersh
End of IBM i5OSUNIX |
6 To prevent deployment errors during the update process proceed as follows
1 Log on to the Central Instance host
2 Start the ConfigTool and in the navigation area choose Cluster-data Global server configuration
Managers ServiceManager
3 In the Global properties panel set the Custom value of the EventTimeout property to 120
4 Choose Save
5 Restart the Central Instance
7 Check whether the used JDK version and the Java VM settings of the Java runtime system comply
with the requirements in SAP Note 723909 Update the JDK and adjust the settings if necessary
NOTE
An update of the used JDK version possibly changes the JVM path In this case you must
make the new path available to all Dialog Instances of the J2EE engine by implementing option
1 of SAP Note 718901
8 Make sure that the J2EE administrator password stored in the secure store for offline usage is
identical with the one stored in the User Management Engine (UME) You can change the password
in the secure store as described in SAP Note 870445
9 If you are running a high availability system on Windows you might need to prepare your system
as described in the online documentation for JSPM see section Preparing Systems That Run in High
Availability Environment
223 Updating the Application Server Java and Java-Based Components
Procedure
Applying a Support Package Stack to SAP NetWeaver Application Server Java and Java-Based Components
NOTE
The JSPM GUI might not work properly on some UNIX systems For more information and the
solution see SAP Note 1013976
1 Log on as user ltsapsidgtadm to the Central Instance host
NOTE
If your operating system is IBM i log on as user ltSIDgtADM or ltSIDgtOFR
2 Close the SAP Management Console (SAP MMC) and the SDM remote GUI client
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2360
3 For UNIX and Windows To start the JSPM navigate to the directory ltINSTDIRgtltSIDgt
ltCentral_Instance_Namegtj2eeJSPM and run the go script file
NOTE
If your system is running on IBM i to start the JSPM proceed as follows
1 To prevent JSPM from automatically starting its GUI in the file usrsapltSIDgt
ltCentral_Instance_Namegtj2eeJSPMparamjspm_configtxt change the
property dialogSDTServerConnectionSDTGuilaunch from true to false
2 On the IBM i host run the go script file using the following command
QSH CMD(usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPMgo)
3 In the mounted directory usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPM run
the StartGui script file The JSPM GUI appears
4 In the Host field enter the target IBM i host
NOTE
Depending on the system type ltCentral_Instance_Namegt has the following syntax
Standalone Java system JCltinstance_nogt
Add-On system DVEBMGSltinstance_nogt
4 Enter your SDM password to log on to the SDM
5 On the Deployment tab page select the Java Support Package Manager option and update the software
component sapcomJSPM to the target SPS level
6 Restart the JSPM and log on with the SDM password
RECOMMENDATION
We strongly recommend that you use the Support and Enhancement Package Stack option when
applying a Support Package Stack Other options can lead to unintended consistency issues
NOTE
If you need to include the latest patches for a particular component during the update process
with the Support and Enhancement Package Stack option stop the JSPM after restart and apply SAP
Note 1080821 Then start the JSPM again
7 On the Deployment tab page select the Support and Enhancement Package Stack option and choose Next
The Support Package Stacks that are available for deployment in the global EPS inbox directory
are displayed
8 In the Target SP Stack Level dropdown box select the Support Package Stack to be applied and choose
Next
In this step JSPM performs various status validations and displays the result of each software
component included in the stack definition XML file on the subsequent screen which includes
the following possible statuses
OK Indicates that the SPS level of the corresponding software component is applicable
WARNING We recommend that you view the details about the component by choosing Show
Details
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2460 CUSTOMER 2012-08-30
This status may indicate that the corresponding software component comprises custom
modifications in an NWDI-controlled system
If your system is used for NWDI development and it is either a DEV or a CONS system
you will be informed that JSPM will not deploy the modified software components but
only transport them to the CMS transport directory JSPM will deploy only the software
components that are not modified
If your system is not used for NWDI development or if your system is used for NWDI
development and it is either a TEST or a PROD system you will be informed that JSPM
has found newer versions of modified software components and will automatically replace
the original versions with the newer versions JSPM will deploy all software components
that are not modified together with the replaced versions of the modified software
components
CAUTION
You may get a warning telling you that there are patches installed in your system
containing fixes which might not be included in the target SP Stack This is possible if
you have applied patches of the start SP Stack level that were delivered later than the
target SP Stack delivery date In order not to lose these fixes you need to download and
apply the corresponding patches of the target SP Stack level
If you are performing an update from SAP NetWeaver 70 including enhancement
package 1 SPS00 and you have not applied any patches for the software component with
status WARNING before the update then you can ignore warnings such as the following
example
The new version of the development component sapcomcomsapnetweaver
bcrfmoni is 70100200806121227180000 and is lower than the already
deployed version 70100200807090143420000
REVISE Indicates inconsistencies with the corresponding software component
The deployment cannot be performed until all problems have been resolved You can view
the problems by choosing Show Details
9 If the status of the selected SP Stack is OK or WARNING you can start the system update by choosing
Start JSPM then changes the status to SCHEDULED
If the SP Stack to be applied includes a kernel update and the current kernel is not already of the
corresponding patch level JSPM arranges the kernel update as the very first Support Package to
be applied JSPM updates the kernel binaries of all instances (including Dialog Instances and SCS
instances in a HA environment) whose kernel directories DIR_CT_RUN effectively reside on the host
indicated by the profile parameter SAPGLOBALHOST
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2560
CAUTION
Kernel binaries of instances whose kernel directories DIR_CT_RUN are not effectively linked
to the host SAPGLOBALHOST must be updated individually as described in section Manually
Updating Instances with Kernel Directory Located on Separate Hosts below
The kernel update (includes update of SAP Kernel and SAP IGS) using JSPM consists of the following
steps
1 JSPM stops the Central Instance automatically and prompts you to stop the remote SCS and
Dialog Instances manually
2 After you have stopped all the instances choose the Next button in the dialog box
The kernel update starts
NOTE
If the system is running in a high availability environment make sure that the HA
software does not restart the instance automatically during the update
NOTE
If kernel binaries of the SCS instance need to be updated manually (see Manually Updating
Instances with Kernel Directory Located on Separate Hosts below) you must perform this at the
time when JSPM is updating the kernel binaries of the Central Instance In any case the
SCS kernel must be up-to-date before the next restart
When the kernel update is finished a dialog box appears in which you are prompted to restart
the SCS instance manually
3 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries
before you can proceed with the next step For more information see Adjusting the Ownership and
Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
4 Choose Next in the dialog box when the SCS instance is running again
After the kernel update JSPM restarts the system for further deployment of the remaining Support
Packages in the stack
RECOMMENDATION
If you need to update the kernel binaries of any Dialog Instances manually (see Manually
Updating Instances with Kernel Directory Located on Separate Hosts below) perform the update when
JSPM is updating the remaining Support Packages in the stack in order to save time
The deployment of each Support Package can end with one of the following statuses
DEPLOYED
The Support Package has been successfully deployed
DEPLOYED WITH WARNING
The Support Package has been deployed but it possibly may not work properly with other
deployed components
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2660 CUSTOMER 2012-08-30
You can view the details by choosing Show Details or examining the log files You can also view
the details about the component by choosing the Deployed Components tab page
ERROR
An error has occurred during the deployment You can view the details by choosing Show
Details or examining the log files
You must correct the error to be able to continue with the SP Stack update
You can proceed as described for a deployment that finished with status DEPLOYED WITH
WARNING
If the error correction does not change the contents in the JSPM inbox you can continue
the deployment by choosing Resume
If the error correction changes the contents in the JSPM inbox you can choose New
Deployment to redeploy the SP Stack
NOT DEPLOYED
JSPM has not attempted to deploy the software component for certain reasons
If your system is not used for NWDI development you can proceed as described for a
deployment that finished with status ERROR
If your system is used for NWDI development and it is either a DEV or a CONS system
the status of the modified software components is always NOT DEPLOYED JSPM has
transported the software components of the Support Package Stack both modified and
not modified to the CMS transport directory The deployment of the modified software
components is handled by NWDI
Manually Updating Instances with Kernel Directory Located on Separate Hosts
JSPM performs kernel update for all instances (including Dialog Instances and SCS instances in a HA
environment) whose kernel directories DIR_CT_RUN effectively reside on the host indicated by the profile
parameter SAPGLOBALHOST (by using folder sharing on Windows or file system mounting on UNIX) In
rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of those sort of instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances individually
To update the kernel of an instance manually proceed as follows
1 Log on as user ltsapsidgtadm to the host of the instance to be updated
2 Back up the kernel directory which is specified by the profile parameter DIR_CT_RUN
3 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory with
SAPCAR [page 56]
4 Stop the instance being updated
NOTE
If the system is running in a HA environment make sure that the HA software does not
restart the instance automatically during the update
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2760
5 Copy or move the extracted programs from the temporary directory to the local kernel directory
6 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries as
described in section Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
7 Restart the instance after JSPM has finished the deployment of all packages on the Central Instance
Only valid for UNIX |
Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms
On UNIX platforms you must adjust the ownership and execution permissions of the kernel binaries
after the update regardless whether you performed the update manually or by using JSPM because
both update procedures are performed with the ltsapsidgtadm user Enter the following command
sequence
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
224 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the Java system
23 Parallel Update of Dual-Stack Systems
If you perform an update of a dual-stack system (ABAP+Java) we recommend that you follow the
procedure described below The procedure has been validated to update the ABAP stack and the Java
stack of a NetWeaver system in parallel thus reducing the overall system downtime by half
Procedure
1 Before applying ABAP and Java Support Packages use the Single Support Packages option in JSPM and
select for update only the components SAP KERNEL and BC-FES-IGS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
23 Parallel Update of Dual-Stack Systems
2860 CUSTOMER 2012-08-30
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS)
runs on a dedicated host In this case JSPM does not support update of kernel binaries and
you need to update them manually Perform the update manually as described under Updating
SAP Kernel and SAP IGS in section Updating the Application Server ABAP and ABAP-Based Software
Components [page 16]
2 Import the Support Packages for the component SAP_BASIS into the ABAP stack using the ABAP
Support Package Manager (SPAM)
3 Import the remaining ABAP Support Packages with SPAM and in parallel apply the Java Support
Package Stack with JSPM
Proceed as described in Updating the Application Server ABAP and ABAP-Based Software Components [page
16] and Updating the Application Server Java and Java-Based Software Components [page 23]
24 Process Integration
241 Planning
Procedure
This section covers all the units of Process Integration that should be updated Particularly the following
units must always have the same Support Package level (the patch level can be different)
Integration Server
XI Adapter Engine
Partner Connectivity Kit
System with the Usage Type Process Integration
Software components of Integration Server
Components to Be Updated SP File Name Tool Used to Apply SP
Java stack
XI TOOLS 702 SAPXITOOLltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
ABAP stack
XI CONTENT SAP_BASIS 702 SAPBASISltSPgt_ltPLgtZIP File upload
XI CONTENT SAP_ABA 702 SAPABAltSPgt_ltPLgtZIP
SAP NetWeaver Application Server ABAP (see table Software components of Application Server ABAP [page 15])Note that update of the following software components of the ABAP system is not required SAP ABA 702 SAP BW 702 PI_BASIS 702
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 2960
J2EE Adapter Engine
If your implemented scenario includes a J2EE Adapter Engine then it must always be of the same
Support Package level as the Integration Server
Components of the J2EE Adapter Engine
Component to Be Updated SP File NameTool Used to Apply SP
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
J2SE Adapter Engine
The installation of the J2SE Adapter Engine depends on the implemented scenario
Components of the J2SE Adapter Engine
Component to Be Updated SP File Name Tool Used to Apply SP
XI CONNECTIVITY SE 702 SAPXICONSltSPgt_ltPLgtSCA ZIP tool (for example WinZip)
Partner Connectivity Kit
If your implemented scenario includes a Partner Connectivity Kit (PCK) then it must always be of the
same Support Package level as the Integration Server
Software components of Partner Connectivity Kit
Components to Be Updated SP File NameTool Used to Apply SP
XI PCK 702 SAPXIPCKltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of the Application Server Java [page 20])
System Landscape Directory (SLD)
The System Landscape Directory is required for the PI operations Although updating the SLD is not
necessarily required it is advisable to update the SLD server and the SAP Master Data Content within
it from time to time The update of the SLD includes
1 The system where the SLD is running
2 The SAP Master Data Content within this SLD
SAP GUI
See table Compatible SAP GUI Versions [page 51]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3060 CUSTOMER 2012-08-30
242 Updating Units of Process Integration
Procedure
Before you start the update perform the following steps
In the Runtime Workbench use Communication Channel Monitoring to stop all sender channels
for all adapter types on all your Adapter Engines
On the Integration Server use transaction SMQR and deregister all qRFC queues
System with the Usage Type Process Integration
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the XI instance is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system where the XI instance is running
For more information see Application Server Java and Java-Based Software Components [page 19]
System Landscape Directory (Optional)
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the SLD is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the entire Support Package Stack to the system where the SLD is running
For more information see Application Server Java and Java-Based Software Components [page 19]
J2EE Adapter Engine
Apply the Support Package Stack to the system where the Adapter Engine is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Partner Connectivity Kit
Apply the Support Package Stack to the system where the PCK is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Front End GUIs
Update the SAP GUI components if necessary
For more information see SAP GUI Family [page 51]
ABAP 700 Business System (Optional)
Apply the Support Packages for SAP NetWeaver Application Server ABAP (including SAP kernel and
the Support Package for SAP BASIS 700)
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 640 Business System (Optional)
Apply the Support Packages for SAP Web Application Server ABAP 640 (including SAP kernel and the
Support Package for SAP BASIS 640)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3160
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 620 Business System (Optional)
1 Update the SAP Kernel 620
2 Import the released Basis Support Packages for SAP Web AS 620 as well as the most recent Add-
On Support Package for APPINT 200_620 in the order described in SAP Note 439915
J2SE Adapter Engine (Optional)
NOTE
The XI Adapter Engine (J2SE) and all its adapters are provided for compatibility reasons only and
are not developed any further You have to use the XI Adapter Engine running on SAP NetWeaver
AS Java For more information see the Master Guide ndash SAP NetWeaver 70 available on SAP Service
Marketplace at httpservicesapcominstallNW70 Planning
1 Extract the SAPXICONSltSPgt_ltPLgtSCA (XI Connectivity SE 700) archive (ZIP format) to a temporary
directory
2 Save the old configuration files as described in the document Adapterpdf in directory
lttemp_directorygttech_adapterAdministrationDocumentation
3 Unpack the ZIP archive TechnicalAdapterssda to the installation directory of the XI Adapter
Engine (J2SE)
4 Restore the configuration files with restore_configuration
243 Post-Installation Steps
Procedure
Communication Channels and Queues
Restart all stopped sender channels and register all deregistered qRFC queues
XI Content
In the system with usage type PI import the XI content from the archives SAPBASISltSPgt_ltPLgtZIP
and SAPABAltSPgt_ltPLgtZIP as follows
1 Unpack the archives using a ZIP tool of your choice
2 Copy the corresponding export files (with file extension tpz) to the import directory ltINSTDIRgt
ltSAPSIDgtSYSglobalxirepository_serverimport
3 Start the Integration Builder (transaction SXMB_IFR)
4 Enter the Integration Repository by choosing Repository (Design)
5 Choose Tools Import design objects
6 Import the tpz files containing the XI content
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3260 CUSTOMER 2012-08-30
NOTE
For more information see SAP Note 836200
Role Generation on the Integration Server
On the Integration Server execute transaction SUPC (mass generation of roles) for all SAP_XI roles in
each of your clients to regenerate possibly changed roles
NOTE
Do not forget to make a user comparison for regenerated roles afterwards
Partner Connectivity Kit (Optional)
Perform the post-installation steps for PCK as described in SAP Note 746328
SAP Master Data within the SLD (Optional)
In the system where your SLD is running import the latest SLD content as described in SAP Note
669669
Receiver-Based EOIO Serialization in J2EE Adapter Engine (Optional)
The J2EE Adapter Engine can be switched to receiver-based EOIO serialization The switch can be
triggered on demand and is executed asynchronously It includes a database migration step during
which all EOIO processing in the Adapter Engine is disabled See SAP Note 973894 for details about how
to start the EOIO serialization migration
Service Metering (Optional)
Service metering gathers information about a service caller transfers it to the service provider and
counts on the service provisioning side how many times a service is called and by which service caller
Service metering is performed for the XI message protocol and the WS message protocol Service
metering is automatically enabled after applying a Support Package Stack By default only non-sensitive
data is transmitted to internal or external service providers in a compatible way
Service metering can be configured in PI in the Integration Engine on sender-side and in the Integration
Directory
Service metering can be configured in AS ABAP in transaction SOAMANAGER
Only if the service provider is allowed to receive more detailed information about the service caller set
the metering level to higher than the default
For more information see SAP Note 1239428
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3360
25 Business Intelligence
251 Planning
Procedure
Business Intelligence includes one or many of the following units that must be updated depending on
your implemented scenarios The usage types Business Intelligence (BI) and Business Intelligence Java
Components (BI-Java) must always have the same Support Package level
Business Intelligence
Software Components of Business Intelligence
Component to Be Updated SP File Name Tool Used to Apply SP
BI CONT ADDON 70x SAPK-70ltxgtltSPgtINBICONT SAINT
SAP NetWeaver Application Server ABAP (see table Software Components of Application Server ABAP [page 15])
NOTE
For information about the dependencies applying to BI Content Support Packages see SAP Note
653814 BI CONT 703 Support Packages are not part of the NetWeaver SP Stacks Updates can be
performed when applicable Alternatively BI CONT 704 Support Packages can be imported See
the BI Content release strategy in SAP Note 153967
Business Intelligence Java Components
BI Java Components
Component to Be Updated SP File NameTool Used to Apply SP
BI REPORTING AND PLANNING 702 BIREPPLANltSPgt_ltPLgtSCA JSPM
BI WEBDYNPRO ALV 702 BIWDALVltSPgt_ltPLgtSCA
BI INFORM BROADCASTING 702 BIIBCltSPgt_ltPLgtSCA
BI WEB APPLICATIONS 702 BIWEBAPPltSPgt_ltPLgtSCA
BI BASE SERVICES 702 BIBASESltSPgt_ltPLgtSCA
VISUAL COMPOSER BI KITS 702 VCKITBIltSPgt_ltPLgtSCA
Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
BI Precalculation Service
Components of the BI Precalculation Service
Component to Be Updated SP File Name Tool Used to Apply SP
BI Pre-calculation Service 700 xPreCalServerltSPgt_ltPLgtexe Installer
Search and Classification (TREX)
See table TREX Component [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3460 CUSTOMER 2012-08-30
BI Accelerator
The BI Accelerator is based on the TREX technology It is a special Linux 64-bit version of SAP NetWeaver
70 Search and Classification (TREX) which is delivered on preconfigured hardware
NOTE
You cannot use a TREX installation based on 32-bit architecture that is configured for searching
in metadata and documents for the BI Accelerator And vice versa a BI Accelerator box cannot
be used for searching in metadata and documents
If you want to use the search functionality as well as the BI Accelerator you require two separate
installations For more information see BI Accelerator [page 47]
Clients
Depending on your implemented scenarios you have to update SAP GUI Components and Business
Explorer (BI Add-OnBW Add-On)
NOTE
See SAP Note 889314 to determine when to use the BI Add-On and the BW Add-On
NOTE
As SAP GUI 640 is no longer supported BI Frontend Support Package 1800 resp patch 1801 is the
last Support Package resp patch based on SAP GUI 640 For more information see SAP Note
1231292 (Frontend Add-in Strategy 640710 GUI Version)
For more information about the new release strategy for the BI Frontend see SAP Note 1231363
(Changed Delivery Strategy for BI Frontend)
252 Preparation
Procedure
For the Support Packages of the most important Business Intelligence units so called SAPBINews
(SAPBWNews) Notes are created Read these Notes before updating Business Intelligence For SAP
NetWeaver 70 including enhancement package 2 SPS 12 these are the following
Business Intelligence ABAP SAP Note 1680996
Business Intelligence Java Components SAP Note 1726461
BI 70 Frontend Add-On for SAP GUI 710 SAP Note 1413032
BI 70 Frontend Add-On for SAP GUI 720 SAP Note 1630112
BI 70 Frontend Add-On for SAP GUI 730 SAP Note 1726739
For more information about BI Support Packages see SAP Community Network at http
scnsapcomcommunitydata-warehousingnetweaver-bw Related Resources SAP NW BW Support
Packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
2012-08-30 CUSTOMER 3560
253 Updating Units of Business Intelligence
Procedure
Business Intelligence
1 Update the SAP NetWeaver Application Server ABAP (with BI CONT 70x if necessary) with the
appropriate Support Packages
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
NOTE
When applying the component SAP BW 702 some generation errors might occur When
you start importing the BI Support Packages in transaction SPAM choose the menu path
Extras Ignore generation errors For more information see SAP Note 114134
2 Apply the Support Package Stack to the system with the usage type BI-Java
For more information see Application Server Java and Java-Based Software Components [page 19]
3 Update the BI Precalculation Service that is used in your scenario
4 Update the standalone engine Search and Classification (TREX) that is used in your scenario For more
information see Standalone Engine Search and Classification (TREX) [page 44]
NOTE
You have to update TREX to the newest version if you use search capabilities within Business
Intelligence
5 Update the BI Accelerator to the newest available version For more information see BI
Accelerator [page 47]
6 Update the SAP GUI and Business Explorer (BI Add-On BW Add-On) on all remote client hosts
that are involved in the scenario
For more information see SAP GUI Family [page 51] and Business Explorer (BI Add-On BW Add-On)
[page 51]
BI Precalculation Service
1 Log on to the host as a user with administration rights
2 Install the Support Package of the BI Precalculation Service by executing the
xPreCalServerexe file
The welcome screen of the BI Precalculation Server setup wizard appears
The setup now checks the system for the prerequisites
3 Choose the option Update for updating the BI Precalculation service to the current patch level and
then Finish
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3660 CUSTOMER 2012-08-30
26 EP Core
261 Planning
Procedure
The following installable software units must be updated
EP Core
Software Components of EP Core
Component to Be Updated SP File Name Tool Used to Apply SP
PORTAL CORE SERVICES 702 EPBCltSPgt_ltPLgtSCA JSPM
PORTAL FRAMEWORK 702 EPBC2ltSPgt_ltPLgtSCA
PORTAL 702 EPPSERVltSPgt_ltPLgtSCA
PORTAL WEB DYNPRO 702 EPWDCltSPgt_ltPLgtSCA
UWL COLL PROCESS ENGINE 702 UWLJWFltSPgt_ltPLgtSCA
CAF EU 702 SAPEUltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
262 Preparation
Procedure
Backing Up the Portal Runtime Configuration
If you have made changes to the standard Portal Runtime configuration you have to make a backup
of the configuration before the update process For more information see SAP Note 1064468
263 Updating EP Core
Procedure
Apply the Support Package Stack to a system with usage type EP Core
For more information see Application Server Java and Java-Based Software Components [page 19]
264 Post-Installation Steps for EP Core
Procedure
Restoring the Portal Runtime Configuration
To make your changes to the standard Portal Runtime Configuration effective you have to restore
the backup of the configuration done before the update process For more information see SAP Note
1064468
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
26 EP Core
2012-08-30 CUSTOMER 3760
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
NOTE
This table contains only software components that belong to the usage type AS Java Software
components of other usage types and Java application units are listed in the corresponding
sections
NOTE
As of Support Package 09 you can update your system with SAP Kernel 720 instead of SAP Kernel
701
222 Preparation for Applying a Support Package Stack
Procedure
1 Download the Support Package Stack with all usage types to be updated and the stack definition
XML file as described in Downloading Support Package Stacks [page 12]
NOTE
You can find the activated usage types in an existing Java system on the Deployed Components tab
page on the JSPM user interface
NOTE
You do not need to download the SP Stacks between the source SP Stack level and target SP
Stack level By default the target SP Stack level is the latest available SP Stack
2 Make sure the following requirements are met prior to applying the Support Package Stack
You have familiarized yourself with SAP Note 891983 before you start the Java Support Package
Manager
The system to be updated is fully functional
The Support Package Stack you want to apply and the corresponding stack definition XML
file are available in the EPS inbox directory usrsaptransEPSin By default this location
can be also referred to as ldquoJSPM inboxrdquo
The SAP NetWeaver Application Server Java (AS Java) and the database have been backed up
You have not deleted renamed or created any directories and files in the following directories
and their subdirectories usrsapltSAPSIDgtSYSexe and usrsapltSAPSIDgtSYS
profile
Otherwise JSPM cannot detect the kernel and the system profiles and cannot be started If a
backup of the kernel and the system profiles has been required it has been created in a different
directory
The ltsapsidgtadm user has Read permissions for the EPS inbox directory usrsaptransEPS
in
If your database is SAP MaxDB the overwrite mode for the log area has been activated
The database and the SDM repository have been synchronized
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2160
For more information see the online documentation for JSPM on SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70 Library
(including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library Administrators Guide
Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems AS Java
(Application Server for Java) Software Logistics Software Maintenance Java Support Package Manager
Then choose Troubleshooting JSPM Does Not Update the Versions of the Deployed Components
There is enough disk space
For more information see SAP Note 891895
Your current SAPCAR tool is able to extract the Support Packages for the SAP kernel and
other OS level binaries delivered as SAR files
RECOMMENDATION
You can download the latest version of SAPCAR from SAP Service Marketplace at
httpservicesapcompatches Entry by Application Group Additional Components
SAPCAR
Put the downloaded version in the same directory in the JSPM inbox in which the kernel
SAR files reside so that JSPM can use this version for extracting the SAR files
3 Only valid for Linux |
For RHEL 4 and SLES 9 you need to install additional operating system packages For more
information see SAP Note 1021236End of Linux |
4 Only valid for Windows |
For Windows you need to install additional operating system packages For more information see
SAP Note 684106End of Windows |
5 To prevent the Software Deployment Manager (SDM) from temporarily exceeding the available
disk space during the update process you can change the file transfer directory of SDM in a system
of SPS09 or higher using the following command sequence
Only valid for Windows |
cd ltsdm_homegt
StopServerbat
sdmbat jstartup mode=standalone
sdmbat filetransferdir dir=ltnew_dirgt
sdmbat jstartup mode=integrated
StartServerbat
End of Windows |
Only valid for IBM i5OSUNIX |
cd ltsdm_homegt
StopServersh
sdmsh jstartup mode=standalone
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2260 CUSTOMER 2012-08-30
sdmsh filetransferdir dir=ltnew_dirgt
sdmsh jstartup mode=integrated
StartServersh
End of IBM i5OSUNIX |
6 To prevent deployment errors during the update process proceed as follows
1 Log on to the Central Instance host
2 Start the ConfigTool and in the navigation area choose Cluster-data Global server configuration
Managers ServiceManager
3 In the Global properties panel set the Custom value of the EventTimeout property to 120
4 Choose Save
5 Restart the Central Instance
7 Check whether the used JDK version and the Java VM settings of the Java runtime system comply
with the requirements in SAP Note 723909 Update the JDK and adjust the settings if necessary
NOTE
An update of the used JDK version possibly changes the JVM path In this case you must
make the new path available to all Dialog Instances of the J2EE engine by implementing option
1 of SAP Note 718901
8 Make sure that the J2EE administrator password stored in the secure store for offline usage is
identical with the one stored in the User Management Engine (UME) You can change the password
in the secure store as described in SAP Note 870445
9 If you are running a high availability system on Windows you might need to prepare your system
as described in the online documentation for JSPM see section Preparing Systems That Run in High
Availability Environment
223 Updating the Application Server Java and Java-Based Components
Procedure
Applying a Support Package Stack to SAP NetWeaver Application Server Java and Java-Based Components
NOTE
The JSPM GUI might not work properly on some UNIX systems For more information and the
solution see SAP Note 1013976
1 Log on as user ltsapsidgtadm to the Central Instance host
NOTE
If your operating system is IBM i log on as user ltSIDgtADM or ltSIDgtOFR
2 Close the SAP Management Console (SAP MMC) and the SDM remote GUI client
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2360
3 For UNIX and Windows To start the JSPM navigate to the directory ltINSTDIRgtltSIDgt
ltCentral_Instance_Namegtj2eeJSPM and run the go script file
NOTE
If your system is running on IBM i to start the JSPM proceed as follows
1 To prevent JSPM from automatically starting its GUI in the file usrsapltSIDgt
ltCentral_Instance_Namegtj2eeJSPMparamjspm_configtxt change the
property dialogSDTServerConnectionSDTGuilaunch from true to false
2 On the IBM i host run the go script file using the following command
QSH CMD(usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPMgo)
3 In the mounted directory usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPM run
the StartGui script file The JSPM GUI appears
4 In the Host field enter the target IBM i host
NOTE
Depending on the system type ltCentral_Instance_Namegt has the following syntax
Standalone Java system JCltinstance_nogt
Add-On system DVEBMGSltinstance_nogt
4 Enter your SDM password to log on to the SDM
5 On the Deployment tab page select the Java Support Package Manager option and update the software
component sapcomJSPM to the target SPS level
6 Restart the JSPM and log on with the SDM password
RECOMMENDATION
We strongly recommend that you use the Support and Enhancement Package Stack option when
applying a Support Package Stack Other options can lead to unintended consistency issues
NOTE
If you need to include the latest patches for a particular component during the update process
with the Support and Enhancement Package Stack option stop the JSPM after restart and apply SAP
Note 1080821 Then start the JSPM again
7 On the Deployment tab page select the Support and Enhancement Package Stack option and choose Next
The Support Package Stacks that are available for deployment in the global EPS inbox directory
are displayed
8 In the Target SP Stack Level dropdown box select the Support Package Stack to be applied and choose
Next
In this step JSPM performs various status validations and displays the result of each software
component included in the stack definition XML file on the subsequent screen which includes
the following possible statuses
OK Indicates that the SPS level of the corresponding software component is applicable
WARNING We recommend that you view the details about the component by choosing Show
Details
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2460 CUSTOMER 2012-08-30
This status may indicate that the corresponding software component comprises custom
modifications in an NWDI-controlled system
If your system is used for NWDI development and it is either a DEV or a CONS system
you will be informed that JSPM will not deploy the modified software components but
only transport them to the CMS transport directory JSPM will deploy only the software
components that are not modified
If your system is not used for NWDI development or if your system is used for NWDI
development and it is either a TEST or a PROD system you will be informed that JSPM
has found newer versions of modified software components and will automatically replace
the original versions with the newer versions JSPM will deploy all software components
that are not modified together with the replaced versions of the modified software
components
CAUTION
You may get a warning telling you that there are patches installed in your system
containing fixes which might not be included in the target SP Stack This is possible if
you have applied patches of the start SP Stack level that were delivered later than the
target SP Stack delivery date In order not to lose these fixes you need to download and
apply the corresponding patches of the target SP Stack level
If you are performing an update from SAP NetWeaver 70 including enhancement
package 1 SPS00 and you have not applied any patches for the software component with
status WARNING before the update then you can ignore warnings such as the following
example
The new version of the development component sapcomcomsapnetweaver
bcrfmoni is 70100200806121227180000 and is lower than the already
deployed version 70100200807090143420000
REVISE Indicates inconsistencies with the corresponding software component
The deployment cannot be performed until all problems have been resolved You can view
the problems by choosing Show Details
9 If the status of the selected SP Stack is OK or WARNING you can start the system update by choosing
Start JSPM then changes the status to SCHEDULED
If the SP Stack to be applied includes a kernel update and the current kernel is not already of the
corresponding patch level JSPM arranges the kernel update as the very first Support Package to
be applied JSPM updates the kernel binaries of all instances (including Dialog Instances and SCS
instances in a HA environment) whose kernel directories DIR_CT_RUN effectively reside on the host
indicated by the profile parameter SAPGLOBALHOST
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2560
CAUTION
Kernel binaries of instances whose kernel directories DIR_CT_RUN are not effectively linked
to the host SAPGLOBALHOST must be updated individually as described in section Manually
Updating Instances with Kernel Directory Located on Separate Hosts below
The kernel update (includes update of SAP Kernel and SAP IGS) using JSPM consists of the following
steps
1 JSPM stops the Central Instance automatically and prompts you to stop the remote SCS and
Dialog Instances manually
2 After you have stopped all the instances choose the Next button in the dialog box
The kernel update starts
NOTE
If the system is running in a high availability environment make sure that the HA
software does not restart the instance automatically during the update
NOTE
If kernel binaries of the SCS instance need to be updated manually (see Manually Updating
Instances with Kernel Directory Located on Separate Hosts below) you must perform this at the
time when JSPM is updating the kernel binaries of the Central Instance In any case the
SCS kernel must be up-to-date before the next restart
When the kernel update is finished a dialog box appears in which you are prompted to restart
the SCS instance manually
3 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries
before you can proceed with the next step For more information see Adjusting the Ownership and
Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
4 Choose Next in the dialog box when the SCS instance is running again
After the kernel update JSPM restarts the system for further deployment of the remaining Support
Packages in the stack
RECOMMENDATION
If you need to update the kernel binaries of any Dialog Instances manually (see Manually
Updating Instances with Kernel Directory Located on Separate Hosts below) perform the update when
JSPM is updating the remaining Support Packages in the stack in order to save time
The deployment of each Support Package can end with one of the following statuses
DEPLOYED
The Support Package has been successfully deployed
DEPLOYED WITH WARNING
The Support Package has been deployed but it possibly may not work properly with other
deployed components
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2660 CUSTOMER 2012-08-30
You can view the details by choosing Show Details or examining the log files You can also view
the details about the component by choosing the Deployed Components tab page
ERROR
An error has occurred during the deployment You can view the details by choosing Show
Details or examining the log files
You must correct the error to be able to continue with the SP Stack update
You can proceed as described for a deployment that finished with status DEPLOYED WITH
WARNING
If the error correction does not change the contents in the JSPM inbox you can continue
the deployment by choosing Resume
If the error correction changes the contents in the JSPM inbox you can choose New
Deployment to redeploy the SP Stack
NOT DEPLOYED
JSPM has not attempted to deploy the software component for certain reasons
If your system is not used for NWDI development you can proceed as described for a
deployment that finished with status ERROR
If your system is used for NWDI development and it is either a DEV or a CONS system
the status of the modified software components is always NOT DEPLOYED JSPM has
transported the software components of the Support Package Stack both modified and
not modified to the CMS transport directory The deployment of the modified software
components is handled by NWDI
Manually Updating Instances with Kernel Directory Located on Separate Hosts
JSPM performs kernel update for all instances (including Dialog Instances and SCS instances in a HA
environment) whose kernel directories DIR_CT_RUN effectively reside on the host indicated by the profile
parameter SAPGLOBALHOST (by using folder sharing on Windows or file system mounting on UNIX) In
rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of those sort of instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances individually
To update the kernel of an instance manually proceed as follows
1 Log on as user ltsapsidgtadm to the host of the instance to be updated
2 Back up the kernel directory which is specified by the profile parameter DIR_CT_RUN
3 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory with
SAPCAR [page 56]
4 Stop the instance being updated
NOTE
If the system is running in a HA environment make sure that the HA software does not
restart the instance automatically during the update
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2760
5 Copy or move the extracted programs from the temporary directory to the local kernel directory
6 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries as
described in section Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
7 Restart the instance after JSPM has finished the deployment of all packages on the Central Instance
Only valid for UNIX |
Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms
On UNIX platforms you must adjust the ownership and execution permissions of the kernel binaries
after the update regardless whether you performed the update manually or by using JSPM because
both update procedures are performed with the ltsapsidgtadm user Enter the following command
sequence
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
224 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the Java system
23 Parallel Update of Dual-Stack Systems
If you perform an update of a dual-stack system (ABAP+Java) we recommend that you follow the
procedure described below The procedure has been validated to update the ABAP stack and the Java
stack of a NetWeaver system in parallel thus reducing the overall system downtime by half
Procedure
1 Before applying ABAP and Java Support Packages use the Single Support Packages option in JSPM and
select for update only the components SAP KERNEL and BC-FES-IGS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
23 Parallel Update of Dual-Stack Systems
2860 CUSTOMER 2012-08-30
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS)
runs on a dedicated host In this case JSPM does not support update of kernel binaries and
you need to update them manually Perform the update manually as described under Updating
SAP Kernel and SAP IGS in section Updating the Application Server ABAP and ABAP-Based Software
Components [page 16]
2 Import the Support Packages for the component SAP_BASIS into the ABAP stack using the ABAP
Support Package Manager (SPAM)
3 Import the remaining ABAP Support Packages with SPAM and in parallel apply the Java Support
Package Stack with JSPM
Proceed as described in Updating the Application Server ABAP and ABAP-Based Software Components [page
16] and Updating the Application Server Java and Java-Based Software Components [page 23]
24 Process Integration
241 Planning
Procedure
This section covers all the units of Process Integration that should be updated Particularly the following
units must always have the same Support Package level (the patch level can be different)
Integration Server
XI Adapter Engine
Partner Connectivity Kit
System with the Usage Type Process Integration
Software components of Integration Server
Components to Be Updated SP File Name Tool Used to Apply SP
Java stack
XI TOOLS 702 SAPXITOOLltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
ABAP stack
XI CONTENT SAP_BASIS 702 SAPBASISltSPgt_ltPLgtZIP File upload
XI CONTENT SAP_ABA 702 SAPABAltSPgt_ltPLgtZIP
SAP NetWeaver Application Server ABAP (see table Software components of Application Server ABAP [page 15])Note that update of the following software components of the ABAP system is not required SAP ABA 702 SAP BW 702 PI_BASIS 702
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 2960
J2EE Adapter Engine
If your implemented scenario includes a J2EE Adapter Engine then it must always be of the same
Support Package level as the Integration Server
Components of the J2EE Adapter Engine
Component to Be Updated SP File NameTool Used to Apply SP
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
J2SE Adapter Engine
The installation of the J2SE Adapter Engine depends on the implemented scenario
Components of the J2SE Adapter Engine
Component to Be Updated SP File Name Tool Used to Apply SP
XI CONNECTIVITY SE 702 SAPXICONSltSPgt_ltPLgtSCA ZIP tool (for example WinZip)
Partner Connectivity Kit
If your implemented scenario includes a Partner Connectivity Kit (PCK) then it must always be of the
same Support Package level as the Integration Server
Software components of Partner Connectivity Kit
Components to Be Updated SP File NameTool Used to Apply SP
XI PCK 702 SAPXIPCKltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of the Application Server Java [page 20])
System Landscape Directory (SLD)
The System Landscape Directory is required for the PI operations Although updating the SLD is not
necessarily required it is advisable to update the SLD server and the SAP Master Data Content within
it from time to time The update of the SLD includes
1 The system where the SLD is running
2 The SAP Master Data Content within this SLD
SAP GUI
See table Compatible SAP GUI Versions [page 51]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3060 CUSTOMER 2012-08-30
242 Updating Units of Process Integration
Procedure
Before you start the update perform the following steps
In the Runtime Workbench use Communication Channel Monitoring to stop all sender channels
for all adapter types on all your Adapter Engines
On the Integration Server use transaction SMQR and deregister all qRFC queues
System with the Usage Type Process Integration
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the XI instance is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system where the XI instance is running
For more information see Application Server Java and Java-Based Software Components [page 19]
System Landscape Directory (Optional)
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the SLD is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the entire Support Package Stack to the system where the SLD is running
For more information see Application Server Java and Java-Based Software Components [page 19]
J2EE Adapter Engine
Apply the Support Package Stack to the system where the Adapter Engine is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Partner Connectivity Kit
Apply the Support Package Stack to the system where the PCK is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Front End GUIs
Update the SAP GUI components if necessary
For more information see SAP GUI Family [page 51]
ABAP 700 Business System (Optional)
Apply the Support Packages for SAP NetWeaver Application Server ABAP (including SAP kernel and
the Support Package for SAP BASIS 700)
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 640 Business System (Optional)
Apply the Support Packages for SAP Web Application Server ABAP 640 (including SAP kernel and the
Support Package for SAP BASIS 640)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3160
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 620 Business System (Optional)
1 Update the SAP Kernel 620
2 Import the released Basis Support Packages for SAP Web AS 620 as well as the most recent Add-
On Support Package for APPINT 200_620 in the order described in SAP Note 439915
J2SE Adapter Engine (Optional)
NOTE
The XI Adapter Engine (J2SE) and all its adapters are provided for compatibility reasons only and
are not developed any further You have to use the XI Adapter Engine running on SAP NetWeaver
AS Java For more information see the Master Guide ndash SAP NetWeaver 70 available on SAP Service
Marketplace at httpservicesapcominstallNW70 Planning
1 Extract the SAPXICONSltSPgt_ltPLgtSCA (XI Connectivity SE 700) archive (ZIP format) to a temporary
directory
2 Save the old configuration files as described in the document Adapterpdf in directory
lttemp_directorygttech_adapterAdministrationDocumentation
3 Unpack the ZIP archive TechnicalAdapterssda to the installation directory of the XI Adapter
Engine (J2SE)
4 Restore the configuration files with restore_configuration
243 Post-Installation Steps
Procedure
Communication Channels and Queues
Restart all stopped sender channels and register all deregistered qRFC queues
XI Content
In the system with usage type PI import the XI content from the archives SAPBASISltSPgt_ltPLgtZIP
and SAPABAltSPgt_ltPLgtZIP as follows
1 Unpack the archives using a ZIP tool of your choice
2 Copy the corresponding export files (with file extension tpz) to the import directory ltINSTDIRgt
ltSAPSIDgtSYSglobalxirepository_serverimport
3 Start the Integration Builder (transaction SXMB_IFR)
4 Enter the Integration Repository by choosing Repository (Design)
5 Choose Tools Import design objects
6 Import the tpz files containing the XI content
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3260 CUSTOMER 2012-08-30
NOTE
For more information see SAP Note 836200
Role Generation on the Integration Server
On the Integration Server execute transaction SUPC (mass generation of roles) for all SAP_XI roles in
each of your clients to regenerate possibly changed roles
NOTE
Do not forget to make a user comparison for regenerated roles afterwards
Partner Connectivity Kit (Optional)
Perform the post-installation steps for PCK as described in SAP Note 746328
SAP Master Data within the SLD (Optional)
In the system where your SLD is running import the latest SLD content as described in SAP Note
669669
Receiver-Based EOIO Serialization in J2EE Adapter Engine (Optional)
The J2EE Adapter Engine can be switched to receiver-based EOIO serialization The switch can be
triggered on demand and is executed asynchronously It includes a database migration step during
which all EOIO processing in the Adapter Engine is disabled See SAP Note 973894 for details about how
to start the EOIO serialization migration
Service Metering (Optional)
Service metering gathers information about a service caller transfers it to the service provider and
counts on the service provisioning side how many times a service is called and by which service caller
Service metering is performed for the XI message protocol and the WS message protocol Service
metering is automatically enabled after applying a Support Package Stack By default only non-sensitive
data is transmitted to internal or external service providers in a compatible way
Service metering can be configured in PI in the Integration Engine on sender-side and in the Integration
Directory
Service metering can be configured in AS ABAP in transaction SOAMANAGER
Only if the service provider is allowed to receive more detailed information about the service caller set
the metering level to higher than the default
For more information see SAP Note 1239428
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3360
25 Business Intelligence
251 Planning
Procedure
Business Intelligence includes one or many of the following units that must be updated depending on
your implemented scenarios The usage types Business Intelligence (BI) and Business Intelligence Java
Components (BI-Java) must always have the same Support Package level
Business Intelligence
Software Components of Business Intelligence
Component to Be Updated SP File Name Tool Used to Apply SP
BI CONT ADDON 70x SAPK-70ltxgtltSPgtINBICONT SAINT
SAP NetWeaver Application Server ABAP (see table Software Components of Application Server ABAP [page 15])
NOTE
For information about the dependencies applying to BI Content Support Packages see SAP Note
653814 BI CONT 703 Support Packages are not part of the NetWeaver SP Stacks Updates can be
performed when applicable Alternatively BI CONT 704 Support Packages can be imported See
the BI Content release strategy in SAP Note 153967
Business Intelligence Java Components
BI Java Components
Component to Be Updated SP File NameTool Used to Apply SP
BI REPORTING AND PLANNING 702 BIREPPLANltSPgt_ltPLgtSCA JSPM
BI WEBDYNPRO ALV 702 BIWDALVltSPgt_ltPLgtSCA
BI INFORM BROADCASTING 702 BIIBCltSPgt_ltPLgtSCA
BI WEB APPLICATIONS 702 BIWEBAPPltSPgt_ltPLgtSCA
BI BASE SERVICES 702 BIBASESltSPgt_ltPLgtSCA
VISUAL COMPOSER BI KITS 702 VCKITBIltSPgt_ltPLgtSCA
Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
BI Precalculation Service
Components of the BI Precalculation Service
Component to Be Updated SP File Name Tool Used to Apply SP
BI Pre-calculation Service 700 xPreCalServerltSPgt_ltPLgtexe Installer
Search and Classification (TREX)
See table TREX Component [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3460 CUSTOMER 2012-08-30
BI Accelerator
The BI Accelerator is based on the TREX technology It is a special Linux 64-bit version of SAP NetWeaver
70 Search and Classification (TREX) which is delivered on preconfigured hardware
NOTE
You cannot use a TREX installation based on 32-bit architecture that is configured for searching
in metadata and documents for the BI Accelerator And vice versa a BI Accelerator box cannot
be used for searching in metadata and documents
If you want to use the search functionality as well as the BI Accelerator you require two separate
installations For more information see BI Accelerator [page 47]
Clients
Depending on your implemented scenarios you have to update SAP GUI Components and Business
Explorer (BI Add-OnBW Add-On)
NOTE
See SAP Note 889314 to determine when to use the BI Add-On and the BW Add-On
NOTE
As SAP GUI 640 is no longer supported BI Frontend Support Package 1800 resp patch 1801 is the
last Support Package resp patch based on SAP GUI 640 For more information see SAP Note
1231292 (Frontend Add-in Strategy 640710 GUI Version)
For more information about the new release strategy for the BI Frontend see SAP Note 1231363
(Changed Delivery Strategy for BI Frontend)
252 Preparation
Procedure
For the Support Packages of the most important Business Intelligence units so called SAPBINews
(SAPBWNews) Notes are created Read these Notes before updating Business Intelligence For SAP
NetWeaver 70 including enhancement package 2 SPS 12 these are the following
Business Intelligence ABAP SAP Note 1680996
Business Intelligence Java Components SAP Note 1726461
BI 70 Frontend Add-On for SAP GUI 710 SAP Note 1413032
BI 70 Frontend Add-On for SAP GUI 720 SAP Note 1630112
BI 70 Frontend Add-On for SAP GUI 730 SAP Note 1726739
For more information about BI Support Packages see SAP Community Network at http
scnsapcomcommunitydata-warehousingnetweaver-bw Related Resources SAP NW BW Support
Packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
2012-08-30 CUSTOMER 3560
253 Updating Units of Business Intelligence
Procedure
Business Intelligence
1 Update the SAP NetWeaver Application Server ABAP (with BI CONT 70x if necessary) with the
appropriate Support Packages
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
NOTE
When applying the component SAP BW 702 some generation errors might occur When
you start importing the BI Support Packages in transaction SPAM choose the menu path
Extras Ignore generation errors For more information see SAP Note 114134
2 Apply the Support Package Stack to the system with the usage type BI-Java
For more information see Application Server Java and Java-Based Software Components [page 19]
3 Update the BI Precalculation Service that is used in your scenario
4 Update the standalone engine Search and Classification (TREX) that is used in your scenario For more
information see Standalone Engine Search and Classification (TREX) [page 44]
NOTE
You have to update TREX to the newest version if you use search capabilities within Business
Intelligence
5 Update the BI Accelerator to the newest available version For more information see BI
Accelerator [page 47]
6 Update the SAP GUI and Business Explorer (BI Add-On BW Add-On) on all remote client hosts
that are involved in the scenario
For more information see SAP GUI Family [page 51] and Business Explorer (BI Add-On BW Add-On)
[page 51]
BI Precalculation Service
1 Log on to the host as a user with administration rights
2 Install the Support Package of the BI Precalculation Service by executing the
xPreCalServerexe file
The welcome screen of the BI Precalculation Server setup wizard appears
The setup now checks the system for the prerequisites
3 Choose the option Update for updating the BI Precalculation service to the current patch level and
then Finish
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3660 CUSTOMER 2012-08-30
26 EP Core
261 Planning
Procedure
The following installable software units must be updated
EP Core
Software Components of EP Core
Component to Be Updated SP File Name Tool Used to Apply SP
PORTAL CORE SERVICES 702 EPBCltSPgt_ltPLgtSCA JSPM
PORTAL FRAMEWORK 702 EPBC2ltSPgt_ltPLgtSCA
PORTAL 702 EPPSERVltSPgt_ltPLgtSCA
PORTAL WEB DYNPRO 702 EPWDCltSPgt_ltPLgtSCA
UWL COLL PROCESS ENGINE 702 UWLJWFltSPgt_ltPLgtSCA
CAF EU 702 SAPEUltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
262 Preparation
Procedure
Backing Up the Portal Runtime Configuration
If you have made changes to the standard Portal Runtime configuration you have to make a backup
of the configuration before the update process For more information see SAP Note 1064468
263 Updating EP Core
Procedure
Apply the Support Package Stack to a system with usage type EP Core
For more information see Application Server Java and Java-Based Software Components [page 19]
264 Post-Installation Steps for EP Core
Procedure
Restoring the Portal Runtime Configuration
To make your changes to the standard Portal Runtime Configuration effective you have to restore
the backup of the configuration done before the update process For more information see SAP Note
1064468
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
26 EP Core
2012-08-30 CUSTOMER 3760
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
For more information see the online documentation for JSPM on SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70 Library
(including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library Administrators Guide
Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems AS Java
(Application Server for Java) Software Logistics Software Maintenance Java Support Package Manager
Then choose Troubleshooting JSPM Does Not Update the Versions of the Deployed Components
There is enough disk space
For more information see SAP Note 891895
Your current SAPCAR tool is able to extract the Support Packages for the SAP kernel and
other OS level binaries delivered as SAR files
RECOMMENDATION
You can download the latest version of SAPCAR from SAP Service Marketplace at
httpservicesapcompatches Entry by Application Group Additional Components
SAPCAR
Put the downloaded version in the same directory in the JSPM inbox in which the kernel
SAR files reside so that JSPM can use this version for extracting the SAR files
3 Only valid for Linux |
For RHEL 4 and SLES 9 you need to install additional operating system packages For more
information see SAP Note 1021236End of Linux |
4 Only valid for Windows |
For Windows you need to install additional operating system packages For more information see
SAP Note 684106End of Windows |
5 To prevent the Software Deployment Manager (SDM) from temporarily exceeding the available
disk space during the update process you can change the file transfer directory of SDM in a system
of SPS09 or higher using the following command sequence
Only valid for Windows |
cd ltsdm_homegt
StopServerbat
sdmbat jstartup mode=standalone
sdmbat filetransferdir dir=ltnew_dirgt
sdmbat jstartup mode=integrated
StartServerbat
End of Windows |
Only valid for IBM i5OSUNIX |
cd ltsdm_homegt
StopServersh
sdmsh jstartup mode=standalone
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2260 CUSTOMER 2012-08-30
sdmsh filetransferdir dir=ltnew_dirgt
sdmsh jstartup mode=integrated
StartServersh
End of IBM i5OSUNIX |
6 To prevent deployment errors during the update process proceed as follows
1 Log on to the Central Instance host
2 Start the ConfigTool and in the navigation area choose Cluster-data Global server configuration
Managers ServiceManager
3 In the Global properties panel set the Custom value of the EventTimeout property to 120
4 Choose Save
5 Restart the Central Instance
7 Check whether the used JDK version and the Java VM settings of the Java runtime system comply
with the requirements in SAP Note 723909 Update the JDK and adjust the settings if necessary
NOTE
An update of the used JDK version possibly changes the JVM path In this case you must
make the new path available to all Dialog Instances of the J2EE engine by implementing option
1 of SAP Note 718901
8 Make sure that the J2EE administrator password stored in the secure store for offline usage is
identical with the one stored in the User Management Engine (UME) You can change the password
in the secure store as described in SAP Note 870445
9 If you are running a high availability system on Windows you might need to prepare your system
as described in the online documentation for JSPM see section Preparing Systems That Run in High
Availability Environment
223 Updating the Application Server Java and Java-Based Components
Procedure
Applying a Support Package Stack to SAP NetWeaver Application Server Java and Java-Based Components
NOTE
The JSPM GUI might not work properly on some UNIX systems For more information and the
solution see SAP Note 1013976
1 Log on as user ltsapsidgtadm to the Central Instance host
NOTE
If your operating system is IBM i log on as user ltSIDgtADM or ltSIDgtOFR
2 Close the SAP Management Console (SAP MMC) and the SDM remote GUI client
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2360
3 For UNIX and Windows To start the JSPM navigate to the directory ltINSTDIRgtltSIDgt
ltCentral_Instance_Namegtj2eeJSPM and run the go script file
NOTE
If your system is running on IBM i to start the JSPM proceed as follows
1 To prevent JSPM from automatically starting its GUI in the file usrsapltSIDgt
ltCentral_Instance_Namegtj2eeJSPMparamjspm_configtxt change the
property dialogSDTServerConnectionSDTGuilaunch from true to false
2 On the IBM i host run the go script file using the following command
QSH CMD(usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPMgo)
3 In the mounted directory usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPM run
the StartGui script file The JSPM GUI appears
4 In the Host field enter the target IBM i host
NOTE
Depending on the system type ltCentral_Instance_Namegt has the following syntax
Standalone Java system JCltinstance_nogt
Add-On system DVEBMGSltinstance_nogt
4 Enter your SDM password to log on to the SDM
5 On the Deployment tab page select the Java Support Package Manager option and update the software
component sapcomJSPM to the target SPS level
6 Restart the JSPM and log on with the SDM password
RECOMMENDATION
We strongly recommend that you use the Support and Enhancement Package Stack option when
applying a Support Package Stack Other options can lead to unintended consistency issues
NOTE
If you need to include the latest patches for a particular component during the update process
with the Support and Enhancement Package Stack option stop the JSPM after restart and apply SAP
Note 1080821 Then start the JSPM again
7 On the Deployment tab page select the Support and Enhancement Package Stack option and choose Next
The Support Package Stacks that are available for deployment in the global EPS inbox directory
are displayed
8 In the Target SP Stack Level dropdown box select the Support Package Stack to be applied and choose
Next
In this step JSPM performs various status validations and displays the result of each software
component included in the stack definition XML file on the subsequent screen which includes
the following possible statuses
OK Indicates that the SPS level of the corresponding software component is applicable
WARNING We recommend that you view the details about the component by choosing Show
Details
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2460 CUSTOMER 2012-08-30
This status may indicate that the corresponding software component comprises custom
modifications in an NWDI-controlled system
If your system is used for NWDI development and it is either a DEV or a CONS system
you will be informed that JSPM will not deploy the modified software components but
only transport them to the CMS transport directory JSPM will deploy only the software
components that are not modified
If your system is not used for NWDI development or if your system is used for NWDI
development and it is either a TEST or a PROD system you will be informed that JSPM
has found newer versions of modified software components and will automatically replace
the original versions with the newer versions JSPM will deploy all software components
that are not modified together with the replaced versions of the modified software
components
CAUTION
You may get a warning telling you that there are patches installed in your system
containing fixes which might not be included in the target SP Stack This is possible if
you have applied patches of the start SP Stack level that were delivered later than the
target SP Stack delivery date In order not to lose these fixes you need to download and
apply the corresponding patches of the target SP Stack level
If you are performing an update from SAP NetWeaver 70 including enhancement
package 1 SPS00 and you have not applied any patches for the software component with
status WARNING before the update then you can ignore warnings such as the following
example
The new version of the development component sapcomcomsapnetweaver
bcrfmoni is 70100200806121227180000 and is lower than the already
deployed version 70100200807090143420000
REVISE Indicates inconsistencies with the corresponding software component
The deployment cannot be performed until all problems have been resolved You can view
the problems by choosing Show Details
9 If the status of the selected SP Stack is OK or WARNING you can start the system update by choosing
Start JSPM then changes the status to SCHEDULED
If the SP Stack to be applied includes a kernel update and the current kernel is not already of the
corresponding patch level JSPM arranges the kernel update as the very first Support Package to
be applied JSPM updates the kernel binaries of all instances (including Dialog Instances and SCS
instances in a HA environment) whose kernel directories DIR_CT_RUN effectively reside on the host
indicated by the profile parameter SAPGLOBALHOST
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2560
CAUTION
Kernel binaries of instances whose kernel directories DIR_CT_RUN are not effectively linked
to the host SAPGLOBALHOST must be updated individually as described in section Manually
Updating Instances with Kernel Directory Located on Separate Hosts below
The kernel update (includes update of SAP Kernel and SAP IGS) using JSPM consists of the following
steps
1 JSPM stops the Central Instance automatically and prompts you to stop the remote SCS and
Dialog Instances manually
2 After you have stopped all the instances choose the Next button in the dialog box
The kernel update starts
NOTE
If the system is running in a high availability environment make sure that the HA
software does not restart the instance automatically during the update
NOTE
If kernel binaries of the SCS instance need to be updated manually (see Manually Updating
Instances with Kernel Directory Located on Separate Hosts below) you must perform this at the
time when JSPM is updating the kernel binaries of the Central Instance In any case the
SCS kernel must be up-to-date before the next restart
When the kernel update is finished a dialog box appears in which you are prompted to restart
the SCS instance manually
3 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries
before you can proceed with the next step For more information see Adjusting the Ownership and
Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
4 Choose Next in the dialog box when the SCS instance is running again
After the kernel update JSPM restarts the system for further deployment of the remaining Support
Packages in the stack
RECOMMENDATION
If you need to update the kernel binaries of any Dialog Instances manually (see Manually
Updating Instances with Kernel Directory Located on Separate Hosts below) perform the update when
JSPM is updating the remaining Support Packages in the stack in order to save time
The deployment of each Support Package can end with one of the following statuses
DEPLOYED
The Support Package has been successfully deployed
DEPLOYED WITH WARNING
The Support Package has been deployed but it possibly may not work properly with other
deployed components
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2660 CUSTOMER 2012-08-30
You can view the details by choosing Show Details or examining the log files You can also view
the details about the component by choosing the Deployed Components tab page
ERROR
An error has occurred during the deployment You can view the details by choosing Show
Details or examining the log files
You must correct the error to be able to continue with the SP Stack update
You can proceed as described for a deployment that finished with status DEPLOYED WITH
WARNING
If the error correction does not change the contents in the JSPM inbox you can continue
the deployment by choosing Resume
If the error correction changes the contents in the JSPM inbox you can choose New
Deployment to redeploy the SP Stack
NOT DEPLOYED
JSPM has not attempted to deploy the software component for certain reasons
If your system is not used for NWDI development you can proceed as described for a
deployment that finished with status ERROR
If your system is used for NWDI development and it is either a DEV or a CONS system
the status of the modified software components is always NOT DEPLOYED JSPM has
transported the software components of the Support Package Stack both modified and
not modified to the CMS transport directory The deployment of the modified software
components is handled by NWDI
Manually Updating Instances with Kernel Directory Located on Separate Hosts
JSPM performs kernel update for all instances (including Dialog Instances and SCS instances in a HA
environment) whose kernel directories DIR_CT_RUN effectively reside on the host indicated by the profile
parameter SAPGLOBALHOST (by using folder sharing on Windows or file system mounting on UNIX) In
rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of those sort of instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances individually
To update the kernel of an instance manually proceed as follows
1 Log on as user ltsapsidgtadm to the host of the instance to be updated
2 Back up the kernel directory which is specified by the profile parameter DIR_CT_RUN
3 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory with
SAPCAR [page 56]
4 Stop the instance being updated
NOTE
If the system is running in a HA environment make sure that the HA software does not
restart the instance automatically during the update
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2760
5 Copy or move the extracted programs from the temporary directory to the local kernel directory
6 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries as
described in section Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
7 Restart the instance after JSPM has finished the deployment of all packages on the Central Instance
Only valid for UNIX |
Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms
On UNIX platforms you must adjust the ownership and execution permissions of the kernel binaries
after the update regardless whether you performed the update manually or by using JSPM because
both update procedures are performed with the ltsapsidgtadm user Enter the following command
sequence
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
224 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the Java system
23 Parallel Update of Dual-Stack Systems
If you perform an update of a dual-stack system (ABAP+Java) we recommend that you follow the
procedure described below The procedure has been validated to update the ABAP stack and the Java
stack of a NetWeaver system in parallel thus reducing the overall system downtime by half
Procedure
1 Before applying ABAP and Java Support Packages use the Single Support Packages option in JSPM and
select for update only the components SAP KERNEL and BC-FES-IGS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
23 Parallel Update of Dual-Stack Systems
2860 CUSTOMER 2012-08-30
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS)
runs on a dedicated host In this case JSPM does not support update of kernel binaries and
you need to update them manually Perform the update manually as described under Updating
SAP Kernel and SAP IGS in section Updating the Application Server ABAP and ABAP-Based Software
Components [page 16]
2 Import the Support Packages for the component SAP_BASIS into the ABAP stack using the ABAP
Support Package Manager (SPAM)
3 Import the remaining ABAP Support Packages with SPAM and in parallel apply the Java Support
Package Stack with JSPM
Proceed as described in Updating the Application Server ABAP and ABAP-Based Software Components [page
16] and Updating the Application Server Java and Java-Based Software Components [page 23]
24 Process Integration
241 Planning
Procedure
This section covers all the units of Process Integration that should be updated Particularly the following
units must always have the same Support Package level (the patch level can be different)
Integration Server
XI Adapter Engine
Partner Connectivity Kit
System with the Usage Type Process Integration
Software components of Integration Server
Components to Be Updated SP File Name Tool Used to Apply SP
Java stack
XI TOOLS 702 SAPXITOOLltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
ABAP stack
XI CONTENT SAP_BASIS 702 SAPBASISltSPgt_ltPLgtZIP File upload
XI CONTENT SAP_ABA 702 SAPABAltSPgt_ltPLgtZIP
SAP NetWeaver Application Server ABAP (see table Software components of Application Server ABAP [page 15])Note that update of the following software components of the ABAP system is not required SAP ABA 702 SAP BW 702 PI_BASIS 702
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 2960
J2EE Adapter Engine
If your implemented scenario includes a J2EE Adapter Engine then it must always be of the same
Support Package level as the Integration Server
Components of the J2EE Adapter Engine
Component to Be Updated SP File NameTool Used to Apply SP
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
J2SE Adapter Engine
The installation of the J2SE Adapter Engine depends on the implemented scenario
Components of the J2SE Adapter Engine
Component to Be Updated SP File Name Tool Used to Apply SP
XI CONNECTIVITY SE 702 SAPXICONSltSPgt_ltPLgtSCA ZIP tool (for example WinZip)
Partner Connectivity Kit
If your implemented scenario includes a Partner Connectivity Kit (PCK) then it must always be of the
same Support Package level as the Integration Server
Software components of Partner Connectivity Kit
Components to Be Updated SP File NameTool Used to Apply SP
XI PCK 702 SAPXIPCKltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of the Application Server Java [page 20])
System Landscape Directory (SLD)
The System Landscape Directory is required for the PI operations Although updating the SLD is not
necessarily required it is advisable to update the SLD server and the SAP Master Data Content within
it from time to time The update of the SLD includes
1 The system where the SLD is running
2 The SAP Master Data Content within this SLD
SAP GUI
See table Compatible SAP GUI Versions [page 51]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3060 CUSTOMER 2012-08-30
242 Updating Units of Process Integration
Procedure
Before you start the update perform the following steps
In the Runtime Workbench use Communication Channel Monitoring to stop all sender channels
for all adapter types on all your Adapter Engines
On the Integration Server use transaction SMQR and deregister all qRFC queues
System with the Usage Type Process Integration
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the XI instance is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system where the XI instance is running
For more information see Application Server Java and Java-Based Software Components [page 19]
System Landscape Directory (Optional)
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the SLD is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the entire Support Package Stack to the system where the SLD is running
For more information see Application Server Java and Java-Based Software Components [page 19]
J2EE Adapter Engine
Apply the Support Package Stack to the system where the Adapter Engine is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Partner Connectivity Kit
Apply the Support Package Stack to the system where the PCK is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Front End GUIs
Update the SAP GUI components if necessary
For more information see SAP GUI Family [page 51]
ABAP 700 Business System (Optional)
Apply the Support Packages for SAP NetWeaver Application Server ABAP (including SAP kernel and
the Support Package for SAP BASIS 700)
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 640 Business System (Optional)
Apply the Support Packages for SAP Web Application Server ABAP 640 (including SAP kernel and the
Support Package for SAP BASIS 640)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3160
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 620 Business System (Optional)
1 Update the SAP Kernel 620
2 Import the released Basis Support Packages for SAP Web AS 620 as well as the most recent Add-
On Support Package for APPINT 200_620 in the order described in SAP Note 439915
J2SE Adapter Engine (Optional)
NOTE
The XI Adapter Engine (J2SE) and all its adapters are provided for compatibility reasons only and
are not developed any further You have to use the XI Adapter Engine running on SAP NetWeaver
AS Java For more information see the Master Guide ndash SAP NetWeaver 70 available on SAP Service
Marketplace at httpservicesapcominstallNW70 Planning
1 Extract the SAPXICONSltSPgt_ltPLgtSCA (XI Connectivity SE 700) archive (ZIP format) to a temporary
directory
2 Save the old configuration files as described in the document Adapterpdf in directory
lttemp_directorygttech_adapterAdministrationDocumentation
3 Unpack the ZIP archive TechnicalAdapterssda to the installation directory of the XI Adapter
Engine (J2SE)
4 Restore the configuration files with restore_configuration
243 Post-Installation Steps
Procedure
Communication Channels and Queues
Restart all stopped sender channels and register all deregistered qRFC queues
XI Content
In the system with usage type PI import the XI content from the archives SAPBASISltSPgt_ltPLgtZIP
and SAPABAltSPgt_ltPLgtZIP as follows
1 Unpack the archives using a ZIP tool of your choice
2 Copy the corresponding export files (with file extension tpz) to the import directory ltINSTDIRgt
ltSAPSIDgtSYSglobalxirepository_serverimport
3 Start the Integration Builder (transaction SXMB_IFR)
4 Enter the Integration Repository by choosing Repository (Design)
5 Choose Tools Import design objects
6 Import the tpz files containing the XI content
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3260 CUSTOMER 2012-08-30
NOTE
For more information see SAP Note 836200
Role Generation on the Integration Server
On the Integration Server execute transaction SUPC (mass generation of roles) for all SAP_XI roles in
each of your clients to regenerate possibly changed roles
NOTE
Do not forget to make a user comparison for regenerated roles afterwards
Partner Connectivity Kit (Optional)
Perform the post-installation steps for PCK as described in SAP Note 746328
SAP Master Data within the SLD (Optional)
In the system where your SLD is running import the latest SLD content as described in SAP Note
669669
Receiver-Based EOIO Serialization in J2EE Adapter Engine (Optional)
The J2EE Adapter Engine can be switched to receiver-based EOIO serialization The switch can be
triggered on demand and is executed asynchronously It includes a database migration step during
which all EOIO processing in the Adapter Engine is disabled See SAP Note 973894 for details about how
to start the EOIO serialization migration
Service Metering (Optional)
Service metering gathers information about a service caller transfers it to the service provider and
counts on the service provisioning side how many times a service is called and by which service caller
Service metering is performed for the XI message protocol and the WS message protocol Service
metering is automatically enabled after applying a Support Package Stack By default only non-sensitive
data is transmitted to internal or external service providers in a compatible way
Service metering can be configured in PI in the Integration Engine on sender-side and in the Integration
Directory
Service metering can be configured in AS ABAP in transaction SOAMANAGER
Only if the service provider is allowed to receive more detailed information about the service caller set
the metering level to higher than the default
For more information see SAP Note 1239428
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3360
25 Business Intelligence
251 Planning
Procedure
Business Intelligence includes one or many of the following units that must be updated depending on
your implemented scenarios The usage types Business Intelligence (BI) and Business Intelligence Java
Components (BI-Java) must always have the same Support Package level
Business Intelligence
Software Components of Business Intelligence
Component to Be Updated SP File Name Tool Used to Apply SP
BI CONT ADDON 70x SAPK-70ltxgtltSPgtINBICONT SAINT
SAP NetWeaver Application Server ABAP (see table Software Components of Application Server ABAP [page 15])
NOTE
For information about the dependencies applying to BI Content Support Packages see SAP Note
653814 BI CONT 703 Support Packages are not part of the NetWeaver SP Stacks Updates can be
performed when applicable Alternatively BI CONT 704 Support Packages can be imported See
the BI Content release strategy in SAP Note 153967
Business Intelligence Java Components
BI Java Components
Component to Be Updated SP File NameTool Used to Apply SP
BI REPORTING AND PLANNING 702 BIREPPLANltSPgt_ltPLgtSCA JSPM
BI WEBDYNPRO ALV 702 BIWDALVltSPgt_ltPLgtSCA
BI INFORM BROADCASTING 702 BIIBCltSPgt_ltPLgtSCA
BI WEB APPLICATIONS 702 BIWEBAPPltSPgt_ltPLgtSCA
BI BASE SERVICES 702 BIBASESltSPgt_ltPLgtSCA
VISUAL COMPOSER BI KITS 702 VCKITBIltSPgt_ltPLgtSCA
Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
BI Precalculation Service
Components of the BI Precalculation Service
Component to Be Updated SP File Name Tool Used to Apply SP
BI Pre-calculation Service 700 xPreCalServerltSPgt_ltPLgtexe Installer
Search and Classification (TREX)
See table TREX Component [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3460 CUSTOMER 2012-08-30
BI Accelerator
The BI Accelerator is based on the TREX technology It is a special Linux 64-bit version of SAP NetWeaver
70 Search and Classification (TREX) which is delivered on preconfigured hardware
NOTE
You cannot use a TREX installation based on 32-bit architecture that is configured for searching
in metadata and documents for the BI Accelerator And vice versa a BI Accelerator box cannot
be used for searching in metadata and documents
If you want to use the search functionality as well as the BI Accelerator you require two separate
installations For more information see BI Accelerator [page 47]
Clients
Depending on your implemented scenarios you have to update SAP GUI Components and Business
Explorer (BI Add-OnBW Add-On)
NOTE
See SAP Note 889314 to determine when to use the BI Add-On and the BW Add-On
NOTE
As SAP GUI 640 is no longer supported BI Frontend Support Package 1800 resp patch 1801 is the
last Support Package resp patch based on SAP GUI 640 For more information see SAP Note
1231292 (Frontend Add-in Strategy 640710 GUI Version)
For more information about the new release strategy for the BI Frontend see SAP Note 1231363
(Changed Delivery Strategy for BI Frontend)
252 Preparation
Procedure
For the Support Packages of the most important Business Intelligence units so called SAPBINews
(SAPBWNews) Notes are created Read these Notes before updating Business Intelligence For SAP
NetWeaver 70 including enhancement package 2 SPS 12 these are the following
Business Intelligence ABAP SAP Note 1680996
Business Intelligence Java Components SAP Note 1726461
BI 70 Frontend Add-On for SAP GUI 710 SAP Note 1413032
BI 70 Frontend Add-On for SAP GUI 720 SAP Note 1630112
BI 70 Frontend Add-On for SAP GUI 730 SAP Note 1726739
For more information about BI Support Packages see SAP Community Network at http
scnsapcomcommunitydata-warehousingnetweaver-bw Related Resources SAP NW BW Support
Packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
2012-08-30 CUSTOMER 3560
253 Updating Units of Business Intelligence
Procedure
Business Intelligence
1 Update the SAP NetWeaver Application Server ABAP (with BI CONT 70x if necessary) with the
appropriate Support Packages
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
NOTE
When applying the component SAP BW 702 some generation errors might occur When
you start importing the BI Support Packages in transaction SPAM choose the menu path
Extras Ignore generation errors For more information see SAP Note 114134
2 Apply the Support Package Stack to the system with the usage type BI-Java
For more information see Application Server Java and Java-Based Software Components [page 19]
3 Update the BI Precalculation Service that is used in your scenario
4 Update the standalone engine Search and Classification (TREX) that is used in your scenario For more
information see Standalone Engine Search and Classification (TREX) [page 44]
NOTE
You have to update TREX to the newest version if you use search capabilities within Business
Intelligence
5 Update the BI Accelerator to the newest available version For more information see BI
Accelerator [page 47]
6 Update the SAP GUI and Business Explorer (BI Add-On BW Add-On) on all remote client hosts
that are involved in the scenario
For more information see SAP GUI Family [page 51] and Business Explorer (BI Add-On BW Add-On)
[page 51]
BI Precalculation Service
1 Log on to the host as a user with administration rights
2 Install the Support Package of the BI Precalculation Service by executing the
xPreCalServerexe file
The welcome screen of the BI Precalculation Server setup wizard appears
The setup now checks the system for the prerequisites
3 Choose the option Update for updating the BI Precalculation service to the current patch level and
then Finish
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3660 CUSTOMER 2012-08-30
26 EP Core
261 Planning
Procedure
The following installable software units must be updated
EP Core
Software Components of EP Core
Component to Be Updated SP File Name Tool Used to Apply SP
PORTAL CORE SERVICES 702 EPBCltSPgt_ltPLgtSCA JSPM
PORTAL FRAMEWORK 702 EPBC2ltSPgt_ltPLgtSCA
PORTAL 702 EPPSERVltSPgt_ltPLgtSCA
PORTAL WEB DYNPRO 702 EPWDCltSPgt_ltPLgtSCA
UWL COLL PROCESS ENGINE 702 UWLJWFltSPgt_ltPLgtSCA
CAF EU 702 SAPEUltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
262 Preparation
Procedure
Backing Up the Portal Runtime Configuration
If you have made changes to the standard Portal Runtime configuration you have to make a backup
of the configuration before the update process For more information see SAP Note 1064468
263 Updating EP Core
Procedure
Apply the Support Package Stack to a system with usage type EP Core
For more information see Application Server Java and Java-Based Software Components [page 19]
264 Post-Installation Steps for EP Core
Procedure
Restoring the Portal Runtime Configuration
To make your changes to the standard Portal Runtime Configuration effective you have to restore
the backup of the configuration done before the update process For more information see SAP Note
1064468
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
26 EP Core
2012-08-30 CUSTOMER 3760
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
sdmsh filetransferdir dir=ltnew_dirgt
sdmsh jstartup mode=integrated
StartServersh
End of IBM i5OSUNIX |
6 To prevent deployment errors during the update process proceed as follows
1 Log on to the Central Instance host
2 Start the ConfigTool and in the navigation area choose Cluster-data Global server configuration
Managers ServiceManager
3 In the Global properties panel set the Custom value of the EventTimeout property to 120
4 Choose Save
5 Restart the Central Instance
7 Check whether the used JDK version and the Java VM settings of the Java runtime system comply
with the requirements in SAP Note 723909 Update the JDK and adjust the settings if necessary
NOTE
An update of the used JDK version possibly changes the JVM path In this case you must
make the new path available to all Dialog Instances of the J2EE engine by implementing option
1 of SAP Note 718901
8 Make sure that the J2EE administrator password stored in the secure store for offline usage is
identical with the one stored in the User Management Engine (UME) You can change the password
in the secure store as described in SAP Note 870445
9 If you are running a high availability system on Windows you might need to prepare your system
as described in the online documentation for JSPM see section Preparing Systems That Run in High
Availability Environment
223 Updating the Application Server Java and Java-Based Components
Procedure
Applying a Support Package Stack to SAP NetWeaver Application Server Java and Java-Based Components
NOTE
The JSPM GUI might not work properly on some UNIX systems For more information and the
solution see SAP Note 1013976
1 Log on as user ltsapsidgtadm to the Central Instance host
NOTE
If your operating system is IBM i log on as user ltSIDgtADM or ltSIDgtOFR
2 Close the SAP Management Console (SAP MMC) and the SDM remote GUI client
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2360
3 For UNIX and Windows To start the JSPM navigate to the directory ltINSTDIRgtltSIDgt
ltCentral_Instance_Namegtj2eeJSPM and run the go script file
NOTE
If your system is running on IBM i to start the JSPM proceed as follows
1 To prevent JSPM from automatically starting its GUI in the file usrsapltSIDgt
ltCentral_Instance_Namegtj2eeJSPMparamjspm_configtxt change the
property dialogSDTServerConnectionSDTGuilaunch from true to false
2 On the IBM i host run the go script file using the following command
QSH CMD(usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPMgo)
3 In the mounted directory usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPM run
the StartGui script file The JSPM GUI appears
4 In the Host field enter the target IBM i host
NOTE
Depending on the system type ltCentral_Instance_Namegt has the following syntax
Standalone Java system JCltinstance_nogt
Add-On system DVEBMGSltinstance_nogt
4 Enter your SDM password to log on to the SDM
5 On the Deployment tab page select the Java Support Package Manager option and update the software
component sapcomJSPM to the target SPS level
6 Restart the JSPM and log on with the SDM password
RECOMMENDATION
We strongly recommend that you use the Support and Enhancement Package Stack option when
applying a Support Package Stack Other options can lead to unintended consistency issues
NOTE
If you need to include the latest patches for a particular component during the update process
with the Support and Enhancement Package Stack option stop the JSPM after restart and apply SAP
Note 1080821 Then start the JSPM again
7 On the Deployment tab page select the Support and Enhancement Package Stack option and choose Next
The Support Package Stacks that are available for deployment in the global EPS inbox directory
are displayed
8 In the Target SP Stack Level dropdown box select the Support Package Stack to be applied and choose
Next
In this step JSPM performs various status validations and displays the result of each software
component included in the stack definition XML file on the subsequent screen which includes
the following possible statuses
OK Indicates that the SPS level of the corresponding software component is applicable
WARNING We recommend that you view the details about the component by choosing Show
Details
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2460 CUSTOMER 2012-08-30
This status may indicate that the corresponding software component comprises custom
modifications in an NWDI-controlled system
If your system is used for NWDI development and it is either a DEV or a CONS system
you will be informed that JSPM will not deploy the modified software components but
only transport them to the CMS transport directory JSPM will deploy only the software
components that are not modified
If your system is not used for NWDI development or if your system is used for NWDI
development and it is either a TEST or a PROD system you will be informed that JSPM
has found newer versions of modified software components and will automatically replace
the original versions with the newer versions JSPM will deploy all software components
that are not modified together with the replaced versions of the modified software
components
CAUTION
You may get a warning telling you that there are patches installed in your system
containing fixes which might not be included in the target SP Stack This is possible if
you have applied patches of the start SP Stack level that were delivered later than the
target SP Stack delivery date In order not to lose these fixes you need to download and
apply the corresponding patches of the target SP Stack level
If you are performing an update from SAP NetWeaver 70 including enhancement
package 1 SPS00 and you have not applied any patches for the software component with
status WARNING before the update then you can ignore warnings such as the following
example
The new version of the development component sapcomcomsapnetweaver
bcrfmoni is 70100200806121227180000 and is lower than the already
deployed version 70100200807090143420000
REVISE Indicates inconsistencies with the corresponding software component
The deployment cannot be performed until all problems have been resolved You can view
the problems by choosing Show Details
9 If the status of the selected SP Stack is OK or WARNING you can start the system update by choosing
Start JSPM then changes the status to SCHEDULED
If the SP Stack to be applied includes a kernel update and the current kernel is not already of the
corresponding patch level JSPM arranges the kernel update as the very first Support Package to
be applied JSPM updates the kernel binaries of all instances (including Dialog Instances and SCS
instances in a HA environment) whose kernel directories DIR_CT_RUN effectively reside on the host
indicated by the profile parameter SAPGLOBALHOST
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2560
CAUTION
Kernel binaries of instances whose kernel directories DIR_CT_RUN are not effectively linked
to the host SAPGLOBALHOST must be updated individually as described in section Manually
Updating Instances with Kernel Directory Located on Separate Hosts below
The kernel update (includes update of SAP Kernel and SAP IGS) using JSPM consists of the following
steps
1 JSPM stops the Central Instance automatically and prompts you to stop the remote SCS and
Dialog Instances manually
2 After you have stopped all the instances choose the Next button in the dialog box
The kernel update starts
NOTE
If the system is running in a high availability environment make sure that the HA
software does not restart the instance automatically during the update
NOTE
If kernel binaries of the SCS instance need to be updated manually (see Manually Updating
Instances with Kernel Directory Located on Separate Hosts below) you must perform this at the
time when JSPM is updating the kernel binaries of the Central Instance In any case the
SCS kernel must be up-to-date before the next restart
When the kernel update is finished a dialog box appears in which you are prompted to restart
the SCS instance manually
3 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries
before you can proceed with the next step For more information see Adjusting the Ownership and
Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
4 Choose Next in the dialog box when the SCS instance is running again
After the kernel update JSPM restarts the system for further deployment of the remaining Support
Packages in the stack
RECOMMENDATION
If you need to update the kernel binaries of any Dialog Instances manually (see Manually
Updating Instances with Kernel Directory Located on Separate Hosts below) perform the update when
JSPM is updating the remaining Support Packages in the stack in order to save time
The deployment of each Support Package can end with one of the following statuses
DEPLOYED
The Support Package has been successfully deployed
DEPLOYED WITH WARNING
The Support Package has been deployed but it possibly may not work properly with other
deployed components
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2660 CUSTOMER 2012-08-30
You can view the details by choosing Show Details or examining the log files You can also view
the details about the component by choosing the Deployed Components tab page
ERROR
An error has occurred during the deployment You can view the details by choosing Show
Details or examining the log files
You must correct the error to be able to continue with the SP Stack update
You can proceed as described for a deployment that finished with status DEPLOYED WITH
WARNING
If the error correction does not change the contents in the JSPM inbox you can continue
the deployment by choosing Resume
If the error correction changes the contents in the JSPM inbox you can choose New
Deployment to redeploy the SP Stack
NOT DEPLOYED
JSPM has not attempted to deploy the software component for certain reasons
If your system is not used for NWDI development you can proceed as described for a
deployment that finished with status ERROR
If your system is used for NWDI development and it is either a DEV or a CONS system
the status of the modified software components is always NOT DEPLOYED JSPM has
transported the software components of the Support Package Stack both modified and
not modified to the CMS transport directory The deployment of the modified software
components is handled by NWDI
Manually Updating Instances with Kernel Directory Located on Separate Hosts
JSPM performs kernel update for all instances (including Dialog Instances and SCS instances in a HA
environment) whose kernel directories DIR_CT_RUN effectively reside on the host indicated by the profile
parameter SAPGLOBALHOST (by using folder sharing on Windows or file system mounting on UNIX) In
rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of those sort of instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances individually
To update the kernel of an instance manually proceed as follows
1 Log on as user ltsapsidgtadm to the host of the instance to be updated
2 Back up the kernel directory which is specified by the profile parameter DIR_CT_RUN
3 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory with
SAPCAR [page 56]
4 Stop the instance being updated
NOTE
If the system is running in a HA environment make sure that the HA software does not
restart the instance automatically during the update
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2760
5 Copy or move the extracted programs from the temporary directory to the local kernel directory
6 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries as
described in section Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
7 Restart the instance after JSPM has finished the deployment of all packages on the Central Instance
Only valid for UNIX |
Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms
On UNIX platforms you must adjust the ownership and execution permissions of the kernel binaries
after the update regardless whether you performed the update manually or by using JSPM because
both update procedures are performed with the ltsapsidgtadm user Enter the following command
sequence
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
224 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the Java system
23 Parallel Update of Dual-Stack Systems
If you perform an update of a dual-stack system (ABAP+Java) we recommend that you follow the
procedure described below The procedure has been validated to update the ABAP stack and the Java
stack of a NetWeaver system in parallel thus reducing the overall system downtime by half
Procedure
1 Before applying ABAP and Java Support Packages use the Single Support Packages option in JSPM and
select for update only the components SAP KERNEL and BC-FES-IGS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
23 Parallel Update of Dual-Stack Systems
2860 CUSTOMER 2012-08-30
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS)
runs on a dedicated host In this case JSPM does not support update of kernel binaries and
you need to update them manually Perform the update manually as described under Updating
SAP Kernel and SAP IGS in section Updating the Application Server ABAP and ABAP-Based Software
Components [page 16]
2 Import the Support Packages for the component SAP_BASIS into the ABAP stack using the ABAP
Support Package Manager (SPAM)
3 Import the remaining ABAP Support Packages with SPAM and in parallel apply the Java Support
Package Stack with JSPM
Proceed as described in Updating the Application Server ABAP and ABAP-Based Software Components [page
16] and Updating the Application Server Java and Java-Based Software Components [page 23]
24 Process Integration
241 Planning
Procedure
This section covers all the units of Process Integration that should be updated Particularly the following
units must always have the same Support Package level (the patch level can be different)
Integration Server
XI Adapter Engine
Partner Connectivity Kit
System with the Usage Type Process Integration
Software components of Integration Server
Components to Be Updated SP File Name Tool Used to Apply SP
Java stack
XI TOOLS 702 SAPXITOOLltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
ABAP stack
XI CONTENT SAP_BASIS 702 SAPBASISltSPgt_ltPLgtZIP File upload
XI CONTENT SAP_ABA 702 SAPABAltSPgt_ltPLgtZIP
SAP NetWeaver Application Server ABAP (see table Software components of Application Server ABAP [page 15])Note that update of the following software components of the ABAP system is not required SAP ABA 702 SAP BW 702 PI_BASIS 702
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 2960
J2EE Adapter Engine
If your implemented scenario includes a J2EE Adapter Engine then it must always be of the same
Support Package level as the Integration Server
Components of the J2EE Adapter Engine
Component to Be Updated SP File NameTool Used to Apply SP
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
J2SE Adapter Engine
The installation of the J2SE Adapter Engine depends on the implemented scenario
Components of the J2SE Adapter Engine
Component to Be Updated SP File Name Tool Used to Apply SP
XI CONNECTIVITY SE 702 SAPXICONSltSPgt_ltPLgtSCA ZIP tool (for example WinZip)
Partner Connectivity Kit
If your implemented scenario includes a Partner Connectivity Kit (PCK) then it must always be of the
same Support Package level as the Integration Server
Software components of Partner Connectivity Kit
Components to Be Updated SP File NameTool Used to Apply SP
XI PCK 702 SAPXIPCKltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of the Application Server Java [page 20])
System Landscape Directory (SLD)
The System Landscape Directory is required for the PI operations Although updating the SLD is not
necessarily required it is advisable to update the SLD server and the SAP Master Data Content within
it from time to time The update of the SLD includes
1 The system where the SLD is running
2 The SAP Master Data Content within this SLD
SAP GUI
See table Compatible SAP GUI Versions [page 51]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3060 CUSTOMER 2012-08-30
242 Updating Units of Process Integration
Procedure
Before you start the update perform the following steps
In the Runtime Workbench use Communication Channel Monitoring to stop all sender channels
for all adapter types on all your Adapter Engines
On the Integration Server use transaction SMQR and deregister all qRFC queues
System with the Usage Type Process Integration
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the XI instance is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system where the XI instance is running
For more information see Application Server Java and Java-Based Software Components [page 19]
System Landscape Directory (Optional)
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the SLD is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the entire Support Package Stack to the system where the SLD is running
For more information see Application Server Java and Java-Based Software Components [page 19]
J2EE Adapter Engine
Apply the Support Package Stack to the system where the Adapter Engine is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Partner Connectivity Kit
Apply the Support Package Stack to the system where the PCK is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Front End GUIs
Update the SAP GUI components if necessary
For more information see SAP GUI Family [page 51]
ABAP 700 Business System (Optional)
Apply the Support Packages for SAP NetWeaver Application Server ABAP (including SAP kernel and
the Support Package for SAP BASIS 700)
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 640 Business System (Optional)
Apply the Support Packages for SAP Web Application Server ABAP 640 (including SAP kernel and the
Support Package for SAP BASIS 640)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3160
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 620 Business System (Optional)
1 Update the SAP Kernel 620
2 Import the released Basis Support Packages for SAP Web AS 620 as well as the most recent Add-
On Support Package for APPINT 200_620 in the order described in SAP Note 439915
J2SE Adapter Engine (Optional)
NOTE
The XI Adapter Engine (J2SE) and all its adapters are provided for compatibility reasons only and
are not developed any further You have to use the XI Adapter Engine running on SAP NetWeaver
AS Java For more information see the Master Guide ndash SAP NetWeaver 70 available on SAP Service
Marketplace at httpservicesapcominstallNW70 Planning
1 Extract the SAPXICONSltSPgt_ltPLgtSCA (XI Connectivity SE 700) archive (ZIP format) to a temporary
directory
2 Save the old configuration files as described in the document Adapterpdf in directory
lttemp_directorygttech_adapterAdministrationDocumentation
3 Unpack the ZIP archive TechnicalAdapterssda to the installation directory of the XI Adapter
Engine (J2SE)
4 Restore the configuration files with restore_configuration
243 Post-Installation Steps
Procedure
Communication Channels and Queues
Restart all stopped sender channels and register all deregistered qRFC queues
XI Content
In the system with usage type PI import the XI content from the archives SAPBASISltSPgt_ltPLgtZIP
and SAPABAltSPgt_ltPLgtZIP as follows
1 Unpack the archives using a ZIP tool of your choice
2 Copy the corresponding export files (with file extension tpz) to the import directory ltINSTDIRgt
ltSAPSIDgtSYSglobalxirepository_serverimport
3 Start the Integration Builder (transaction SXMB_IFR)
4 Enter the Integration Repository by choosing Repository (Design)
5 Choose Tools Import design objects
6 Import the tpz files containing the XI content
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3260 CUSTOMER 2012-08-30
NOTE
For more information see SAP Note 836200
Role Generation on the Integration Server
On the Integration Server execute transaction SUPC (mass generation of roles) for all SAP_XI roles in
each of your clients to regenerate possibly changed roles
NOTE
Do not forget to make a user comparison for regenerated roles afterwards
Partner Connectivity Kit (Optional)
Perform the post-installation steps for PCK as described in SAP Note 746328
SAP Master Data within the SLD (Optional)
In the system where your SLD is running import the latest SLD content as described in SAP Note
669669
Receiver-Based EOIO Serialization in J2EE Adapter Engine (Optional)
The J2EE Adapter Engine can be switched to receiver-based EOIO serialization The switch can be
triggered on demand and is executed asynchronously It includes a database migration step during
which all EOIO processing in the Adapter Engine is disabled See SAP Note 973894 for details about how
to start the EOIO serialization migration
Service Metering (Optional)
Service metering gathers information about a service caller transfers it to the service provider and
counts on the service provisioning side how many times a service is called and by which service caller
Service metering is performed for the XI message protocol and the WS message protocol Service
metering is automatically enabled after applying a Support Package Stack By default only non-sensitive
data is transmitted to internal or external service providers in a compatible way
Service metering can be configured in PI in the Integration Engine on sender-side and in the Integration
Directory
Service metering can be configured in AS ABAP in transaction SOAMANAGER
Only if the service provider is allowed to receive more detailed information about the service caller set
the metering level to higher than the default
For more information see SAP Note 1239428
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3360
25 Business Intelligence
251 Planning
Procedure
Business Intelligence includes one or many of the following units that must be updated depending on
your implemented scenarios The usage types Business Intelligence (BI) and Business Intelligence Java
Components (BI-Java) must always have the same Support Package level
Business Intelligence
Software Components of Business Intelligence
Component to Be Updated SP File Name Tool Used to Apply SP
BI CONT ADDON 70x SAPK-70ltxgtltSPgtINBICONT SAINT
SAP NetWeaver Application Server ABAP (see table Software Components of Application Server ABAP [page 15])
NOTE
For information about the dependencies applying to BI Content Support Packages see SAP Note
653814 BI CONT 703 Support Packages are not part of the NetWeaver SP Stacks Updates can be
performed when applicable Alternatively BI CONT 704 Support Packages can be imported See
the BI Content release strategy in SAP Note 153967
Business Intelligence Java Components
BI Java Components
Component to Be Updated SP File NameTool Used to Apply SP
BI REPORTING AND PLANNING 702 BIREPPLANltSPgt_ltPLgtSCA JSPM
BI WEBDYNPRO ALV 702 BIWDALVltSPgt_ltPLgtSCA
BI INFORM BROADCASTING 702 BIIBCltSPgt_ltPLgtSCA
BI WEB APPLICATIONS 702 BIWEBAPPltSPgt_ltPLgtSCA
BI BASE SERVICES 702 BIBASESltSPgt_ltPLgtSCA
VISUAL COMPOSER BI KITS 702 VCKITBIltSPgt_ltPLgtSCA
Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
BI Precalculation Service
Components of the BI Precalculation Service
Component to Be Updated SP File Name Tool Used to Apply SP
BI Pre-calculation Service 700 xPreCalServerltSPgt_ltPLgtexe Installer
Search and Classification (TREX)
See table TREX Component [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3460 CUSTOMER 2012-08-30
BI Accelerator
The BI Accelerator is based on the TREX technology It is a special Linux 64-bit version of SAP NetWeaver
70 Search and Classification (TREX) which is delivered on preconfigured hardware
NOTE
You cannot use a TREX installation based on 32-bit architecture that is configured for searching
in metadata and documents for the BI Accelerator And vice versa a BI Accelerator box cannot
be used for searching in metadata and documents
If you want to use the search functionality as well as the BI Accelerator you require two separate
installations For more information see BI Accelerator [page 47]
Clients
Depending on your implemented scenarios you have to update SAP GUI Components and Business
Explorer (BI Add-OnBW Add-On)
NOTE
See SAP Note 889314 to determine when to use the BI Add-On and the BW Add-On
NOTE
As SAP GUI 640 is no longer supported BI Frontend Support Package 1800 resp patch 1801 is the
last Support Package resp patch based on SAP GUI 640 For more information see SAP Note
1231292 (Frontend Add-in Strategy 640710 GUI Version)
For more information about the new release strategy for the BI Frontend see SAP Note 1231363
(Changed Delivery Strategy for BI Frontend)
252 Preparation
Procedure
For the Support Packages of the most important Business Intelligence units so called SAPBINews
(SAPBWNews) Notes are created Read these Notes before updating Business Intelligence For SAP
NetWeaver 70 including enhancement package 2 SPS 12 these are the following
Business Intelligence ABAP SAP Note 1680996
Business Intelligence Java Components SAP Note 1726461
BI 70 Frontend Add-On for SAP GUI 710 SAP Note 1413032
BI 70 Frontend Add-On for SAP GUI 720 SAP Note 1630112
BI 70 Frontend Add-On for SAP GUI 730 SAP Note 1726739
For more information about BI Support Packages see SAP Community Network at http
scnsapcomcommunitydata-warehousingnetweaver-bw Related Resources SAP NW BW Support
Packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
2012-08-30 CUSTOMER 3560
253 Updating Units of Business Intelligence
Procedure
Business Intelligence
1 Update the SAP NetWeaver Application Server ABAP (with BI CONT 70x if necessary) with the
appropriate Support Packages
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
NOTE
When applying the component SAP BW 702 some generation errors might occur When
you start importing the BI Support Packages in transaction SPAM choose the menu path
Extras Ignore generation errors For more information see SAP Note 114134
2 Apply the Support Package Stack to the system with the usage type BI-Java
For more information see Application Server Java and Java-Based Software Components [page 19]
3 Update the BI Precalculation Service that is used in your scenario
4 Update the standalone engine Search and Classification (TREX) that is used in your scenario For more
information see Standalone Engine Search and Classification (TREX) [page 44]
NOTE
You have to update TREX to the newest version if you use search capabilities within Business
Intelligence
5 Update the BI Accelerator to the newest available version For more information see BI
Accelerator [page 47]
6 Update the SAP GUI and Business Explorer (BI Add-On BW Add-On) on all remote client hosts
that are involved in the scenario
For more information see SAP GUI Family [page 51] and Business Explorer (BI Add-On BW Add-On)
[page 51]
BI Precalculation Service
1 Log on to the host as a user with administration rights
2 Install the Support Package of the BI Precalculation Service by executing the
xPreCalServerexe file
The welcome screen of the BI Precalculation Server setup wizard appears
The setup now checks the system for the prerequisites
3 Choose the option Update for updating the BI Precalculation service to the current patch level and
then Finish
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3660 CUSTOMER 2012-08-30
26 EP Core
261 Planning
Procedure
The following installable software units must be updated
EP Core
Software Components of EP Core
Component to Be Updated SP File Name Tool Used to Apply SP
PORTAL CORE SERVICES 702 EPBCltSPgt_ltPLgtSCA JSPM
PORTAL FRAMEWORK 702 EPBC2ltSPgt_ltPLgtSCA
PORTAL 702 EPPSERVltSPgt_ltPLgtSCA
PORTAL WEB DYNPRO 702 EPWDCltSPgt_ltPLgtSCA
UWL COLL PROCESS ENGINE 702 UWLJWFltSPgt_ltPLgtSCA
CAF EU 702 SAPEUltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
262 Preparation
Procedure
Backing Up the Portal Runtime Configuration
If you have made changes to the standard Portal Runtime configuration you have to make a backup
of the configuration before the update process For more information see SAP Note 1064468
263 Updating EP Core
Procedure
Apply the Support Package Stack to a system with usage type EP Core
For more information see Application Server Java and Java-Based Software Components [page 19]
264 Post-Installation Steps for EP Core
Procedure
Restoring the Portal Runtime Configuration
To make your changes to the standard Portal Runtime Configuration effective you have to restore
the backup of the configuration done before the update process For more information see SAP Note
1064468
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
26 EP Core
2012-08-30 CUSTOMER 3760
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
3 For UNIX and Windows To start the JSPM navigate to the directory ltINSTDIRgtltSIDgt
ltCentral_Instance_Namegtj2eeJSPM and run the go script file
NOTE
If your system is running on IBM i to start the JSPM proceed as follows
1 To prevent JSPM from automatically starting its GUI in the file usrsapltSIDgt
ltCentral_Instance_Namegtj2eeJSPMparamjspm_configtxt change the
property dialogSDTServerConnectionSDTGuilaunch from true to false
2 On the IBM i host run the go script file using the following command
QSH CMD(usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPMgo)
3 In the mounted directory usrsapltSIDgtltCentral_Instance_Namegtj2eeJSPM run
the StartGui script file The JSPM GUI appears
4 In the Host field enter the target IBM i host
NOTE
Depending on the system type ltCentral_Instance_Namegt has the following syntax
Standalone Java system JCltinstance_nogt
Add-On system DVEBMGSltinstance_nogt
4 Enter your SDM password to log on to the SDM
5 On the Deployment tab page select the Java Support Package Manager option and update the software
component sapcomJSPM to the target SPS level
6 Restart the JSPM and log on with the SDM password
RECOMMENDATION
We strongly recommend that you use the Support and Enhancement Package Stack option when
applying a Support Package Stack Other options can lead to unintended consistency issues
NOTE
If you need to include the latest patches for a particular component during the update process
with the Support and Enhancement Package Stack option stop the JSPM after restart and apply SAP
Note 1080821 Then start the JSPM again
7 On the Deployment tab page select the Support and Enhancement Package Stack option and choose Next
The Support Package Stacks that are available for deployment in the global EPS inbox directory
are displayed
8 In the Target SP Stack Level dropdown box select the Support Package Stack to be applied and choose
Next
In this step JSPM performs various status validations and displays the result of each software
component included in the stack definition XML file on the subsequent screen which includes
the following possible statuses
OK Indicates that the SPS level of the corresponding software component is applicable
WARNING We recommend that you view the details about the component by choosing Show
Details
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2460 CUSTOMER 2012-08-30
This status may indicate that the corresponding software component comprises custom
modifications in an NWDI-controlled system
If your system is used for NWDI development and it is either a DEV or a CONS system
you will be informed that JSPM will not deploy the modified software components but
only transport them to the CMS transport directory JSPM will deploy only the software
components that are not modified
If your system is not used for NWDI development or if your system is used for NWDI
development and it is either a TEST or a PROD system you will be informed that JSPM
has found newer versions of modified software components and will automatically replace
the original versions with the newer versions JSPM will deploy all software components
that are not modified together with the replaced versions of the modified software
components
CAUTION
You may get a warning telling you that there are patches installed in your system
containing fixes which might not be included in the target SP Stack This is possible if
you have applied patches of the start SP Stack level that were delivered later than the
target SP Stack delivery date In order not to lose these fixes you need to download and
apply the corresponding patches of the target SP Stack level
If you are performing an update from SAP NetWeaver 70 including enhancement
package 1 SPS00 and you have not applied any patches for the software component with
status WARNING before the update then you can ignore warnings such as the following
example
The new version of the development component sapcomcomsapnetweaver
bcrfmoni is 70100200806121227180000 and is lower than the already
deployed version 70100200807090143420000
REVISE Indicates inconsistencies with the corresponding software component
The deployment cannot be performed until all problems have been resolved You can view
the problems by choosing Show Details
9 If the status of the selected SP Stack is OK or WARNING you can start the system update by choosing
Start JSPM then changes the status to SCHEDULED
If the SP Stack to be applied includes a kernel update and the current kernel is not already of the
corresponding patch level JSPM arranges the kernel update as the very first Support Package to
be applied JSPM updates the kernel binaries of all instances (including Dialog Instances and SCS
instances in a HA environment) whose kernel directories DIR_CT_RUN effectively reside on the host
indicated by the profile parameter SAPGLOBALHOST
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2560
CAUTION
Kernel binaries of instances whose kernel directories DIR_CT_RUN are not effectively linked
to the host SAPGLOBALHOST must be updated individually as described in section Manually
Updating Instances with Kernel Directory Located on Separate Hosts below
The kernel update (includes update of SAP Kernel and SAP IGS) using JSPM consists of the following
steps
1 JSPM stops the Central Instance automatically and prompts you to stop the remote SCS and
Dialog Instances manually
2 After you have stopped all the instances choose the Next button in the dialog box
The kernel update starts
NOTE
If the system is running in a high availability environment make sure that the HA
software does not restart the instance automatically during the update
NOTE
If kernel binaries of the SCS instance need to be updated manually (see Manually Updating
Instances with Kernel Directory Located on Separate Hosts below) you must perform this at the
time when JSPM is updating the kernel binaries of the Central Instance In any case the
SCS kernel must be up-to-date before the next restart
When the kernel update is finished a dialog box appears in which you are prompted to restart
the SCS instance manually
3 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries
before you can proceed with the next step For more information see Adjusting the Ownership and
Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
4 Choose Next in the dialog box when the SCS instance is running again
After the kernel update JSPM restarts the system for further deployment of the remaining Support
Packages in the stack
RECOMMENDATION
If you need to update the kernel binaries of any Dialog Instances manually (see Manually
Updating Instances with Kernel Directory Located on Separate Hosts below) perform the update when
JSPM is updating the remaining Support Packages in the stack in order to save time
The deployment of each Support Package can end with one of the following statuses
DEPLOYED
The Support Package has been successfully deployed
DEPLOYED WITH WARNING
The Support Package has been deployed but it possibly may not work properly with other
deployed components
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2660 CUSTOMER 2012-08-30
You can view the details by choosing Show Details or examining the log files You can also view
the details about the component by choosing the Deployed Components tab page
ERROR
An error has occurred during the deployment You can view the details by choosing Show
Details or examining the log files
You must correct the error to be able to continue with the SP Stack update
You can proceed as described for a deployment that finished with status DEPLOYED WITH
WARNING
If the error correction does not change the contents in the JSPM inbox you can continue
the deployment by choosing Resume
If the error correction changes the contents in the JSPM inbox you can choose New
Deployment to redeploy the SP Stack
NOT DEPLOYED
JSPM has not attempted to deploy the software component for certain reasons
If your system is not used for NWDI development you can proceed as described for a
deployment that finished with status ERROR
If your system is used for NWDI development and it is either a DEV or a CONS system
the status of the modified software components is always NOT DEPLOYED JSPM has
transported the software components of the Support Package Stack both modified and
not modified to the CMS transport directory The deployment of the modified software
components is handled by NWDI
Manually Updating Instances with Kernel Directory Located on Separate Hosts
JSPM performs kernel update for all instances (including Dialog Instances and SCS instances in a HA
environment) whose kernel directories DIR_CT_RUN effectively reside on the host indicated by the profile
parameter SAPGLOBALHOST (by using folder sharing on Windows or file system mounting on UNIX) In
rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of those sort of instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances individually
To update the kernel of an instance manually proceed as follows
1 Log on as user ltsapsidgtadm to the host of the instance to be updated
2 Back up the kernel directory which is specified by the profile parameter DIR_CT_RUN
3 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory with
SAPCAR [page 56]
4 Stop the instance being updated
NOTE
If the system is running in a HA environment make sure that the HA software does not
restart the instance automatically during the update
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2760
5 Copy or move the extracted programs from the temporary directory to the local kernel directory
6 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries as
described in section Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
7 Restart the instance after JSPM has finished the deployment of all packages on the Central Instance
Only valid for UNIX |
Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms
On UNIX platforms you must adjust the ownership and execution permissions of the kernel binaries
after the update regardless whether you performed the update manually or by using JSPM because
both update procedures are performed with the ltsapsidgtadm user Enter the following command
sequence
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
224 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the Java system
23 Parallel Update of Dual-Stack Systems
If you perform an update of a dual-stack system (ABAP+Java) we recommend that you follow the
procedure described below The procedure has been validated to update the ABAP stack and the Java
stack of a NetWeaver system in parallel thus reducing the overall system downtime by half
Procedure
1 Before applying ABAP and Java Support Packages use the Single Support Packages option in JSPM and
select for update only the components SAP KERNEL and BC-FES-IGS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
23 Parallel Update of Dual-Stack Systems
2860 CUSTOMER 2012-08-30
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS)
runs on a dedicated host In this case JSPM does not support update of kernel binaries and
you need to update them manually Perform the update manually as described under Updating
SAP Kernel and SAP IGS in section Updating the Application Server ABAP and ABAP-Based Software
Components [page 16]
2 Import the Support Packages for the component SAP_BASIS into the ABAP stack using the ABAP
Support Package Manager (SPAM)
3 Import the remaining ABAP Support Packages with SPAM and in parallel apply the Java Support
Package Stack with JSPM
Proceed as described in Updating the Application Server ABAP and ABAP-Based Software Components [page
16] and Updating the Application Server Java and Java-Based Software Components [page 23]
24 Process Integration
241 Planning
Procedure
This section covers all the units of Process Integration that should be updated Particularly the following
units must always have the same Support Package level (the patch level can be different)
Integration Server
XI Adapter Engine
Partner Connectivity Kit
System with the Usage Type Process Integration
Software components of Integration Server
Components to Be Updated SP File Name Tool Used to Apply SP
Java stack
XI TOOLS 702 SAPXITOOLltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
ABAP stack
XI CONTENT SAP_BASIS 702 SAPBASISltSPgt_ltPLgtZIP File upload
XI CONTENT SAP_ABA 702 SAPABAltSPgt_ltPLgtZIP
SAP NetWeaver Application Server ABAP (see table Software components of Application Server ABAP [page 15])Note that update of the following software components of the ABAP system is not required SAP ABA 702 SAP BW 702 PI_BASIS 702
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 2960
J2EE Adapter Engine
If your implemented scenario includes a J2EE Adapter Engine then it must always be of the same
Support Package level as the Integration Server
Components of the J2EE Adapter Engine
Component to Be Updated SP File NameTool Used to Apply SP
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
J2SE Adapter Engine
The installation of the J2SE Adapter Engine depends on the implemented scenario
Components of the J2SE Adapter Engine
Component to Be Updated SP File Name Tool Used to Apply SP
XI CONNECTIVITY SE 702 SAPXICONSltSPgt_ltPLgtSCA ZIP tool (for example WinZip)
Partner Connectivity Kit
If your implemented scenario includes a Partner Connectivity Kit (PCK) then it must always be of the
same Support Package level as the Integration Server
Software components of Partner Connectivity Kit
Components to Be Updated SP File NameTool Used to Apply SP
XI PCK 702 SAPXIPCKltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of the Application Server Java [page 20])
System Landscape Directory (SLD)
The System Landscape Directory is required for the PI operations Although updating the SLD is not
necessarily required it is advisable to update the SLD server and the SAP Master Data Content within
it from time to time The update of the SLD includes
1 The system where the SLD is running
2 The SAP Master Data Content within this SLD
SAP GUI
See table Compatible SAP GUI Versions [page 51]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3060 CUSTOMER 2012-08-30
242 Updating Units of Process Integration
Procedure
Before you start the update perform the following steps
In the Runtime Workbench use Communication Channel Monitoring to stop all sender channels
for all adapter types on all your Adapter Engines
On the Integration Server use transaction SMQR and deregister all qRFC queues
System with the Usage Type Process Integration
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the XI instance is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system where the XI instance is running
For more information see Application Server Java and Java-Based Software Components [page 19]
System Landscape Directory (Optional)
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the SLD is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the entire Support Package Stack to the system where the SLD is running
For more information see Application Server Java and Java-Based Software Components [page 19]
J2EE Adapter Engine
Apply the Support Package Stack to the system where the Adapter Engine is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Partner Connectivity Kit
Apply the Support Package Stack to the system where the PCK is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Front End GUIs
Update the SAP GUI components if necessary
For more information see SAP GUI Family [page 51]
ABAP 700 Business System (Optional)
Apply the Support Packages for SAP NetWeaver Application Server ABAP (including SAP kernel and
the Support Package for SAP BASIS 700)
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 640 Business System (Optional)
Apply the Support Packages for SAP Web Application Server ABAP 640 (including SAP kernel and the
Support Package for SAP BASIS 640)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3160
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 620 Business System (Optional)
1 Update the SAP Kernel 620
2 Import the released Basis Support Packages for SAP Web AS 620 as well as the most recent Add-
On Support Package for APPINT 200_620 in the order described in SAP Note 439915
J2SE Adapter Engine (Optional)
NOTE
The XI Adapter Engine (J2SE) and all its adapters are provided for compatibility reasons only and
are not developed any further You have to use the XI Adapter Engine running on SAP NetWeaver
AS Java For more information see the Master Guide ndash SAP NetWeaver 70 available on SAP Service
Marketplace at httpservicesapcominstallNW70 Planning
1 Extract the SAPXICONSltSPgt_ltPLgtSCA (XI Connectivity SE 700) archive (ZIP format) to a temporary
directory
2 Save the old configuration files as described in the document Adapterpdf in directory
lttemp_directorygttech_adapterAdministrationDocumentation
3 Unpack the ZIP archive TechnicalAdapterssda to the installation directory of the XI Adapter
Engine (J2SE)
4 Restore the configuration files with restore_configuration
243 Post-Installation Steps
Procedure
Communication Channels and Queues
Restart all stopped sender channels and register all deregistered qRFC queues
XI Content
In the system with usage type PI import the XI content from the archives SAPBASISltSPgt_ltPLgtZIP
and SAPABAltSPgt_ltPLgtZIP as follows
1 Unpack the archives using a ZIP tool of your choice
2 Copy the corresponding export files (with file extension tpz) to the import directory ltINSTDIRgt
ltSAPSIDgtSYSglobalxirepository_serverimport
3 Start the Integration Builder (transaction SXMB_IFR)
4 Enter the Integration Repository by choosing Repository (Design)
5 Choose Tools Import design objects
6 Import the tpz files containing the XI content
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3260 CUSTOMER 2012-08-30
NOTE
For more information see SAP Note 836200
Role Generation on the Integration Server
On the Integration Server execute transaction SUPC (mass generation of roles) for all SAP_XI roles in
each of your clients to regenerate possibly changed roles
NOTE
Do not forget to make a user comparison for regenerated roles afterwards
Partner Connectivity Kit (Optional)
Perform the post-installation steps for PCK as described in SAP Note 746328
SAP Master Data within the SLD (Optional)
In the system where your SLD is running import the latest SLD content as described in SAP Note
669669
Receiver-Based EOIO Serialization in J2EE Adapter Engine (Optional)
The J2EE Adapter Engine can be switched to receiver-based EOIO serialization The switch can be
triggered on demand and is executed asynchronously It includes a database migration step during
which all EOIO processing in the Adapter Engine is disabled See SAP Note 973894 for details about how
to start the EOIO serialization migration
Service Metering (Optional)
Service metering gathers information about a service caller transfers it to the service provider and
counts on the service provisioning side how many times a service is called and by which service caller
Service metering is performed for the XI message protocol and the WS message protocol Service
metering is automatically enabled after applying a Support Package Stack By default only non-sensitive
data is transmitted to internal or external service providers in a compatible way
Service metering can be configured in PI in the Integration Engine on sender-side and in the Integration
Directory
Service metering can be configured in AS ABAP in transaction SOAMANAGER
Only if the service provider is allowed to receive more detailed information about the service caller set
the metering level to higher than the default
For more information see SAP Note 1239428
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3360
25 Business Intelligence
251 Planning
Procedure
Business Intelligence includes one or many of the following units that must be updated depending on
your implemented scenarios The usage types Business Intelligence (BI) and Business Intelligence Java
Components (BI-Java) must always have the same Support Package level
Business Intelligence
Software Components of Business Intelligence
Component to Be Updated SP File Name Tool Used to Apply SP
BI CONT ADDON 70x SAPK-70ltxgtltSPgtINBICONT SAINT
SAP NetWeaver Application Server ABAP (see table Software Components of Application Server ABAP [page 15])
NOTE
For information about the dependencies applying to BI Content Support Packages see SAP Note
653814 BI CONT 703 Support Packages are not part of the NetWeaver SP Stacks Updates can be
performed when applicable Alternatively BI CONT 704 Support Packages can be imported See
the BI Content release strategy in SAP Note 153967
Business Intelligence Java Components
BI Java Components
Component to Be Updated SP File NameTool Used to Apply SP
BI REPORTING AND PLANNING 702 BIREPPLANltSPgt_ltPLgtSCA JSPM
BI WEBDYNPRO ALV 702 BIWDALVltSPgt_ltPLgtSCA
BI INFORM BROADCASTING 702 BIIBCltSPgt_ltPLgtSCA
BI WEB APPLICATIONS 702 BIWEBAPPltSPgt_ltPLgtSCA
BI BASE SERVICES 702 BIBASESltSPgt_ltPLgtSCA
VISUAL COMPOSER BI KITS 702 VCKITBIltSPgt_ltPLgtSCA
Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
BI Precalculation Service
Components of the BI Precalculation Service
Component to Be Updated SP File Name Tool Used to Apply SP
BI Pre-calculation Service 700 xPreCalServerltSPgt_ltPLgtexe Installer
Search and Classification (TREX)
See table TREX Component [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3460 CUSTOMER 2012-08-30
BI Accelerator
The BI Accelerator is based on the TREX technology It is a special Linux 64-bit version of SAP NetWeaver
70 Search and Classification (TREX) which is delivered on preconfigured hardware
NOTE
You cannot use a TREX installation based on 32-bit architecture that is configured for searching
in metadata and documents for the BI Accelerator And vice versa a BI Accelerator box cannot
be used for searching in metadata and documents
If you want to use the search functionality as well as the BI Accelerator you require two separate
installations For more information see BI Accelerator [page 47]
Clients
Depending on your implemented scenarios you have to update SAP GUI Components and Business
Explorer (BI Add-OnBW Add-On)
NOTE
See SAP Note 889314 to determine when to use the BI Add-On and the BW Add-On
NOTE
As SAP GUI 640 is no longer supported BI Frontend Support Package 1800 resp patch 1801 is the
last Support Package resp patch based on SAP GUI 640 For more information see SAP Note
1231292 (Frontend Add-in Strategy 640710 GUI Version)
For more information about the new release strategy for the BI Frontend see SAP Note 1231363
(Changed Delivery Strategy for BI Frontend)
252 Preparation
Procedure
For the Support Packages of the most important Business Intelligence units so called SAPBINews
(SAPBWNews) Notes are created Read these Notes before updating Business Intelligence For SAP
NetWeaver 70 including enhancement package 2 SPS 12 these are the following
Business Intelligence ABAP SAP Note 1680996
Business Intelligence Java Components SAP Note 1726461
BI 70 Frontend Add-On for SAP GUI 710 SAP Note 1413032
BI 70 Frontend Add-On for SAP GUI 720 SAP Note 1630112
BI 70 Frontend Add-On for SAP GUI 730 SAP Note 1726739
For more information about BI Support Packages see SAP Community Network at http
scnsapcomcommunitydata-warehousingnetweaver-bw Related Resources SAP NW BW Support
Packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
2012-08-30 CUSTOMER 3560
253 Updating Units of Business Intelligence
Procedure
Business Intelligence
1 Update the SAP NetWeaver Application Server ABAP (with BI CONT 70x if necessary) with the
appropriate Support Packages
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
NOTE
When applying the component SAP BW 702 some generation errors might occur When
you start importing the BI Support Packages in transaction SPAM choose the menu path
Extras Ignore generation errors For more information see SAP Note 114134
2 Apply the Support Package Stack to the system with the usage type BI-Java
For more information see Application Server Java and Java-Based Software Components [page 19]
3 Update the BI Precalculation Service that is used in your scenario
4 Update the standalone engine Search and Classification (TREX) that is used in your scenario For more
information see Standalone Engine Search and Classification (TREX) [page 44]
NOTE
You have to update TREX to the newest version if you use search capabilities within Business
Intelligence
5 Update the BI Accelerator to the newest available version For more information see BI
Accelerator [page 47]
6 Update the SAP GUI and Business Explorer (BI Add-On BW Add-On) on all remote client hosts
that are involved in the scenario
For more information see SAP GUI Family [page 51] and Business Explorer (BI Add-On BW Add-On)
[page 51]
BI Precalculation Service
1 Log on to the host as a user with administration rights
2 Install the Support Package of the BI Precalculation Service by executing the
xPreCalServerexe file
The welcome screen of the BI Precalculation Server setup wizard appears
The setup now checks the system for the prerequisites
3 Choose the option Update for updating the BI Precalculation service to the current patch level and
then Finish
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3660 CUSTOMER 2012-08-30
26 EP Core
261 Planning
Procedure
The following installable software units must be updated
EP Core
Software Components of EP Core
Component to Be Updated SP File Name Tool Used to Apply SP
PORTAL CORE SERVICES 702 EPBCltSPgt_ltPLgtSCA JSPM
PORTAL FRAMEWORK 702 EPBC2ltSPgt_ltPLgtSCA
PORTAL 702 EPPSERVltSPgt_ltPLgtSCA
PORTAL WEB DYNPRO 702 EPWDCltSPgt_ltPLgtSCA
UWL COLL PROCESS ENGINE 702 UWLJWFltSPgt_ltPLgtSCA
CAF EU 702 SAPEUltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
262 Preparation
Procedure
Backing Up the Portal Runtime Configuration
If you have made changes to the standard Portal Runtime configuration you have to make a backup
of the configuration before the update process For more information see SAP Note 1064468
263 Updating EP Core
Procedure
Apply the Support Package Stack to a system with usage type EP Core
For more information see Application Server Java and Java-Based Software Components [page 19]
264 Post-Installation Steps for EP Core
Procedure
Restoring the Portal Runtime Configuration
To make your changes to the standard Portal Runtime Configuration effective you have to restore
the backup of the configuration done before the update process For more information see SAP Note
1064468
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
26 EP Core
2012-08-30 CUSTOMER 3760
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
This status may indicate that the corresponding software component comprises custom
modifications in an NWDI-controlled system
If your system is used for NWDI development and it is either a DEV or a CONS system
you will be informed that JSPM will not deploy the modified software components but
only transport them to the CMS transport directory JSPM will deploy only the software
components that are not modified
If your system is not used for NWDI development or if your system is used for NWDI
development and it is either a TEST or a PROD system you will be informed that JSPM
has found newer versions of modified software components and will automatically replace
the original versions with the newer versions JSPM will deploy all software components
that are not modified together with the replaced versions of the modified software
components
CAUTION
You may get a warning telling you that there are patches installed in your system
containing fixes which might not be included in the target SP Stack This is possible if
you have applied patches of the start SP Stack level that were delivered later than the
target SP Stack delivery date In order not to lose these fixes you need to download and
apply the corresponding patches of the target SP Stack level
If you are performing an update from SAP NetWeaver 70 including enhancement
package 1 SPS00 and you have not applied any patches for the software component with
status WARNING before the update then you can ignore warnings such as the following
example
The new version of the development component sapcomcomsapnetweaver
bcrfmoni is 70100200806121227180000 and is lower than the already
deployed version 70100200807090143420000
REVISE Indicates inconsistencies with the corresponding software component
The deployment cannot be performed until all problems have been resolved You can view
the problems by choosing Show Details
9 If the status of the selected SP Stack is OK or WARNING you can start the system update by choosing
Start JSPM then changes the status to SCHEDULED
If the SP Stack to be applied includes a kernel update and the current kernel is not already of the
corresponding patch level JSPM arranges the kernel update as the very first Support Package to
be applied JSPM updates the kernel binaries of all instances (including Dialog Instances and SCS
instances in a HA environment) whose kernel directories DIR_CT_RUN effectively reside on the host
indicated by the profile parameter SAPGLOBALHOST
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2560
CAUTION
Kernel binaries of instances whose kernel directories DIR_CT_RUN are not effectively linked
to the host SAPGLOBALHOST must be updated individually as described in section Manually
Updating Instances with Kernel Directory Located on Separate Hosts below
The kernel update (includes update of SAP Kernel and SAP IGS) using JSPM consists of the following
steps
1 JSPM stops the Central Instance automatically and prompts you to stop the remote SCS and
Dialog Instances manually
2 After you have stopped all the instances choose the Next button in the dialog box
The kernel update starts
NOTE
If the system is running in a high availability environment make sure that the HA
software does not restart the instance automatically during the update
NOTE
If kernel binaries of the SCS instance need to be updated manually (see Manually Updating
Instances with Kernel Directory Located on Separate Hosts below) you must perform this at the
time when JSPM is updating the kernel binaries of the Central Instance In any case the
SCS kernel must be up-to-date before the next restart
When the kernel update is finished a dialog box appears in which you are prompted to restart
the SCS instance manually
3 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries
before you can proceed with the next step For more information see Adjusting the Ownership and
Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
4 Choose Next in the dialog box when the SCS instance is running again
After the kernel update JSPM restarts the system for further deployment of the remaining Support
Packages in the stack
RECOMMENDATION
If you need to update the kernel binaries of any Dialog Instances manually (see Manually
Updating Instances with Kernel Directory Located on Separate Hosts below) perform the update when
JSPM is updating the remaining Support Packages in the stack in order to save time
The deployment of each Support Package can end with one of the following statuses
DEPLOYED
The Support Package has been successfully deployed
DEPLOYED WITH WARNING
The Support Package has been deployed but it possibly may not work properly with other
deployed components
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2660 CUSTOMER 2012-08-30
You can view the details by choosing Show Details or examining the log files You can also view
the details about the component by choosing the Deployed Components tab page
ERROR
An error has occurred during the deployment You can view the details by choosing Show
Details or examining the log files
You must correct the error to be able to continue with the SP Stack update
You can proceed as described for a deployment that finished with status DEPLOYED WITH
WARNING
If the error correction does not change the contents in the JSPM inbox you can continue
the deployment by choosing Resume
If the error correction changes the contents in the JSPM inbox you can choose New
Deployment to redeploy the SP Stack
NOT DEPLOYED
JSPM has not attempted to deploy the software component for certain reasons
If your system is not used for NWDI development you can proceed as described for a
deployment that finished with status ERROR
If your system is used for NWDI development and it is either a DEV or a CONS system
the status of the modified software components is always NOT DEPLOYED JSPM has
transported the software components of the Support Package Stack both modified and
not modified to the CMS transport directory The deployment of the modified software
components is handled by NWDI
Manually Updating Instances with Kernel Directory Located on Separate Hosts
JSPM performs kernel update for all instances (including Dialog Instances and SCS instances in a HA
environment) whose kernel directories DIR_CT_RUN effectively reside on the host indicated by the profile
parameter SAPGLOBALHOST (by using folder sharing on Windows or file system mounting on UNIX) In
rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of those sort of instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances individually
To update the kernel of an instance manually proceed as follows
1 Log on as user ltsapsidgtadm to the host of the instance to be updated
2 Back up the kernel directory which is specified by the profile parameter DIR_CT_RUN
3 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory with
SAPCAR [page 56]
4 Stop the instance being updated
NOTE
If the system is running in a HA environment make sure that the HA software does not
restart the instance automatically during the update
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2760
5 Copy or move the extracted programs from the temporary directory to the local kernel directory
6 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries as
described in section Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
7 Restart the instance after JSPM has finished the deployment of all packages on the Central Instance
Only valid for UNIX |
Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms
On UNIX platforms you must adjust the ownership and execution permissions of the kernel binaries
after the update regardless whether you performed the update manually or by using JSPM because
both update procedures are performed with the ltsapsidgtadm user Enter the following command
sequence
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
224 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the Java system
23 Parallel Update of Dual-Stack Systems
If you perform an update of a dual-stack system (ABAP+Java) we recommend that you follow the
procedure described below The procedure has been validated to update the ABAP stack and the Java
stack of a NetWeaver system in parallel thus reducing the overall system downtime by half
Procedure
1 Before applying ABAP and Java Support Packages use the Single Support Packages option in JSPM and
select for update only the components SAP KERNEL and BC-FES-IGS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
23 Parallel Update of Dual-Stack Systems
2860 CUSTOMER 2012-08-30
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS)
runs on a dedicated host In this case JSPM does not support update of kernel binaries and
you need to update them manually Perform the update manually as described under Updating
SAP Kernel and SAP IGS in section Updating the Application Server ABAP and ABAP-Based Software
Components [page 16]
2 Import the Support Packages for the component SAP_BASIS into the ABAP stack using the ABAP
Support Package Manager (SPAM)
3 Import the remaining ABAP Support Packages with SPAM and in parallel apply the Java Support
Package Stack with JSPM
Proceed as described in Updating the Application Server ABAP and ABAP-Based Software Components [page
16] and Updating the Application Server Java and Java-Based Software Components [page 23]
24 Process Integration
241 Planning
Procedure
This section covers all the units of Process Integration that should be updated Particularly the following
units must always have the same Support Package level (the patch level can be different)
Integration Server
XI Adapter Engine
Partner Connectivity Kit
System with the Usage Type Process Integration
Software components of Integration Server
Components to Be Updated SP File Name Tool Used to Apply SP
Java stack
XI TOOLS 702 SAPXITOOLltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
ABAP stack
XI CONTENT SAP_BASIS 702 SAPBASISltSPgt_ltPLgtZIP File upload
XI CONTENT SAP_ABA 702 SAPABAltSPgt_ltPLgtZIP
SAP NetWeaver Application Server ABAP (see table Software components of Application Server ABAP [page 15])Note that update of the following software components of the ABAP system is not required SAP ABA 702 SAP BW 702 PI_BASIS 702
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 2960
J2EE Adapter Engine
If your implemented scenario includes a J2EE Adapter Engine then it must always be of the same
Support Package level as the Integration Server
Components of the J2EE Adapter Engine
Component to Be Updated SP File NameTool Used to Apply SP
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
J2SE Adapter Engine
The installation of the J2SE Adapter Engine depends on the implemented scenario
Components of the J2SE Adapter Engine
Component to Be Updated SP File Name Tool Used to Apply SP
XI CONNECTIVITY SE 702 SAPXICONSltSPgt_ltPLgtSCA ZIP tool (for example WinZip)
Partner Connectivity Kit
If your implemented scenario includes a Partner Connectivity Kit (PCK) then it must always be of the
same Support Package level as the Integration Server
Software components of Partner Connectivity Kit
Components to Be Updated SP File NameTool Used to Apply SP
XI PCK 702 SAPXIPCKltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of the Application Server Java [page 20])
System Landscape Directory (SLD)
The System Landscape Directory is required for the PI operations Although updating the SLD is not
necessarily required it is advisable to update the SLD server and the SAP Master Data Content within
it from time to time The update of the SLD includes
1 The system where the SLD is running
2 The SAP Master Data Content within this SLD
SAP GUI
See table Compatible SAP GUI Versions [page 51]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3060 CUSTOMER 2012-08-30
242 Updating Units of Process Integration
Procedure
Before you start the update perform the following steps
In the Runtime Workbench use Communication Channel Monitoring to stop all sender channels
for all adapter types on all your Adapter Engines
On the Integration Server use transaction SMQR and deregister all qRFC queues
System with the Usage Type Process Integration
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the XI instance is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system where the XI instance is running
For more information see Application Server Java and Java-Based Software Components [page 19]
System Landscape Directory (Optional)
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the SLD is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the entire Support Package Stack to the system where the SLD is running
For more information see Application Server Java and Java-Based Software Components [page 19]
J2EE Adapter Engine
Apply the Support Package Stack to the system where the Adapter Engine is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Partner Connectivity Kit
Apply the Support Package Stack to the system where the PCK is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Front End GUIs
Update the SAP GUI components if necessary
For more information see SAP GUI Family [page 51]
ABAP 700 Business System (Optional)
Apply the Support Packages for SAP NetWeaver Application Server ABAP (including SAP kernel and
the Support Package for SAP BASIS 700)
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 640 Business System (Optional)
Apply the Support Packages for SAP Web Application Server ABAP 640 (including SAP kernel and the
Support Package for SAP BASIS 640)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3160
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 620 Business System (Optional)
1 Update the SAP Kernel 620
2 Import the released Basis Support Packages for SAP Web AS 620 as well as the most recent Add-
On Support Package for APPINT 200_620 in the order described in SAP Note 439915
J2SE Adapter Engine (Optional)
NOTE
The XI Adapter Engine (J2SE) and all its adapters are provided for compatibility reasons only and
are not developed any further You have to use the XI Adapter Engine running on SAP NetWeaver
AS Java For more information see the Master Guide ndash SAP NetWeaver 70 available on SAP Service
Marketplace at httpservicesapcominstallNW70 Planning
1 Extract the SAPXICONSltSPgt_ltPLgtSCA (XI Connectivity SE 700) archive (ZIP format) to a temporary
directory
2 Save the old configuration files as described in the document Adapterpdf in directory
lttemp_directorygttech_adapterAdministrationDocumentation
3 Unpack the ZIP archive TechnicalAdapterssda to the installation directory of the XI Adapter
Engine (J2SE)
4 Restore the configuration files with restore_configuration
243 Post-Installation Steps
Procedure
Communication Channels and Queues
Restart all stopped sender channels and register all deregistered qRFC queues
XI Content
In the system with usage type PI import the XI content from the archives SAPBASISltSPgt_ltPLgtZIP
and SAPABAltSPgt_ltPLgtZIP as follows
1 Unpack the archives using a ZIP tool of your choice
2 Copy the corresponding export files (with file extension tpz) to the import directory ltINSTDIRgt
ltSAPSIDgtSYSglobalxirepository_serverimport
3 Start the Integration Builder (transaction SXMB_IFR)
4 Enter the Integration Repository by choosing Repository (Design)
5 Choose Tools Import design objects
6 Import the tpz files containing the XI content
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3260 CUSTOMER 2012-08-30
NOTE
For more information see SAP Note 836200
Role Generation on the Integration Server
On the Integration Server execute transaction SUPC (mass generation of roles) for all SAP_XI roles in
each of your clients to regenerate possibly changed roles
NOTE
Do not forget to make a user comparison for regenerated roles afterwards
Partner Connectivity Kit (Optional)
Perform the post-installation steps for PCK as described in SAP Note 746328
SAP Master Data within the SLD (Optional)
In the system where your SLD is running import the latest SLD content as described in SAP Note
669669
Receiver-Based EOIO Serialization in J2EE Adapter Engine (Optional)
The J2EE Adapter Engine can be switched to receiver-based EOIO serialization The switch can be
triggered on demand and is executed asynchronously It includes a database migration step during
which all EOIO processing in the Adapter Engine is disabled See SAP Note 973894 for details about how
to start the EOIO serialization migration
Service Metering (Optional)
Service metering gathers information about a service caller transfers it to the service provider and
counts on the service provisioning side how many times a service is called and by which service caller
Service metering is performed for the XI message protocol and the WS message protocol Service
metering is automatically enabled after applying a Support Package Stack By default only non-sensitive
data is transmitted to internal or external service providers in a compatible way
Service metering can be configured in PI in the Integration Engine on sender-side and in the Integration
Directory
Service metering can be configured in AS ABAP in transaction SOAMANAGER
Only if the service provider is allowed to receive more detailed information about the service caller set
the metering level to higher than the default
For more information see SAP Note 1239428
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3360
25 Business Intelligence
251 Planning
Procedure
Business Intelligence includes one or many of the following units that must be updated depending on
your implemented scenarios The usage types Business Intelligence (BI) and Business Intelligence Java
Components (BI-Java) must always have the same Support Package level
Business Intelligence
Software Components of Business Intelligence
Component to Be Updated SP File Name Tool Used to Apply SP
BI CONT ADDON 70x SAPK-70ltxgtltSPgtINBICONT SAINT
SAP NetWeaver Application Server ABAP (see table Software Components of Application Server ABAP [page 15])
NOTE
For information about the dependencies applying to BI Content Support Packages see SAP Note
653814 BI CONT 703 Support Packages are not part of the NetWeaver SP Stacks Updates can be
performed when applicable Alternatively BI CONT 704 Support Packages can be imported See
the BI Content release strategy in SAP Note 153967
Business Intelligence Java Components
BI Java Components
Component to Be Updated SP File NameTool Used to Apply SP
BI REPORTING AND PLANNING 702 BIREPPLANltSPgt_ltPLgtSCA JSPM
BI WEBDYNPRO ALV 702 BIWDALVltSPgt_ltPLgtSCA
BI INFORM BROADCASTING 702 BIIBCltSPgt_ltPLgtSCA
BI WEB APPLICATIONS 702 BIWEBAPPltSPgt_ltPLgtSCA
BI BASE SERVICES 702 BIBASESltSPgt_ltPLgtSCA
VISUAL COMPOSER BI KITS 702 VCKITBIltSPgt_ltPLgtSCA
Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
BI Precalculation Service
Components of the BI Precalculation Service
Component to Be Updated SP File Name Tool Used to Apply SP
BI Pre-calculation Service 700 xPreCalServerltSPgt_ltPLgtexe Installer
Search and Classification (TREX)
See table TREX Component [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3460 CUSTOMER 2012-08-30
BI Accelerator
The BI Accelerator is based on the TREX technology It is a special Linux 64-bit version of SAP NetWeaver
70 Search and Classification (TREX) which is delivered on preconfigured hardware
NOTE
You cannot use a TREX installation based on 32-bit architecture that is configured for searching
in metadata and documents for the BI Accelerator And vice versa a BI Accelerator box cannot
be used for searching in metadata and documents
If you want to use the search functionality as well as the BI Accelerator you require two separate
installations For more information see BI Accelerator [page 47]
Clients
Depending on your implemented scenarios you have to update SAP GUI Components and Business
Explorer (BI Add-OnBW Add-On)
NOTE
See SAP Note 889314 to determine when to use the BI Add-On and the BW Add-On
NOTE
As SAP GUI 640 is no longer supported BI Frontend Support Package 1800 resp patch 1801 is the
last Support Package resp patch based on SAP GUI 640 For more information see SAP Note
1231292 (Frontend Add-in Strategy 640710 GUI Version)
For more information about the new release strategy for the BI Frontend see SAP Note 1231363
(Changed Delivery Strategy for BI Frontend)
252 Preparation
Procedure
For the Support Packages of the most important Business Intelligence units so called SAPBINews
(SAPBWNews) Notes are created Read these Notes before updating Business Intelligence For SAP
NetWeaver 70 including enhancement package 2 SPS 12 these are the following
Business Intelligence ABAP SAP Note 1680996
Business Intelligence Java Components SAP Note 1726461
BI 70 Frontend Add-On for SAP GUI 710 SAP Note 1413032
BI 70 Frontend Add-On for SAP GUI 720 SAP Note 1630112
BI 70 Frontend Add-On for SAP GUI 730 SAP Note 1726739
For more information about BI Support Packages see SAP Community Network at http
scnsapcomcommunitydata-warehousingnetweaver-bw Related Resources SAP NW BW Support
Packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
2012-08-30 CUSTOMER 3560
253 Updating Units of Business Intelligence
Procedure
Business Intelligence
1 Update the SAP NetWeaver Application Server ABAP (with BI CONT 70x if necessary) with the
appropriate Support Packages
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
NOTE
When applying the component SAP BW 702 some generation errors might occur When
you start importing the BI Support Packages in transaction SPAM choose the menu path
Extras Ignore generation errors For more information see SAP Note 114134
2 Apply the Support Package Stack to the system with the usage type BI-Java
For more information see Application Server Java and Java-Based Software Components [page 19]
3 Update the BI Precalculation Service that is used in your scenario
4 Update the standalone engine Search and Classification (TREX) that is used in your scenario For more
information see Standalone Engine Search and Classification (TREX) [page 44]
NOTE
You have to update TREX to the newest version if you use search capabilities within Business
Intelligence
5 Update the BI Accelerator to the newest available version For more information see BI
Accelerator [page 47]
6 Update the SAP GUI and Business Explorer (BI Add-On BW Add-On) on all remote client hosts
that are involved in the scenario
For more information see SAP GUI Family [page 51] and Business Explorer (BI Add-On BW Add-On)
[page 51]
BI Precalculation Service
1 Log on to the host as a user with administration rights
2 Install the Support Package of the BI Precalculation Service by executing the
xPreCalServerexe file
The welcome screen of the BI Precalculation Server setup wizard appears
The setup now checks the system for the prerequisites
3 Choose the option Update for updating the BI Precalculation service to the current patch level and
then Finish
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3660 CUSTOMER 2012-08-30
26 EP Core
261 Planning
Procedure
The following installable software units must be updated
EP Core
Software Components of EP Core
Component to Be Updated SP File Name Tool Used to Apply SP
PORTAL CORE SERVICES 702 EPBCltSPgt_ltPLgtSCA JSPM
PORTAL FRAMEWORK 702 EPBC2ltSPgt_ltPLgtSCA
PORTAL 702 EPPSERVltSPgt_ltPLgtSCA
PORTAL WEB DYNPRO 702 EPWDCltSPgt_ltPLgtSCA
UWL COLL PROCESS ENGINE 702 UWLJWFltSPgt_ltPLgtSCA
CAF EU 702 SAPEUltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
262 Preparation
Procedure
Backing Up the Portal Runtime Configuration
If you have made changes to the standard Portal Runtime configuration you have to make a backup
of the configuration before the update process For more information see SAP Note 1064468
263 Updating EP Core
Procedure
Apply the Support Package Stack to a system with usage type EP Core
For more information see Application Server Java and Java-Based Software Components [page 19]
264 Post-Installation Steps for EP Core
Procedure
Restoring the Portal Runtime Configuration
To make your changes to the standard Portal Runtime Configuration effective you have to restore
the backup of the configuration done before the update process For more information see SAP Note
1064468
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
26 EP Core
2012-08-30 CUSTOMER 3760
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
CAUTION
Kernel binaries of instances whose kernel directories DIR_CT_RUN are not effectively linked
to the host SAPGLOBALHOST must be updated individually as described in section Manually
Updating Instances with Kernel Directory Located on Separate Hosts below
The kernel update (includes update of SAP Kernel and SAP IGS) using JSPM consists of the following
steps
1 JSPM stops the Central Instance automatically and prompts you to stop the remote SCS and
Dialog Instances manually
2 After you have stopped all the instances choose the Next button in the dialog box
The kernel update starts
NOTE
If the system is running in a high availability environment make sure that the HA
software does not restart the instance automatically during the update
NOTE
If kernel binaries of the SCS instance need to be updated manually (see Manually Updating
Instances with Kernel Directory Located on Separate Hosts below) you must perform this at the
time when JSPM is updating the kernel binaries of the Central Instance In any case the
SCS kernel must be up-to-date before the next restart
When the kernel update is finished a dialog box appears in which you are prompted to restart
the SCS instance manually
3 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries
before you can proceed with the next step For more information see Adjusting the Ownership and
Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
4 Choose Next in the dialog box when the SCS instance is running again
After the kernel update JSPM restarts the system for further deployment of the remaining Support
Packages in the stack
RECOMMENDATION
If you need to update the kernel binaries of any Dialog Instances manually (see Manually
Updating Instances with Kernel Directory Located on Separate Hosts below) perform the update when
JSPM is updating the remaining Support Packages in the stack in order to save time
The deployment of each Support Package can end with one of the following statuses
DEPLOYED
The Support Package has been successfully deployed
DEPLOYED WITH WARNING
The Support Package has been deployed but it possibly may not work properly with other
deployed components
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2660 CUSTOMER 2012-08-30
You can view the details by choosing Show Details or examining the log files You can also view
the details about the component by choosing the Deployed Components tab page
ERROR
An error has occurred during the deployment You can view the details by choosing Show
Details or examining the log files
You must correct the error to be able to continue with the SP Stack update
You can proceed as described for a deployment that finished with status DEPLOYED WITH
WARNING
If the error correction does not change the contents in the JSPM inbox you can continue
the deployment by choosing Resume
If the error correction changes the contents in the JSPM inbox you can choose New
Deployment to redeploy the SP Stack
NOT DEPLOYED
JSPM has not attempted to deploy the software component for certain reasons
If your system is not used for NWDI development you can proceed as described for a
deployment that finished with status ERROR
If your system is used for NWDI development and it is either a DEV or a CONS system
the status of the modified software components is always NOT DEPLOYED JSPM has
transported the software components of the Support Package Stack both modified and
not modified to the CMS transport directory The deployment of the modified software
components is handled by NWDI
Manually Updating Instances with Kernel Directory Located on Separate Hosts
JSPM performs kernel update for all instances (including Dialog Instances and SCS instances in a HA
environment) whose kernel directories DIR_CT_RUN effectively reside on the host indicated by the profile
parameter SAPGLOBALHOST (by using folder sharing on Windows or file system mounting on UNIX) In
rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of those sort of instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances individually
To update the kernel of an instance manually proceed as follows
1 Log on as user ltsapsidgtadm to the host of the instance to be updated
2 Back up the kernel directory which is specified by the profile parameter DIR_CT_RUN
3 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory with
SAPCAR [page 56]
4 Stop the instance being updated
NOTE
If the system is running in a HA environment make sure that the HA software does not
restart the instance automatically during the update
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2760
5 Copy or move the extracted programs from the temporary directory to the local kernel directory
6 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries as
described in section Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
7 Restart the instance after JSPM has finished the deployment of all packages on the Central Instance
Only valid for UNIX |
Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms
On UNIX platforms you must adjust the ownership and execution permissions of the kernel binaries
after the update regardless whether you performed the update manually or by using JSPM because
both update procedures are performed with the ltsapsidgtadm user Enter the following command
sequence
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
224 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the Java system
23 Parallel Update of Dual-Stack Systems
If you perform an update of a dual-stack system (ABAP+Java) we recommend that you follow the
procedure described below The procedure has been validated to update the ABAP stack and the Java
stack of a NetWeaver system in parallel thus reducing the overall system downtime by half
Procedure
1 Before applying ABAP and Java Support Packages use the Single Support Packages option in JSPM and
select for update only the components SAP KERNEL and BC-FES-IGS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
23 Parallel Update of Dual-Stack Systems
2860 CUSTOMER 2012-08-30
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS)
runs on a dedicated host In this case JSPM does not support update of kernel binaries and
you need to update them manually Perform the update manually as described under Updating
SAP Kernel and SAP IGS in section Updating the Application Server ABAP and ABAP-Based Software
Components [page 16]
2 Import the Support Packages for the component SAP_BASIS into the ABAP stack using the ABAP
Support Package Manager (SPAM)
3 Import the remaining ABAP Support Packages with SPAM and in parallel apply the Java Support
Package Stack with JSPM
Proceed as described in Updating the Application Server ABAP and ABAP-Based Software Components [page
16] and Updating the Application Server Java and Java-Based Software Components [page 23]
24 Process Integration
241 Planning
Procedure
This section covers all the units of Process Integration that should be updated Particularly the following
units must always have the same Support Package level (the patch level can be different)
Integration Server
XI Adapter Engine
Partner Connectivity Kit
System with the Usage Type Process Integration
Software components of Integration Server
Components to Be Updated SP File Name Tool Used to Apply SP
Java stack
XI TOOLS 702 SAPXITOOLltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
ABAP stack
XI CONTENT SAP_BASIS 702 SAPBASISltSPgt_ltPLgtZIP File upload
XI CONTENT SAP_ABA 702 SAPABAltSPgt_ltPLgtZIP
SAP NetWeaver Application Server ABAP (see table Software components of Application Server ABAP [page 15])Note that update of the following software components of the ABAP system is not required SAP ABA 702 SAP BW 702 PI_BASIS 702
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 2960
J2EE Adapter Engine
If your implemented scenario includes a J2EE Adapter Engine then it must always be of the same
Support Package level as the Integration Server
Components of the J2EE Adapter Engine
Component to Be Updated SP File NameTool Used to Apply SP
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
J2SE Adapter Engine
The installation of the J2SE Adapter Engine depends on the implemented scenario
Components of the J2SE Adapter Engine
Component to Be Updated SP File Name Tool Used to Apply SP
XI CONNECTIVITY SE 702 SAPXICONSltSPgt_ltPLgtSCA ZIP tool (for example WinZip)
Partner Connectivity Kit
If your implemented scenario includes a Partner Connectivity Kit (PCK) then it must always be of the
same Support Package level as the Integration Server
Software components of Partner Connectivity Kit
Components to Be Updated SP File NameTool Used to Apply SP
XI PCK 702 SAPXIPCKltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of the Application Server Java [page 20])
System Landscape Directory (SLD)
The System Landscape Directory is required for the PI operations Although updating the SLD is not
necessarily required it is advisable to update the SLD server and the SAP Master Data Content within
it from time to time The update of the SLD includes
1 The system where the SLD is running
2 The SAP Master Data Content within this SLD
SAP GUI
See table Compatible SAP GUI Versions [page 51]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3060 CUSTOMER 2012-08-30
242 Updating Units of Process Integration
Procedure
Before you start the update perform the following steps
In the Runtime Workbench use Communication Channel Monitoring to stop all sender channels
for all adapter types on all your Adapter Engines
On the Integration Server use transaction SMQR and deregister all qRFC queues
System with the Usage Type Process Integration
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the XI instance is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system where the XI instance is running
For more information see Application Server Java and Java-Based Software Components [page 19]
System Landscape Directory (Optional)
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the SLD is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the entire Support Package Stack to the system where the SLD is running
For more information see Application Server Java and Java-Based Software Components [page 19]
J2EE Adapter Engine
Apply the Support Package Stack to the system where the Adapter Engine is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Partner Connectivity Kit
Apply the Support Package Stack to the system where the PCK is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Front End GUIs
Update the SAP GUI components if necessary
For more information see SAP GUI Family [page 51]
ABAP 700 Business System (Optional)
Apply the Support Packages for SAP NetWeaver Application Server ABAP (including SAP kernel and
the Support Package for SAP BASIS 700)
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 640 Business System (Optional)
Apply the Support Packages for SAP Web Application Server ABAP 640 (including SAP kernel and the
Support Package for SAP BASIS 640)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3160
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 620 Business System (Optional)
1 Update the SAP Kernel 620
2 Import the released Basis Support Packages for SAP Web AS 620 as well as the most recent Add-
On Support Package for APPINT 200_620 in the order described in SAP Note 439915
J2SE Adapter Engine (Optional)
NOTE
The XI Adapter Engine (J2SE) and all its adapters are provided for compatibility reasons only and
are not developed any further You have to use the XI Adapter Engine running on SAP NetWeaver
AS Java For more information see the Master Guide ndash SAP NetWeaver 70 available on SAP Service
Marketplace at httpservicesapcominstallNW70 Planning
1 Extract the SAPXICONSltSPgt_ltPLgtSCA (XI Connectivity SE 700) archive (ZIP format) to a temporary
directory
2 Save the old configuration files as described in the document Adapterpdf in directory
lttemp_directorygttech_adapterAdministrationDocumentation
3 Unpack the ZIP archive TechnicalAdapterssda to the installation directory of the XI Adapter
Engine (J2SE)
4 Restore the configuration files with restore_configuration
243 Post-Installation Steps
Procedure
Communication Channels and Queues
Restart all stopped sender channels and register all deregistered qRFC queues
XI Content
In the system with usage type PI import the XI content from the archives SAPBASISltSPgt_ltPLgtZIP
and SAPABAltSPgt_ltPLgtZIP as follows
1 Unpack the archives using a ZIP tool of your choice
2 Copy the corresponding export files (with file extension tpz) to the import directory ltINSTDIRgt
ltSAPSIDgtSYSglobalxirepository_serverimport
3 Start the Integration Builder (transaction SXMB_IFR)
4 Enter the Integration Repository by choosing Repository (Design)
5 Choose Tools Import design objects
6 Import the tpz files containing the XI content
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3260 CUSTOMER 2012-08-30
NOTE
For more information see SAP Note 836200
Role Generation on the Integration Server
On the Integration Server execute transaction SUPC (mass generation of roles) for all SAP_XI roles in
each of your clients to regenerate possibly changed roles
NOTE
Do not forget to make a user comparison for regenerated roles afterwards
Partner Connectivity Kit (Optional)
Perform the post-installation steps for PCK as described in SAP Note 746328
SAP Master Data within the SLD (Optional)
In the system where your SLD is running import the latest SLD content as described in SAP Note
669669
Receiver-Based EOIO Serialization in J2EE Adapter Engine (Optional)
The J2EE Adapter Engine can be switched to receiver-based EOIO serialization The switch can be
triggered on demand and is executed asynchronously It includes a database migration step during
which all EOIO processing in the Adapter Engine is disabled See SAP Note 973894 for details about how
to start the EOIO serialization migration
Service Metering (Optional)
Service metering gathers information about a service caller transfers it to the service provider and
counts on the service provisioning side how many times a service is called and by which service caller
Service metering is performed for the XI message protocol and the WS message protocol Service
metering is automatically enabled after applying a Support Package Stack By default only non-sensitive
data is transmitted to internal or external service providers in a compatible way
Service metering can be configured in PI in the Integration Engine on sender-side and in the Integration
Directory
Service metering can be configured in AS ABAP in transaction SOAMANAGER
Only if the service provider is allowed to receive more detailed information about the service caller set
the metering level to higher than the default
For more information see SAP Note 1239428
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3360
25 Business Intelligence
251 Planning
Procedure
Business Intelligence includes one or many of the following units that must be updated depending on
your implemented scenarios The usage types Business Intelligence (BI) and Business Intelligence Java
Components (BI-Java) must always have the same Support Package level
Business Intelligence
Software Components of Business Intelligence
Component to Be Updated SP File Name Tool Used to Apply SP
BI CONT ADDON 70x SAPK-70ltxgtltSPgtINBICONT SAINT
SAP NetWeaver Application Server ABAP (see table Software Components of Application Server ABAP [page 15])
NOTE
For information about the dependencies applying to BI Content Support Packages see SAP Note
653814 BI CONT 703 Support Packages are not part of the NetWeaver SP Stacks Updates can be
performed when applicable Alternatively BI CONT 704 Support Packages can be imported See
the BI Content release strategy in SAP Note 153967
Business Intelligence Java Components
BI Java Components
Component to Be Updated SP File NameTool Used to Apply SP
BI REPORTING AND PLANNING 702 BIREPPLANltSPgt_ltPLgtSCA JSPM
BI WEBDYNPRO ALV 702 BIWDALVltSPgt_ltPLgtSCA
BI INFORM BROADCASTING 702 BIIBCltSPgt_ltPLgtSCA
BI WEB APPLICATIONS 702 BIWEBAPPltSPgt_ltPLgtSCA
BI BASE SERVICES 702 BIBASESltSPgt_ltPLgtSCA
VISUAL COMPOSER BI KITS 702 VCKITBIltSPgt_ltPLgtSCA
Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
BI Precalculation Service
Components of the BI Precalculation Service
Component to Be Updated SP File Name Tool Used to Apply SP
BI Pre-calculation Service 700 xPreCalServerltSPgt_ltPLgtexe Installer
Search and Classification (TREX)
See table TREX Component [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3460 CUSTOMER 2012-08-30
BI Accelerator
The BI Accelerator is based on the TREX technology It is a special Linux 64-bit version of SAP NetWeaver
70 Search and Classification (TREX) which is delivered on preconfigured hardware
NOTE
You cannot use a TREX installation based on 32-bit architecture that is configured for searching
in metadata and documents for the BI Accelerator And vice versa a BI Accelerator box cannot
be used for searching in metadata and documents
If you want to use the search functionality as well as the BI Accelerator you require two separate
installations For more information see BI Accelerator [page 47]
Clients
Depending on your implemented scenarios you have to update SAP GUI Components and Business
Explorer (BI Add-OnBW Add-On)
NOTE
See SAP Note 889314 to determine when to use the BI Add-On and the BW Add-On
NOTE
As SAP GUI 640 is no longer supported BI Frontend Support Package 1800 resp patch 1801 is the
last Support Package resp patch based on SAP GUI 640 For more information see SAP Note
1231292 (Frontend Add-in Strategy 640710 GUI Version)
For more information about the new release strategy for the BI Frontend see SAP Note 1231363
(Changed Delivery Strategy for BI Frontend)
252 Preparation
Procedure
For the Support Packages of the most important Business Intelligence units so called SAPBINews
(SAPBWNews) Notes are created Read these Notes before updating Business Intelligence For SAP
NetWeaver 70 including enhancement package 2 SPS 12 these are the following
Business Intelligence ABAP SAP Note 1680996
Business Intelligence Java Components SAP Note 1726461
BI 70 Frontend Add-On for SAP GUI 710 SAP Note 1413032
BI 70 Frontend Add-On for SAP GUI 720 SAP Note 1630112
BI 70 Frontend Add-On for SAP GUI 730 SAP Note 1726739
For more information about BI Support Packages see SAP Community Network at http
scnsapcomcommunitydata-warehousingnetweaver-bw Related Resources SAP NW BW Support
Packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
2012-08-30 CUSTOMER 3560
253 Updating Units of Business Intelligence
Procedure
Business Intelligence
1 Update the SAP NetWeaver Application Server ABAP (with BI CONT 70x if necessary) with the
appropriate Support Packages
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
NOTE
When applying the component SAP BW 702 some generation errors might occur When
you start importing the BI Support Packages in transaction SPAM choose the menu path
Extras Ignore generation errors For more information see SAP Note 114134
2 Apply the Support Package Stack to the system with the usage type BI-Java
For more information see Application Server Java and Java-Based Software Components [page 19]
3 Update the BI Precalculation Service that is used in your scenario
4 Update the standalone engine Search and Classification (TREX) that is used in your scenario For more
information see Standalone Engine Search and Classification (TREX) [page 44]
NOTE
You have to update TREX to the newest version if you use search capabilities within Business
Intelligence
5 Update the BI Accelerator to the newest available version For more information see BI
Accelerator [page 47]
6 Update the SAP GUI and Business Explorer (BI Add-On BW Add-On) on all remote client hosts
that are involved in the scenario
For more information see SAP GUI Family [page 51] and Business Explorer (BI Add-On BW Add-On)
[page 51]
BI Precalculation Service
1 Log on to the host as a user with administration rights
2 Install the Support Package of the BI Precalculation Service by executing the
xPreCalServerexe file
The welcome screen of the BI Precalculation Server setup wizard appears
The setup now checks the system for the prerequisites
3 Choose the option Update for updating the BI Precalculation service to the current patch level and
then Finish
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3660 CUSTOMER 2012-08-30
26 EP Core
261 Planning
Procedure
The following installable software units must be updated
EP Core
Software Components of EP Core
Component to Be Updated SP File Name Tool Used to Apply SP
PORTAL CORE SERVICES 702 EPBCltSPgt_ltPLgtSCA JSPM
PORTAL FRAMEWORK 702 EPBC2ltSPgt_ltPLgtSCA
PORTAL 702 EPPSERVltSPgt_ltPLgtSCA
PORTAL WEB DYNPRO 702 EPWDCltSPgt_ltPLgtSCA
UWL COLL PROCESS ENGINE 702 UWLJWFltSPgt_ltPLgtSCA
CAF EU 702 SAPEUltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
262 Preparation
Procedure
Backing Up the Portal Runtime Configuration
If you have made changes to the standard Portal Runtime configuration you have to make a backup
of the configuration before the update process For more information see SAP Note 1064468
263 Updating EP Core
Procedure
Apply the Support Package Stack to a system with usage type EP Core
For more information see Application Server Java and Java-Based Software Components [page 19]
264 Post-Installation Steps for EP Core
Procedure
Restoring the Portal Runtime Configuration
To make your changes to the standard Portal Runtime Configuration effective you have to restore
the backup of the configuration done before the update process For more information see SAP Note
1064468
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
26 EP Core
2012-08-30 CUSTOMER 3760
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
You can view the details by choosing Show Details or examining the log files You can also view
the details about the component by choosing the Deployed Components tab page
ERROR
An error has occurred during the deployment You can view the details by choosing Show
Details or examining the log files
You must correct the error to be able to continue with the SP Stack update
You can proceed as described for a deployment that finished with status DEPLOYED WITH
WARNING
If the error correction does not change the contents in the JSPM inbox you can continue
the deployment by choosing Resume
If the error correction changes the contents in the JSPM inbox you can choose New
Deployment to redeploy the SP Stack
NOT DEPLOYED
JSPM has not attempted to deploy the software component for certain reasons
If your system is not used for NWDI development you can proceed as described for a
deployment that finished with status ERROR
If your system is used for NWDI development and it is either a DEV or a CONS system
the status of the modified software components is always NOT DEPLOYED JSPM has
transported the software components of the Support Package Stack both modified and
not modified to the CMS transport directory The deployment of the modified software
components is handled by NWDI
Manually Updating Instances with Kernel Directory Located on Separate Hosts
JSPM performs kernel update for all instances (including Dialog Instances and SCS instances in a HA
environment) whose kernel directories DIR_CT_RUN effectively reside on the host indicated by the profile
parameter SAPGLOBALHOST (by using folder sharing on Windows or file system mounting on UNIX) In
rare cases there are systems with instances intentionally using kernel directories located on separate
hosts This means the profile parameter DIR_CT_RUN of those sort of instances does not point to
SAPGLOBALHOST You must perform kernel updates for those instances individually
To update the kernel of an instance manually proceed as follows
1 Log on as user ltsapsidgtadm to the host of the instance to be updated
2 Back up the kernel directory which is specified by the profile parameter DIR_CT_RUN
3 Extract the SAR files of the SAP kernel and IGS Support Packages to a temporary directory with
SAPCAR [page 56]
4 Stop the instance being updated
NOTE
If the system is running in a HA environment make sure that the HA software does not
restart the instance automatically during the update
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
22 Application Server Java and Java-Based Software Components
2012-08-30 CUSTOMER 2760
5 Copy or move the extracted programs from the temporary directory to the local kernel directory
6 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries as
described in section Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
7 Restart the instance after JSPM has finished the deployment of all packages on the Central Instance
Only valid for UNIX |
Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms
On UNIX platforms you must adjust the ownership and execution permissions of the kernel binaries
after the update regardless whether you performed the update manually or by using JSPM because
both update procedures are performed with the ltsapsidgtadm user Enter the following command
sequence
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
224 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the Java system
23 Parallel Update of Dual-Stack Systems
If you perform an update of a dual-stack system (ABAP+Java) we recommend that you follow the
procedure described below The procedure has been validated to update the ABAP stack and the Java
stack of a NetWeaver system in parallel thus reducing the overall system downtime by half
Procedure
1 Before applying ABAP and Java Support Packages use the Single Support Packages option in JSPM and
select for update only the components SAP KERNEL and BC-FES-IGS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
23 Parallel Update of Dual-Stack Systems
2860 CUSTOMER 2012-08-30
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS)
runs on a dedicated host In this case JSPM does not support update of kernel binaries and
you need to update them manually Perform the update manually as described under Updating
SAP Kernel and SAP IGS in section Updating the Application Server ABAP and ABAP-Based Software
Components [page 16]
2 Import the Support Packages for the component SAP_BASIS into the ABAP stack using the ABAP
Support Package Manager (SPAM)
3 Import the remaining ABAP Support Packages with SPAM and in parallel apply the Java Support
Package Stack with JSPM
Proceed as described in Updating the Application Server ABAP and ABAP-Based Software Components [page
16] and Updating the Application Server Java and Java-Based Software Components [page 23]
24 Process Integration
241 Planning
Procedure
This section covers all the units of Process Integration that should be updated Particularly the following
units must always have the same Support Package level (the patch level can be different)
Integration Server
XI Adapter Engine
Partner Connectivity Kit
System with the Usage Type Process Integration
Software components of Integration Server
Components to Be Updated SP File Name Tool Used to Apply SP
Java stack
XI TOOLS 702 SAPXITOOLltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
ABAP stack
XI CONTENT SAP_BASIS 702 SAPBASISltSPgt_ltPLgtZIP File upload
XI CONTENT SAP_ABA 702 SAPABAltSPgt_ltPLgtZIP
SAP NetWeaver Application Server ABAP (see table Software components of Application Server ABAP [page 15])Note that update of the following software components of the ABAP system is not required SAP ABA 702 SAP BW 702 PI_BASIS 702
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 2960
J2EE Adapter Engine
If your implemented scenario includes a J2EE Adapter Engine then it must always be of the same
Support Package level as the Integration Server
Components of the J2EE Adapter Engine
Component to Be Updated SP File NameTool Used to Apply SP
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
J2SE Adapter Engine
The installation of the J2SE Adapter Engine depends on the implemented scenario
Components of the J2SE Adapter Engine
Component to Be Updated SP File Name Tool Used to Apply SP
XI CONNECTIVITY SE 702 SAPXICONSltSPgt_ltPLgtSCA ZIP tool (for example WinZip)
Partner Connectivity Kit
If your implemented scenario includes a Partner Connectivity Kit (PCK) then it must always be of the
same Support Package level as the Integration Server
Software components of Partner Connectivity Kit
Components to Be Updated SP File NameTool Used to Apply SP
XI PCK 702 SAPXIPCKltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of the Application Server Java [page 20])
System Landscape Directory (SLD)
The System Landscape Directory is required for the PI operations Although updating the SLD is not
necessarily required it is advisable to update the SLD server and the SAP Master Data Content within
it from time to time The update of the SLD includes
1 The system where the SLD is running
2 The SAP Master Data Content within this SLD
SAP GUI
See table Compatible SAP GUI Versions [page 51]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3060 CUSTOMER 2012-08-30
242 Updating Units of Process Integration
Procedure
Before you start the update perform the following steps
In the Runtime Workbench use Communication Channel Monitoring to stop all sender channels
for all adapter types on all your Adapter Engines
On the Integration Server use transaction SMQR and deregister all qRFC queues
System with the Usage Type Process Integration
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the XI instance is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system where the XI instance is running
For more information see Application Server Java and Java-Based Software Components [page 19]
System Landscape Directory (Optional)
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the SLD is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the entire Support Package Stack to the system where the SLD is running
For more information see Application Server Java and Java-Based Software Components [page 19]
J2EE Adapter Engine
Apply the Support Package Stack to the system where the Adapter Engine is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Partner Connectivity Kit
Apply the Support Package Stack to the system where the PCK is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Front End GUIs
Update the SAP GUI components if necessary
For more information see SAP GUI Family [page 51]
ABAP 700 Business System (Optional)
Apply the Support Packages for SAP NetWeaver Application Server ABAP (including SAP kernel and
the Support Package for SAP BASIS 700)
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 640 Business System (Optional)
Apply the Support Packages for SAP Web Application Server ABAP 640 (including SAP kernel and the
Support Package for SAP BASIS 640)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3160
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 620 Business System (Optional)
1 Update the SAP Kernel 620
2 Import the released Basis Support Packages for SAP Web AS 620 as well as the most recent Add-
On Support Package for APPINT 200_620 in the order described in SAP Note 439915
J2SE Adapter Engine (Optional)
NOTE
The XI Adapter Engine (J2SE) and all its adapters are provided for compatibility reasons only and
are not developed any further You have to use the XI Adapter Engine running on SAP NetWeaver
AS Java For more information see the Master Guide ndash SAP NetWeaver 70 available on SAP Service
Marketplace at httpservicesapcominstallNW70 Planning
1 Extract the SAPXICONSltSPgt_ltPLgtSCA (XI Connectivity SE 700) archive (ZIP format) to a temporary
directory
2 Save the old configuration files as described in the document Adapterpdf in directory
lttemp_directorygttech_adapterAdministrationDocumentation
3 Unpack the ZIP archive TechnicalAdapterssda to the installation directory of the XI Adapter
Engine (J2SE)
4 Restore the configuration files with restore_configuration
243 Post-Installation Steps
Procedure
Communication Channels and Queues
Restart all stopped sender channels and register all deregistered qRFC queues
XI Content
In the system with usage type PI import the XI content from the archives SAPBASISltSPgt_ltPLgtZIP
and SAPABAltSPgt_ltPLgtZIP as follows
1 Unpack the archives using a ZIP tool of your choice
2 Copy the corresponding export files (with file extension tpz) to the import directory ltINSTDIRgt
ltSAPSIDgtSYSglobalxirepository_serverimport
3 Start the Integration Builder (transaction SXMB_IFR)
4 Enter the Integration Repository by choosing Repository (Design)
5 Choose Tools Import design objects
6 Import the tpz files containing the XI content
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3260 CUSTOMER 2012-08-30
NOTE
For more information see SAP Note 836200
Role Generation on the Integration Server
On the Integration Server execute transaction SUPC (mass generation of roles) for all SAP_XI roles in
each of your clients to regenerate possibly changed roles
NOTE
Do not forget to make a user comparison for regenerated roles afterwards
Partner Connectivity Kit (Optional)
Perform the post-installation steps for PCK as described in SAP Note 746328
SAP Master Data within the SLD (Optional)
In the system where your SLD is running import the latest SLD content as described in SAP Note
669669
Receiver-Based EOIO Serialization in J2EE Adapter Engine (Optional)
The J2EE Adapter Engine can be switched to receiver-based EOIO serialization The switch can be
triggered on demand and is executed asynchronously It includes a database migration step during
which all EOIO processing in the Adapter Engine is disabled See SAP Note 973894 for details about how
to start the EOIO serialization migration
Service Metering (Optional)
Service metering gathers information about a service caller transfers it to the service provider and
counts on the service provisioning side how many times a service is called and by which service caller
Service metering is performed for the XI message protocol and the WS message protocol Service
metering is automatically enabled after applying a Support Package Stack By default only non-sensitive
data is transmitted to internal or external service providers in a compatible way
Service metering can be configured in PI in the Integration Engine on sender-side and in the Integration
Directory
Service metering can be configured in AS ABAP in transaction SOAMANAGER
Only if the service provider is allowed to receive more detailed information about the service caller set
the metering level to higher than the default
For more information see SAP Note 1239428
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3360
25 Business Intelligence
251 Planning
Procedure
Business Intelligence includes one or many of the following units that must be updated depending on
your implemented scenarios The usage types Business Intelligence (BI) and Business Intelligence Java
Components (BI-Java) must always have the same Support Package level
Business Intelligence
Software Components of Business Intelligence
Component to Be Updated SP File Name Tool Used to Apply SP
BI CONT ADDON 70x SAPK-70ltxgtltSPgtINBICONT SAINT
SAP NetWeaver Application Server ABAP (see table Software Components of Application Server ABAP [page 15])
NOTE
For information about the dependencies applying to BI Content Support Packages see SAP Note
653814 BI CONT 703 Support Packages are not part of the NetWeaver SP Stacks Updates can be
performed when applicable Alternatively BI CONT 704 Support Packages can be imported See
the BI Content release strategy in SAP Note 153967
Business Intelligence Java Components
BI Java Components
Component to Be Updated SP File NameTool Used to Apply SP
BI REPORTING AND PLANNING 702 BIREPPLANltSPgt_ltPLgtSCA JSPM
BI WEBDYNPRO ALV 702 BIWDALVltSPgt_ltPLgtSCA
BI INFORM BROADCASTING 702 BIIBCltSPgt_ltPLgtSCA
BI WEB APPLICATIONS 702 BIWEBAPPltSPgt_ltPLgtSCA
BI BASE SERVICES 702 BIBASESltSPgt_ltPLgtSCA
VISUAL COMPOSER BI KITS 702 VCKITBIltSPgt_ltPLgtSCA
Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
BI Precalculation Service
Components of the BI Precalculation Service
Component to Be Updated SP File Name Tool Used to Apply SP
BI Pre-calculation Service 700 xPreCalServerltSPgt_ltPLgtexe Installer
Search and Classification (TREX)
See table TREX Component [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3460 CUSTOMER 2012-08-30
BI Accelerator
The BI Accelerator is based on the TREX technology It is a special Linux 64-bit version of SAP NetWeaver
70 Search and Classification (TREX) which is delivered on preconfigured hardware
NOTE
You cannot use a TREX installation based on 32-bit architecture that is configured for searching
in metadata and documents for the BI Accelerator And vice versa a BI Accelerator box cannot
be used for searching in metadata and documents
If you want to use the search functionality as well as the BI Accelerator you require two separate
installations For more information see BI Accelerator [page 47]
Clients
Depending on your implemented scenarios you have to update SAP GUI Components and Business
Explorer (BI Add-OnBW Add-On)
NOTE
See SAP Note 889314 to determine when to use the BI Add-On and the BW Add-On
NOTE
As SAP GUI 640 is no longer supported BI Frontend Support Package 1800 resp patch 1801 is the
last Support Package resp patch based on SAP GUI 640 For more information see SAP Note
1231292 (Frontend Add-in Strategy 640710 GUI Version)
For more information about the new release strategy for the BI Frontend see SAP Note 1231363
(Changed Delivery Strategy for BI Frontend)
252 Preparation
Procedure
For the Support Packages of the most important Business Intelligence units so called SAPBINews
(SAPBWNews) Notes are created Read these Notes before updating Business Intelligence For SAP
NetWeaver 70 including enhancement package 2 SPS 12 these are the following
Business Intelligence ABAP SAP Note 1680996
Business Intelligence Java Components SAP Note 1726461
BI 70 Frontend Add-On for SAP GUI 710 SAP Note 1413032
BI 70 Frontend Add-On for SAP GUI 720 SAP Note 1630112
BI 70 Frontend Add-On for SAP GUI 730 SAP Note 1726739
For more information about BI Support Packages see SAP Community Network at http
scnsapcomcommunitydata-warehousingnetweaver-bw Related Resources SAP NW BW Support
Packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
2012-08-30 CUSTOMER 3560
253 Updating Units of Business Intelligence
Procedure
Business Intelligence
1 Update the SAP NetWeaver Application Server ABAP (with BI CONT 70x if necessary) with the
appropriate Support Packages
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
NOTE
When applying the component SAP BW 702 some generation errors might occur When
you start importing the BI Support Packages in transaction SPAM choose the menu path
Extras Ignore generation errors For more information see SAP Note 114134
2 Apply the Support Package Stack to the system with the usage type BI-Java
For more information see Application Server Java and Java-Based Software Components [page 19]
3 Update the BI Precalculation Service that is used in your scenario
4 Update the standalone engine Search and Classification (TREX) that is used in your scenario For more
information see Standalone Engine Search and Classification (TREX) [page 44]
NOTE
You have to update TREX to the newest version if you use search capabilities within Business
Intelligence
5 Update the BI Accelerator to the newest available version For more information see BI
Accelerator [page 47]
6 Update the SAP GUI and Business Explorer (BI Add-On BW Add-On) on all remote client hosts
that are involved in the scenario
For more information see SAP GUI Family [page 51] and Business Explorer (BI Add-On BW Add-On)
[page 51]
BI Precalculation Service
1 Log on to the host as a user with administration rights
2 Install the Support Package of the BI Precalculation Service by executing the
xPreCalServerexe file
The welcome screen of the BI Precalculation Server setup wizard appears
The setup now checks the system for the prerequisites
3 Choose the option Update for updating the BI Precalculation service to the current patch level and
then Finish
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3660 CUSTOMER 2012-08-30
26 EP Core
261 Planning
Procedure
The following installable software units must be updated
EP Core
Software Components of EP Core
Component to Be Updated SP File Name Tool Used to Apply SP
PORTAL CORE SERVICES 702 EPBCltSPgt_ltPLgtSCA JSPM
PORTAL FRAMEWORK 702 EPBC2ltSPgt_ltPLgtSCA
PORTAL 702 EPPSERVltSPgt_ltPLgtSCA
PORTAL WEB DYNPRO 702 EPWDCltSPgt_ltPLgtSCA
UWL COLL PROCESS ENGINE 702 UWLJWFltSPgt_ltPLgtSCA
CAF EU 702 SAPEUltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
262 Preparation
Procedure
Backing Up the Portal Runtime Configuration
If you have made changes to the standard Portal Runtime configuration you have to make a backup
of the configuration before the update process For more information see SAP Note 1064468
263 Updating EP Core
Procedure
Apply the Support Package Stack to a system with usage type EP Core
For more information see Application Server Java and Java-Based Software Components [page 19]
264 Post-Installation Steps for EP Core
Procedure
Restoring the Portal Runtime Configuration
To make your changes to the standard Portal Runtime Configuration effective you have to restore
the backup of the configuration done before the update process For more information see SAP Note
1064468
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
26 EP Core
2012-08-30 CUSTOMER 3760
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
5 Copy or move the extracted programs from the temporary directory to the local kernel directory
6 Only valid for UNIX |
On UNIX platforms you must adjust the ownership and permissions of the kernel binaries as
described in section Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms belowEnd of UNIX |
7 Restart the instance after JSPM has finished the deployment of all packages on the Central Instance
Only valid for UNIX |
Adjusting the Ownership and Permissions of Kernel Binaries on UNIX Platforms
On UNIX platforms you must adjust the ownership and execution permissions of the kernel binaries
after the update regardless whether you performed the update manually or by using JSPM because
both update procedures are performed with the ltsapsidgtadm user Enter the following command
sequence
For IBM DB2 for Linux UNIX and Windows
su root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
For IBM DB2 for zOS SAP MaxDB and Oracle
su - root
cd ltkrnl_directorygt
saprootsh ltSAPSIDgt
exit
End of UNIX |
224 Post-Installation Steps
Procedure
Perform the post-installation steps as described in the corresponding sections of the usage types that
have been updated along with the Java system
23 Parallel Update of Dual-Stack Systems
If you perform an update of a dual-stack system (ABAP+Java) we recommend that you follow the
procedure described below The procedure has been validated to update the ABAP stack and the Java
stack of a NetWeaver system in parallel thus reducing the overall system downtime by half
Procedure
1 Before applying ABAP and Java Support Packages use the Single Support Packages option in JSPM and
select for update only the components SAP KERNEL and BC-FES-IGS
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
23 Parallel Update of Dual-Stack Systems
2860 CUSTOMER 2012-08-30
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS)
runs on a dedicated host In this case JSPM does not support update of kernel binaries and
you need to update them manually Perform the update manually as described under Updating
SAP Kernel and SAP IGS in section Updating the Application Server ABAP and ABAP-Based Software
Components [page 16]
2 Import the Support Packages for the component SAP_BASIS into the ABAP stack using the ABAP
Support Package Manager (SPAM)
3 Import the remaining ABAP Support Packages with SPAM and in parallel apply the Java Support
Package Stack with JSPM
Proceed as described in Updating the Application Server ABAP and ABAP-Based Software Components [page
16] and Updating the Application Server Java and Java-Based Software Components [page 23]
24 Process Integration
241 Planning
Procedure
This section covers all the units of Process Integration that should be updated Particularly the following
units must always have the same Support Package level (the patch level can be different)
Integration Server
XI Adapter Engine
Partner Connectivity Kit
System with the Usage Type Process Integration
Software components of Integration Server
Components to Be Updated SP File Name Tool Used to Apply SP
Java stack
XI TOOLS 702 SAPXITOOLltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
ABAP stack
XI CONTENT SAP_BASIS 702 SAPBASISltSPgt_ltPLgtZIP File upload
XI CONTENT SAP_ABA 702 SAPABAltSPgt_ltPLgtZIP
SAP NetWeaver Application Server ABAP (see table Software components of Application Server ABAP [page 15])Note that update of the following software components of the ABAP system is not required SAP ABA 702 SAP BW 702 PI_BASIS 702
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 2960
J2EE Adapter Engine
If your implemented scenario includes a J2EE Adapter Engine then it must always be of the same
Support Package level as the Integration Server
Components of the J2EE Adapter Engine
Component to Be Updated SP File NameTool Used to Apply SP
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
J2SE Adapter Engine
The installation of the J2SE Adapter Engine depends on the implemented scenario
Components of the J2SE Adapter Engine
Component to Be Updated SP File Name Tool Used to Apply SP
XI CONNECTIVITY SE 702 SAPXICONSltSPgt_ltPLgtSCA ZIP tool (for example WinZip)
Partner Connectivity Kit
If your implemented scenario includes a Partner Connectivity Kit (PCK) then it must always be of the
same Support Package level as the Integration Server
Software components of Partner Connectivity Kit
Components to Be Updated SP File NameTool Used to Apply SP
XI PCK 702 SAPXIPCKltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of the Application Server Java [page 20])
System Landscape Directory (SLD)
The System Landscape Directory is required for the PI operations Although updating the SLD is not
necessarily required it is advisable to update the SLD server and the SAP Master Data Content within
it from time to time The update of the SLD includes
1 The system where the SLD is running
2 The SAP Master Data Content within this SLD
SAP GUI
See table Compatible SAP GUI Versions [page 51]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3060 CUSTOMER 2012-08-30
242 Updating Units of Process Integration
Procedure
Before you start the update perform the following steps
In the Runtime Workbench use Communication Channel Monitoring to stop all sender channels
for all adapter types on all your Adapter Engines
On the Integration Server use transaction SMQR and deregister all qRFC queues
System with the Usage Type Process Integration
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the XI instance is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system where the XI instance is running
For more information see Application Server Java and Java-Based Software Components [page 19]
System Landscape Directory (Optional)
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the SLD is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the entire Support Package Stack to the system where the SLD is running
For more information see Application Server Java and Java-Based Software Components [page 19]
J2EE Adapter Engine
Apply the Support Package Stack to the system where the Adapter Engine is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Partner Connectivity Kit
Apply the Support Package Stack to the system where the PCK is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Front End GUIs
Update the SAP GUI components if necessary
For more information see SAP GUI Family [page 51]
ABAP 700 Business System (Optional)
Apply the Support Packages for SAP NetWeaver Application Server ABAP (including SAP kernel and
the Support Package for SAP BASIS 700)
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 640 Business System (Optional)
Apply the Support Packages for SAP Web Application Server ABAP 640 (including SAP kernel and the
Support Package for SAP BASIS 640)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3160
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 620 Business System (Optional)
1 Update the SAP Kernel 620
2 Import the released Basis Support Packages for SAP Web AS 620 as well as the most recent Add-
On Support Package for APPINT 200_620 in the order described in SAP Note 439915
J2SE Adapter Engine (Optional)
NOTE
The XI Adapter Engine (J2SE) and all its adapters are provided for compatibility reasons only and
are not developed any further You have to use the XI Adapter Engine running on SAP NetWeaver
AS Java For more information see the Master Guide ndash SAP NetWeaver 70 available on SAP Service
Marketplace at httpservicesapcominstallNW70 Planning
1 Extract the SAPXICONSltSPgt_ltPLgtSCA (XI Connectivity SE 700) archive (ZIP format) to a temporary
directory
2 Save the old configuration files as described in the document Adapterpdf in directory
lttemp_directorygttech_adapterAdministrationDocumentation
3 Unpack the ZIP archive TechnicalAdapterssda to the installation directory of the XI Adapter
Engine (J2SE)
4 Restore the configuration files with restore_configuration
243 Post-Installation Steps
Procedure
Communication Channels and Queues
Restart all stopped sender channels and register all deregistered qRFC queues
XI Content
In the system with usage type PI import the XI content from the archives SAPBASISltSPgt_ltPLgtZIP
and SAPABAltSPgt_ltPLgtZIP as follows
1 Unpack the archives using a ZIP tool of your choice
2 Copy the corresponding export files (with file extension tpz) to the import directory ltINSTDIRgt
ltSAPSIDgtSYSglobalxirepository_serverimport
3 Start the Integration Builder (transaction SXMB_IFR)
4 Enter the Integration Repository by choosing Repository (Design)
5 Choose Tools Import design objects
6 Import the tpz files containing the XI content
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3260 CUSTOMER 2012-08-30
NOTE
For more information see SAP Note 836200
Role Generation on the Integration Server
On the Integration Server execute transaction SUPC (mass generation of roles) for all SAP_XI roles in
each of your clients to regenerate possibly changed roles
NOTE
Do not forget to make a user comparison for regenerated roles afterwards
Partner Connectivity Kit (Optional)
Perform the post-installation steps for PCK as described in SAP Note 746328
SAP Master Data within the SLD (Optional)
In the system where your SLD is running import the latest SLD content as described in SAP Note
669669
Receiver-Based EOIO Serialization in J2EE Adapter Engine (Optional)
The J2EE Adapter Engine can be switched to receiver-based EOIO serialization The switch can be
triggered on demand and is executed asynchronously It includes a database migration step during
which all EOIO processing in the Adapter Engine is disabled See SAP Note 973894 for details about how
to start the EOIO serialization migration
Service Metering (Optional)
Service metering gathers information about a service caller transfers it to the service provider and
counts on the service provisioning side how many times a service is called and by which service caller
Service metering is performed for the XI message protocol and the WS message protocol Service
metering is automatically enabled after applying a Support Package Stack By default only non-sensitive
data is transmitted to internal or external service providers in a compatible way
Service metering can be configured in PI in the Integration Engine on sender-side and in the Integration
Directory
Service metering can be configured in AS ABAP in transaction SOAMANAGER
Only if the service provider is allowed to receive more detailed information about the service caller set
the metering level to higher than the default
For more information see SAP Note 1239428
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3360
25 Business Intelligence
251 Planning
Procedure
Business Intelligence includes one or many of the following units that must be updated depending on
your implemented scenarios The usage types Business Intelligence (BI) and Business Intelligence Java
Components (BI-Java) must always have the same Support Package level
Business Intelligence
Software Components of Business Intelligence
Component to Be Updated SP File Name Tool Used to Apply SP
BI CONT ADDON 70x SAPK-70ltxgtltSPgtINBICONT SAINT
SAP NetWeaver Application Server ABAP (see table Software Components of Application Server ABAP [page 15])
NOTE
For information about the dependencies applying to BI Content Support Packages see SAP Note
653814 BI CONT 703 Support Packages are not part of the NetWeaver SP Stacks Updates can be
performed when applicable Alternatively BI CONT 704 Support Packages can be imported See
the BI Content release strategy in SAP Note 153967
Business Intelligence Java Components
BI Java Components
Component to Be Updated SP File NameTool Used to Apply SP
BI REPORTING AND PLANNING 702 BIREPPLANltSPgt_ltPLgtSCA JSPM
BI WEBDYNPRO ALV 702 BIWDALVltSPgt_ltPLgtSCA
BI INFORM BROADCASTING 702 BIIBCltSPgt_ltPLgtSCA
BI WEB APPLICATIONS 702 BIWEBAPPltSPgt_ltPLgtSCA
BI BASE SERVICES 702 BIBASESltSPgt_ltPLgtSCA
VISUAL COMPOSER BI KITS 702 VCKITBIltSPgt_ltPLgtSCA
Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
BI Precalculation Service
Components of the BI Precalculation Service
Component to Be Updated SP File Name Tool Used to Apply SP
BI Pre-calculation Service 700 xPreCalServerltSPgt_ltPLgtexe Installer
Search and Classification (TREX)
See table TREX Component [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3460 CUSTOMER 2012-08-30
BI Accelerator
The BI Accelerator is based on the TREX technology It is a special Linux 64-bit version of SAP NetWeaver
70 Search and Classification (TREX) which is delivered on preconfigured hardware
NOTE
You cannot use a TREX installation based on 32-bit architecture that is configured for searching
in metadata and documents for the BI Accelerator And vice versa a BI Accelerator box cannot
be used for searching in metadata and documents
If you want to use the search functionality as well as the BI Accelerator you require two separate
installations For more information see BI Accelerator [page 47]
Clients
Depending on your implemented scenarios you have to update SAP GUI Components and Business
Explorer (BI Add-OnBW Add-On)
NOTE
See SAP Note 889314 to determine when to use the BI Add-On and the BW Add-On
NOTE
As SAP GUI 640 is no longer supported BI Frontend Support Package 1800 resp patch 1801 is the
last Support Package resp patch based on SAP GUI 640 For more information see SAP Note
1231292 (Frontend Add-in Strategy 640710 GUI Version)
For more information about the new release strategy for the BI Frontend see SAP Note 1231363
(Changed Delivery Strategy for BI Frontend)
252 Preparation
Procedure
For the Support Packages of the most important Business Intelligence units so called SAPBINews
(SAPBWNews) Notes are created Read these Notes before updating Business Intelligence For SAP
NetWeaver 70 including enhancement package 2 SPS 12 these are the following
Business Intelligence ABAP SAP Note 1680996
Business Intelligence Java Components SAP Note 1726461
BI 70 Frontend Add-On for SAP GUI 710 SAP Note 1413032
BI 70 Frontend Add-On for SAP GUI 720 SAP Note 1630112
BI 70 Frontend Add-On for SAP GUI 730 SAP Note 1726739
For more information about BI Support Packages see SAP Community Network at http
scnsapcomcommunitydata-warehousingnetweaver-bw Related Resources SAP NW BW Support
Packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
2012-08-30 CUSTOMER 3560
253 Updating Units of Business Intelligence
Procedure
Business Intelligence
1 Update the SAP NetWeaver Application Server ABAP (with BI CONT 70x if necessary) with the
appropriate Support Packages
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
NOTE
When applying the component SAP BW 702 some generation errors might occur When
you start importing the BI Support Packages in transaction SPAM choose the menu path
Extras Ignore generation errors For more information see SAP Note 114134
2 Apply the Support Package Stack to the system with the usage type BI-Java
For more information see Application Server Java and Java-Based Software Components [page 19]
3 Update the BI Precalculation Service that is used in your scenario
4 Update the standalone engine Search and Classification (TREX) that is used in your scenario For more
information see Standalone Engine Search and Classification (TREX) [page 44]
NOTE
You have to update TREX to the newest version if you use search capabilities within Business
Intelligence
5 Update the BI Accelerator to the newest available version For more information see BI
Accelerator [page 47]
6 Update the SAP GUI and Business Explorer (BI Add-On BW Add-On) on all remote client hosts
that are involved in the scenario
For more information see SAP GUI Family [page 51] and Business Explorer (BI Add-On BW Add-On)
[page 51]
BI Precalculation Service
1 Log on to the host as a user with administration rights
2 Install the Support Package of the BI Precalculation Service by executing the
xPreCalServerexe file
The welcome screen of the BI Precalculation Server setup wizard appears
The setup now checks the system for the prerequisites
3 Choose the option Update for updating the BI Precalculation service to the current patch level and
then Finish
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3660 CUSTOMER 2012-08-30
26 EP Core
261 Planning
Procedure
The following installable software units must be updated
EP Core
Software Components of EP Core
Component to Be Updated SP File Name Tool Used to Apply SP
PORTAL CORE SERVICES 702 EPBCltSPgt_ltPLgtSCA JSPM
PORTAL FRAMEWORK 702 EPBC2ltSPgt_ltPLgtSCA
PORTAL 702 EPPSERVltSPgt_ltPLgtSCA
PORTAL WEB DYNPRO 702 EPWDCltSPgt_ltPLgtSCA
UWL COLL PROCESS ENGINE 702 UWLJWFltSPgt_ltPLgtSCA
CAF EU 702 SAPEUltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
262 Preparation
Procedure
Backing Up the Portal Runtime Configuration
If you have made changes to the standard Portal Runtime configuration you have to make a backup
of the configuration before the update process For more information see SAP Note 1064468
263 Updating EP Core
Procedure
Apply the Support Package Stack to a system with usage type EP Core
For more information see Application Server Java and Java-Based Software Components [page 19]
264 Post-Installation Steps for EP Core
Procedure
Restoring the Portal Runtime Configuration
To make your changes to the standard Portal Runtime Configuration effective you have to restore
the backup of the configuration done before the update process For more information see SAP Note
1064468
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
26 EP Core
2012-08-30 CUSTOMER 3760
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
NOTE
In a distributed or high availability environment the ABAP Central Services Instance (ASCS)
runs on a dedicated host In this case JSPM does not support update of kernel binaries and
you need to update them manually Perform the update manually as described under Updating
SAP Kernel and SAP IGS in section Updating the Application Server ABAP and ABAP-Based Software
Components [page 16]
2 Import the Support Packages for the component SAP_BASIS into the ABAP stack using the ABAP
Support Package Manager (SPAM)
3 Import the remaining ABAP Support Packages with SPAM and in parallel apply the Java Support
Package Stack with JSPM
Proceed as described in Updating the Application Server ABAP and ABAP-Based Software Components [page
16] and Updating the Application Server Java and Java-Based Software Components [page 23]
24 Process Integration
241 Planning
Procedure
This section covers all the units of Process Integration that should be updated Particularly the following
units must always have the same Support Package level (the patch level can be different)
Integration Server
XI Adapter Engine
Partner Connectivity Kit
System with the Usage Type Process Integration
Software components of Integration Server
Components to Be Updated SP File Name Tool Used to Apply SP
Java stack
XI TOOLS 702 SAPXITOOLltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
ABAP stack
XI CONTENT SAP_BASIS 702 SAPBASISltSPgt_ltPLgtZIP File upload
XI CONTENT SAP_ABA 702 SAPABAltSPgt_ltPLgtZIP
SAP NetWeaver Application Server ABAP (see table Software components of Application Server ABAP [page 15])Note that update of the following software components of the ABAP system is not required SAP ABA 702 SAP BW 702 PI_BASIS 702
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 2960
J2EE Adapter Engine
If your implemented scenario includes a J2EE Adapter Engine then it must always be of the same
Support Package level as the Integration Server
Components of the J2EE Adapter Engine
Component to Be Updated SP File NameTool Used to Apply SP
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
J2SE Adapter Engine
The installation of the J2SE Adapter Engine depends on the implemented scenario
Components of the J2SE Adapter Engine
Component to Be Updated SP File Name Tool Used to Apply SP
XI CONNECTIVITY SE 702 SAPXICONSltSPgt_ltPLgtSCA ZIP tool (for example WinZip)
Partner Connectivity Kit
If your implemented scenario includes a Partner Connectivity Kit (PCK) then it must always be of the
same Support Package level as the Integration Server
Software components of Partner Connectivity Kit
Components to Be Updated SP File NameTool Used to Apply SP
XI PCK 702 SAPXIPCKltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of the Application Server Java [page 20])
System Landscape Directory (SLD)
The System Landscape Directory is required for the PI operations Although updating the SLD is not
necessarily required it is advisable to update the SLD server and the SAP Master Data Content within
it from time to time The update of the SLD includes
1 The system where the SLD is running
2 The SAP Master Data Content within this SLD
SAP GUI
See table Compatible SAP GUI Versions [page 51]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3060 CUSTOMER 2012-08-30
242 Updating Units of Process Integration
Procedure
Before you start the update perform the following steps
In the Runtime Workbench use Communication Channel Monitoring to stop all sender channels
for all adapter types on all your Adapter Engines
On the Integration Server use transaction SMQR and deregister all qRFC queues
System with the Usage Type Process Integration
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the XI instance is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system where the XI instance is running
For more information see Application Server Java and Java-Based Software Components [page 19]
System Landscape Directory (Optional)
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the SLD is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the entire Support Package Stack to the system where the SLD is running
For more information see Application Server Java and Java-Based Software Components [page 19]
J2EE Adapter Engine
Apply the Support Package Stack to the system where the Adapter Engine is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Partner Connectivity Kit
Apply the Support Package Stack to the system where the PCK is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Front End GUIs
Update the SAP GUI components if necessary
For more information see SAP GUI Family [page 51]
ABAP 700 Business System (Optional)
Apply the Support Packages for SAP NetWeaver Application Server ABAP (including SAP kernel and
the Support Package for SAP BASIS 700)
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 640 Business System (Optional)
Apply the Support Packages for SAP Web Application Server ABAP 640 (including SAP kernel and the
Support Package for SAP BASIS 640)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3160
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 620 Business System (Optional)
1 Update the SAP Kernel 620
2 Import the released Basis Support Packages for SAP Web AS 620 as well as the most recent Add-
On Support Package for APPINT 200_620 in the order described in SAP Note 439915
J2SE Adapter Engine (Optional)
NOTE
The XI Adapter Engine (J2SE) and all its adapters are provided for compatibility reasons only and
are not developed any further You have to use the XI Adapter Engine running on SAP NetWeaver
AS Java For more information see the Master Guide ndash SAP NetWeaver 70 available on SAP Service
Marketplace at httpservicesapcominstallNW70 Planning
1 Extract the SAPXICONSltSPgt_ltPLgtSCA (XI Connectivity SE 700) archive (ZIP format) to a temporary
directory
2 Save the old configuration files as described in the document Adapterpdf in directory
lttemp_directorygttech_adapterAdministrationDocumentation
3 Unpack the ZIP archive TechnicalAdapterssda to the installation directory of the XI Adapter
Engine (J2SE)
4 Restore the configuration files with restore_configuration
243 Post-Installation Steps
Procedure
Communication Channels and Queues
Restart all stopped sender channels and register all deregistered qRFC queues
XI Content
In the system with usage type PI import the XI content from the archives SAPBASISltSPgt_ltPLgtZIP
and SAPABAltSPgt_ltPLgtZIP as follows
1 Unpack the archives using a ZIP tool of your choice
2 Copy the corresponding export files (with file extension tpz) to the import directory ltINSTDIRgt
ltSAPSIDgtSYSglobalxirepository_serverimport
3 Start the Integration Builder (transaction SXMB_IFR)
4 Enter the Integration Repository by choosing Repository (Design)
5 Choose Tools Import design objects
6 Import the tpz files containing the XI content
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3260 CUSTOMER 2012-08-30
NOTE
For more information see SAP Note 836200
Role Generation on the Integration Server
On the Integration Server execute transaction SUPC (mass generation of roles) for all SAP_XI roles in
each of your clients to regenerate possibly changed roles
NOTE
Do not forget to make a user comparison for regenerated roles afterwards
Partner Connectivity Kit (Optional)
Perform the post-installation steps for PCK as described in SAP Note 746328
SAP Master Data within the SLD (Optional)
In the system where your SLD is running import the latest SLD content as described in SAP Note
669669
Receiver-Based EOIO Serialization in J2EE Adapter Engine (Optional)
The J2EE Adapter Engine can be switched to receiver-based EOIO serialization The switch can be
triggered on demand and is executed asynchronously It includes a database migration step during
which all EOIO processing in the Adapter Engine is disabled See SAP Note 973894 for details about how
to start the EOIO serialization migration
Service Metering (Optional)
Service metering gathers information about a service caller transfers it to the service provider and
counts on the service provisioning side how many times a service is called and by which service caller
Service metering is performed for the XI message protocol and the WS message protocol Service
metering is automatically enabled after applying a Support Package Stack By default only non-sensitive
data is transmitted to internal or external service providers in a compatible way
Service metering can be configured in PI in the Integration Engine on sender-side and in the Integration
Directory
Service metering can be configured in AS ABAP in transaction SOAMANAGER
Only if the service provider is allowed to receive more detailed information about the service caller set
the metering level to higher than the default
For more information see SAP Note 1239428
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3360
25 Business Intelligence
251 Planning
Procedure
Business Intelligence includes one or many of the following units that must be updated depending on
your implemented scenarios The usage types Business Intelligence (BI) and Business Intelligence Java
Components (BI-Java) must always have the same Support Package level
Business Intelligence
Software Components of Business Intelligence
Component to Be Updated SP File Name Tool Used to Apply SP
BI CONT ADDON 70x SAPK-70ltxgtltSPgtINBICONT SAINT
SAP NetWeaver Application Server ABAP (see table Software Components of Application Server ABAP [page 15])
NOTE
For information about the dependencies applying to BI Content Support Packages see SAP Note
653814 BI CONT 703 Support Packages are not part of the NetWeaver SP Stacks Updates can be
performed when applicable Alternatively BI CONT 704 Support Packages can be imported See
the BI Content release strategy in SAP Note 153967
Business Intelligence Java Components
BI Java Components
Component to Be Updated SP File NameTool Used to Apply SP
BI REPORTING AND PLANNING 702 BIREPPLANltSPgt_ltPLgtSCA JSPM
BI WEBDYNPRO ALV 702 BIWDALVltSPgt_ltPLgtSCA
BI INFORM BROADCASTING 702 BIIBCltSPgt_ltPLgtSCA
BI WEB APPLICATIONS 702 BIWEBAPPltSPgt_ltPLgtSCA
BI BASE SERVICES 702 BIBASESltSPgt_ltPLgtSCA
VISUAL COMPOSER BI KITS 702 VCKITBIltSPgt_ltPLgtSCA
Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
BI Precalculation Service
Components of the BI Precalculation Service
Component to Be Updated SP File Name Tool Used to Apply SP
BI Pre-calculation Service 700 xPreCalServerltSPgt_ltPLgtexe Installer
Search and Classification (TREX)
See table TREX Component [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3460 CUSTOMER 2012-08-30
BI Accelerator
The BI Accelerator is based on the TREX technology It is a special Linux 64-bit version of SAP NetWeaver
70 Search and Classification (TREX) which is delivered on preconfigured hardware
NOTE
You cannot use a TREX installation based on 32-bit architecture that is configured for searching
in metadata and documents for the BI Accelerator And vice versa a BI Accelerator box cannot
be used for searching in metadata and documents
If you want to use the search functionality as well as the BI Accelerator you require two separate
installations For more information see BI Accelerator [page 47]
Clients
Depending on your implemented scenarios you have to update SAP GUI Components and Business
Explorer (BI Add-OnBW Add-On)
NOTE
See SAP Note 889314 to determine when to use the BI Add-On and the BW Add-On
NOTE
As SAP GUI 640 is no longer supported BI Frontend Support Package 1800 resp patch 1801 is the
last Support Package resp patch based on SAP GUI 640 For more information see SAP Note
1231292 (Frontend Add-in Strategy 640710 GUI Version)
For more information about the new release strategy for the BI Frontend see SAP Note 1231363
(Changed Delivery Strategy for BI Frontend)
252 Preparation
Procedure
For the Support Packages of the most important Business Intelligence units so called SAPBINews
(SAPBWNews) Notes are created Read these Notes before updating Business Intelligence For SAP
NetWeaver 70 including enhancement package 2 SPS 12 these are the following
Business Intelligence ABAP SAP Note 1680996
Business Intelligence Java Components SAP Note 1726461
BI 70 Frontend Add-On for SAP GUI 710 SAP Note 1413032
BI 70 Frontend Add-On for SAP GUI 720 SAP Note 1630112
BI 70 Frontend Add-On for SAP GUI 730 SAP Note 1726739
For more information about BI Support Packages see SAP Community Network at http
scnsapcomcommunitydata-warehousingnetweaver-bw Related Resources SAP NW BW Support
Packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
2012-08-30 CUSTOMER 3560
253 Updating Units of Business Intelligence
Procedure
Business Intelligence
1 Update the SAP NetWeaver Application Server ABAP (with BI CONT 70x if necessary) with the
appropriate Support Packages
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
NOTE
When applying the component SAP BW 702 some generation errors might occur When
you start importing the BI Support Packages in transaction SPAM choose the menu path
Extras Ignore generation errors For more information see SAP Note 114134
2 Apply the Support Package Stack to the system with the usage type BI-Java
For more information see Application Server Java and Java-Based Software Components [page 19]
3 Update the BI Precalculation Service that is used in your scenario
4 Update the standalone engine Search and Classification (TREX) that is used in your scenario For more
information see Standalone Engine Search and Classification (TREX) [page 44]
NOTE
You have to update TREX to the newest version if you use search capabilities within Business
Intelligence
5 Update the BI Accelerator to the newest available version For more information see BI
Accelerator [page 47]
6 Update the SAP GUI and Business Explorer (BI Add-On BW Add-On) on all remote client hosts
that are involved in the scenario
For more information see SAP GUI Family [page 51] and Business Explorer (BI Add-On BW Add-On)
[page 51]
BI Precalculation Service
1 Log on to the host as a user with administration rights
2 Install the Support Package of the BI Precalculation Service by executing the
xPreCalServerexe file
The welcome screen of the BI Precalculation Server setup wizard appears
The setup now checks the system for the prerequisites
3 Choose the option Update for updating the BI Precalculation service to the current patch level and
then Finish
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3660 CUSTOMER 2012-08-30
26 EP Core
261 Planning
Procedure
The following installable software units must be updated
EP Core
Software Components of EP Core
Component to Be Updated SP File Name Tool Used to Apply SP
PORTAL CORE SERVICES 702 EPBCltSPgt_ltPLgtSCA JSPM
PORTAL FRAMEWORK 702 EPBC2ltSPgt_ltPLgtSCA
PORTAL 702 EPPSERVltSPgt_ltPLgtSCA
PORTAL WEB DYNPRO 702 EPWDCltSPgt_ltPLgtSCA
UWL COLL PROCESS ENGINE 702 UWLJWFltSPgt_ltPLgtSCA
CAF EU 702 SAPEUltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
262 Preparation
Procedure
Backing Up the Portal Runtime Configuration
If you have made changes to the standard Portal Runtime configuration you have to make a backup
of the configuration before the update process For more information see SAP Note 1064468
263 Updating EP Core
Procedure
Apply the Support Package Stack to a system with usage type EP Core
For more information see Application Server Java and Java-Based Software Components [page 19]
264 Post-Installation Steps for EP Core
Procedure
Restoring the Portal Runtime Configuration
To make your changes to the standard Portal Runtime Configuration effective you have to restore
the backup of the configuration done before the update process For more information see SAP Note
1064468
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
26 EP Core
2012-08-30 CUSTOMER 3760
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
J2EE Adapter Engine
If your implemented scenario includes a J2EE Adapter Engine then it must always be of the same
Support Package level as the Integration Server
Components of the J2EE Adapter Engine
Component to Be Updated SP File NameTool Used to Apply SP
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of Application Server Java [page 20])
J2SE Adapter Engine
The installation of the J2SE Adapter Engine depends on the implemented scenario
Components of the J2SE Adapter Engine
Component to Be Updated SP File Name Tool Used to Apply SP
XI CONNECTIVITY SE 702 SAPXICONSltSPgt_ltPLgtSCA ZIP tool (for example WinZip)
Partner Connectivity Kit
If your implemented scenario includes a Partner Connectivity Kit (PCK) then it must always be of the
same Support Package level as the Integration Server
Software components of Partner Connectivity Kit
Components to Be Updated SP File NameTool Used to Apply SP
XI PCK 702 SAPXIPCKltSPgt_ltPLgtSCA JSPM
XI ADAPTER FRAMEWORK 702 SAPXIAFltSPgt_ltPLgtSCA
XI ADAPTER FRAMEWORK CORE 702 SAPXIAFCltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software components of the Application Server Java [page 20])
System Landscape Directory (SLD)
The System Landscape Directory is required for the PI operations Although updating the SLD is not
necessarily required it is advisable to update the SLD server and the SAP Master Data Content within
it from time to time The update of the SLD includes
1 The system where the SLD is running
2 The SAP Master Data Content within this SLD
SAP GUI
See table Compatible SAP GUI Versions [page 51]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3060 CUSTOMER 2012-08-30
242 Updating Units of Process Integration
Procedure
Before you start the update perform the following steps
In the Runtime Workbench use Communication Channel Monitoring to stop all sender channels
for all adapter types on all your Adapter Engines
On the Integration Server use transaction SMQR and deregister all qRFC queues
System with the Usage Type Process Integration
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the XI instance is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system where the XI instance is running
For more information see Application Server Java and Java-Based Software Components [page 19]
System Landscape Directory (Optional)
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the SLD is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the entire Support Package Stack to the system where the SLD is running
For more information see Application Server Java and Java-Based Software Components [page 19]
J2EE Adapter Engine
Apply the Support Package Stack to the system where the Adapter Engine is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Partner Connectivity Kit
Apply the Support Package Stack to the system where the PCK is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Front End GUIs
Update the SAP GUI components if necessary
For more information see SAP GUI Family [page 51]
ABAP 700 Business System (Optional)
Apply the Support Packages for SAP NetWeaver Application Server ABAP (including SAP kernel and
the Support Package for SAP BASIS 700)
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 640 Business System (Optional)
Apply the Support Packages for SAP Web Application Server ABAP 640 (including SAP kernel and the
Support Package for SAP BASIS 640)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3160
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 620 Business System (Optional)
1 Update the SAP Kernel 620
2 Import the released Basis Support Packages for SAP Web AS 620 as well as the most recent Add-
On Support Package for APPINT 200_620 in the order described in SAP Note 439915
J2SE Adapter Engine (Optional)
NOTE
The XI Adapter Engine (J2SE) and all its adapters are provided for compatibility reasons only and
are not developed any further You have to use the XI Adapter Engine running on SAP NetWeaver
AS Java For more information see the Master Guide ndash SAP NetWeaver 70 available on SAP Service
Marketplace at httpservicesapcominstallNW70 Planning
1 Extract the SAPXICONSltSPgt_ltPLgtSCA (XI Connectivity SE 700) archive (ZIP format) to a temporary
directory
2 Save the old configuration files as described in the document Adapterpdf in directory
lttemp_directorygttech_adapterAdministrationDocumentation
3 Unpack the ZIP archive TechnicalAdapterssda to the installation directory of the XI Adapter
Engine (J2SE)
4 Restore the configuration files with restore_configuration
243 Post-Installation Steps
Procedure
Communication Channels and Queues
Restart all stopped sender channels and register all deregistered qRFC queues
XI Content
In the system with usage type PI import the XI content from the archives SAPBASISltSPgt_ltPLgtZIP
and SAPABAltSPgt_ltPLgtZIP as follows
1 Unpack the archives using a ZIP tool of your choice
2 Copy the corresponding export files (with file extension tpz) to the import directory ltINSTDIRgt
ltSAPSIDgtSYSglobalxirepository_serverimport
3 Start the Integration Builder (transaction SXMB_IFR)
4 Enter the Integration Repository by choosing Repository (Design)
5 Choose Tools Import design objects
6 Import the tpz files containing the XI content
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3260 CUSTOMER 2012-08-30
NOTE
For more information see SAP Note 836200
Role Generation on the Integration Server
On the Integration Server execute transaction SUPC (mass generation of roles) for all SAP_XI roles in
each of your clients to regenerate possibly changed roles
NOTE
Do not forget to make a user comparison for regenerated roles afterwards
Partner Connectivity Kit (Optional)
Perform the post-installation steps for PCK as described in SAP Note 746328
SAP Master Data within the SLD (Optional)
In the system where your SLD is running import the latest SLD content as described in SAP Note
669669
Receiver-Based EOIO Serialization in J2EE Adapter Engine (Optional)
The J2EE Adapter Engine can be switched to receiver-based EOIO serialization The switch can be
triggered on demand and is executed asynchronously It includes a database migration step during
which all EOIO processing in the Adapter Engine is disabled See SAP Note 973894 for details about how
to start the EOIO serialization migration
Service Metering (Optional)
Service metering gathers information about a service caller transfers it to the service provider and
counts on the service provisioning side how many times a service is called and by which service caller
Service metering is performed for the XI message protocol and the WS message protocol Service
metering is automatically enabled after applying a Support Package Stack By default only non-sensitive
data is transmitted to internal or external service providers in a compatible way
Service metering can be configured in PI in the Integration Engine on sender-side and in the Integration
Directory
Service metering can be configured in AS ABAP in transaction SOAMANAGER
Only if the service provider is allowed to receive more detailed information about the service caller set
the metering level to higher than the default
For more information see SAP Note 1239428
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3360
25 Business Intelligence
251 Planning
Procedure
Business Intelligence includes one or many of the following units that must be updated depending on
your implemented scenarios The usage types Business Intelligence (BI) and Business Intelligence Java
Components (BI-Java) must always have the same Support Package level
Business Intelligence
Software Components of Business Intelligence
Component to Be Updated SP File Name Tool Used to Apply SP
BI CONT ADDON 70x SAPK-70ltxgtltSPgtINBICONT SAINT
SAP NetWeaver Application Server ABAP (see table Software Components of Application Server ABAP [page 15])
NOTE
For information about the dependencies applying to BI Content Support Packages see SAP Note
653814 BI CONT 703 Support Packages are not part of the NetWeaver SP Stacks Updates can be
performed when applicable Alternatively BI CONT 704 Support Packages can be imported See
the BI Content release strategy in SAP Note 153967
Business Intelligence Java Components
BI Java Components
Component to Be Updated SP File NameTool Used to Apply SP
BI REPORTING AND PLANNING 702 BIREPPLANltSPgt_ltPLgtSCA JSPM
BI WEBDYNPRO ALV 702 BIWDALVltSPgt_ltPLgtSCA
BI INFORM BROADCASTING 702 BIIBCltSPgt_ltPLgtSCA
BI WEB APPLICATIONS 702 BIWEBAPPltSPgt_ltPLgtSCA
BI BASE SERVICES 702 BIBASESltSPgt_ltPLgtSCA
VISUAL COMPOSER BI KITS 702 VCKITBIltSPgt_ltPLgtSCA
Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
BI Precalculation Service
Components of the BI Precalculation Service
Component to Be Updated SP File Name Tool Used to Apply SP
BI Pre-calculation Service 700 xPreCalServerltSPgt_ltPLgtexe Installer
Search and Classification (TREX)
See table TREX Component [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3460 CUSTOMER 2012-08-30
BI Accelerator
The BI Accelerator is based on the TREX technology It is a special Linux 64-bit version of SAP NetWeaver
70 Search and Classification (TREX) which is delivered on preconfigured hardware
NOTE
You cannot use a TREX installation based on 32-bit architecture that is configured for searching
in metadata and documents for the BI Accelerator And vice versa a BI Accelerator box cannot
be used for searching in metadata and documents
If you want to use the search functionality as well as the BI Accelerator you require two separate
installations For more information see BI Accelerator [page 47]
Clients
Depending on your implemented scenarios you have to update SAP GUI Components and Business
Explorer (BI Add-OnBW Add-On)
NOTE
See SAP Note 889314 to determine when to use the BI Add-On and the BW Add-On
NOTE
As SAP GUI 640 is no longer supported BI Frontend Support Package 1800 resp patch 1801 is the
last Support Package resp patch based on SAP GUI 640 For more information see SAP Note
1231292 (Frontend Add-in Strategy 640710 GUI Version)
For more information about the new release strategy for the BI Frontend see SAP Note 1231363
(Changed Delivery Strategy for BI Frontend)
252 Preparation
Procedure
For the Support Packages of the most important Business Intelligence units so called SAPBINews
(SAPBWNews) Notes are created Read these Notes before updating Business Intelligence For SAP
NetWeaver 70 including enhancement package 2 SPS 12 these are the following
Business Intelligence ABAP SAP Note 1680996
Business Intelligence Java Components SAP Note 1726461
BI 70 Frontend Add-On for SAP GUI 710 SAP Note 1413032
BI 70 Frontend Add-On for SAP GUI 720 SAP Note 1630112
BI 70 Frontend Add-On for SAP GUI 730 SAP Note 1726739
For more information about BI Support Packages see SAP Community Network at http
scnsapcomcommunitydata-warehousingnetweaver-bw Related Resources SAP NW BW Support
Packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
2012-08-30 CUSTOMER 3560
253 Updating Units of Business Intelligence
Procedure
Business Intelligence
1 Update the SAP NetWeaver Application Server ABAP (with BI CONT 70x if necessary) with the
appropriate Support Packages
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
NOTE
When applying the component SAP BW 702 some generation errors might occur When
you start importing the BI Support Packages in transaction SPAM choose the menu path
Extras Ignore generation errors For more information see SAP Note 114134
2 Apply the Support Package Stack to the system with the usage type BI-Java
For more information see Application Server Java and Java-Based Software Components [page 19]
3 Update the BI Precalculation Service that is used in your scenario
4 Update the standalone engine Search and Classification (TREX) that is used in your scenario For more
information see Standalone Engine Search and Classification (TREX) [page 44]
NOTE
You have to update TREX to the newest version if you use search capabilities within Business
Intelligence
5 Update the BI Accelerator to the newest available version For more information see BI
Accelerator [page 47]
6 Update the SAP GUI and Business Explorer (BI Add-On BW Add-On) on all remote client hosts
that are involved in the scenario
For more information see SAP GUI Family [page 51] and Business Explorer (BI Add-On BW Add-On)
[page 51]
BI Precalculation Service
1 Log on to the host as a user with administration rights
2 Install the Support Package of the BI Precalculation Service by executing the
xPreCalServerexe file
The welcome screen of the BI Precalculation Server setup wizard appears
The setup now checks the system for the prerequisites
3 Choose the option Update for updating the BI Precalculation service to the current patch level and
then Finish
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3660 CUSTOMER 2012-08-30
26 EP Core
261 Planning
Procedure
The following installable software units must be updated
EP Core
Software Components of EP Core
Component to Be Updated SP File Name Tool Used to Apply SP
PORTAL CORE SERVICES 702 EPBCltSPgt_ltPLgtSCA JSPM
PORTAL FRAMEWORK 702 EPBC2ltSPgt_ltPLgtSCA
PORTAL 702 EPPSERVltSPgt_ltPLgtSCA
PORTAL WEB DYNPRO 702 EPWDCltSPgt_ltPLgtSCA
UWL COLL PROCESS ENGINE 702 UWLJWFltSPgt_ltPLgtSCA
CAF EU 702 SAPEUltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
262 Preparation
Procedure
Backing Up the Portal Runtime Configuration
If you have made changes to the standard Portal Runtime configuration you have to make a backup
of the configuration before the update process For more information see SAP Note 1064468
263 Updating EP Core
Procedure
Apply the Support Package Stack to a system with usage type EP Core
For more information see Application Server Java and Java-Based Software Components [page 19]
264 Post-Installation Steps for EP Core
Procedure
Restoring the Portal Runtime Configuration
To make your changes to the standard Portal Runtime Configuration effective you have to restore
the backup of the configuration done before the update process For more information see SAP Note
1064468
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
26 EP Core
2012-08-30 CUSTOMER 3760
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
242 Updating Units of Process Integration
Procedure
Before you start the update perform the following steps
In the Runtime Workbench use Communication Channel Monitoring to stop all sender channels
for all adapter types on all your Adapter Engines
On the Integration Server use transaction SMQR and deregister all qRFC queues
System with the Usage Type Process Integration
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the XI instance is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system where the XI instance is running
For more information see Application Server Java and Java-Based Software Components [page 19]
System Landscape Directory (Optional)
1 Update the SAP NetWeaver Application Server ABAP with the appropriate Support Packages where
the SLD is running
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the entire Support Package Stack to the system where the SLD is running
For more information see Application Server Java and Java-Based Software Components [page 19]
J2EE Adapter Engine
Apply the Support Package Stack to the system where the Adapter Engine is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Partner Connectivity Kit
Apply the Support Package Stack to the system where the PCK is running
For more information see Application Server Java and Java-Based Software Components [page 19]
Front End GUIs
Update the SAP GUI components if necessary
For more information see SAP GUI Family [page 51]
ABAP 700 Business System (Optional)
Apply the Support Packages for SAP NetWeaver Application Server ABAP (including SAP kernel and
the Support Package for SAP BASIS 700)
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 640 Business System (Optional)
Apply the Support Packages for SAP Web Application Server ABAP 640 (including SAP kernel and the
Support Package for SAP BASIS 640)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3160
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 620 Business System (Optional)
1 Update the SAP Kernel 620
2 Import the released Basis Support Packages for SAP Web AS 620 as well as the most recent Add-
On Support Package for APPINT 200_620 in the order described in SAP Note 439915
J2SE Adapter Engine (Optional)
NOTE
The XI Adapter Engine (J2SE) and all its adapters are provided for compatibility reasons only and
are not developed any further You have to use the XI Adapter Engine running on SAP NetWeaver
AS Java For more information see the Master Guide ndash SAP NetWeaver 70 available on SAP Service
Marketplace at httpservicesapcominstallNW70 Planning
1 Extract the SAPXICONSltSPgt_ltPLgtSCA (XI Connectivity SE 700) archive (ZIP format) to a temporary
directory
2 Save the old configuration files as described in the document Adapterpdf in directory
lttemp_directorygttech_adapterAdministrationDocumentation
3 Unpack the ZIP archive TechnicalAdapterssda to the installation directory of the XI Adapter
Engine (J2SE)
4 Restore the configuration files with restore_configuration
243 Post-Installation Steps
Procedure
Communication Channels and Queues
Restart all stopped sender channels and register all deregistered qRFC queues
XI Content
In the system with usage type PI import the XI content from the archives SAPBASISltSPgt_ltPLgtZIP
and SAPABAltSPgt_ltPLgtZIP as follows
1 Unpack the archives using a ZIP tool of your choice
2 Copy the corresponding export files (with file extension tpz) to the import directory ltINSTDIRgt
ltSAPSIDgtSYSglobalxirepository_serverimport
3 Start the Integration Builder (transaction SXMB_IFR)
4 Enter the Integration Repository by choosing Repository (Design)
5 Choose Tools Import design objects
6 Import the tpz files containing the XI content
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3260 CUSTOMER 2012-08-30
NOTE
For more information see SAP Note 836200
Role Generation on the Integration Server
On the Integration Server execute transaction SUPC (mass generation of roles) for all SAP_XI roles in
each of your clients to regenerate possibly changed roles
NOTE
Do not forget to make a user comparison for regenerated roles afterwards
Partner Connectivity Kit (Optional)
Perform the post-installation steps for PCK as described in SAP Note 746328
SAP Master Data within the SLD (Optional)
In the system where your SLD is running import the latest SLD content as described in SAP Note
669669
Receiver-Based EOIO Serialization in J2EE Adapter Engine (Optional)
The J2EE Adapter Engine can be switched to receiver-based EOIO serialization The switch can be
triggered on demand and is executed asynchronously It includes a database migration step during
which all EOIO processing in the Adapter Engine is disabled See SAP Note 973894 for details about how
to start the EOIO serialization migration
Service Metering (Optional)
Service metering gathers information about a service caller transfers it to the service provider and
counts on the service provisioning side how many times a service is called and by which service caller
Service metering is performed for the XI message protocol and the WS message protocol Service
metering is automatically enabled after applying a Support Package Stack By default only non-sensitive
data is transmitted to internal or external service providers in a compatible way
Service metering can be configured in PI in the Integration Engine on sender-side and in the Integration
Directory
Service metering can be configured in AS ABAP in transaction SOAMANAGER
Only if the service provider is allowed to receive more detailed information about the service caller set
the metering level to higher than the default
For more information see SAP Note 1239428
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3360
25 Business Intelligence
251 Planning
Procedure
Business Intelligence includes one or many of the following units that must be updated depending on
your implemented scenarios The usage types Business Intelligence (BI) and Business Intelligence Java
Components (BI-Java) must always have the same Support Package level
Business Intelligence
Software Components of Business Intelligence
Component to Be Updated SP File Name Tool Used to Apply SP
BI CONT ADDON 70x SAPK-70ltxgtltSPgtINBICONT SAINT
SAP NetWeaver Application Server ABAP (see table Software Components of Application Server ABAP [page 15])
NOTE
For information about the dependencies applying to BI Content Support Packages see SAP Note
653814 BI CONT 703 Support Packages are not part of the NetWeaver SP Stacks Updates can be
performed when applicable Alternatively BI CONT 704 Support Packages can be imported See
the BI Content release strategy in SAP Note 153967
Business Intelligence Java Components
BI Java Components
Component to Be Updated SP File NameTool Used to Apply SP
BI REPORTING AND PLANNING 702 BIREPPLANltSPgt_ltPLgtSCA JSPM
BI WEBDYNPRO ALV 702 BIWDALVltSPgt_ltPLgtSCA
BI INFORM BROADCASTING 702 BIIBCltSPgt_ltPLgtSCA
BI WEB APPLICATIONS 702 BIWEBAPPltSPgt_ltPLgtSCA
BI BASE SERVICES 702 BIBASESltSPgt_ltPLgtSCA
VISUAL COMPOSER BI KITS 702 VCKITBIltSPgt_ltPLgtSCA
Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
BI Precalculation Service
Components of the BI Precalculation Service
Component to Be Updated SP File Name Tool Used to Apply SP
BI Pre-calculation Service 700 xPreCalServerltSPgt_ltPLgtexe Installer
Search and Classification (TREX)
See table TREX Component [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3460 CUSTOMER 2012-08-30
BI Accelerator
The BI Accelerator is based on the TREX technology It is a special Linux 64-bit version of SAP NetWeaver
70 Search and Classification (TREX) which is delivered on preconfigured hardware
NOTE
You cannot use a TREX installation based on 32-bit architecture that is configured for searching
in metadata and documents for the BI Accelerator And vice versa a BI Accelerator box cannot
be used for searching in metadata and documents
If you want to use the search functionality as well as the BI Accelerator you require two separate
installations For more information see BI Accelerator [page 47]
Clients
Depending on your implemented scenarios you have to update SAP GUI Components and Business
Explorer (BI Add-OnBW Add-On)
NOTE
See SAP Note 889314 to determine when to use the BI Add-On and the BW Add-On
NOTE
As SAP GUI 640 is no longer supported BI Frontend Support Package 1800 resp patch 1801 is the
last Support Package resp patch based on SAP GUI 640 For more information see SAP Note
1231292 (Frontend Add-in Strategy 640710 GUI Version)
For more information about the new release strategy for the BI Frontend see SAP Note 1231363
(Changed Delivery Strategy for BI Frontend)
252 Preparation
Procedure
For the Support Packages of the most important Business Intelligence units so called SAPBINews
(SAPBWNews) Notes are created Read these Notes before updating Business Intelligence For SAP
NetWeaver 70 including enhancement package 2 SPS 12 these are the following
Business Intelligence ABAP SAP Note 1680996
Business Intelligence Java Components SAP Note 1726461
BI 70 Frontend Add-On for SAP GUI 710 SAP Note 1413032
BI 70 Frontend Add-On for SAP GUI 720 SAP Note 1630112
BI 70 Frontend Add-On for SAP GUI 730 SAP Note 1726739
For more information about BI Support Packages see SAP Community Network at http
scnsapcomcommunitydata-warehousingnetweaver-bw Related Resources SAP NW BW Support
Packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
2012-08-30 CUSTOMER 3560
253 Updating Units of Business Intelligence
Procedure
Business Intelligence
1 Update the SAP NetWeaver Application Server ABAP (with BI CONT 70x if necessary) with the
appropriate Support Packages
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
NOTE
When applying the component SAP BW 702 some generation errors might occur When
you start importing the BI Support Packages in transaction SPAM choose the menu path
Extras Ignore generation errors For more information see SAP Note 114134
2 Apply the Support Package Stack to the system with the usage type BI-Java
For more information see Application Server Java and Java-Based Software Components [page 19]
3 Update the BI Precalculation Service that is used in your scenario
4 Update the standalone engine Search and Classification (TREX) that is used in your scenario For more
information see Standalone Engine Search and Classification (TREX) [page 44]
NOTE
You have to update TREX to the newest version if you use search capabilities within Business
Intelligence
5 Update the BI Accelerator to the newest available version For more information see BI
Accelerator [page 47]
6 Update the SAP GUI and Business Explorer (BI Add-On BW Add-On) on all remote client hosts
that are involved in the scenario
For more information see SAP GUI Family [page 51] and Business Explorer (BI Add-On BW Add-On)
[page 51]
BI Precalculation Service
1 Log on to the host as a user with administration rights
2 Install the Support Package of the BI Precalculation Service by executing the
xPreCalServerexe file
The welcome screen of the BI Precalculation Server setup wizard appears
The setup now checks the system for the prerequisites
3 Choose the option Update for updating the BI Precalculation service to the current patch level and
then Finish
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3660 CUSTOMER 2012-08-30
26 EP Core
261 Planning
Procedure
The following installable software units must be updated
EP Core
Software Components of EP Core
Component to Be Updated SP File Name Tool Used to Apply SP
PORTAL CORE SERVICES 702 EPBCltSPgt_ltPLgtSCA JSPM
PORTAL FRAMEWORK 702 EPBC2ltSPgt_ltPLgtSCA
PORTAL 702 EPPSERVltSPgt_ltPLgtSCA
PORTAL WEB DYNPRO 702 EPWDCltSPgt_ltPLgtSCA
UWL COLL PROCESS ENGINE 702 UWLJWFltSPgt_ltPLgtSCA
CAF EU 702 SAPEUltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
262 Preparation
Procedure
Backing Up the Portal Runtime Configuration
If you have made changes to the standard Portal Runtime configuration you have to make a backup
of the configuration before the update process For more information see SAP Note 1064468
263 Updating EP Core
Procedure
Apply the Support Package Stack to a system with usage type EP Core
For more information see Application Server Java and Java-Based Software Components [page 19]
264 Post-Installation Steps for EP Core
Procedure
Restoring the Portal Runtime Configuration
To make your changes to the standard Portal Runtime Configuration effective you have to restore
the backup of the configuration done before the update process For more information see SAP Note
1064468
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
26 EP Core
2012-08-30 CUSTOMER 3760
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
For more information see Applicaion Server ABAP and ABAP-Based Software Components [page 15]
ABAP 620 Business System (Optional)
1 Update the SAP Kernel 620
2 Import the released Basis Support Packages for SAP Web AS 620 as well as the most recent Add-
On Support Package for APPINT 200_620 in the order described in SAP Note 439915
J2SE Adapter Engine (Optional)
NOTE
The XI Adapter Engine (J2SE) and all its adapters are provided for compatibility reasons only and
are not developed any further You have to use the XI Adapter Engine running on SAP NetWeaver
AS Java For more information see the Master Guide ndash SAP NetWeaver 70 available on SAP Service
Marketplace at httpservicesapcominstallNW70 Planning
1 Extract the SAPXICONSltSPgt_ltPLgtSCA (XI Connectivity SE 700) archive (ZIP format) to a temporary
directory
2 Save the old configuration files as described in the document Adapterpdf in directory
lttemp_directorygttech_adapterAdministrationDocumentation
3 Unpack the ZIP archive TechnicalAdapterssda to the installation directory of the XI Adapter
Engine (J2SE)
4 Restore the configuration files with restore_configuration
243 Post-Installation Steps
Procedure
Communication Channels and Queues
Restart all stopped sender channels and register all deregistered qRFC queues
XI Content
In the system with usage type PI import the XI content from the archives SAPBASISltSPgt_ltPLgtZIP
and SAPABAltSPgt_ltPLgtZIP as follows
1 Unpack the archives using a ZIP tool of your choice
2 Copy the corresponding export files (with file extension tpz) to the import directory ltINSTDIRgt
ltSAPSIDgtSYSglobalxirepository_serverimport
3 Start the Integration Builder (transaction SXMB_IFR)
4 Enter the Integration Repository by choosing Repository (Design)
5 Choose Tools Import design objects
6 Import the tpz files containing the XI content
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
3260 CUSTOMER 2012-08-30
NOTE
For more information see SAP Note 836200
Role Generation on the Integration Server
On the Integration Server execute transaction SUPC (mass generation of roles) for all SAP_XI roles in
each of your clients to regenerate possibly changed roles
NOTE
Do not forget to make a user comparison for regenerated roles afterwards
Partner Connectivity Kit (Optional)
Perform the post-installation steps for PCK as described in SAP Note 746328
SAP Master Data within the SLD (Optional)
In the system where your SLD is running import the latest SLD content as described in SAP Note
669669
Receiver-Based EOIO Serialization in J2EE Adapter Engine (Optional)
The J2EE Adapter Engine can be switched to receiver-based EOIO serialization The switch can be
triggered on demand and is executed asynchronously It includes a database migration step during
which all EOIO processing in the Adapter Engine is disabled See SAP Note 973894 for details about how
to start the EOIO serialization migration
Service Metering (Optional)
Service metering gathers information about a service caller transfers it to the service provider and
counts on the service provisioning side how many times a service is called and by which service caller
Service metering is performed for the XI message protocol and the WS message protocol Service
metering is automatically enabled after applying a Support Package Stack By default only non-sensitive
data is transmitted to internal or external service providers in a compatible way
Service metering can be configured in PI in the Integration Engine on sender-side and in the Integration
Directory
Service metering can be configured in AS ABAP in transaction SOAMANAGER
Only if the service provider is allowed to receive more detailed information about the service caller set
the metering level to higher than the default
For more information see SAP Note 1239428
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3360
25 Business Intelligence
251 Planning
Procedure
Business Intelligence includes one or many of the following units that must be updated depending on
your implemented scenarios The usage types Business Intelligence (BI) and Business Intelligence Java
Components (BI-Java) must always have the same Support Package level
Business Intelligence
Software Components of Business Intelligence
Component to Be Updated SP File Name Tool Used to Apply SP
BI CONT ADDON 70x SAPK-70ltxgtltSPgtINBICONT SAINT
SAP NetWeaver Application Server ABAP (see table Software Components of Application Server ABAP [page 15])
NOTE
For information about the dependencies applying to BI Content Support Packages see SAP Note
653814 BI CONT 703 Support Packages are not part of the NetWeaver SP Stacks Updates can be
performed when applicable Alternatively BI CONT 704 Support Packages can be imported See
the BI Content release strategy in SAP Note 153967
Business Intelligence Java Components
BI Java Components
Component to Be Updated SP File NameTool Used to Apply SP
BI REPORTING AND PLANNING 702 BIREPPLANltSPgt_ltPLgtSCA JSPM
BI WEBDYNPRO ALV 702 BIWDALVltSPgt_ltPLgtSCA
BI INFORM BROADCASTING 702 BIIBCltSPgt_ltPLgtSCA
BI WEB APPLICATIONS 702 BIWEBAPPltSPgt_ltPLgtSCA
BI BASE SERVICES 702 BIBASESltSPgt_ltPLgtSCA
VISUAL COMPOSER BI KITS 702 VCKITBIltSPgt_ltPLgtSCA
Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
BI Precalculation Service
Components of the BI Precalculation Service
Component to Be Updated SP File Name Tool Used to Apply SP
BI Pre-calculation Service 700 xPreCalServerltSPgt_ltPLgtexe Installer
Search and Classification (TREX)
See table TREX Component [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3460 CUSTOMER 2012-08-30
BI Accelerator
The BI Accelerator is based on the TREX technology It is a special Linux 64-bit version of SAP NetWeaver
70 Search and Classification (TREX) which is delivered on preconfigured hardware
NOTE
You cannot use a TREX installation based on 32-bit architecture that is configured for searching
in metadata and documents for the BI Accelerator And vice versa a BI Accelerator box cannot
be used for searching in metadata and documents
If you want to use the search functionality as well as the BI Accelerator you require two separate
installations For more information see BI Accelerator [page 47]
Clients
Depending on your implemented scenarios you have to update SAP GUI Components and Business
Explorer (BI Add-OnBW Add-On)
NOTE
See SAP Note 889314 to determine when to use the BI Add-On and the BW Add-On
NOTE
As SAP GUI 640 is no longer supported BI Frontend Support Package 1800 resp patch 1801 is the
last Support Package resp patch based on SAP GUI 640 For more information see SAP Note
1231292 (Frontend Add-in Strategy 640710 GUI Version)
For more information about the new release strategy for the BI Frontend see SAP Note 1231363
(Changed Delivery Strategy for BI Frontend)
252 Preparation
Procedure
For the Support Packages of the most important Business Intelligence units so called SAPBINews
(SAPBWNews) Notes are created Read these Notes before updating Business Intelligence For SAP
NetWeaver 70 including enhancement package 2 SPS 12 these are the following
Business Intelligence ABAP SAP Note 1680996
Business Intelligence Java Components SAP Note 1726461
BI 70 Frontend Add-On for SAP GUI 710 SAP Note 1413032
BI 70 Frontend Add-On for SAP GUI 720 SAP Note 1630112
BI 70 Frontend Add-On for SAP GUI 730 SAP Note 1726739
For more information about BI Support Packages see SAP Community Network at http
scnsapcomcommunitydata-warehousingnetweaver-bw Related Resources SAP NW BW Support
Packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
2012-08-30 CUSTOMER 3560
253 Updating Units of Business Intelligence
Procedure
Business Intelligence
1 Update the SAP NetWeaver Application Server ABAP (with BI CONT 70x if necessary) with the
appropriate Support Packages
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
NOTE
When applying the component SAP BW 702 some generation errors might occur When
you start importing the BI Support Packages in transaction SPAM choose the menu path
Extras Ignore generation errors For more information see SAP Note 114134
2 Apply the Support Package Stack to the system with the usage type BI-Java
For more information see Application Server Java and Java-Based Software Components [page 19]
3 Update the BI Precalculation Service that is used in your scenario
4 Update the standalone engine Search and Classification (TREX) that is used in your scenario For more
information see Standalone Engine Search and Classification (TREX) [page 44]
NOTE
You have to update TREX to the newest version if you use search capabilities within Business
Intelligence
5 Update the BI Accelerator to the newest available version For more information see BI
Accelerator [page 47]
6 Update the SAP GUI and Business Explorer (BI Add-On BW Add-On) on all remote client hosts
that are involved in the scenario
For more information see SAP GUI Family [page 51] and Business Explorer (BI Add-On BW Add-On)
[page 51]
BI Precalculation Service
1 Log on to the host as a user with administration rights
2 Install the Support Package of the BI Precalculation Service by executing the
xPreCalServerexe file
The welcome screen of the BI Precalculation Server setup wizard appears
The setup now checks the system for the prerequisites
3 Choose the option Update for updating the BI Precalculation service to the current patch level and
then Finish
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3660 CUSTOMER 2012-08-30
26 EP Core
261 Planning
Procedure
The following installable software units must be updated
EP Core
Software Components of EP Core
Component to Be Updated SP File Name Tool Used to Apply SP
PORTAL CORE SERVICES 702 EPBCltSPgt_ltPLgtSCA JSPM
PORTAL FRAMEWORK 702 EPBC2ltSPgt_ltPLgtSCA
PORTAL 702 EPPSERVltSPgt_ltPLgtSCA
PORTAL WEB DYNPRO 702 EPWDCltSPgt_ltPLgtSCA
UWL COLL PROCESS ENGINE 702 UWLJWFltSPgt_ltPLgtSCA
CAF EU 702 SAPEUltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
262 Preparation
Procedure
Backing Up the Portal Runtime Configuration
If you have made changes to the standard Portal Runtime configuration you have to make a backup
of the configuration before the update process For more information see SAP Note 1064468
263 Updating EP Core
Procedure
Apply the Support Package Stack to a system with usage type EP Core
For more information see Application Server Java and Java-Based Software Components [page 19]
264 Post-Installation Steps for EP Core
Procedure
Restoring the Portal Runtime Configuration
To make your changes to the standard Portal Runtime Configuration effective you have to restore
the backup of the configuration done before the update process For more information see SAP Note
1064468
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
26 EP Core
2012-08-30 CUSTOMER 3760
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
NOTE
For more information see SAP Note 836200
Role Generation on the Integration Server
On the Integration Server execute transaction SUPC (mass generation of roles) for all SAP_XI roles in
each of your clients to regenerate possibly changed roles
NOTE
Do not forget to make a user comparison for regenerated roles afterwards
Partner Connectivity Kit (Optional)
Perform the post-installation steps for PCK as described in SAP Note 746328
SAP Master Data within the SLD (Optional)
In the system where your SLD is running import the latest SLD content as described in SAP Note
669669
Receiver-Based EOIO Serialization in J2EE Adapter Engine (Optional)
The J2EE Adapter Engine can be switched to receiver-based EOIO serialization The switch can be
triggered on demand and is executed asynchronously It includes a database migration step during
which all EOIO processing in the Adapter Engine is disabled See SAP Note 973894 for details about how
to start the EOIO serialization migration
Service Metering (Optional)
Service metering gathers information about a service caller transfers it to the service provider and
counts on the service provisioning side how many times a service is called and by which service caller
Service metering is performed for the XI message protocol and the WS message protocol Service
metering is automatically enabled after applying a Support Package Stack By default only non-sensitive
data is transmitted to internal or external service providers in a compatible way
Service metering can be configured in PI in the Integration Engine on sender-side and in the Integration
Directory
Service metering can be configured in AS ABAP in transaction SOAMANAGER
Only if the service provider is allowed to receive more detailed information about the service caller set
the metering level to higher than the default
For more information see SAP Note 1239428
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
24 Process Integration
2012-08-30 CUSTOMER 3360
25 Business Intelligence
251 Planning
Procedure
Business Intelligence includes one or many of the following units that must be updated depending on
your implemented scenarios The usage types Business Intelligence (BI) and Business Intelligence Java
Components (BI-Java) must always have the same Support Package level
Business Intelligence
Software Components of Business Intelligence
Component to Be Updated SP File Name Tool Used to Apply SP
BI CONT ADDON 70x SAPK-70ltxgtltSPgtINBICONT SAINT
SAP NetWeaver Application Server ABAP (see table Software Components of Application Server ABAP [page 15])
NOTE
For information about the dependencies applying to BI Content Support Packages see SAP Note
653814 BI CONT 703 Support Packages are not part of the NetWeaver SP Stacks Updates can be
performed when applicable Alternatively BI CONT 704 Support Packages can be imported See
the BI Content release strategy in SAP Note 153967
Business Intelligence Java Components
BI Java Components
Component to Be Updated SP File NameTool Used to Apply SP
BI REPORTING AND PLANNING 702 BIREPPLANltSPgt_ltPLgtSCA JSPM
BI WEBDYNPRO ALV 702 BIWDALVltSPgt_ltPLgtSCA
BI INFORM BROADCASTING 702 BIIBCltSPgt_ltPLgtSCA
BI WEB APPLICATIONS 702 BIWEBAPPltSPgt_ltPLgtSCA
BI BASE SERVICES 702 BIBASESltSPgt_ltPLgtSCA
VISUAL COMPOSER BI KITS 702 VCKITBIltSPgt_ltPLgtSCA
Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
BI Precalculation Service
Components of the BI Precalculation Service
Component to Be Updated SP File Name Tool Used to Apply SP
BI Pre-calculation Service 700 xPreCalServerltSPgt_ltPLgtexe Installer
Search and Classification (TREX)
See table TREX Component [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3460 CUSTOMER 2012-08-30
BI Accelerator
The BI Accelerator is based on the TREX technology It is a special Linux 64-bit version of SAP NetWeaver
70 Search and Classification (TREX) which is delivered on preconfigured hardware
NOTE
You cannot use a TREX installation based on 32-bit architecture that is configured for searching
in metadata and documents for the BI Accelerator And vice versa a BI Accelerator box cannot
be used for searching in metadata and documents
If you want to use the search functionality as well as the BI Accelerator you require two separate
installations For more information see BI Accelerator [page 47]
Clients
Depending on your implemented scenarios you have to update SAP GUI Components and Business
Explorer (BI Add-OnBW Add-On)
NOTE
See SAP Note 889314 to determine when to use the BI Add-On and the BW Add-On
NOTE
As SAP GUI 640 is no longer supported BI Frontend Support Package 1800 resp patch 1801 is the
last Support Package resp patch based on SAP GUI 640 For more information see SAP Note
1231292 (Frontend Add-in Strategy 640710 GUI Version)
For more information about the new release strategy for the BI Frontend see SAP Note 1231363
(Changed Delivery Strategy for BI Frontend)
252 Preparation
Procedure
For the Support Packages of the most important Business Intelligence units so called SAPBINews
(SAPBWNews) Notes are created Read these Notes before updating Business Intelligence For SAP
NetWeaver 70 including enhancement package 2 SPS 12 these are the following
Business Intelligence ABAP SAP Note 1680996
Business Intelligence Java Components SAP Note 1726461
BI 70 Frontend Add-On for SAP GUI 710 SAP Note 1413032
BI 70 Frontend Add-On for SAP GUI 720 SAP Note 1630112
BI 70 Frontend Add-On for SAP GUI 730 SAP Note 1726739
For more information about BI Support Packages see SAP Community Network at http
scnsapcomcommunitydata-warehousingnetweaver-bw Related Resources SAP NW BW Support
Packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
2012-08-30 CUSTOMER 3560
253 Updating Units of Business Intelligence
Procedure
Business Intelligence
1 Update the SAP NetWeaver Application Server ABAP (with BI CONT 70x if necessary) with the
appropriate Support Packages
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
NOTE
When applying the component SAP BW 702 some generation errors might occur When
you start importing the BI Support Packages in transaction SPAM choose the menu path
Extras Ignore generation errors For more information see SAP Note 114134
2 Apply the Support Package Stack to the system with the usage type BI-Java
For more information see Application Server Java and Java-Based Software Components [page 19]
3 Update the BI Precalculation Service that is used in your scenario
4 Update the standalone engine Search and Classification (TREX) that is used in your scenario For more
information see Standalone Engine Search and Classification (TREX) [page 44]
NOTE
You have to update TREX to the newest version if you use search capabilities within Business
Intelligence
5 Update the BI Accelerator to the newest available version For more information see BI
Accelerator [page 47]
6 Update the SAP GUI and Business Explorer (BI Add-On BW Add-On) on all remote client hosts
that are involved in the scenario
For more information see SAP GUI Family [page 51] and Business Explorer (BI Add-On BW Add-On)
[page 51]
BI Precalculation Service
1 Log on to the host as a user with administration rights
2 Install the Support Package of the BI Precalculation Service by executing the
xPreCalServerexe file
The welcome screen of the BI Precalculation Server setup wizard appears
The setup now checks the system for the prerequisites
3 Choose the option Update for updating the BI Precalculation service to the current patch level and
then Finish
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3660 CUSTOMER 2012-08-30
26 EP Core
261 Planning
Procedure
The following installable software units must be updated
EP Core
Software Components of EP Core
Component to Be Updated SP File Name Tool Used to Apply SP
PORTAL CORE SERVICES 702 EPBCltSPgt_ltPLgtSCA JSPM
PORTAL FRAMEWORK 702 EPBC2ltSPgt_ltPLgtSCA
PORTAL 702 EPPSERVltSPgt_ltPLgtSCA
PORTAL WEB DYNPRO 702 EPWDCltSPgt_ltPLgtSCA
UWL COLL PROCESS ENGINE 702 UWLJWFltSPgt_ltPLgtSCA
CAF EU 702 SAPEUltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
262 Preparation
Procedure
Backing Up the Portal Runtime Configuration
If you have made changes to the standard Portal Runtime configuration you have to make a backup
of the configuration before the update process For more information see SAP Note 1064468
263 Updating EP Core
Procedure
Apply the Support Package Stack to a system with usage type EP Core
For more information see Application Server Java and Java-Based Software Components [page 19]
264 Post-Installation Steps for EP Core
Procedure
Restoring the Portal Runtime Configuration
To make your changes to the standard Portal Runtime Configuration effective you have to restore
the backup of the configuration done before the update process For more information see SAP Note
1064468
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
26 EP Core
2012-08-30 CUSTOMER 3760
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
25 Business Intelligence
251 Planning
Procedure
Business Intelligence includes one or many of the following units that must be updated depending on
your implemented scenarios The usage types Business Intelligence (BI) and Business Intelligence Java
Components (BI-Java) must always have the same Support Package level
Business Intelligence
Software Components of Business Intelligence
Component to Be Updated SP File Name Tool Used to Apply SP
BI CONT ADDON 70x SAPK-70ltxgtltSPgtINBICONT SAINT
SAP NetWeaver Application Server ABAP (see table Software Components of Application Server ABAP [page 15])
NOTE
For information about the dependencies applying to BI Content Support Packages see SAP Note
653814 BI CONT 703 Support Packages are not part of the NetWeaver SP Stacks Updates can be
performed when applicable Alternatively BI CONT 704 Support Packages can be imported See
the BI Content release strategy in SAP Note 153967
Business Intelligence Java Components
BI Java Components
Component to Be Updated SP File NameTool Used to Apply SP
BI REPORTING AND PLANNING 702 BIREPPLANltSPgt_ltPLgtSCA JSPM
BI WEBDYNPRO ALV 702 BIWDALVltSPgt_ltPLgtSCA
BI INFORM BROADCASTING 702 BIIBCltSPgt_ltPLgtSCA
BI WEB APPLICATIONS 702 BIWEBAPPltSPgt_ltPLgtSCA
BI BASE SERVICES 702 BIBASESltSPgt_ltPLgtSCA
VISUAL COMPOSER BI KITS 702 VCKITBIltSPgt_ltPLgtSCA
Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
BI Precalculation Service
Components of the BI Precalculation Service
Component to Be Updated SP File Name Tool Used to Apply SP
BI Pre-calculation Service 700 xPreCalServerltSPgt_ltPLgtexe Installer
Search and Classification (TREX)
See table TREX Component [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3460 CUSTOMER 2012-08-30
BI Accelerator
The BI Accelerator is based on the TREX technology It is a special Linux 64-bit version of SAP NetWeaver
70 Search and Classification (TREX) which is delivered on preconfigured hardware
NOTE
You cannot use a TREX installation based on 32-bit architecture that is configured for searching
in metadata and documents for the BI Accelerator And vice versa a BI Accelerator box cannot
be used for searching in metadata and documents
If you want to use the search functionality as well as the BI Accelerator you require two separate
installations For more information see BI Accelerator [page 47]
Clients
Depending on your implemented scenarios you have to update SAP GUI Components and Business
Explorer (BI Add-OnBW Add-On)
NOTE
See SAP Note 889314 to determine when to use the BI Add-On and the BW Add-On
NOTE
As SAP GUI 640 is no longer supported BI Frontend Support Package 1800 resp patch 1801 is the
last Support Package resp patch based on SAP GUI 640 For more information see SAP Note
1231292 (Frontend Add-in Strategy 640710 GUI Version)
For more information about the new release strategy for the BI Frontend see SAP Note 1231363
(Changed Delivery Strategy for BI Frontend)
252 Preparation
Procedure
For the Support Packages of the most important Business Intelligence units so called SAPBINews
(SAPBWNews) Notes are created Read these Notes before updating Business Intelligence For SAP
NetWeaver 70 including enhancement package 2 SPS 12 these are the following
Business Intelligence ABAP SAP Note 1680996
Business Intelligence Java Components SAP Note 1726461
BI 70 Frontend Add-On for SAP GUI 710 SAP Note 1413032
BI 70 Frontend Add-On for SAP GUI 720 SAP Note 1630112
BI 70 Frontend Add-On for SAP GUI 730 SAP Note 1726739
For more information about BI Support Packages see SAP Community Network at http
scnsapcomcommunitydata-warehousingnetweaver-bw Related Resources SAP NW BW Support
Packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
2012-08-30 CUSTOMER 3560
253 Updating Units of Business Intelligence
Procedure
Business Intelligence
1 Update the SAP NetWeaver Application Server ABAP (with BI CONT 70x if necessary) with the
appropriate Support Packages
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
NOTE
When applying the component SAP BW 702 some generation errors might occur When
you start importing the BI Support Packages in transaction SPAM choose the menu path
Extras Ignore generation errors For more information see SAP Note 114134
2 Apply the Support Package Stack to the system with the usage type BI-Java
For more information see Application Server Java and Java-Based Software Components [page 19]
3 Update the BI Precalculation Service that is used in your scenario
4 Update the standalone engine Search and Classification (TREX) that is used in your scenario For more
information see Standalone Engine Search and Classification (TREX) [page 44]
NOTE
You have to update TREX to the newest version if you use search capabilities within Business
Intelligence
5 Update the BI Accelerator to the newest available version For more information see BI
Accelerator [page 47]
6 Update the SAP GUI and Business Explorer (BI Add-On BW Add-On) on all remote client hosts
that are involved in the scenario
For more information see SAP GUI Family [page 51] and Business Explorer (BI Add-On BW Add-On)
[page 51]
BI Precalculation Service
1 Log on to the host as a user with administration rights
2 Install the Support Package of the BI Precalculation Service by executing the
xPreCalServerexe file
The welcome screen of the BI Precalculation Server setup wizard appears
The setup now checks the system for the prerequisites
3 Choose the option Update for updating the BI Precalculation service to the current patch level and
then Finish
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3660 CUSTOMER 2012-08-30
26 EP Core
261 Planning
Procedure
The following installable software units must be updated
EP Core
Software Components of EP Core
Component to Be Updated SP File Name Tool Used to Apply SP
PORTAL CORE SERVICES 702 EPBCltSPgt_ltPLgtSCA JSPM
PORTAL FRAMEWORK 702 EPBC2ltSPgt_ltPLgtSCA
PORTAL 702 EPPSERVltSPgt_ltPLgtSCA
PORTAL WEB DYNPRO 702 EPWDCltSPgt_ltPLgtSCA
UWL COLL PROCESS ENGINE 702 UWLJWFltSPgt_ltPLgtSCA
CAF EU 702 SAPEUltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
262 Preparation
Procedure
Backing Up the Portal Runtime Configuration
If you have made changes to the standard Portal Runtime configuration you have to make a backup
of the configuration before the update process For more information see SAP Note 1064468
263 Updating EP Core
Procedure
Apply the Support Package Stack to a system with usage type EP Core
For more information see Application Server Java and Java-Based Software Components [page 19]
264 Post-Installation Steps for EP Core
Procedure
Restoring the Portal Runtime Configuration
To make your changes to the standard Portal Runtime Configuration effective you have to restore
the backup of the configuration done before the update process For more information see SAP Note
1064468
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
26 EP Core
2012-08-30 CUSTOMER 3760
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
BI Accelerator
The BI Accelerator is based on the TREX technology It is a special Linux 64-bit version of SAP NetWeaver
70 Search and Classification (TREX) which is delivered on preconfigured hardware
NOTE
You cannot use a TREX installation based on 32-bit architecture that is configured for searching
in metadata and documents for the BI Accelerator And vice versa a BI Accelerator box cannot
be used for searching in metadata and documents
If you want to use the search functionality as well as the BI Accelerator you require two separate
installations For more information see BI Accelerator [page 47]
Clients
Depending on your implemented scenarios you have to update SAP GUI Components and Business
Explorer (BI Add-OnBW Add-On)
NOTE
See SAP Note 889314 to determine when to use the BI Add-On and the BW Add-On
NOTE
As SAP GUI 640 is no longer supported BI Frontend Support Package 1800 resp patch 1801 is the
last Support Package resp patch based on SAP GUI 640 For more information see SAP Note
1231292 (Frontend Add-in Strategy 640710 GUI Version)
For more information about the new release strategy for the BI Frontend see SAP Note 1231363
(Changed Delivery Strategy for BI Frontend)
252 Preparation
Procedure
For the Support Packages of the most important Business Intelligence units so called SAPBINews
(SAPBWNews) Notes are created Read these Notes before updating Business Intelligence For SAP
NetWeaver 70 including enhancement package 2 SPS 12 these are the following
Business Intelligence ABAP SAP Note 1680996
Business Intelligence Java Components SAP Note 1726461
BI 70 Frontend Add-On for SAP GUI 710 SAP Note 1413032
BI 70 Frontend Add-On for SAP GUI 720 SAP Note 1630112
BI 70 Frontend Add-On for SAP GUI 730 SAP Note 1726739
For more information about BI Support Packages see SAP Community Network at http
scnsapcomcommunitydata-warehousingnetweaver-bw Related Resources SAP NW BW Support
Packages
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
2012-08-30 CUSTOMER 3560
253 Updating Units of Business Intelligence
Procedure
Business Intelligence
1 Update the SAP NetWeaver Application Server ABAP (with BI CONT 70x if necessary) with the
appropriate Support Packages
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
NOTE
When applying the component SAP BW 702 some generation errors might occur When
you start importing the BI Support Packages in transaction SPAM choose the menu path
Extras Ignore generation errors For more information see SAP Note 114134
2 Apply the Support Package Stack to the system with the usage type BI-Java
For more information see Application Server Java and Java-Based Software Components [page 19]
3 Update the BI Precalculation Service that is used in your scenario
4 Update the standalone engine Search and Classification (TREX) that is used in your scenario For more
information see Standalone Engine Search and Classification (TREX) [page 44]
NOTE
You have to update TREX to the newest version if you use search capabilities within Business
Intelligence
5 Update the BI Accelerator to the newest available version For more information see BI
Accelerator [page 47]
6 Update the SAP GUI and Business Explorer (BI Add-On BW Add-On) on all remote client hosts
that are involved in the scenario
For more information see SAP GUI Family [page 51] and Business Explorer (BI Add-On BW Add-On)
[page 51]
BI Precalculation Service
1 Log on to the host as a user with administration rights
2 Install the Support Package of the BI Precalculation Service by executing the
xPreCalServerexe file
The welcome screen of the BI Precalculation Server setup wizard appears
The setup now checks the system for the prerequisites
3 Choose the option Update for updating the BI Precalculation service to the current patch level and
then Finish
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3660 CUSTOMER 2012-08-30
26 EP Core
261 Planning
Procedure
The following installable software units must be updated
EP Core
Software Components of EP Core
Component to Be Updated SP File Name Tool Used to Apply SP
PORTAL CORE SERVICES 702 EPBCltSPgt_ltPLgtSCA JSPM
PORTAL FRAMEWORK 702 EPBC2ltSPgt_ltPLgtSCA
PORTAL 702 EPPSERVltSPgt_ltPLgtSCA
PORTAL WEB DYNPRO 702 EPWDCltSPgt_ltPLgtSCA
UWL COLL PROCESS ENGINE 702 UWLJWFltSPgt_ltPLgtSCA
CAF EU 702 SAPEUltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
262 Preparation
Procedure
Backing Up the Portal Runtime Configuration
If you have made changes to the standard Portal Runtime configuration you have to make a backup
of the configuration before the update process For more information see SAP Note 1064468
263 Updating EP Core
Procedure
Apply the Support Package Stack to a system with usage type EP Core
For more information see Application Server Java and Java-Based Software Components [page 19]
264 Post-Installation Steps for EP Core
Procedure
Restoring the Portal Runtime Configuration
To make your changes to the standard Portal Runtime Configuration effective you have to restore
the backup of the configuration done before the update process For more information see SAP Note
1064468
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
26 EP Core
2012-08-30 CUSTOMER 3760
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
253 Updating Units of Business Intelligence
Procedure
Business Intelligence
1 Update the SAP NetWeaver Application Server ABAP (with BI CONT 70x if necessary) with the
appropriate Support Packages
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
NOTE
When applying the component SAP BW 702 some generation errors might occur When
you start importing the BI Support Packages in transaction SPAM choose the menu path
Extras Ignore generation errors For more information see SAP Note 114134
2 Apply the Support Package Stack to the system with the usage type BI-Java
For more information see Application Server Java and Java-Based Software Components [page 19]
3 Update the BI Precalculation Service that is used in your scenario
4 Update the standalone engine Search and Classification (TREX) that is used in your scenario For more
information see Standalone Engine Search and Classification (TREX) [page 44]
NOTE
You have to update TREX to the newest version if you use search capabilities within Business
Intelligence
5 Update the BI Accelerator to the newest available version For more information see BI
Accelerator [page 47]
6 Update the SAP GUI and Business Explorer (BI Add-On BW Add-On) on all remote client hosts
that are involved in the scenario
For more information see SAP GUI Family [page 51] and Business Explorer (BI Add-On BW Add-On)
[page 51]
BI Precalculation Service
1 Log on to the host as a user with administration rights
2 Install the Support Package of the BI Precalculation Service by executing the
xPreCalServerexe file
The welcome screen of the BI Precalculation Server setup wizard appears
The setup now checks the system for the prerequisites
3 Choose the option Update for updating the BI Precalculation service to the current patch level and
then Finish
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
25 Business Intelligence
3660 CUSTOMER 2012-08-30
26 EP Core
261 Planning
Procedure
The following installable software units must be updated
EP Core
Software Components of EP Core
Component to Be Updated SP File Name Tool Used to Apply SP
PORTAL CORE SERVICES 702 EPBCltSPgt_ltPLgtSCA JSPM
PORTAL FRAMEWORK 702 EPBC2ltSPgt_ltPLgtSCA
PORTAL 702 EPPSERVltSPgt_ltPLgtSCA
PORTAL WEB DYNPRO 702 EPWDCltSPgt_ltPLgtSCA
UWL COLL PROCESS ENGINE 702 UWLJWFltSPgt_ltPLgtSCA
CAF EU 702 SAPEUltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
262 Preparation
Procedure
Backing Up the Portal Runtime Configuration
If you have made changes to the standard Portal Runtime configuration you have to make a backup
of the configuration before the update process For more information see SAP Note 1064468
263 Updating EP Core
Procedure
Apply the Support Package Stack to a system with usage type EP Core
For more information see Application Server Java and Java-Based Software Components [page 19]
264 Post-Installation Steps for EP Core
Procedure
Restoring the Portal Runtime Configuration
To make your changes to the standard Portal Runtime Configuration effective you have to restore
the backup of the configuration done before the update process For more information see SAP Note
1064468
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
26 EP Core
2012-08-30 CUSTOMER 3760
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
26 EP Core
261 Planning
Procedure
The following installable software units must be updated
EP Core
Software Components of EP Core
Component to Be Updated SP File Name Tool Used to Apply SP
PORTAL CORE SERVICES 702 EPBCltSPgt_ltPLgtSCA JSPM
PORTAL FRAMEWORK 702 EPBC2ltSPgt_ltPLgtSCA
PORTAL 702 EPPSERVltSPgt_ltPLgtSCA
PORTAL WEB DYNPRO 702 EPWDCltSPgt_ltPLgtSCA
UWL COLL PROCESS ENGINE 702 UWLJWFltSPgt_ltPLgtSCA
CAF EU 702 SAPEUltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
262 Preparation
Procedure
Backing Up the Portal Runtime Configuration
If you have made changes to the standard Portal Runtime configuration you have to make a backup
of the configuration before the update process For more information see SAP Note 1064468
263 Updating EP Core
Procedure
Apply the Support Package Stack to a system with usage type EP Core
For more information see Application Server Java and Java-Based Software Components [page 19]
264 Post-Installation Steps for EP Core
Procedure
Restoring the Portal Runtime Configuration
To make your changes to the standard Portal Runtime Configuration effective you have to restore
the backup of the configuration done before the update process For more information see SAP Note
1064468
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
26 EP Core
2012-08-30 CUSTOMER 3760
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
27 Enterprise Portal
271 Planning
Procedure
The following installable software units must be updated
Enterprise Portal
Software Components of Enterprise Portal
Component to Be Updated SP File Name Tool Used to Apply SP
PDK PORTAL SERVICES 702 NETPDKltSPgt_ltPLgtSCA JSPM
RTC-STREAM 702 RTCSTREAMltSPgt_ltPLgtSCA
RTC 702 RTCltSPgt_ltPLgtSCA
KMC COLLABORATION 702 KMCCOLLltSPgt_ltPLgtSCA
KMC BASE COMPONENTS 702 KMCBCltSPgt_ltPLgtSCA
KMC CONTENT MANAGEMENT 702 KMCCMltSPgt_ltPLgtSCA
LIFECYCLE MGMT PORTAL 702 LMPORTALltSPgt_ltPLgtSCA
SAP CAF-KM 702 CAFKMltSPgt_ltPLgtSCA
VISUAL COMPOSER BASE 702 VCBASEltSPgt_ltPLgtSCA
VISUAL COMPOSER FRAMEWORK 702 VCFRAMEWORKltSPgt_ltPLgtSCA
VISUAL COMPOSER FLEX 702 VCFLEXltSPgt_ltPLgtSCA
VISUAL COMPOSER GP KITS 702 VCKITGPltSPgt_ltPLgtSCA
VISUAL COMPOSER XX KITS 702 VCKITXXltSPgt_ltPLgtSCA
WEB DYNPRO EXTENSIONS 702 WDEXTENSIONSltSPgt_ltPLgtSCA
EP BUILD TOOL 702 EPBUILDTltSPgt_ltPLgtSCA
EP Core (see table Software Components of EP Core [page 37])
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Search and Classification (TREX)
See table Components of TREX [page 44]
272 Updating Enterprise Portal
Procedure
1 Apply the Support Package Stack to a system with usage type EP
For more information see Application Server Java and Java-Based Software Components [page 19]
NOTE
During the deployment of the EP Support Packages JSPM will possibly abort on converting
the table EP_PRT_CACHE In such case empty this table with the SQL statement delete from
EP_PRT_CACHE For more information see SAP Note 939108
2 Apply the Support Package of the same SP level to the standalone engine TREX [page 44]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
3860 CUSTOMER 2012-08-30
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
273 Post-Installation Steps for Enterprise Portal
ProcedureOnly valid for Windows |
Collaboration Updating Groupware Connectivity
Use
If you have configured groupware exchange connectivity you need to update the MSX-A components
on the remote groupware server Update the components directly after the EP update otherwise errors
can occur
Prerequisites
Make sure that you know the location of the directory of the SAPExchange web site This is the home
directory you have specified for the SAPExchange IIS web site that you created when you originally
configured groupware connectivity
Procedure
1 Stop the SAPExchange IIS web site for groupware exchange connectivity
2 Deregister SapExchangeConnectordll To do this open a command prompt and enter the
following command replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ndashu ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordllgt
EXAMPLE
cwinntsystem32regsvr32exe ndashu cSAPExchangeTransport
SapExchangeConnectordll
3 Delete the MSX-A components (all files) located in the directory for the SAPExchange web site for
example in cSAPExchangeTransport
4 Copy the new MSX-A components to the directory for the SAPExchange web site The components
are located under
ltirjgtrootportalappscomsapnetweavercollapplgwexternalexchange
5 Register SapExchangeConnectordll To do this enter the following in the command prompt
replacing the placeholders
ltDrivegtwinntsystem32regsvr32exe ltDrivegt
ltpath_to_SAPExchange_website_directorygtSapExchangeConnectordll
EXAMPLE
cwinntsystem32regsvr32exe cSAPExchangeTransport
SapExchangeConnectordll
6 Restart the SAPExchange web siteEnd of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
27 Enterprise Portal
2012-08-30 CUSTOMER 3960
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
Optimizing KM Database Tables
An optimized procedure for storing application-specific properties for feedback items comments and
personal notes is used in database tables You have to execute a report after the update of the system
It is located in the portal at Content Administration KM Content Toolbox Reports Tools Consistency
Checks Collaboration Consistency Checks Select the Recalculate the Collaboration Item Count parameter and then
start the report
CAUTION
The runtime of the report depends on the number of resources for which feedback items
comments or personal notes exist Tables in the database are optimized when you run the report
As long as the report is being run you may not create feedback items comments or personal
notes for resources However you can navigate as normal
Updating Web Page Composer
If you are updating your system from SAP NetWeaver 70 SPS 13 and using the Web Page Composer
you have to perform the following additional steps
After the update of your system is completed run a report that migrates the former XML definitions
of the standard web content to new definitions For more information see SAP Note 1135274 and
proceed as described in the Note
Reassign the relevant users and groups to the Web Page Composer Editor role The role is located
in pcdportal_contentcomsapfolderwpcwpc_roleswpc_editor_role For more
information about how to assign a role in Web Page Composer see SAP Note 1080110
The complete update procedure for the Web Page Composer is described in detail in SAP Note
1080110
28 Development Infrastructure
281 Planning
Procedure
The Development Infrastructure includes one or more of the following installable software units that
must be updated depending on your implemented scenarios
SAP NetWeaver Application Server ABAP
See table Software Components of Application Server ABAP [page 15]
Development Infrastructure
Software Components of Development Infrastructure
Component to Be Updated SP File NameTool Used to Apply SP
DI CHANGE MGMT SERVER 702 DICMSltSPgt_ltPLgtSCA JSPM
DI COMPONENT BUILD SERVER 702 DICBSltSPgt_ltPLgtSCA
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4060 CUSTOMER 2012-08-30
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
Component to Be Updated SP File NameTool Used to Apply SP
DI DESIGN TIME REPOSITORY 702 DIDTRltSPgt_ltPLgtSCA
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])
Developer Workplace
A Developer Workplace installation includes an installation of SAP NetWeaver Developer Studio and
(optionally) a local installation of SAP NetWeaver Application Server Java with the usage type Enterprise
Portal
Components of Developer Workplace Installation
Component to Be Updated SP File Name Tool Used to Apply SP
NW DEVELOPER STUDIO 702 JIDEltSPgt_ltPLgtSAR IDE70setup
OptionalSAP NetWeaver Application Server Java with Enterprise Portal (see table Software Components of Enterprise Portal [page 38])
Front-End GUI
Depending on your implemented scenario the SAP GUI in use may need to be updated For more
information see SAP GUI Family [page 51]
Adobe LiveCycle Designer (Optional)
Depending on your implemented scenario the Adobe LiveCycle Designer may need to be updated
The update is not covered by SP Stacks for SAP NetWeaver 70 including enhancement package 2 but
synchronized with the SAP GUI updates
Component of Adobe LiveCycle Designer
Component to Be Updated SP File Name Tool Used to Apply SP
ADOBE LIVECYCLE DESIGNER 71 (or higher) Installer
You can download the Adobe LiveCycle Designer installer from SAP Service Marketplace at http
servicesapcominstallations Entry by Application Group SAP NetWeaver SAP NETWEAVER
SAP EHP2 FOR SAP NETWEAVER 70 Installation and Upgrade ltOSgt ltDBgt Adobe LiveCycle Designer
ltVersiongt
282 Updating Development Infrastructure
Procedure
Updating the server systems of the Development Infrastructure
1 Apply any Support Packages to SAP NetWeaver AS ABAP if applicable
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
2012-08-30 CUSTOMER 4160
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
2 Apply the Support Package Stack to the system with the usage type DI
For more information see Application Server Java and Java-Based Software Components [page 19]
Updating the Developer Workplace
SAP NetWeaver Developer Studio
1 Extract the downloaded archive file JIDEltSPgt_ltPLgtSAR to ltsp_directorygt
2 Stop all SAP applications (including the Developer Studio itself SAP GUILogon local J2EE Engine
and so on) that are still running on the local host to be updated
3 In ltsp_directorygt execute the IDE70setupexe file
4 On the Welcome screen choose Next
5 On the next screen choose the Update option and then Finish
The Developer Studio is then updated
Local SAP NetWeaver Application Server Java
Apply the Support Package Stack with the usage type Enterprise Portal to the local Application Server
Java as described in Application Server Java and Java-Based Software Components [page 19]
CAUTION
For SAP MaxDB Before updating your local Application Server Java you have to increase the
parameter MAXUSERTASKS of the underlying SAP MaxDB instance to at least 85 You can set this
parameter of the relevant database instance either in the SAPMMC or in the SAP MaxDB Database
Manager GUI by choosing Configuration Parameters You have to restart the database instance
afterwards to make the change effective
Updating Adobe LiveCycle Designer
1 Uninstall any previous versions of Adobe LiveCycle Designer Choose Start Settings Control Panel
Add or Remove Programs
The old versions of Adobe LiveCycle Designer may have been installed in various ways Depending
on how they are installed perform one of the following alternatives
Standalone installation using Adobe LiveCycle Designer installer Select Adobe LiveCycle
Designer and choose the ChangeRemove button to uninstall the whole application
Integrated installation with SAP GUI or SAP NetWeaver Developer Studio Select the relevant
item from the list and choose the Change button and deselect the Interactive Forms element to
uninstall the Adobe LiveCycle Designer feature from the respective applications
2 Extract the downloaded package to a temporary directory
3 Install Adobe LiveCycle Designer 80 by invoking the executable file ALDsetupexe from the
temporary directory of the extracted files
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
28 Development Infrastructure
4260 CUSTOMER 2012-08-30
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
29 Mobile Infrastructure
291 Planning
Procedure
The following installable software units must be updated
SAP NetWeaver Application Server ABAP
See table Software Components of AS ABAP [page 15]
Mobile Infrastructure
Software Components of Mobile Infrastructure
Component to Be Updated SP File Name
Tool Used to Apply SP
MI CLIENT 702 NWMCLIENTltSPgt_ltPLgtSCA JSPM
MI DRIVERS 702 NWMDRIVERSltSPgt_ltPLgtSCA
MI ADMINSTRATION 702 NWMADMINltSPgt_ltPLgtSCA
MI WD LAPTOP 702 NWMWDLAPltSPgt_ltPLgtSCA (Optional see release restriction 853508)
SAP NetWeaver Application Server Java (see table Software Components of Application Server Java [page 20])Update of the following software components of the ABAP system is not required SAP BW 702 PI_BASIS 702
292 Preparation
1 Read SAP Note 1740624 (SAP Mobile Infrastructure 702 SPS12 ndash Composite Note)
2 Read the latest documentation for SAP MI Administrator available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver SAP
NetWeaver by Key Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for
Administrators
293 Updating Mobile Infrastructure
Procedure
1 Apply the Support Packages to SAP NetWeaver AS ABAP
For more information see Application Server ABAP and ABAP-Based Software Components [page 15]
2 Apply the Support Package Stack to the system on which the Mobile Infrastructure is running
For more information see Application Server Java and Java-Based Software Components [page 19]
CAUTION
Updating the component NWMADMINSCA may result in the loss of some setup package
parameters Consequently you may need to reset the setup package parameters after the
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
29 Mobile Infrastructure
2012-08-30 CUSTOMER 4360
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
update of your MI system For more information see SAP Help Portal at http
helpsapcomnw70 SAP NetWeaver 70 including Enhancement Package 2 SAP NetWeaver 70
Library (including Enhancement Package 2) ltLanguagegt SAP NetWeaver Library SAP NetWeaver by Key
Capability People Integration by Key Capability SAP Mobile Infrastructure SAP MI for Administrators
Tasks Installing SAP MI on the Mobile Device Mobile Device Installation Using Setup Packages
Allowing the Creation of Setup Packages
3 Apply the Support Package for SAP GUI For more information see SAP GUI Family [page 51]
4 Open SAP NetWeaver Mobile Administrator Mobile Component and choose Reload to reload the client
installation files deployed in the second step
The new framework is available
5 Set up SAP Mobile Infrastructure on the mobile devices
For more information see SAP Help Portal at httphelpsapcomnw70 SAP NetWeaver 70
including Enhancement Package 2 SAP NetWeaver 70 Library (including Enhancement Package 2) ltLanguagegt
SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability SAP
Mobile Infrastructure SAP MI for Administrators Tasks Installing SAP MI on the Mobile Device
210 Standalone Engines
2101 Search and Classification (TREX)
21011 Planning
Procedure
You can download the TREX Revision update from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
Components of TREX
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 TREX70_ltREVISIONgtSAR SAPinst
21012 Preparation
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as follows UNIX usrsapltsapsidgtTRXltinstance_nogt Windows ltdisk_drivegtusrsapltSAPSIDgtTRXltinstance_nogt
ltTREX_UPDATEgt Directory used for applying TREX update
1 Read SAP Note 802987 (TREX 70 Central Note)
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4460 CUSTOMER 2012-08-30
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
2 Download the required update package from SAP Support Portal at httpservicesapcom
swdc Support Packages and Patches A ndash Z Index ldquoNrdquo SAP NETWEAVER SAP EHP2 FOR SAP
NETWEAVER 70 Entry by Component Search and Classif (TREX) TREX 700
3 Create a directory ltTREX_UPDATEgt for the TREX update package
4 Use SAPCAR (see SAPCAR [page 56]) to extract the downloaded Support Package file
TREX70_ltREVISIONgtSAR into the directory ltTREX_UPDATEgt
The extraction of the archive generates several subdirectories under the directory
ltTREX_UPDATEgt The relevant directory for this description is the SAPinst directory
ltTREX_UPDATEgtims_sapinst_standalone_trexltOS_DIRgt
21013 Updating TREX
Prerequisites
You have installed at least one previous TREX 70 release (Version 70XXXX)
If you have already installed TREX refer to file ltTREX_DIRgtexedocTREXVersionhtml to find
out its version
If you do not have TREX installed at all install TREX 70 from scratch as described in Installation
Guide ndash SAP NetWeaver 70 Standalone Engine Search and Classification (TREX) Single Host For more
information see SAP Service Marketplace at httpservicesapcominstallnw70
NOTE
In a distributed scenario all TREX systems must have the same TREX release with the same patch
level Mixed installations with different TREX releases are not supported
Procedure
1 Log on to the host on which you want to apply the TREX Support Package either as root user (on
UNIX) or as administrator (on Windows)
CAUTION
Do not use the user ltsapsidgtadm for updating TREX The ltsapsidgtadm users do not possess
all permissions for updating a TREX system Therefore do not use the ltsapsidgtadm user of
another SAP system either to update a TREX system
NOTE
For a distributed TREX system you have to perform the update on the TREX host on which
the TREX global file system is installed The TREX instance on this host is to be updated first
With the restart of TREX after the update all other TREX instances of the TREX system are
updated automatically by replicating the updated binaries
2 Navigate to the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt which has
been created by SAPCAR
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4560
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
NOTE
Before starting the update you have to close the TREX Admintool
3 Start SAPinst from the directory ltTREX_UPDATEgtim_sapinst_standalone_trexltOS_DIRgt
4 On the Welcome screen of SAPinst choose SAP NetWeaver 70 Search and Classification (TREX)
TREX Instance
5 Choose Next and follow the instructions on your screen The necessary input parameters are listed
in the following table
Window Input OptionEntry
TREX gt Installation Confirm the installation of TREX Search and ClassificationChoose Next
SAP System gt General Parameters 1 In SAP System Parameters Profile Directory enter the path to the directory in which SAP system profiles are storedOnly valid for Windows |
ltSAPGLOBALHOSTgtsapmntltSAPSIDgtSYSprofile
End of Windows |
Only valid for UNIX |
ltSAP System Mount DirectorygtltSAPSIDgtprofile
End of UNIX |
In the default scenario the SAP system profiles are located on the host on which the TREX global file system and the first TREX instance are installed You can choose Browse to search for the directory
2 Choose Next
SAP System gt OS User Passwords 1 Enter the passwords of the operating system users1 SAP System Administrator Password of SAP System Administrator
Here you enter the password for the operating system user ltsapsidgtadm with which you log on to administrate TREX
2 SAP System Service User Password of SAP System Service UserHere you enter the password for the operating system user SAPServiceltSAPSIDgt under which the TREX processes run
2 Choose Next
TREX gt Instance Choose an existing TREX instance to upgradeTREX Installation Mode SAP System ID (SAPSID)
The SAP system ID ltSAPSIDgt is displayed hereTREX Installation Mode Installation Mode
Choose upgrade an existing TREX instanceDetected TREX Instances TREX instances for Upgrade
A list with the TREX instances which can be updated is displayed1 Select one of the TREX instances where the hotfixes should be applied
EXAMPLE
If you want to update TREX instance 11 you selectOnly valid for UNIX |
TREX instance 11 [usrsapltSAPSIDgtTRX11]
End of UNIX |
Only valid for Windows |
TREX instance 11 [Cusrsapltsapsidgttrx11]
End of Windows |
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4660 CUSTOMER 2012-08-30
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
Window Input OptionEntryNOTE
For a distributed TREX system landscape you have to perform the update on the host where the TREX global file system and the first TREX instance are installed
2 Choose Next
Check Parameters Before the installation starts the system displays the parameters that you enteredChoose Start to start the installation
Task Progress
Finished successfully Choose OK to finish the installation
After the update finishes successfully restart TREX by means of the SAP Management Console or the TREX Admintool
NOTE
After you restart TREX all TREX instances of a distributed TREX system landscape are updated automatically by replication of the updated binaries
When you have entered all input parameters SAPinst starts the installation and displays the installation progress during the processing phase If the installation is successful SAPinst displays the message The installation finished successfully
NOTE
In some cases you may have to restart the Application Pool of the MS Internet Information Server
For Windows Server 2003 Choose Start Administrative Tools Internet Information Services (IIS)
Manager Application Pools AppPool_TREX_ltnumbergt and restart the service
2102 BI Accelerator
21021 Planning
Procedure
The BI Accelerator is a special build of the SAP NetWeaver Search and Classification (TREX) for
Linux 64-bit which is delivered with pre-configured hardware The following units should be updated
Components of BI Accelerator
Component to Be Updated Update File Name Tool Used to Apply Update
TREX 700 BIA70_ltREVISIONgtSAR (Linux on x86_64 64bit) SAPinst
NOTE
You have to download the update package for SAP NetWeaver 70 Search and Classification
(TREX) Linux 64bit from SAP Support Portal at httpservicesapcomswdc Download
Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4760
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
NETWEAVER 70 SAP BI Accelerator SAP BI ACCELERATOR 70 TREX 700 Linux on x86_64
64bit
CAUTION
This package is intended only for updating the BI Accelerator systems For information about
updating a TREX system see section Search and Classificaiton (TREX) [page 44]
21022 Preparation
Procedure
In this section the following variables are used
Variable Meaning
ltTREX_DIRgt Installation directory for TREX The path to the directory is as followsUNIX usrsapltsapsidgtTRXltinstance_numbergt
ltTREX_UPDATEgt Directory used for the patching of TREX
1 Read SAP Note 883725 BIA 700 Updating SAP NetWeaver 70 BI accelerator
2 Read SAP Note 883726 BIA 700 Central Note SAP NetWeaver BI accelerator
3 Download the required Support Package and extract it to the directory ltTREX_UPDATEgt using
SAPCAR
EXAMPLE
SAPCAR -xvf BIA70_ltREVISIONgtsar -R ltTREX_UPDATEgt
4 Prevent the corresponding BI system from starting queries or indexing jobs on the BI Accelerator
system to be updated
21023 Updating BI Accelerator
Procedure
1 Log on to the host of the BI Accelerator system as user root
NOTE
If during the update procedure a question for a password appears you need to enter the
root password
2 Navigate to the directory ltTREX_UPDATEgt and start the update script with the following commands
cd ltTREX_UPDATEgt
sh installsh
3 After starting the script the following options will be displayed
1 ndash install a new TREX instance
2 ndash clone an existing TREX instance to a new blade host
3 ndash update an existing TREX instance
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
4860 CUSTOMER 2012-08-30
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
4 ndash configure RFC connection of an existing TREX instance
5 ndash deinstall an existing TREX instance
6 ndash quit without any system change
To start the BIA update select option 3 ndash update an existing TREX instance and press Enter
4 The following screen appears and displays an overview of the overall update procedure
The script performs the following actions
Step 1 Get parameters for BI accelerator (TREX) update
Step 2 Stop the TREX landscape before update
Step 3 BI accelerator (TREX) software update
Step 4 Restart the TREX landscape
Step 5 Switch RFC server to multithreaded mode
Continue with Step 1 Get parameters for BI accelerator (TREX) update
5 The script guides you through the BIA update process In each step it asks for specific parameters
Screen Output Required Input
Choose one of these installed TREX
systems
No ltngt SID ltSAPSIDgt
instance ltinstance_nogt
[ltBIA_versiongt]
Enter the number of the installed system you want to update
Enter the root user to be used for ssh
remote access to all blades [default
1]
Enter the root user to be used for the ssh (Secure Shell) remote access to all blades
Choose one of the following options
c = Stop all running instances of the
landscape and start update
e = exit the script no actions are
taken
r = Repeat Step 1 Parameter questions
To continue with the update procedure you have to choose cOptions for input c
Continue with the update Make sure that the displayed parameters are correct before you continue
e
Exit the installation script If you select this option the installation script terminates without changes to your system
r
Repeat the questions for the first step to change or correct the parameters
21024 Post-Installation Steps
Procedure
Re-enable the corresponding BI system to access the BI accelerator system
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
2012-08-30 CUSTOMER 4960
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
2103 Gateway
Procedure
There are two different ways to run SAP Gateway Service
The Gateway server is installed and configured with SAP NetWeaver Application Server ABAP In
this case the Gateway service is updated along with the kernel update of the ABAP-based system
The Gateway server is installed as a standalone engine In this case you must update the system
manually
To update a standalone Gateway engine proceed as follows
1 Download the non-Unicode kernel patch file SAPEXESAR from the SAP Service Marketplace at
httpservicesapcompatches
2 Log on as user ltsapsidgtadm to the host where the Gateway service is running
3 Stop the Gateway system and the OS level service
4 Extract the kernel SAR file with the command SAPCAR -vxf SAPEXESAR -R
ltkrnl_directorygt
5 Start the OS level service and the system
2104 SAP Web Dispatcher
Procedure
Updates for the executable and required library files of SAP Web Dispatcher are included in the SAP
kernel update file SAPEXESAR
1 Log on to the host where the Web Dispatcher is running as user ltsapsidgtadm
2 Stop the SAP Web Dispatcher process
3 Extract the kernel update file with the command SAPCAR -vxf SAPEXESAR -R
ltkernel_directorygt
4 Restart the SAP Web Dispatcher
2105 Other Standalone Engines
Procedure
Content Server
For information on Content Server update see SAP Note 514500
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
210 Standalone Engines
5060 CUSTOMER 2012-08-30
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2111 SAP GUI Family
Procedure
The table below lists the versions of the SAP GUI components that are recommended for SAP NetWeaver
70 Application Server ABAP including enhancement package 2 and all applications running on it
Compatible SAP GUI Versions
SAP GUI Family
SAP GUI FOR WINDOWS 620
SAP GUI FOR WINDOWS 710 CORE
SAP GUI FOR WINDOWS 720 CORE
SAP GUI FOR JAVA 710
SAP GUI FOR JAVA 720
All SAP GUI versions are downward compatible which means the SAP GUI versions recommended
for the latest release of Application Server ABAP can also be used with lower releases of the Application
Server ABAP
Although you can continue using older SAP GUI versions (as long as your SAP Systems with the
underlying SAP Web AS do not require new features supported by newer SAP GUI versions) we
recommend that you update your SAP GUI on a regular basis Check the corresponding sections of
this document for requirements of the particular usage types
SAP GUI patches are cumulative which means the latest SAP GUI update includes all corrections
implemented so far Applying the single package of the latest update is sufficient You can download
the SAP GUI patches for Java at httpservicesapcomswdc Support Packages and Patches A - Z
Index ldquoGrdquo SAP GUI FOR JAVA You can download the SAP GUI patches for Windows at http
servicesapcomswdc Support Packages and Patches A - Z Index ldquoGrdquo SAP GUI FOR WINDOWS
For more information about updating the SAP GUI components see the SAP Frontend Installation Guide
available on SAP Service Marketplace at httpservicesapcomsapgui
2112 Business Explorer (BI Add-On BW Add-On)
Procedure
Business Explorer (BI Add-On BW Add-On) is updated along with the update of SAP GUI for Windows
on client computers where the BI Add-On or BW Add-On is installed
For more information see Business Intelligence [page 34]
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
2012-08-30 CUSTOMER 5160
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
2113 Other Clients
Procedure
SAP NetWeaver Developer Workplace
For more information see Development Infrastructure [page 40]
SAP NetWeaver Developer Studio
For more information see Development Infrastructure [page 40]
Adobe LiveCycle Designer
For more information see Development Infrastructure [page 40]
J2SE Adapter Engine (PIXI)
For more information see Process Integration [page 29]
MI Client
For more information see Mobile Infrastructure [page 43]
212 SAP Library
SAP delivers updates of SAP Library in connection with Support Package Stacks which can be applied
to your local installation of SAP Library A local installation has one of the following formats
HtmlHelp Compiled HTML files that can be displayed on Windows platforms using HTML Help
Viewer
PlainHtml Standard HTML files that can be displayed with a standard Web browser
You can download the updates of SAP Library for SAP NetWeaver 70 including enhancement package
2 with appropriate formats and languages from SAP Service Marketplace at http
servicesapcommaintenanceNW70
Prerequisites
You have installed SAP Library for SAP NetWeaver 70 including enhancement package 2 from the
online documentation DVD which you can order from SAP Help Portal at http
helpsapcomnw702
You have downloaded the update files of SAP Library for SAP NetWeaver 70 including
enhancement package 2
Procedure
To update SAP Library to the intended (target) SPS level you must apply the updates for all Support
Package Stacks subsequent to the currently installed SPS level
To apply a single update proceed as follows
1 Extract the update file to a temporary directory using a ZIP tool of your choice
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
5260 CUSTOMER 2012-08-30
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
2 For HtmlHelp copy the directory HtmlhelpHelpdataltlanguagegt with all its subdirectories
extracted from the HtmlHelp ZIP file to the documentation directory on the server
For PlainHtml execute the installation program (this can be either INSTALL or INSTHELP) which
is located in the directory lttemp_dirgtltlanguagegtPlainHTMLPLAINHTMINSTALLltOSgt Then
enter the path to the directory where SAP Library is installed
Repeat the steps for all subsequent SPS levels
2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
212 SAP Library
2012-08-30 CUSTOMER 5360
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
This page is left blank for documents that are printed on both sides
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
A Appendix
A1 Determining the Current Component Versions
Procedure
This section describes how to determine the currently installed component versions
SAP NetWeaver Application Server ABAP
You can find out the current kernel patch level of the Application Server ABAP in one of following
ways
If the system is running choose System Status and then press SHIFT + F5 The kernel patch
level is displayed in the SupPkglvl field
If the system is not running you can find out the kernel patch level in the text file ltkrnl_directorygt
sapmanifestmf
To find out the current Support Package level of all software components running on the ABAP system
call the transaction SPAM and then choose Package level
SAP NetWeaver Application Server Java
You can find out the current kernel patch level of the Application Server Java in the text file
ltkrnl_directorygtsapmanifestmf
To find out the current Support Package level of all software components running on the Java system
follow the path httplthostgtlthttp_portgtsapmonitoringSystemInfo Software Components
all components
Search and Classification (TREX)
The file ltTREX_DIRgtexedocTREXVersionhtml indicates the current TREX version
XIPI Adapter Engine (J2SE)
To find out the current Support Package level of the XIPI Adapter Engine (J2SE) follow the path
httplthostgt8200monitoraction=about Information
MI Client
To find out the current MI Client version installed on the mobile device choose Info Buildversion
SAP Internet Graphic Server (IGS)
The administration page httplthostgt4ltinstance_nogt80 only indicates the status of the IGS To
find out the current version of the IGS you must first enable the HTTP administration as described in
SAP Note 959358
A Appendix
A1 Determining the Current Component Versions
2012-08-30 CUSTOMER 5560
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
SAP NetWeaver Developer Studio
To find out the current version of the SAP NetWeaver Developer Studio choose Help About SAP
NetWeaver Developer Studio
SAP MASTER DATA CONTENT for SLD
To find out the version of the current SAP MASTER DATA CONTENT in the SLD follow the path
httplthostgtlthttp_portgtsldadmindetailsjspview=data SAP CR Content Version
BI Precalculation Service
The version number of the BI Precalculation Service is denoted by the file version of
BExPreCalcServerProgramexe In the file browser navigate to the directory ltDrivegtProgram Files
SAPFrontEndBW and choose Properties in the context menu of the BExPreCalcServerProgramexe
file
A2 Tools Used During the System Update
This section provides further information about the tools that you need to apply Support Packages
A21 SAPCAR
SAPCAR is used to extract SAR archives It is installed with each SAP NetWeaver AS in the kernel
directory and its patch is delivered with the SAP KERNEL package (SAPEXESAR)
NOTE
In rare cases for example when the currently installed SAPCAR tool is defective and you cannot
extract the Kernel patch itself you can download the unpacked version of the SAPCAR tool at
httpservicesapcomswdc Support Packages and Patches A - Z Index SAPCAR
Procedure
Using SAPCAR
1 Navigate to the directory in which you have downloaded or copied the archives
Only valid for UNIX |
cd ltsp_directorygt
End of UNIX |
Only valid for Windows |
cd ltsp_directorygt
End of Windows |
2 Start SAPCAR to extract the archive to the current directory ltsp_directorygt
A Appendix
A2 Tools Used During the System Update
5660 CUSTOMER 2012-08-30
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
Only valid for UNIX |
ltpath to SAPCARgtsapcar ndashxvf ltfile_namegtSAR
End of UNIX |
Only valid for Windows |
ltpath to SAPCAREXEgtsapcarexe ndashxvf ltfile_namegtSAR
End of Windows |
NOTE
Instead of using ltsp_directorygt as the target directory you can use the option -R to specify
a particular target directory For example sapcar -xvf ltSAR_filegt -R lttarget_dirgt
NOTE
Directories in the archive will be created as subdirectories of the target directory by keeping
the directory structure of the archive
A22 ABAP Support Package Manager and Add-On Installation Tool
The Support Package Manager (transaction SPAM) imports ABAP Support Packages into an ABAP system
or into an ABAP stack of a dual-stack system
The Add-On Installation Tool (transaction SAINT) enables you to install and update add-on
components You can use the Add-On Installation Tool to import add-on components with their
prerequisite ABAP Support Packages in a single import queue
For information about applying ABAP Support Packages or add-on installation packages see section
Application Server ABAP and ABAP-Based Software Components [page 15]
CAUTION
Before you start using the Support Package Manager see SAP Note 822379
RECOMMENDATION
We recommend that you always use the latest version of the Support Package Manager You can
download it from SAP Service Marketplace at httpservicesapcomspmanager ABAP
Support Package Manager Download the Support Package Manager for your release
For more information about SPAM and SAINT see the online documentation on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS ABAP (Application Server for ABAP) Software Logistics Software Maintenance
A Appendix
A2 Tools Used During the System Update
2012-08-30 CUSTOMER 5760
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
A23 Java Support Package Manager
The Java Support Package Manager (JSPM) is used for applying Support Packages to SAP NetWeaver
Application Server Java (AS Java) and all Java-based software components running on it JSPM is able
to update all integral parts of a Java system or a Java stack of a dual-stack system
For information about applying a Support Package Stack with JSPM see Application Server Java and Java-
Based Software Components [page 19]
NOTE
Before you start using the Java Support Package Manager see SAP Note 891983
For more information about JSPM see the online documentation available on SAP Help Portal at
httphelpsapcomnw702 Application Help SAP Library ltLanguagegt SAP NetWeaver
Administrators Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems
AS Java (Application Server for Java) Software Logistics Software Maintenance Java Support Package
Manager
A3 System Profile Parameters
Procedure
You can find out the current values of system profile parameters in one of the following ways
If a system is an ABAP system and it is running you can use the transaction RZ11
If a system is either a non-ABAP system or not running proceed as follows
1 Log on to the host with the user ltsapsidgtadm
2 Call the command
sappfpar[exe] name=ltSAPSIDgt nr=ltinstance_nogt
pf=ltSAPSIDgt_ltinstance_namegt_lthostgt ltPAR_NAMEgt
ltPAR_NAMEgt stands for the particular profile parameter in question
A Appendix
A3 System Profile Parameters
5860 CUSTOMER 2012-08-30
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +4918 0534 34 34F +4918 0534 34 20wwwsapcom
copy Copyright 2012 SAP AG All rights reservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG The information contained herein may be changed without prior notice
- SAP NetWeaver 70 Including Enhancement Package 2 SPS 12
-
- Table of Contents
- 1 Overview
-
- 11 Before You Start
- 12 Types of Support Packages
- 13 Downloading Support Package Stacks
-
- 2 Applying Support Packages to Installable Software Units of SAP NetWeaver 70 Including Enhancement Package 2
-
- 21 Application Server ABAP and ABAP-Based Software Components
-
- 211 Planning
- 212 Preparation
- 213 Updating the Application Server ABAP and ABAP-Based Software Components
- 214 Post-Installation Steps
-
- 22 Application Server Java and Java-Based Software Components
-
- 221 Planning
- 222 Preparation for Applying a Support Package Stack
- 223 Updating the Application Server Java and Java-Based Components
- 224 Post-Installation Steps
-
- 23 Parallel Update of Dual-Stack Systems
- 24 Process Integration
-
- 241 Planning
- 242 Updating Units of Process Integration
- 243 Post-Installation Steps
-
- 25 Business Intelligence
-
- 251 Planning
- 252 Preparation
- 253 Updating Units of Business Intelligence
-
- 26 EP Core
-
- 261 Planning
- 262 Preparation
- 263 Updating EP Core
- 264 Post-Installation Steps for EP Core
-
- 27 Enterprise Portal
-
- 271 Planning
- 272 Updating Enterprise Portal
- 273 Post-Installation Steps for Enterprise Portal
-
- 28 Development Infrastructure
-
- 281 Planning
- 282 Updating Development Infrastructure
-
- 29 Mobile Infrastructure
-
- 291 Planning
- 292 Preparation
- 293 Updating Mobile Infrastructure
-
- 210 Standalone Engines
-
- 2101 Search and Classification (TREX)
-
- 21011 Planning
- 21012 Preparation
- 21013 Updating TREX
-
- 2102 BI Accelerator
-
- 21021 Planning
- 21022 Preparation
- 21023 Updating BI Accelerator
- 21024 Post-Installation Steps
-
- 2103 Gateway
- 2104 SAP Web Dispatcher
- 2105 Other Standalone Engines
-
- 211 Clients of SAP NetWeaver 70 Including Enhancement Package 2
-
- 2111 SAP GUI Family
- 2112 Business Explorer (BI Add-On BW Add-On)
- 2113 Other Clients
-
- 212 SAP Library
-
- A Appendix
-
- A1 Determining the Current Component Versions
- A2 Tools Used During the System Update
-
- A21 SAPCAR
- A22 ABAP Support Package Manager and Add-On Installation Tool
- A23 Java Support Package Manager
-
- A3 System Profile Parameters
-
- Copyright and trademarks
-