You are on page 1of 11

Best Practice Approach for SolMan 7.

2 Upgrade
TCS Smart Operations for SAP CoE, 2016

| Copyright 2015 Tata Consultancy Services Limited 1


Agenda

1 SolMan 7.2 Upgrade Path

2 Upgrade Preparations

2
SolMan 7.2 Upgrade Path
SolMan 7.2 Upgrade Path
First go through SolMan 7.2 Upgrade Central Note 2227300
If most SolMan areas in use, please check Release Restrictions Note 2194918
You can check SolMan 7.2 Master Guide available on, https://service.sap.com/instguides

Prerequisites Check:
Source version has to be on SolMan 7.1.
It can be upgraded to 7.2 SPS03 from any SPS of 7.1.
Upgrade to SolMan 7.2 SPS03 not possible if components installed = ST-QCA, ST-SPA or ST-OST
(ST-QCA and ST-SPA can be uninstalled Note 1109650)
Check Add-on availability for SolMan 7.2 (Netweaver 7.40)
Plan for stack split option (same host/different, same DB-MCOD/different DB)
Plan to move BPMon on MAI (Monitoring and Alerting Infrastructure), before/after upgrade

Upgrade to SolMan 7.2 contains 3 major steps:


Upgrade Preparation (Content Activation Preparation)
Upgrade Process Using SUM and stack split
Post Upgrade (Content Activation)
Optional Migration to HANA

4
SolMan 7.2 Upgrade
Relevant for all customers:
No CRM issues this time: SAP Solution Manager 7.2 does not contain a new SAP CRM
release. As we only move to a new enhancement package, the impact of the 7.2
upgrade is significantly lower than in the 7.1 upgrade.

If you already adopted the Monitoring and Alerting infrastructure, then you are fine.
Note that business process monitoring based on the Monitoring and Alerting
Infrastructure (MAI) is mandatory in 7.2.

The split of ABAP and Java stacks, and the upgrade to SAP NetWeaver7.40, are
performed with a standard upgrade procedure

Content Activation of Solution Documentation can be prepared well in advance of the


upgrade

5
Upgrade Preparations
SolMan 7.2 Upgrade - Preparation

Upgrade Preparation
Applying Notes as mentioned in Note - 2227300
Content Activation preparation (Tcode PREPARE_ACTIVATION)
Host Agent Upgrade (7.20 or higher)
Wily Upgrade (9.5.6 or higher)
SLD CR Content update to latest
Verify the System Data in Maintenance Planner, any discrepancy has to be resolved by generating (CISI file) Correction of Installed
Software Information and Implementing the system change using this file with SUM.
Generate stack xml file using Planning activity of Maintenance Planner only.
Upgrade to SolMan 7.2 SP03 comes with SAP_UI component upgraded to 750, select 750 for SAP_UI explicitly in Maintenance
Planner.
If TREX is being used, follow Note - 1750162
Check LMDB has correct Product version and system data.
Check if Agents are connection setting is MS/P4 or MS/P4 SSL.
Check all Diagnostic Agents run on JVM 1.6 or higher.
Change Diagnostic Agent authentication policy to Certificate now or after the upgrade, as SolMan 7.2 only supports Agent
connectivity through certificate method.
If Java stack going to be on separate server or on separate DB as a part of the Stack Split process, plan HW accordingly.
SLD Administration -> make sld/active = false

7
SolMan 7.2 Upgrade Preparation Content Activation

8
SolMan 7.2 Upgrade Preparation Content Activation
Preparation for Content Activation:
Understand the concept through Solution Documentation Content Activation Guide, available on
https://service.sap.com/instguides -> SAP Components -> Solution Manager -> 7.2 -> Upgrade
Run report RSOLAR_PROJSOL_OVERVIEW to get details of Solutions and Projects in use, Note - 2161244
Implement the Note - 2324520 - Guided Procedure (7.10) to run Content Activation of Solution Documentation for 7.20 SPS03
This Note will import transaction PREPARE_ACTIVATION, where you can define the scope for content activation to transfer to 7.2
This transaction has wizard with following steps:
1. Scope of Content Activation - Identify sources of content in 7.1 (Identify Projects and Solutions to transfer to 7.2)
2. System Landscape for 7.2 - Design the 7.2 target entities that will receive the 7.1 content (define Logical Component Groups)
3. Target Branches and Remote Sources - Link 7.2 target entities to 7.1 content sources (assign Systems with Branch)
4. Summary - Have a last look at and close your scope definition

9
References
Installation & Upgrade:
https://service.sap.com/~form/handler?_APP=00200682500000002672&_EVENT=DISPLAY&_SCENARIO=0110003587
0000000122&_HIER_KEY=501100035870000015092&_HIER_KEY=601100035870000179416&_HIER_KEY=601100035
870000179443&_HIER_KEY=701200252311000003762&

References:
https://wiki.scn.sap.com/wiki/display/SM/SAP+Solution+Manager+7.2+Content+Activation
http://help.sap.com/solutionmanager72
https://support.sap.com/ekt-solutionmanager
http://scn.sap.com/community/it-management/alm/solution-manager/blog/2016/02/16/solution-manager-72--
installation-and-configuration--i--installations
https://wiki.scn.sap.com/wiki/display/SM/SAP+Solution+Manager+WIKI+-
+Solution+Documentation+and+Implementation
https://www.youtube.com/playlist?list=PLFrwZZeBUtfiJgBrepFlRhZ7PFXayd6Lh (SAP Solution Manager 7.2 What you
need to know)
https://www.youtube.com/playlist?list=PLFrwZZeBUtfiUyYjHlNJiDE81074H7xCv (SAP Solution Manager 7.2 Guided
Demo Tour)

10
Thank You

TCS Smart Operations for SAP CoE,


2016
| Copyright 2015 Tata Consultancy Services Limited 11

You might also like