SAP Software Update Manager 1.0 SP02, SAP PI 7.1 SP04 on Oracle 10.2.0.2.

Summary This article demonstrates the use SAP Software Update Manager in applying Support Package Stack in a dual SAP PI system. The demo use case is shown with the help of various screenshots. Additionally discussion on new features of the SUM tool is also included. SAP Software Update Manager

The Software Update Manager is a multi-purpose tool, which supports various processes, such as performing a release upgrade, installing enhancement packages or applying Support Package stacks. Traditionally for applying SPS we use SPAM for ABAP & JSPM for Java. Some of the benefits of using SUM tool over these tools among others are

Two different tools are not required to apply SPS. One SUM tool is used. No need to uncar the SAR files. Minimum downtime (Single downtime for both ABAP & Java combined). Simultaneously the SPS are applied to both the stacks.

This document contains a demo scenario where we are the SUM tool is used to apply a support package stack to a PI 7.1 system SP04 to take the system to a targeted release of PI 7.1 SP08. For the scenario we have a PI 7.1 SP4 system installed on Linux (RHEL). Database used is Oracle 10.2.0.2. We will be updating the system from SPS4 to SPS8 (Including Kernel upgrade). You can use the SP stack application in SAP Service market place to know which support packages you need. For this you need to put in the SP stack application source stack and target stack. In Source stack you need to put SAP NetWeaver PI 7.1 SPS04 and in the Target stack you need to put SAP NetWeaver PI 7.1 SPS08. You also need to download the stack.xml file Once you have downloaded the packages dump the files and the stack into a download directory. The SUM tool will pick the required files from the download directory only. Note: In SMP the current SUM package is SUM 1.0 SP02 (SUM10SP02_-*.SAR) This is a two part article. This article contains demonstration until Check Phase of the Roadmap.

Demo: Support Package Application using SUM tool

In this section we will use the SUM tool to apply the Support Package Stack in a PI system. The source system is in PI 7.1 SP04 & the target System is PI 7.1 SP08. It is a dual stack. Normally we use SPAM to apply the ABAP part of SPS and JSPM to apply the Java SPS part. Let us start the SPS application using SUM tool. Once you have downloaded & extracted the SUM tool, start the SUM tool: ./STARTUP

The SDT server and Program starts. You can now go to web browser and start the Installation GUI. To start the GUI from a browser, enter the following Internet address: http://<host name>:4239. Replace <host name> with the name of the host on which the installation program is running. Once you open the URL, the SDT GUI is automatically launched.

Ensure that you have installed JRE for the SUM GUI to run You need to provide a username and the password for the user (Administrator & not Observer mode) who is running the SUM GUI.

The SUM tool detects the source system information and displays the information. The SUM tool can be used to

Upgrading to SAP NetWeaver 7.3 including enhancement package 1 Upgrading to SAP NetWeaver 7.3 Upgrading to SAP Business Suite 7 Innovation 2011 Updating to SAP Business Suite 7 Innovation 2011 (enhancement package installation) Applying Support Packages Stacks Installing additional Java technical usages or usage types on top of existing Java systems on SAP NetWeaver 7.3 EHP1

Note: Check SAP Note 1557404 - Central Note - Software Update Manager 1.0 SP02 [lmt_007] for more information The GUI provides you with functions for monitoring and navigating through the roadmap steps of the procedure. The complete procedure consists of several roadmap steps that contain modules, which in turn consist of the individual phases.

In the next screen provide the complete path to the stack.xml (including the xml name)

Once you have provided the stack.xml. The SUM tool evaluates the xml and determines the target release (In this case the target is also PI 7.1). Provide the Keyword (Refer to the SAP note mentioned in the screen)

Once you click next the target release is confirmed. In the next screen the roadmap appears.

Click Next to Initialize.

Once you click next to go to Extraction Phase, the Extraction phase will extract the relevant files from the download directory. Before you start the SUM tool do ensure that

Latest Kernel is applied to the Source System Latest SPAM patch is applied.

Provide the DDIC password for the Client 000 & DB password for the SUM tool to connect to the system and database.

Clone Mode: The Software Update Manager checks the tables in the database which will be cloned to the shadow system later on during the update. Here a shadow instance will be created with tables copied from source system. Next input screens will ask for SPAM update.the SPAM was already updated, we choose to ignore the SPAM update.As in case of other tools such as SAPup & EHPI tool, SUM tool will also prompt for any missing notes that should be applied

Clicked next to start configuration. The Java configuration steps also starts.

With SUM tool you can choose to automatically update the additional dialog instances if any. In older times we had to manually uninstall and install dialog instances

Java is also in parallel running

For ABAP stack in configuration phase the following options comes up

As in case of SAPup or EHPI tool where you can import only one transport request here in SUM tool you can import multiple custom transports

You can also enter the SPDD & SPAU transport numbers. Earlier you had to manually enter the SPDD & SPAU transports in umodauto.lst file.

Here in SUM tool in addition to the ABAP Shadow instance entires you can also enter the Java Shadow Instance & SCS Shadow instance numbers. In addition to this if you have used the SUM tool procedure in any previous system you can use the generated profiles there for the Shadow system. In case you want to use this feature, copy and put the profiles under the subdirectory <save> The Configuration phase ends. Clicking next starts the CHECK phase. The CHECK Phase is same as in case of SAPup and EHPI tool.In this demo installation, we do until check phase, rest of the phases are PREPROCESSING, DOWNTIME, POST-PROCESSING & FINALIZATION.