Preparing your Solution Manager

7.2 for upgrade

Dale Beistel
NIMBL
TOPICS

• Solution Documentation has been completely rebuilt in

Solution Manager 7.2
• How can I prepare my system for the upgrade to 7.2
• Logical Components become Logical Component Groups –
how will this impact me?
• What will I need to do after the upgrade to Solution Manager
7.2?
RECOMMENDED PROCEDURE
Preparation Upgrade Content
Activation
•SolDoc Content •Technical •Post-processing
Activation Upgrade to SAP activities on SAP
Preparation on Solution Solution
SAP Solution Manager 7.2 Manager 7.2
Manager 7.1 •Execution of
SOLMAN_SETUP

Source: SAP
SAP recommends to prepare the Content Activation on your up-and-running SAP Solution Manager 7.1 system. This can
be done at any point in time and does not affect your productive environment in any way. After the preparation, the
technical upgrade to release 7.2 is followed by post-processing Content Activation activities in SAP Solution Manager
7.2.
ALTERNATE PROCEDURE
Upgrade Preparation Content
Activation
•Technical •SolDoc Content •Post-processing
Upgrade to SAP Activation activities on SAP
Solution Preparation on Solution
Manager 7.2 SAP Solution Manager 7.2
•Execution of Manager 7.2
SOLMAN_SETUP

Source: SAP
BEFORE YOU UPGRADE

• Install two important SAP notes

– 2161244 – Installs report to help you analyze your projects
– 2324520 – Installs guided procedure for PREPARE_ACTVATION
• Re-execute your Solution Manager sizing
– http://service.sap.com/sizing-solman
• Plan for JAVA stack split
– New database instance
• Plan for TREX or use HANA Enterprise Search
ANALYZING PROJECTS
LOGICAL COMPONENT GROUPS

• Shared between Solution Documentation & CHARM

• No longer product version specific
– No need to create new logical component during upgrades
– DEV BW 7.4, QA BW 7.31, PRD BW 7.31
BIGGER PICTURE
CONTENT ACTIVATION – PRE UPGRADE
CONTENT ACTIVATION – POST UPGRADE
LEVERAGE SOFTWARE UPDATE MANAGER

• Plan your upgrade with Maintenance Planner

– Maintenance Optimizer does not support 7.2 upgrade
– Make sure your LMDB information is correct!
• Utilize single system mode – avoid shadow system create
– Downtime minimized is available – if you need it
– Total processing time reduced with single system mode
• Typical upgrade process is 4-5 days of preprocessing
– No more tan 8-12 hours downtime
– When you lock repository – SOLAR01/SOLAR02 are locked
TECHNICAL ACTIVITIES

• Verify all SPAU and SPDD Modifications have been completed

and are in a green status.
• Verify you don’t have any inactive objects within your Solution
Manager system, via transaction SE80.
• Release all Transports within your Solution Manager system.
To ensure no objects are locked.
• Update your SLD and check out SAP Note 1817310 - Double
Stack System automatic move functionality
SAP WEB DISPATCHER
• Splitting the dual stack can require the need of a SAP Web
Dispatcher to handle the communication between Solution
Manager and other applications.
• A web dispatcher is only required for the following reasons.
– The ABAP stack and Java stack are running on separate hosts.
– The Java stack was configured to use different ports.
– Solution Manager has multiple ABAP and Java application servers.
• If a web dispatcher is required, be sure to configure the connection
within transaction SOLMAN_SETUP under the Infrastructure guided
procedure. Step 2.1 – Define HTTP Connectivity
POST UPGRADE

• Update the SNOTE with SNOTE 

– SAP Note 1668882
• Execute SOLMAN_SETUP
– Basic Config
– System Prep
– Managed System Config
• Upgrade your SAP Host Agents
– You need to do it anyways – used by SUM in the future.
CONTACT ME

Dale Beistel
dale.beistel@benimbl.com
http://benimbl.com
FOLLOW US

Thank you for your time

Follow us on at @ASUG365