Expert Guided Implementation

Update to EhP1

1st November 2010

Mary Harrison
 Agenda

 Expert Guided Implementation Methodology

 Motivation

 Check of Pre-requisites

 Upgrade EhP1

 Execution of Implementation Steps

(SOLMAN_SETUP)

© SAP 2008 / Page 2

 Expert Guided Implementation

Key Messages

 Expert Guided Implementation is offered by SAP to support our

customers and partners in the activation and maintenance of
specific SAP Solution Manager scenarios.

 During Expert Guided Implementation the customer receives

direct guidance from an SAP Scenario Expert and is not alone
with configuration guides.

© SAP 2010 / Page 3

 SAP Expert demonstrates to group of
customers how to implement a scenario

Empowering Execution

SAP Scenario Expert

Customer SAP Scenario Expert

Customer

SAP Expert explains implementation steps Customer executes Registered customer

to group of customers within the SAP demonstrated steps at has access to SAP
Solution Manager system. In addition he the same day. Expert
explains do’s and don’t to avoid problems.

© SAP 2010 / Page 4

 Expert Guided Implementation
– How to get help

How to get help

+353 91 40 47 07
Customer
m.harrison@sap.com SAP Expert

During the execution part you have direct access to the Expert via telephone to
solve questions quickly. Please ensure that the R/3 support and http connections
are open that we can logon to your system.

© SAP 2010 / Page 5

 Daily Feedback Document

Daily feedback document provides us information about your activities and

problems encountered during this week.
Document will be uploaded after the presentation with SAP Connect session
and can be downloaded.

Please send us the filled document according to your current

implementation state after each working day.

© SAP 2010 / Page 6

 Expert Guided Implementation Schedule
Day 1 Day 2
Expert explains: Expert explains:
•Explanation of scenario Check for successful upgrade
•Checking of prerequisites  Prepare for
•Upgrade kernel, WebAS Java SOLMAN_SETUP
and WebAS ABAP Implementation / Verification
Wily Products (Introscope
Customer executes: Agent, Enterprise Manager)
•Check and fulfill prerequisites
•Download SAP Media for Customer executes:
Upgrade Checks for successful
• Execute demonstrated upgrade
upgrade steps Prepare for
SOLMAN_SETUP
Result: Verify Wily Products
-Starting of Upgrade to EhP1 Receives on demand support
by SAP scenario expert, if
needed
Result:
SAP Solution Manager 7.0 EhP1
© SAP 2010 / Page 7
Day 3 – Day 5
Expert explains:
• Initial configuration
• Basic configuration
• E2E RCA Basis configuration
(Diagnostics Managed
System configuration)
Customer executes:
• Executes explained
configuration steps
• Receives on demand
support by SAP scenario
expert, if needed
Result:
SAP Solution Manager readiness
 Expert Guided Implementation schedule
Implementation steps in detail

Day 3 Day 4 Day 5

Initial Configuration SAP Basic Configuration SAP Managed System

Solution Manager Solution Manager Configuration (End to End
Root Cause Analyze Tools)
• User Administration • Create Project
• Technical Configuration • Import Note
• Connect Managed System
• SLD Configuration • Installation Check
• Check Prerequisites
• User Data
• Manual Configuration
• Landscape Data
• Diagnostics Configuration
• Manual Configuration
• Wily Introscope Configuration
• Automatic Configuration
• Create Logical Components
• Check the Demo Launch-Pad

© SAP 2010 / Page 8

 Agenda

 Expert Guided Implementation Methodology

 Motivation

 Check of Pre-requisites

 Upgrade EhP1

 Execution of Implementation Steps

(SOLMAN_SETUP)

 Appendix - Information EhP4 for SAP ERP

© SAP 2008 / Page 9

 SAP Solution Manager as Collaboration
Platform

© SAP 2010 / Page 10

 SAP Solution Manager Provides Scenarios for All
Phases of the Application Management Life Cycle
Implementation of Solution Monitoring
SAP  System monitoring
solutions  Business process monitoring
 SAP methods & tools  Central system administration
 Global rollout  Solution reporting
 Customizing sync.  Service Level reporting
 E-learning mgmt.  SAP EarlyWatch Alert
CORE
 Test management
BUSINESS
Upgrade of PROCESSES Service Desk
SAP solutions  Best Practices for
messaging
 SAP methods & tools
 Integration of 3rd-party
 E-learning mgmt. help desks
 Test management

