This blog post introduces a new, simplified upgrade and migration procedure for customers upgrading from SAP Solution Manager 7.1 to SAP Solution Manager 7.2.
Details on SAP Solution Manager 7.2 can be found here.
If you want to upgrade your SAP Solution Manager 7.1 system running on any database to SAP Solution Manager 7.2, you have to consider that SAP Solution Manager 7.2 is based on SAP NetWeaver 7.4.
There, no dual-stack systems are supported any longer.
As a consequence, your existing SAP Solution Manager system has to be split as part of the procedure – that is, the Java part gets extracted into a standalone system, next to the persistent ABAP system.
This is also a good opportunity to migrate your database to SAP HANA or SAP ASE as part of the upgrade project, since all customers with a valid SAP maintenance agreement can use SAP HANA or SAP ASE as database for SAP Solution Manager without additional licensing costs.
The standard procedure, which is documented in SAP Note 2227300, comprises the following basic steps to upgrade your SAP Solution Manager 7.1 system to SAP Solution Manager 7.2 and migrate the database to SAP HANA or SAP ASE:
- Upgrade your SAP Solution Manager system to version 7.2
with the Software Update Manager (SUM). - Perform a Dual-Stack Split with the Software Provisioning Manager (SWPM)
- Migrate your AS ABAP system to SAP HANA or SAP ASE by performing a heterogeneous system copy with the SWPM.
- Migrate your AS Java system to SAP HANA or SAP ASE by performing a heterogeneous system copy with the SWPM.
- Configure your new SAP Solution Manager 7.2 system using SOLMAN_SETUP
With the standard procedure, you also have the option to use SAP Solution Manager 7.2 before the migration to SAP HANA or SAP ASE (for example, to have a separation of concerns or to get two separate downtime windows/an interim phase of production usage).
If you want to do this, you can perform the configuration (using SOLMAN_SETUP) after the
Dual-Stack Split procedure, as depicted below.
However, if you already decided to migrate to SAP HANA or SAP ASE with your new SAP Solution Manager 7.2 and if you do not need the option to use SAP Solution Manager 7.2 before the migration step, there is another technical path, which might be interesting for you:
A simplified upgrade and migration procedure incorporating the Database Migration Option of the SUM and the combined split and migration in SWPM.
The graphic shows an overview of this simplified procedure, which consists of the following basic steps:
1. Upgrade your SAP Solution Manager system to version 7.2 and migrate your AS ABAP system to SAP HANA or SAP ASE in one step with the Software Update Manager (SUM).
Technically, this step is a dual stack upgrade with Database Migration Option (DMO), which efficiently combines system update, Unicode conversion and database migration.
If you want to find out more about DMO, the blog post Database Migration Option (DMO) of SUM - Introduction is a good starting point.
The newly introduced Dual Stack UI of the SUM guides you through the upgrade steps of the ABAP and Java parts of the dual stack, taking care of the synchronization between the ABAP upgrade and the Java upgrade.
The DMO option migrates the ABAP part of the system to SAP HANA or SAP ASE as part of the upgrade, which makes a heterogeneous system copy of the ABAP stack superfluous.
This step has the potential to reduce the business downtime, since the old SAP Solution Manager 7.1 system can be used in parallel while the SUM is already upgrading and preparing the migration of the system.
Parts of the migration can be performed during the uptime processing of the SUM.
The downtime of the SAP Solution Manager system and the switch of the connected agents in the maintenance mode can be delayed until the technical downtime of the ABAP part starts in the SUM.
Additionally, there are several ways to optimize the DMO migration performance, as described in the blog post Optimizing DMO Performance.
Watch the demo video:
The result of the dual-stack upgrade with DMO is an SAP Solution Manager 7.2 dual-stack system with the APAB stack already running on SAP HANA or SAP ASE and the Java part still running on the old database.
Afterwards, a Dual-Stack Split is required, since dual-stack systems are not supported anymore for systems based on SAP NetWeaver 7.4. The Dual-Stack Split will separate the ABAP stack and the Java stack into two SAP Systems.
2. Perform a Dual-Stack Split and migrate your AS Java system to SAP HANA or SAP ASE with the Software Provisioning Manager (SWPM).
The database migration can be done as integral part of the Dual-Stack Split.
The outcome is equivalent to the classic way, where a heterogeneous system copy procedure has to be performed after splitting the dual-stack system into a separate ABAP system and a Java system.
The main benefit here is that there are less steps to perform, which reduces the complexity and the possibility of user errors during the procedure:
a) Export the Java stack from your source database.
Watch the demo video:
b) Install a new Java system on the target database using the export file you just created.
Watch the demo video:
c) Remove the Java stack from the old dual-stack system on the source database.
The removal of the Java stack is part of the follow-up activities, which are described in the
Dual-Stack Split Guide, which is available on
http://help.sap.com/sltoolset -> System Provisioning -> Split Option.
In chapter 6.1 of this guide, you can also find a checklist for these activities.
Watch the demo video:
3. Configure your new SAP Solution Manager 7.2 system using SOLMAN_SETUP.
Finally, the new SAP Solution Manager 7.2 system needs to be configured and some post steps have to be performed, which are described in SAP Note 2227300.
This is common with both procedures, for which also variants are possible.
Migration Paths
The following matrix gives an overview of the benefits and considerations of the migration paths described above.
Upgrade to SAP Solution Manager 7.2 and migration to SAP HANA or SAP ASE
Migration path | Description | Value proposition | Considerations |
Standard procedure |
|
|
|
Simplified procedure |
|
|
|
The simplified procedure is recommended by SAP, if no interim production use is necessary, since it comprises a simpler usage and has the potential to minimize the business downtime.
The simplified procedure is general available for all customers as of SL Toolset 1.0 SPS 19.
Download links and related information about SUM 1.0 and SWPM 1.0 can be found here: https://support.sap.com/sltoolset
- SAP Managed Tags:
45 Comments
