- Sap Solution Manager 7.1 Upgrade Guide
- Sap Solution Manager 7.1 Upgrade Key
- Sap Solution Manager 7.1 Upgrade Tool
- Sap Solution Manager
- Sap Solution Manager 7.1 Upgrade To 7.2
You plan to upgrade to SAP Solution Manager 7.2, but do not know where to start, what to do in which timely order, and where to get help. The goal of this blog is to give you some guidance provided by SAP Enterprise Support Academy for all SAP Enterprise Support and PSLE customers.
To begin, it makes sense to take a glance at what the update will entail overall, and then get some insight on the delta between the old and the new release. Companies using scenarios like Change Request Management, Solution Documentation or Process Management should then prepare for the so-called “Content Activation”. For all companies the technical upgrade should be the next step, followed by the Basic Configuration. Companies using enterprise scenarios mentioned above should then proceed with Content Activation, part two. Upgrade preparations should begin as early as possible.
The purpose of this page to explain in a simple word for how to Install Solution Manager 7.1 and Upgrade it to the latest SP stack SP14. Idea behind to create this page is collect all those fundamental need and compile them together for the convenient of people who is not much aware of the Solution Manager system. Mainstream maintenance for SAP Solution Manager 7.1 ended on. If you are still on SAP Solution Manager 7.1, your support for SAP Solution Manager 7.1 has been automatically switched to Customer-Specific Maintenance with restricted support. This means you will only receive: No Support Packages; Limited technology updates.
To participate in the trainings described in the following passages you need to register to SAP Learning Hub. Click here for more information.
Step 1: Overview and Delta between 7.1 and 7.2
Join the meet the expert (MTE) session SAP Solution Manager 7.2: Installation, Upgrade and Maintenance. You will receive recommendations and best practices to prepare for your upgrade. You will get a detailed overview on the recommended and necessary steps you will need to take – the procedure, tools, stack split, SAP HANA migration (optional), and scenario-dependent activities.
Step 2: Prepare Content Activation
Customers using scenarios like Change Request Management, Solution Documentation or Process Management should join the expert-guided implementation (EGI) session SAP Solution Manager in the SAP CAL for Content Activation. Participants can test the one-time content activation procedure to evaluate how their solution documentation will appear in the new 7.2 system. Best of all, through power of cloud infrastructure they can restore the system to a previous state easily and repeat the activation process as many times as necessary.
The purpose of this EGI is to understand the content activation impact for all effected SAP Solution Manager 7.1 functionalities. Furthermore, participants are able to test and evaluate the content activation process for solution documentation, that moves SAP Solution Manager 7.1 content into the new 7.2 solution documentation UI after an upgrade.
The delivery demonstrates how customers save 7.1 solution documentation and landscape information to transport files, and then add them to the 7.2 system in SAP CAL.
Step 3: Technical Upgrade
Before joining the EGI session Technical Upgrade to SAP Solution Manager 7.2, you should read the Master Guide for SAP Solution Manager 7.2 and make sure that you fulfill the technical prerequisites.
The 5-day session will cover the complete process from download to preparation and will conclude with the upgrade. Topics are system preparation, download and usage of tools, such as Software Update Manager (SUM), and guiding you through all roadmap steps from initialization through extraction, preprocessing, and execution.
Step 4: Basic Configuration
To support you in your basic configuration, SAP offers the 5-day EGI session Basic Configuration for SAP Solution Manager 7.2. This has been designed primarily for new installations. In the case of an upgrade, not all parts of the EGI may be needed. The goal of this session is to have customer’s SAP Solution Manager ready for productive usage, including the configuration of root cause analysis. An SAP expert explains all configuration steps and guides the participants through the configuration process. The requirements are listed here.
Step 5: Content Activation, Part 2
In step 2, companies using the scenarios mentioned above performed the steps SAP recommends them to realize in release 7.1. Now they perform the final steps of content activation, which already have been demonstrated in the Content Activation EGI described in step 2.
Further information
- Brand new tutorial: Transition to SAP Solution Manager 7.2 to get familiar with the upgrade strategy and scenario-specific upgrade information
- PDF-based tool to guide you through the transition details: Transition to SAP Solution Manager 7.2: All You Need to Know
- Blog: Have you migrated your SAP Solution Manager already to release 7.2?
- Lifecycle Management Value Map, section SAP Solution Manager Setup
The exercise was completed on below environments,
• Windows Server 2012 64 bit
• Microsoft SQL Server 2012 64 bit
• Solution Manager 7.1 Dual Stack (ABAP & JAVA)
So, our aim is to upgrade the Solution Manager 7.1 to the latest support package stacks available in the SAP Service Marketplace. In this example, we are going to implement support package stack upgrade from SPS04 to SPS08.
Sap Solution Manager 7.1 Upgrade Guide
Before we begin, you need to download the necessary media files as below,
• Software Update Manager (SUM) 1.0 SP09 Patch 2 or higher
• The latest SAP Solution Manager 7.1 stack kernel
• The latest SAP Solution Manager 7.1 ABAP stack
• The latest SAP Solution Manager 7.1 Java stack
Launch the Software Update Manager and enter the username and password. Click OK.
1. The Welcome screen of Software Update Manager. SUM will automatically detected any installed SAP system. Click Next.
2. Enter the password of sidadm. Click Next.
3. Select Stack configuration file (XML) and locate the stack file directory. Click Next.
4. Open the SAP Note provided from the installation screen, find the keyword and paste it to this screen. Click Next.
5. The next screen will be the roadmap steps. The roadmap is consists of multiple phases which are Initialization, Extraction, Configuration, Checks, Preprocessing, Execution, Postprocessing and Finalization. You can monitor on each tab, ABAP and Java for the progress in details.
Initialization
5.1 The Initialization roadmap step. Once the step is completed, click Next to start the Extraction roadmap step.
Extraction
5.2 The Extraction roadmap step. During this phase, you will prompted on below requests,
5.2.1 Enter the password of DDIC user for client 000 and OS specific password (SAPServiceSID).
5.2.2 Provide the latest SPAM version to the EPS/in directory.
5.2.3 You may apply some SNOTE(s) if required.
5.2.4 Extraction – Initial Software Extraction completed. Click Next.
Configuration
5.3 Next, the Configuration roadmap step. During the phase, below actions may required,
5.3.1 Tool Configuration. Choose Standard.
5.3.2 User credentials. Enter the password of J2EE_ADMIN and SDM user.
5.3.3 Information gathering. Accept default values.
5.3.4 AS Java Super Admin Credentials. Enter the password of SAP*.
5.3.5 Enter the SAP OS Service Users credentials.
5.3.6 Apply the missing Certificate Revocation List (CRL) Status.
5.3.7 Include Change Request. If you do not want to include, leave the field empty.
5.3.8 Component Status: Review component status. You can ignore this – click Continue.
5.3.9 Modification Adjustment. If no SPAU/SPDD transport request – click Continue.
5.3.10 Configuration roadmap phase completed.
Checks
5.4 The Checks roadmap step. The phase will check the requirements for the SPS upgrade. No manual actions required here. Once this roadmap phase completed, click Next.
Preprocessing
Sap Solution Manager 7.1 Upgrade Key
5.5 Next step is the Preprocessing roadmap step. Some actions required on this phase,
5.5.1 Open Repairs – Locked SAP objects have been found in open repairs, corrections, or transport orders. If these orders are not released, you will not be able to adjust these objects if necessary.
5.5.2 Lock Development Environment. Choose option Lock now.
5.5.3 Perform the listed activities and once all are completed – Select Actions completed.
5.5.4 Perform the transaction log backup.
5.5.5 The roadmap of Preprocessing is completed. Click Next to proceed on Execution roadmap.
Execution
Sap Solution Manager 7.1 Upgrade Tool
5.6 Execution roadmap step. The software update manager now performing the actual update in the system.
5.6.1 Perform a full backup of the database.
5.6.2 End of Downtime. Click Continue.
5.6.3 The Execution roadmap completed.
Postprocessing
5.7 Once the Execution roadmap step is completed. You will be on Postprocessing roadmap phase. This step creates the update evaluation and saves the log files.
5.7.1 If no SPAU transport imported, click Continue. Else, get the ABAP and Functional team to verify the SPAU.
5.7.2 Click Continue.
5.7.3 The Postprocessing roadmap completed.
Finalization
Sap Solution Manager
5.8 At last, the Finalization roadmap step. No critical actions required here. Click Next.
Summary
Sap Solution Manager 7.1 Upgrade To 7.2
6. Finally, the Summary and Evaluation of the Process screen. You will find the information of the upgrade from here. As for feedback, you can answer all the questions provided and send the upgrade overview to SAP. By doing this, we can help SAP to improve the SUM tool usage!