Root Cause
Change Request
Analysis
Management  Safe remote access
 Follows ITIL standards Delivery of  Performance measurement
 Maintenance processes SAP Services  Logs and Dumps
 Onsite/remote delivery  Traces
 Issue Management  Technical configuration
© SAP 2010 / Page 11
 SAP Solution Manager Provides Scenarios for All
Phases of the Application Management Life Cycle
Implementation of Solution Monitoring
SAP  System monitoring
solutions  Business process monitoring
 SAP methods & tools  Central system administration
 Global rollout  Solution reporting
 Customizing sync.  Service Level reporting
 E-learning mgmt.  SAP EarlyWatch Alert
CORE
 Test management
BUSINESS
Upgrade of PROCESSES Service Desk
SAP solutions  Best Practices for
messaging
 SAP methods & tools
 Integration of 3rd-party
 E-learning mgmt. help desks
 Test management

Root Cause
Change Request
Analysis
Management  Safe remote access
 Follows ITIL standards Delivery of  Performance measurement
 Maintenance processes SAP Services  Logs and Dumps
 Onsite/remote delivery  Traces
 Issue Management  Technical configuration
© SAP 2010 / Page 12
 Focus of Expert Guided Implementation
during this week

Enable root
cause analysis

Enable Delivery of
Prerequisite:
SAP Services
Productive
running SAP
Solution Enable system landscape
Manager documentation

Check basis
configuration

Update SAP
Solution Manager

Configuration Managed
Connect
Upgrade EhP1 Setup System System
to SAP
Landscape Configuration

© SAP 2010 / Page 13

 Agenda

 Expert Guided Implementation Methodology

 Motivation

 Check of Pre-requisites

 Upgrade EhP1

 Execution of Implementation Steps

(SOLMAN_SETUP)

© SAP 2008 / Page 14

 Important Information

Ensure that you read the following SAP Notes before starting the upgrade:
 1169247 - Additional info for Solution Manager 7.0 EHP1 update
 1142832 - Installation Enhancement Package 1 for Netweaver 700
 Please also verify the prerequisites for the Managed Systems to be connected in
Diagnostics listed in SAP Note 1274287.

Tips:
 You can upgrade your SAP Solution Manager directly to EhP1 from Stack 17. Otherwise,
if you are at < Stack 17, upgrade your Solution Manager system to Stack 17 first and then
perform another upgrade to EhP1.

 Be sure to de-schedule the "LANDSCAPE FETCH“ job before the upgrade to EhP1
 Implement SAP Notes 1155107 and 1256384 to avoid ABAP generation errors
during upgrade
 Define 5 parallel R3trans processes in SAINT in the Extra --> Settings menu

The following guide has information on planning, preparing, and updating to SAP Solution
Manager 7.0 EHP 1, including OS specific information:

http://service.sap.com/instguides --> SAP Components --> SAP Solution Manager 

Release 7.0 EHP 1  Upgrade
 Update to SAP Solution Manager 7.0 EHP 1 Using SAINT/JSPM
© SAP 2010 / Page 15
 Check of Pre-requisites

Service & Support

For the comunication of your Solution Manager Backbone
with SAP Backbone please ensure that the
following pre-requisites are fulfilled

© SAP 2010 / Page 16

 Check of Pre-requisites
RFC Connection to SAP

Transaction: SM59
You can check the connection to SAP with Utilities  Test  Authorization Test for the
RFC SAPOSS in transaction SM59. This will do the connection test using the user and
password that was assigned to the RFC.

The SAPOSS RFC should

have the Logon Load
Group EWA

The User / Password is

always OSS_RFC / CPIC
© SAP 2010 / Page 17
 Check of Pre-requisites
RFC Connection to SAP

Transaction: OSS1

If you have problems with the connection

test of SAPOSS you can check and maintain
settings for the connection in transaction
OSS1. The RFC SAPOSS will be adapted
automatically after change of configuration in You can find detailed information about
OSS1. transaction OSS1 and RFC connection
SAPOSS in SAP Note 33135. For
troubleshooting see SAP Note 24177.

© SAP 2010 / Page 18

 Check of Prerequisites
S-User Authorizations

URL: http://service.sap.com/user-admin

You can check the authorization objects of your Solution

