Scribd
Upload
136 views

SAP Solution Manager 7.2: Simplified Upgrade and Migration To SAP HANA

The document discusses two procedures for upgrading an SAP Solution Manager 7.1 system to version 7.2 and migrating the database to SAP HANA or ASE. The standard procedure involves first upgrading to 7.2, then splitting the dual-stack system and migrating each part separately. The simplified procedure upgrades to 7.2 and migrates the ABAP system in one step using database migration option (DMO), then splits and migrates the Java system. The simplified procedure reduces complexity and potential downtime but does not allow interim production use between steps.

Uploaded by

Jose Alexander Vides
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
136 views

SAP Solution Manager 7.2: Simplified Upgrade and Migration To SAP HANA

The document discusses two procedures for upgrading an SAP Solution Manager 7.1 system to version 7.2 and migrating the database to SAP HANA or ASE. The standard procedure involves first upgrading to 7.2, then splitting the dual-stack system and migrating each part separately. The simplified procedure upgrades to 7.2 and migrates the ABAP system in one step using database migration option (DMO), then splits and migrates the Java system. The simplified procedure reduces complexity and potential downtime but does not allow interim production use between steps.

Uploaded by

Jose Alexander Vides
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

SAP Solution Manager 7.

2: Simplified Upgrade and Migration to SAP HANA

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.

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:

1. Upgrade your SAP Solution Manager system to version 7.2


with the Software Update Manager (SUM).
2. Perform a Dual-Stack Split with the Software Provisioning Manager (SWPM)
3. Migrate your AS ABAP system to SAP HANA or SAP ASE by performing a heterogeneous system
copy with the SWPM.
4. Migrate your AS Java system to SAP HANA or SAP ASE by performing a heterogeneous system
copy with the SWPM.
5. 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.

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.

b) Install a new Java system on the target database using the export file you just created.
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.

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  First upgrade your  Interim production  Longer downtime


dual-stack system, use is possible after and more steps than
then the Dual-Stack Split other procedure
 split the ABAP
stack and the Java
stack and
 optionally migrate
one or both stacks
to SAP HANA or
SAP ASE.

Simplified procedure  First upgrade and  Reduced complexity  No interim


migrate the ABAP of the procedure production use
stack of your dual-  Reduced downtime possible, since the
stack system with for migration split and the
DMO of SUM and migration of the Java
then stack is integrated
 split and migrate into one step.
the Java stack to  After the upgrade
SAP HANA or SAP with DMO of SUM,
ASE. the ABAP part is
already migrated.

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.

You might also like