Upload
daniel-wood
View
138
Download
2
Tags:
Embed Size (px)
Citation preview
ASUG INSTALLATION MEMBERMEMBER SINCE: 2001
LORI NORMAN[ASUG INSTALLATION MEMBER MEMBER SINCE: 2004
GLENN WINTER[ASUG INSTALLATION MEMBER MEMBER SINCE: 1998
DIANE MOREHOUSE[
]Configuring and Using
the Maintenance Optimizer
[Dan McKay, Alpha Sirius Inc.
May 6, 2008
[
2
In This Session, you will . . .
Learn about the Maintenance Optimizer in SAP Solution Manager 7.0, the new tool for downloading maintenance updates for SAP NetWeaver 7.0 applications.
Obtain a step-by-step guide to the technical configuration process to set up the Maintenance Optimizer.
Gain insight into why it’s best and simplest to implement ST-ICO along with the latest support package stack before beginning to set up the Maintenance Optimizer.
See how to use the Maintenance Optimizer to download, for example, Support Package Stacks.
Discover how to upgrade your Solution Manager’s support package stacks to the highest available level before starting to configure the Maintenance Optimizer.
[
3 33
What We’ll Cover …
SAP’s April 2, 2007 announcement and its implications
Prerequisites to Maintenance Optimizer configuration
Evolution of M.O. configuration, via SP Stacks
Defining a solution Configuring M.O. Demo: Using M.O. to download SP stacks Wrap-up
[
4
SAP’s Announcement on Service Marketplace
Maintenance Optimizer (M.O.) has been required for more than a year now.
“All corrective software packages, including Support Packages (Stacks) for SAP NetWeaver 2004s and subsequent versions, as well as all applications which are based on this software, will be available exclusively through the Maintenance Optimizer in SAP Solution Manager as of April 2, 2007.”
[
5
Improvements Provided by M.O.
Maintenance Optimizer provides the following benefits:
An end-to-end process for maintaining all your SAP landscapes.
Centralized place for planning and implementing all maintenance-related activities.
Greater automation and transparency of operations processes to increase efficiency of the operations team and reduce costs.
ITIL-compliant standardized and streamlined support processes that facilitate preparation for Enterprise Service Oriented Architecture.
[
6
Improvements Provided by M.O.
[
7
Improvements Provided by M.O.
[
8
What Does this Mean?
M.O. is SAP’s new M.O.
[
9
What Does this Mean?
M.O. (Maintenance Optimizer)is SAP’s new
M.O. (modis operandi)
for downloading corrective software
[
10
SAP Download Manager Is Still Required
[
11
You’ll Still Add Items to Your Download Basket
[
12
Support Package Considerations
The core Maintenance Optimizer functionality is contained in ST (SAP Solution Manager Tool) Support Package (SP) 9 - SAPKITL419
However, subsequent SP stacks have delivered more robust functionality that streamlines and simplifies the process of configuring M.O.
[
13
The Legacy Method
Corrective software released before April 2, 2007 can still be downloaded from the Service Marketplace without the Maintenance Optimizer and without assistance from SAP’s Active Global Support team.
[
14 1414
What We’ll Cover …
SAP’s April 2, 2007 announcement and its implications
Prerequisites to Maintenance Optimizer configuration
Evolution of M.O. configuration, via SP Stacks
Defining a solution Configuring M.O. Demo: Using M.O. to download SP stacks Wrap-up
[
15
Security Required for Maintenance Optimizer Users
Role SAP_MAINT_OPT_ADMIN
Authorizations D_SOL_VSBL
Determines which Solution(s) a user sees * CRM_ORD_PR
Enables users to access specific required CRM transaction types
*Maintenance Optimizer users must be able to see at least one Solution
Don't Forget
[Key OSS Notes
1024932 - Maintenance Optimizer: Collective 662441 - SAP Notes for Support Packages 1008717 - HTMLViewer 0950975 - SAP GUI for Windows: Support for
Internet Explorer 7 1022797 - Cannot select product version 990534 - Solution Manager Maintenance Optimizer:
BC Set 1126859 (End-to-End Diagnostics SP15)
Recommendation: Review all new or recently updated Notes in component SV-SMG-MAI.
[
17
Recommendations
First ensure that your Solution Manager system – and the other systems in your SAP environment – have the latest versions of the following: Support Package Stacks (15 now, 16 coming in
June) Service Tools SPAM SAINT SAP Download Manager
Read OSS Note 662441 – Solution Manager: SAP Notes for Support Packages
[
18
Tips to Prevent Timeouts
Ensure that the dynamic parameter rdisp/max_wprun_time at least 3600. Otherwise, your SPAM or SAINT import process may time out.
Also make sure you have the latest version of SPAM. Click on the “Info” link for each support package in the “Download” area in Service Marketplace to see which SPAM patch level is required. Here you will also see other dependencies such as possible kernel patch levels, etc.
[
19
A Sure Sign That Something is Missing
Initially, until you apply all the required support packages and Notes, trying to configure the Maintenance Optimizer via SPRO will generate the following error: DBIF_RSQL_INVALID_REQUEST
GOTCHA!
[
20
A Sure Sign That Something is Missing
[
21
What to Do If You Want Service Pack Stack 15 Before You Set up M.O.?
If urgently required, you can create a customer message in SAP Service Marketplace and request that SAP release the required items from your download basket!
Select component SV-SMG-MAI-APR for this type of message
[
22 2222
What We’ll Cover …
SAP’s April 2, 2007 announcement and its implications
Prerequisites to Maintenance Optimizer configuration
Evolution of M.O. configuration, via SP Stacks
Defining a solution Configuring M.O. Demo: Using M.O. to download SP stacks Wrap-up
[
23
Evolution of M.O. Configuration, via SP Stacks
Support Package 9 (ST 400 SP09) Transaction SPRO
SAP Reference IMG SAP Solution Manager Implementation Guide SAP Solution Manager Basic Settings Set Up Maintenance Optimizer
Refer to OSS Note #990534 Call SM_PREP_MAINTENANCE_OPTIMIZER
(in SE38), a program provided in OSS Note #990534
[
24
Evolution of M.O. Configuration, via SP Stacks (cont.)
Support Package 10 (ST 400 SP10+)
[
25
Evolution of M.O. Configuration, via SP Stacks (cont.)
[
26
Evolution of M.O. Configuration, via SP Stacks (cont.)
Support Package 13 (ST 400 SP12+) with Standard Configuration
[
27
M.O. Configuration Recommendations
Always prepare your system with the latest available Support Package stacks, service tools, SPAM, SAINT, and Download Manager to streamline your setup
The latest available installation kit for Solution Managerr 7.0, SR3, includes Support Package Stack 12
Additional features (e.g., M.O. setup via wizard) are delivered in SP Stacks 13 and 15.
Personal recommendation Before starting, put SP Stack 13-15 in your
download basket and open a customer message to request its release Remember to open the message in component
SV-SMG-MAI-APR!
[
28
An Important Consideration
If you’ve got Java stacks in your SAP environment, you want at least SP Stack 13, because this delivers CTS+ (for both ABAP and Java support packages)
[
29 2929
What We’ll Cover …
SAP’s April 2, 2007 announcement and its implications
Prerequisites to Maintenance Optimizer configuration
Evolution of M.O. configuration, via SP Stacks
Defining a solution Configuring M.O. Demo: Using M.O. to download SP stacks Wrap-up
[
30
Create a Solution
Transaction: solution_manager Alias: DSWP
If you haven’t defined any solutions yet, now is the time to do so.
This is a prerequisite for using the Maintenance Optimizer you’ve set up.
[
31
Create a Solution
[
32
Create a Solution
Problem Unable to create a new solution
How to solve it If you’re having trouble viewing the
solution, apply Note #1008717
GOTCHA!
[
33
Create a SolutionGo to System Landscape Maintenance
[
34
Create a SolutionTransaction Code (DSWP)
[
35
Create a SolutionSelect ‘New’ for a New Solution
[Create a SolutionProvide a Name
for the Solution
[
37
Create a SolutionLandscape Maintena
nce’
[
38
Create a Solution Landscape in SMSY
[
39 3939
What We’ll Cover …
SAP’s April 2, 2007 announcement and its implications
Prerequisites to Maintenance Optimizer configuration
Evolution of M.O. configuration, via SP Stacks
Defining a solution Configuring M.O. Demo: Using M.O. to download SP stacks Wrap-up
[
40
Define Service Marketplace users
Before you can use M.O. with your solution, you must define users in your organization who are authorized to do so.
Requirements A valid S-Number in the SAP Service
Marketplace. Download authorization.
Note: M.O. users can now be defined through the IMG.
[
41
Define Service Marketplace Users
[
42
Define Service Marketplace Users
See the following Notes about S-Users: 1082010 1140822 1112983
Use S-Numbers, without the initial “S000,” for the Contact Person column entries
Truncate users’ S--Numbers
[
43
Define Service Marketplace Users
Tip: Always log on to the SAP Support Portal with the same S-User assigned to your Solution Manager user.
If you don’t, M.O. won’t be able to confirm and approve any files you place in that S-User’s Download Basket!
[
44
Define Service Marketplace Users
[
45
Launching the M.O. Configuration
Two choices: A. Execute IMG activity "Set Up
Maintenance Optimizer” B. Call transaction SM_MOPZ.
[
46
Launching the M.O. Configuration
With all pre-requisites met, and if everything goes right, the following message will appear about five minutes after clicking on the “Yes” button:
SAP MOPZ auto-configured
Congratulations!
[
47
Set up the SAP-OSS RFCNot the same as your existing SAPOSS RFC
Note: this is SAP-OSS,not the existing SAPOSSconnection!
[
48
Set up the SAP-OSS RFC Connection, and test it.
Test your new SAP-OSS connection
[
49
Using the Maintenance Optimizer
Once configured, you can begin to download support package stacks and other corrective software through this new interface
SAP Service Marketplace and the SAP Download Manager remain part of the process
[
50 5050
What We’ll Cover …
SAP’s April 2, 2007 announcement and its implications
Prerequisites to Maintenance Optimizer configuration
Evolution of M.O. configuration, via SP Stacks Defining a solution Configuring M.O. Demo: Using M.O. to download SP
stacks Wrap-up
[
51
All Set Up, Now Let’s Use It!Select your Solution
[
52
Step 1 - Plan Maintenance
Click on the icon to the right of “Not Selected” to bring up the list of your target system products.
[
53
Step 1 - Plan Maintenance
Place a checkmark to the left of the system for which you are downloading corrective software.
[
54
Select Files
When the Maintenance Optimizer starts, select the appropriate product and version
Select “Save” “Procedure xxxxxx Saved” appears in the
status bar at the bottom of the page
[
55
Step 2 - Select Files by Product, Version
[
56
Step 2 - Select Files by Product, VersionClicking on the “Select Files” button produces the familiar SAP Service Marketplace pop-up.
[
57
Step 2 - Select Files by Product, VersionOnce Authenticated, select “Support Package Stacks”
[
58
Step 2 - Select Files by Product, Version
[
59
Step 2 - Select Files by Product, Version
[
60
Step 2 - Select Files by Product, Version
[
61
Step 2 - Select Files by Product, Version
[
62
Step 2 - Select Files by Product, Version
[
63
Step 2 - Select Files by Product, Version
[
64
Step 3 – View and Select Downloadable Support Packages
[
65
Select Support Package Stacks to Be Downloaded
[
66
Select Support Package Stacks to Be Downloaded
[
67
Select Support Package Stacks to Be Downloaded
[
68
Step 3 – Download Files
[
69
Select Support Package Stacks to Be Downloaded
[
70
Select Support Package Stacks to Be Downloaded
[
71
Select Support Package Stacks to Be Downloaded
[
72
Step 4 – Perform Implementation
[
73
Step 4 – Perform Implementation
[
74
Select Support Package Stacks to Be Downloaded
[
75
If you want to return later, click on “Yes.”
[
76
Upon returning to the M.O. screen, click on “Refresh.”
[
77
Important Information about SP 15
Before you can import all Support Packages from Stack 15, you must upgrade software component ST-SER to the current release using transaction SAINT.
Find installation and upgrade packages on the SAP Service Marketplace: http://service.sap.com/swdc, search all categories, with search term “SAPKITLONB.”
[
78
More Important Information about SP 15
Implement Note 1128026 to your Solution Manager system after loading ST 400 SP15 (SAPKITL425). The note correction is valid for SAP_ABA 700 SP 14 (SAPKA70014) required by SP15 and part of the stack. This correction is necessary to work within service sessions. – OSS Note 662441
[
79
Once you’re done with support packages, click on “Complete Transaction.”
[
80 8080
What We’ll Cover …
SAP’s April 2, 2007 announcement and its implications
Prerequisites to Maintenance Optimizer configuration
Evolution of M.O. configuration, via SP Stacks
Defining a solution Configuring M.O. Demo: Using M.O. to download SP stacks Wrap-up
[
81
What Lies Ahead for the Maintenance Optimizer?
Q: With the Maintenance Optimizer now required for current NetWeaver corrective software, will the SAP Download Manager ever go away?
A: Although SAP often embeds the functions of standalone products into core products, the current architecture in 4.0 continues to rely on the familiar SAP Service Marketplace and the SAP Download Manager.
[
82
A Key Point to Remember
For getting these essential items Support package stacks, Service tools, SPAM/SAINT etc.
M.O. is the way to go!
[
83
Resources
SAP Service Marketplace http://service.sap.com/solman-mopz
Solution Manager Online Knowledge Products (OKPs) http://service.sap.com/solutionmanager
Training
• SAP Tutors "Request SAP Tutor" leads to the order page.
[
84
Resources
OKPs: http://service.sap.com/solutionmanager Training E-Learning Solution Manager 7.0
[
85
7 Key Points to Take Home
SAP requires Maintenance Optimizer for “all corrective software . . . as of April 2, 2007.”
M.O. is an ITIL-compliant centralized tool to facilitate technical support in distributed systems.
Configuration is much simpler on SP 15 than on SP 9.
Once configured, M.O. is easy to use. M.O. process includes familiar SAP Service
Marketplace and Download Basket steps. M.O. is not used to download kernel upgrades. You can still download support package stacks, etc.,
without M.O., but it requires intervention by SAP.
[
87
] Thank you for participating.