Manager S-user with the “Authorisation reports“. Please
ensure that your S-user have at least the marked
authorisation objects.
Further information about the S-user and authorizations can be
found in SAP Note 1041351
© SAP 2010 / Page 19
 Check of Pre-requisites
Required Users

 SAP Solution Manager server user (<SID>adm) for upgrading the kernel and WebAS
Java with JSPM
 User for configuration with administrative authorization (authorization like DDIC, please do
not use the DDIC user itself)
– For client 000
– For productive Solution Manager client
– For BI client

© SAP 2010 / Page 20

 Check of Prerequisites (5 of 5)
SAP Media for Upgrade available

Software Components:
1. SPAM/SAINT version should be a minimum release of 39
2. Kernel upgrade
3. Java files
4. ABAP files

Where to find:
All Files can be download from the SAP Service Market Place.
The following slides describe one method of getting all the
required files.

Please follow also SAP Note 1169247 for further (actual)

information for Upgrading on EhP1

© SAP 2010 / Page 21

 Download from the Service Marketplace
SPAM / SAINT download of version 40

Start in your browser the SAP Service Marketplace: http://service.sap.com/swdc

Logon with your administration S-User for the SAP Solution Manager
Navigate in the right navigation pane to „Support Packages and Patches“
Navigate in the left navigation tree to „Entry by Application Group“
In the main frame you will get a new navigation frame where you should select as
following:
 Additional Components  SAP SPAM/SAINT UPDATE  SPAM/SAINT UPDATE 700
Add the package SAPKD70040 to your download basket. In case of an upgrade to
Version 40, a maintenance certificate is needed. For more information about this topic
please refer to http://service.sap.com/maintenancecertificate
Approve the download with the Maintenance Optimizer of your SAP Solution Manager

© SAP 2010 / Page 22

 Software Download from the Service
Marketplace (1 of 5)

Use the Maintenance Optimizer to download the kernel, Java, and ABAP components
together:

 Start in your Browser the SAP Service Marketplace software download center
http://service.sap.com/swdc
 Logon with your administration S-User for the SAP Solution Manager
 From the left hand pane, navigate to Download  Support Packages and Patches 
Entry by Application Group
– In the main frame you will get a new navigation frame where you should select as
follows:  SAP Technology Components  SAP SOLUTION MANAGER  SAP
SOLUTION MANAGER 7.0  Support Package Stacks

Ensure that your S-user has all of the required authorizations or some files
may be missing from the Stack Download!

© SAP 2010 / Page 23

 Download from the Service Marketplace

1. Select target stack SAP Solution Manager 7.0 EHP1 – 25

2. Select your SAP Solution Manager source stack
3. Click Next Step

Example:

© SAP 2010 / Page 24

 Download from the Service Marketplace

4. Expand the entry for SAP Kernel 7.01 which fits for your system architecture and make a
selection for your operating system (SAP Solution Manager ABAP and Java Stack)
5. Expand the entry for SAP IGS 7.00 and make a selection for your operating system.
6. Then check the OS-independent and the database relevant checkboxes according to your
operating system.
7. Click Next Step to continue

© SAP 2010 / Page 25

 Download from the Service Marketplace

All the Java and ABAP Support Packages are displayed and selected by default.
This listing needs to be saved as a xml file for the Java Support Package Manager.
Therefore, click the button Save as File

© SAP 2010 / Page 26

 Download from the Service Marketplace

Save the table as an XML file. This file is required for the Support and Enhancement
Package option of Java Support Package Manager. This option uses the configuration
file, whereas the option Business Packages cannot process this file.

Save this file in your global

EPS Inbox directory
/usr/sap/trans/EPS/in

Next, add all the files to your download basket, then approve the files in the Maintenance
Optimizer and download them to /usr/sap/trans

© SAP 2010 / Page 27

 Software Download with SAP Solution
Manager Maintenance Optimizer

Demo:
Software Download with SAP Solution Manager Maintenance Optimizer

© SAP 2010 / Page 28

 Software Download from the Service
Marketplace

After downloading the files as shown in the preceding slides, you will have all the files
required for updating your SAP Solution Manager to the latest EhP1

 SPAM/SAINT
 IGS and kernel files
 Java files
 ABAP files

Kernel Upgrade
Please also download the actual C++ Runtime
Library for the Kernel in case of Windows
Operating System.

Update the C++ Runtime Library before

starting the Upgrade procedure.

For more information please refer to SAP Note

684106

© SAP 2010 / Page 29

 Agenda

 Expert Guided Implementation Methodology

 Motivation

 Check of Pre-requisites

 Upgrade EhP1

 Execution of Implementation Steps

(SOLMAN_SETUP)

 Appendix - Information EhP4 for SAP ERP

© SAP 2008 / Page 30

 SMD Agent Connectivity to Solution Manager
Diagnostics

If you already use SAP Solution Manager Diagnostics productively, please set in the
Agent Administration the Maintenance Mode option to “On” . (Before the Java
Upgrade) This option will disconnect the SMD Agents.

© SAP 2010 / Page 31

 Solution Manager Upgrade to EhP1

The steps we will use to update Solution Manager to EhP1 are as follows:

 Use JSPM to update the IGS, kernel, and Java components together
 Use transaction SPAM to update SPAM / SAINT to version 40
 Use transaction SAINT to update the ABAP Stack

The following slides will show this procedure

© SAP 2010 / Page 32

 WebAS Kernel and Java Upgrade with Java
Support Package Manager

The JSPM is a SAP tool based on the Software Deployment Manager (SDM). The JSPM
enables administrators to deploy (upgrade) the WebAS Java. Start JSPM on the SAP Solution
Manager at \usr\sap\<SID>\DVBMGS**\j2ee\JSPM\<executable, e.g., go.bat>

Guidance for Upgrade of WebAS Java:

1.The IGS kernel, the kernel, java files (SCA and JAR), and the xml file that were downloaded
need to be in the /EPS/in directory. You do not have to uncar the kernel files.
2.Start on the local Server the JSPM of the SAP Solution Manager 
\\<server>\sapmnt\<SID>\DVBMGS**\j2ee\JSPM the appropriate executable, e.g., go.bat
3.Update JSPM first using the below option

© SAP 2010 / Page 33

 WebAS Kernel and Java Upgrade with Java
Support Package Manager

4. Next, select the option

to apply a support and
enhancement package
stack

5. Upon continuing, you will

see the product version
and target stack
EhP1 SP25 in the queue

© SAP 2010 / Page 34

 Kernel and Java Upgrade with JSPM

Validation

© SAP 2010 / Page 35

 Kernel and Java Upgrade with JSPM

Note that the Kernel will be updated first followed by the java stack components.
The J2EE engine will be restarted during the deployment

© SAP 2010 / Page 36

 Kernel and Java Upgrade with JSPM

When the deployment finishes both the kernel and the Java stack will be
at the target levels.
© SAP 2010 / Page 37
 WebAS Kernel and Java Upgrade with Java
Support Package Manager

Demo:
WebAS Kernel and Java Upgrade with Java Support Package Manager

© SAP 2010 / Page 38

 WebAS ABAP Upgrade with SPAM/SAINT
SPAM / SAINT Update

SPAM/SAINT
 A SPAM/SAINT Update (SPAM update for short) contains updates and improvements to
Support Package Manager and Add-On Installation Tool. There is always one SPAM update
for each release. To find out which version you are using, look at the following in your system:
 The short description, for example SPAM/SAINT update - version <REL>/0001
 The package name, for example SAPKD<REL>01
 The latest SPAM update is also available in SAP Support Portal, under
http://service.sap.com/spManager

Prerequisites:
 You can only import a SPAM update if there are no terminated packages in the system. A
dialog box informs you if there are any terminated packages. You then have two options:
 Start with the import of the entire queue and perform the SPAM update afterwards.
 Delete the queue, import the SPAM update and finally calculate and import the actual
queue.

© SAP 2010 / Page 39

 WebAS ABAP Upgrade with SPAM/SAINT
SPAM / SAINT Update (2 of 3)

Guidance for SPAM / SAINT Update:

1. Call Support Package Manager (transaction SPAM).
2. Upload the Update Package on the SAP SOLUTION MANAGER
3. Check if the SPAM update offered is newer than the one in your system.
4. To import the most recent SPAM update, choose Support Package  Import SPAM update.
5. SPAM updates are automatically confirmed once they have been imported.

© SAP 2010 / Page 40

 SPAM / SAINT Update (3 of 3)

© SAP 2010 / Page 41

 SPAM / SAINT Update

Demo:

© SAP 2010 / Page 42

 ABAP Stack Upgrade with SAINT
Uncar the files

Prerequisite: The files from the Stack Download are in /usr/sap/trans

Uncar the SAR and CAR file in the /usr/sap/trans directory. This will place them in the
/usr/sap/trans/EPS/in directory where they can be accessed by SAINT

Example in Windows OS:

>cd G:\usr\sap\trans
>sapcar -xvf “*.SAR”
>sapcar -xvf “*.CAR”

Please note that the double-quotes are required!

The result is that all the necessary files for the SAINT upload are available in
/usr/sap/trans/EPS/in directory

© SAP 2010 / Page 43

 ABAP Stack Upgrade with SAINT

Be sure to de-schedule the "LANDSCAPE FETCH“ job before the upgrade to
EhP1

 Implement SAP Notes 1155107 and 1256384 to avoid ABAP generation errors
during upgrade

 Define 5 parallel R3trans processes in SAINT in the Extra  Settings menu

© SAP 2010 / Page 44

 WebAS ABAP Upgrade
- Upload the Upgrade Packages (2 of 6)

Execute SAINT in the SAP Solution Manager and upload the files

SAINT is required for the EhP1 upgrade. (Upgrade from SP17 to EhP1 SP 18 or higher)
If you are upgrading to a prior level first, e.g. from SP 15 to SP 17, then you need to use
SPAM.

Upload the OCS Packages from

the transport directory into the
inbox of the SSM

© SAP 2010 / Page 45

 WebAS ABAP Upgrade
- Define the Upgrade Queue (3 of 6)

1 Select all the components that

have to be upgraded for EhP1.
(You can use the Selection for
all)
When you go on further to the
next step you will be asked if
you are sure to upgrade
manually. Please confirm this
with YES.

2
Define in the next
section the Upgrade
queue. Please choose
all EhP1 involved
objects. (See Slide six
for more information).

© SAP 2010 / Page 46

 WebAS ABAP Upgrade
- Confirm Queue for Upgrade (4 of 6)

3
The Systems checks the
defined import queue for
consistency. Add named
absentee Packages if
needed and restart the
check. When everything
is consistent you are
able to go on

4
Confirm that you have
read the SAP Notes:
- 1169247
- 1142832
-939897
-by entering the
passwords that are
contained in the notes.

© SAP 2010 / Page 47

 WebAS ABAP Upgrade
- Start ABAP Upgrade (5 of 6)

5
Decide in which mode
you wish to run the
upgrade.

© SAP 2010 / Page 48

 WebAS ABAP Upgrade
- Completion of the Upgrade (6 of 6)

6
In Import Phase two the System will ask
you to restart the System. So confirm this
and trigger a restart of the SSM.
When the System is online again start
again the Transaction SAINT in client 000
and continue with Upgrade process. Just
confirm your execution mode.

© SAP 2010 / Page 49

 WebAS ABAP Upgrade

Demo:
WebAS ABAP Upgrade

© SAP 2010 / Page 50

 Additional Information
- Approximate timings

The following are the approximate timings for the following upgrades:

 Stack 15 – 17 Kernel and Java Stack upgrade: 1 – 2 hours

 Stack 15 – 17 ABAP Stack upgrade: 2 - 4 hours

 Stack 17 to 22 Kernel and Java Stack upgrade: 1 – 2 hours

 Stack 17 to 24 ABAP Stack upgrade: 10 - 12 hours

 SGEN after the upgrade to EhP1: 5 – 7 hours

© SAP 2010 / Page 51

 Execution of Day 1 Activities

 Check RFC connection “SAPOSS”

 Check the authorization on SAP service
marketplace for your Solution Manager S-user
 Download the SAP Media for the Upgrade from the
SAP Service Market Place
 Update the WebAS kernel, Java Stack and ABAP
Stack of the SAP Solution Manager 7.0 to EhP1

© SAP 2010 / Page 52

 Expert Guided Implementation
- Forecast

Day 2

 Check for successful upgrade

 Verification Wily Products
 SOLMAN_SETUP prerequisites

To avoid problems with the next steps it is

important that all points from today are
implemented carefully in your system

© SAP 2010 / Page 53

 Questions

© SAP 2010 / Page 54

 Thank you!

© SAP 2008 / Page 55