technical path to sap solution manager 7.2 on sap hana

Technical Path from SAP Solution Manager 7.1 to SAP Solution Manager 7.2 on SAP HANA Process overview, comprising system upgrade, dual-stack split, system migration

Version from September 15, 2016

© 2016 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

www.sap.com

TABLE OF CONTENTS

INTRODUCTION ............................................................................................................................................... 3

OVERVIEW OF MIGRATION PATH USING THE CURRENT STANDARD PROCEDURE ............................ 4 Migration Sub-Options of the Current Standard Procedure ....................................................................... 6 Sub-Option 1: In-Place Move ............................................................................................................................ 7 Sub-Option 2: Move with Parallel Export/Import ............................................................................................... 9

OVERVIEW OF MIGRATION PATH WITH THE SIMPLIFIED PROCEDURE ............................................... 11

CHOOSING YOUR RIGHT MIGRATION PATH ............................................................................................. 14

http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark

TECHNICAL PATH TO SAP SOLUTION MANAGER 7.2 ON SAP HANA

3

INTRODUCTION

This document provides an overview about how to bring existing SAP Solution Manager 7.1 systems running on any database to SAP Solution Manager 7.2 on SAP HANA.

This documentation focusses only on additional findings for this particular scenario and does not intend to replace standard documentation from SAP.

Target group of this documentation are technical consultants experienced with update and migration.

Although some aspects might also be relevant for the migration to other databases, the corresponding procedures were only validated for the migration of SAP Solution Manager to SAP HANA and to SAP ASE.

The overall procedure is customer- and system-specific – use the best practice recommendations from this documentation with caution.

Since the beginning of the ramp-up of SAP Solution Manager 7.2, we offer a procedure using standard processes for upgrade, split and migration (named current standard procedure in this documentation). This procedure is still valid today – nevertheless, with general availability of SAP Solution Manager 7.2, we offer a simplified procedure in addition.

In the upcoming sections, both procedures are described in detail (including instructions about two options to perform the migration of AS ABAP as part of the current standard procedure). In the final section of this guide, aspects for selecting the right procedure for your requirements are provided.


4

OVERVIEW OF MIGRATION PATH USING THE CURRENT STANDARD PROCEDURE

The following figure provides a high-level end-to-end overview of the current standard procedure:

© 2015 SAP SE or an SAP affiliate company. All rights reserved. 15Confidential

SAP Solution Manager 7.1 Upgrade to SAP Solution Manager 7.2 on SAP HANA

Standard procedure

SplitJava

AnyDB

ABAPUpgrade

Java

AnyDB

ABAP

ABAP

AnyDB

Java

Migrate

Migrate

ABAP

(optional)

Production

usage

(SOLMAN_SETUP)

1 2

3

4

Configure5

Java

Production

usage

Solution

Manager

7.2

Solution

Manager

7.1

Solution

Manager

7.2

So, with this procedure, you perform the following activities in the given order to bring your existing SAP Solution Manager 7.1 system to SAP Solution Manager 7.2 on SAP HANA:

1. You upgrade your SAP Solution Manager system to version 7.2, using Software Update Manager.

Java

AnyDB

ABAPUpgrade

Java

AnyDB

ABAP

(SUM)

1

SolutionManager

7.2

SolutionManager

7.1

2. You perform a dual-stack split, including required post-configuration activities (such as re-connectivity

of ABAP and Java stacks), using the dual-stack split procedure as offered by Software Provisioning Manager.

NOTE 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 persisted ABAP system. NOTE The dual-stack split procedure offers two options:

Keep DB option installs a new Java stack without additional database, but reuses the existing database also for the new Java system, using multiple components in one database (MCOD) This option is not available for SAP ASE as target database, since SAP ASE does not support MCOD.

Move DB option installs a new Java stack with an additional database (as depicted below).

SplitJava

AnyDB

ABAP

ABAP

AnyDB

Java

2

(SoftwareProvisioning

Manager)


5

3. You perform a heterogeneous system copy of your AS ABAP system to SAP HANA (using the heterogeneous system copy procedure as offered by Software Provisioning Manager), including post-copy activities.

ABAP

AnyDB

Java

Migrate ABAP3

Java

AnyDB

For this step, we offer two sub-options, which are described in more detail in the upcoming sub-sections: the in-place move and the move with parallel export/import. See below for more information.

4. Optionally, you perform a heterogeneous system copy of your AS Java system to SAP HANA (or any other database, such as SAP ASE – again, using the heterogeneous system copy procedure as offered by Software Provisioning Manager), including post-copy activities.

ABAP

Java

AnyDB

Migrate

ABAP

(optional)

4 Java

5. You configure SAP Solution Manager 7.2, using SOLMAN_SETUP and perform post steps. For more

information, see SAP Note 2227300.

ABAP

Productionusage

(SOLMAN_SETUP)

Configure5

Java

Productionusage

SolutionManager

7.2

If you want to use SAP Solution Manager 7.2 before the migration to SAP HANA (for example, to have a separation of concerns or to get two separate downtime windows/an interim phase of production usage), perform the configuration (using SOLMAN_SETUP) after the dual-stack split procedure.

http://service.sap.com/sap/support/notes/2227300


6

Migration Sub-Options of the Current Standard Procedure For the heterogeneous system copy of your AS ABAP system (as listed in step 3 above), this document describes two sub-options, which are described in more detail in the upcoming sub-sections. The following table provides a combined overview of these migration sub-options including aspects that you should consider for choosing the right procedure for your individual boundary conditions:

Migration sub-option Description Value proposition Considerations

1: In-place move

For the migration of your AS ABAP to SAP HANA, you perform a sequential export/import procedure (that is, you first perform the export on the source system, then you import on the target system)

When you uninstall the former system after the export, you can persist the settings of the application system (ports, host name, instance number, SAP system ID)

Straight-forward, reliable standard procedure

Longer runtime and downtimes than other procedures

2. Move with parallel export/import

For the migration of your AS ABAP to SAP HANA, you perform a parallel export/import procedure

Reduced runtime for heterogeneous system copy, as export on source system and import on target system overlap

Straight-forward, reliable standard procedure

Old and new system are available in parallel throughout procedure, so switchback and comparison is easier

As both source and target have to run throughout the migration procedure, the settings of the application server (such as SAP system ID and port numbers) have to change, affecting agent connectivity, for example


7

Sub-Option 1: In-Place Move Goal of the first sub-option is to retain existing setups as far as possible, while using a reliable standard procedure – in detail, with this approach, you can retain the host and the technical identity (that is, the host name, the SAP System ID, the instance number, and ports) of your existing application server. As a sequential standard procedure is used, you have to expect longer runtimes and downtimes, compared to the other approaches. To perform the in-place move with a standard sequential procedure:

1. You prepare your existing SAP Solution Manager 7.1 system and the overall procedure as described in step 1 of SAP Note 2227300 (Further Upgrade Information for SAP Solution Manager 7.2).

2. You upgrade your existing system to SAP Solution Manager 7.2. For this, you perform a maintenance procedure, as offered by Software Update Manager, as described in step 2 of SAP Note 2227300.

3. As existing profiles would get deleted as part of the uninstallation described below, we recommend

that you persist existing profile files (or the file systems /usr/sap/<SAPSID> and

/sapmnt/<SAPSID>, if you have enough free disk space available).

4. You perform the dual-stack split procedure of the upgraded system, as offered by Software

Provisioning Manager – including disabling of AS Java (so that the procedure adapts profile parameters), required post-split activities (such as enablement of SAP NetWeaver Administrator for remote access, SAP license installation, and adaptation of security settings), and removal of the Java stack parts from the former dual-stack system, as described in the dual-stack split documentation. NOTE

Make sure to benefit from the option of the dual-stack split procedure to take over existing configuration settings (such as Internet Communication manager ports) and to use the option to automatically create RFC destinations in AS ABAP to re-establish the connectivity between ABAP and Java as part of the split.

For SAP Solution Manager 7.2, both split options (Move DB and Keep DB) are supported. For this use case, SAP recommends the Keep DB option, as this makes it easier to re-connect ABAP and Java.

For more information, see the guide Dual-Stack Split: Systems based on SAP NetWeaver 7.1 and Higher, available at http://support.sap.com/sltoolset System Provisioning. For post-split activities especially for SAP Solution Manager, also see the corresponding dual-stack split section of step 2 of SAP Note 2227300.

5. You perform a heterogeneous system copy of the ABAP part of your SAP Solution Manager system to SAP HANA, using a sequential procedure, as outlined in the following figure:

Export

ABAP

AnyDB

ABAP

AnyDB

UninstallABAP

Install + import

with same parameters

a. You run Software Provisioning Manager on the source system to generate a database-

independent export of the source database. b. You run Software Provisioning Manager to uninstall the former ABAP system without

removing the database (that is, you uninstall the ABAP central services instance [ASCS instance], the enqueue replication server instance [ERS instance] if available, and the application server instances, but not the database instance, as this might still host the Java part, if you decided to use the Keep DB option) from the source host, so that you can re-use the technical parameters of the source system (host name, instance number, SAP system ID) for the new system running on SAP HANA that you now want to install in the next step.




http://support.sap.com/sltoolset



8

c. You run Software Provisioning Manager on the source system to build up the new SAP system running on the SAP HANA database, using the same parameters as the previous system (SAP system ID, instance number) and the load from the source system.

Result: new SAP system running on SAP HANA, built sequentially, with same identity as source system (same host name, same SAP system ID, same instance number). For more information, see the system copy guide for target database SAP HANA, available at: http://support.sap.com/sltoolset System Provisioning System Copy: Systems Based on SAP NetWeaver 7.1 and Higher Database of the target system: SAP HANA.

6. Optionally, you perform a heterogeneous system copy of the Java part to SAP HANA (or any other database):

a. You run Software Provisioning Manager on the source Java system to generate a database-independent export of the source Java database.

b. You run Software Provisioning Manager to uninstall the former Java system from the source host, so that you can re-use the technical parameters of the source system (host name, instance number, SAP system ID) for the new system running on SAP HANA that you now want to install.

c. You run Software Provisioning Manager on the source system to build up the new Java system running on the SAP HANA database, using the same parameters as the previous system (SAP system ID, instance number) and the load from the source system.

For more information, see the corresponding system copy guide, available at: http://support.sap.com/sltoolset System Provisioning System Copy: Systems Based on SAP NetWeaver 7.1 and Higher.

7. You perform follow-up activities, including the activities required after every system copy (such as installing a new license, adapting batch jobs, performing an installation check, and adapting the Transport Management System). Especially for SAP Solution Manager, you run SOLMAN_SETUP in SAP Solution Manager 7.2, as described in step 3 of SAP Note 2227300. Before activating the solution documentation content in SAP Solution Manager 7.2, see step 4 of SAP Note 2227300.






9

Sub-Option 2: Move with Parallel Export/Import Goal of the second option is to reduce the runtime via a parallel export/import phase, while using standard procedures also for the migration to SAP HANA. Nevertheless, as both source and target system have to run throughout the migration procedure, the settings of the application server (such as SAP system ID and port numbers) have to change (for example, affecting agent connectivity). To perform the move with a standard parallel export/import procedure:

1. You prepare your existing SAP Solution Manager 7.1 system and the overall procedure as described in step 1 of SAP Note 2227300 (Further Upgrade Information for SAP Solution Manager 7.2).

2. You upgrade your existing system to SAP Solution Manager 7.2. For this, you perform a maintenance procedure, as offered by Software Update Manager, as described in step 2 of SAP Note 2227300.

3. You perform the dual-stack split procedure of the upgraded system, as offered by Software Provisioning Manager – including disabling of AS Java (so that the procedure adapts profile parameters), required post-split activities (such as enablement of SAP NetWeaver Administrator for remote access, SAP license installation, and adaptation of security settings), and removal of the Java stack parts from the former dual-stack system, as described in the dual-stack split documentation. NOTE

Make sure to benefit from the option of the dual-stack split procedure to take over existing configuration settings (such as Internet Communication manager ports) and to use the option to automatically create RFC destinations in AS ABAP to re-establish the connectivity between ABAP and Java as part of the split.

For SAP Solution Manager 7.2, both split options (Move DB and Keep DB) are supported. For this use case, SAP recommends the Keep DB option, as this makes it easier to re-connect ABAP and Java.

For more information, see the guide Dual-Stack Split: Systems based on SAP NetWeaver 7.1 and Higher, available at http://support.sap.com/sltoolset System Provisioning. For post-split activities especially for SAP Solution Manager, also see the corresponding dual-stack split section of step 2 of SAP Note 2227300.

4. You perform a heterogeneous system copy of your SAP Solution Manager system to SAP HANA, using a parallel procedure for the ABAP part, as outlined in the following figure:

ABAP

AnyDB

ABAP

Install

ABAP

AnyDB

ABAP

Share

Export

Import

ABAP

Switch

a. You run Software Provisioning Manager on the target host to install a new target system

(with new technical parameters – new host name and new SAP system ID) running on SAP HANA without database load, as preparation for the parallel migration procedure.

b. You run Software Provisioning Manager in parallel on both the source host and the target host to export the source database and import it into the newly installed target system – so that export and import phases overlap.

c. Optionally, you perform a heterogeneous system copy of the Java part to SAP HANA (or any other database):

i. You run Software Provisioning Manager on the source Java system to generate a database-independent export of the source Java database.

ii. You run Software Provisioning Manager to uninstall the former Java system from the source host, so that you can re-use the technical parameters of the source system







10

(host name, instance number, SAP system ID) for the new system running on SAP HANA that you now want to install.

iii. You run Software Provisioning Manager on the source system to build up the new Java system running on the SAP HANA database, using the same parameters as the previous system (SAP system ID, instance number) and the load from the source system.

d. You switch to the newly set up system running on SAP HANA (including required post-copy activities, such as re-configuration of connected systems, installing a new license, adapting batch jobs, performing an installation check, and adapting the Transport Management System). Especially for SAP Solution Manager, you run SOLMAN_SETUP in SAP Solution Manager 7.2, as described in step 3 of SAP Note 2227300. Before activating the solution documentation content in SAP Solution Manager 7.2, see step 4 of SAP Note 2227300.

e. You run Software Provisioning Manager to uninstall the source ABAP system without removing the database (that is, you uninstall the ABAP central services instance [ASCS instance], the enqueue replication server instance [ERS instance] if available, and the application server instances, but not the database instance) from the source host.

Result: new SAP system running on SAP HANA with new identity (new host name, new SAP system ID), built with parallel load. For more information, see the system copy guide for target database SAP HANA, available at: http://support.sap.com/sltoolset System Provisioning System Copy: Systems Based on SAP NetWeaver 7.1 and Higher Database of the target system: SAP HANA.





11

OVERVIEW OF MIGRATION PATH WITH THE SIMPLIFIED PROCEDURE

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 (no interim production use), we offer another technical path: a simplified upgrade and migration procedure incorporating the Database Migration Option of the SUM and the combined split and migration in the Software Provisioning Manager. The following figure provides a corresponding high-level end-to-end overview of the simplified procedure:

© 2015 SAP SE or an SAP affiliate company. All rights reserved. 15Confidential

SAP Solution Manager 7.1 Upgrade to SAP Solution Manager 7.2 on SAP HANA

Simplified procedure

Solution

Manager

7.2

Solution

Manager

7.1

SplitJava

AnyDB

ABAP

UpgradeJava

AnyDB

ABAP

(DMO of SUM

resp. SUM)

ABAP

Java

DMO*

Production

usage

(SOLMAN_SETUP)

1 2 3 Configure

(Software

Provisioning

Manager)

Production

usage

Solution

Manager

7.2

The simplified procedure consists of the following basic steps: 1. You 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).

SolutionManager

7.2

SolutionManager

7.1

Java

AnyDB

ABAP

UpgradeJava

AnyDB

ABAP

(DMO of SUM resp. SUM)

DMO*1

Technically, this step is a dual-stack upgrade with Database Migration Option (DMO) of SUM, which efficiently combines system update, Unicode conversion and database migration. For more information about DMO, see the blog post Database Migration Option (DMO) of SUM - Introduction. 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.

http://scn.sap.com/docs/DOC-49580

http://scn.sap.com/docs/DOC-49580


12

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 and higher. The dual-stack split will separate the ABAP stack and the Java stack into two SAP Systems.

http://scn.sap.com/community/it-management/alm/software-logistics/blog/2015/12/15/optimizing-dmo-performance


13

2. You perform a dual-stack split and migrate your AS Java system to SAP HANA or SAP ASE with the Software Provisioning Manager.

SplitJava

AnyDB

ABAP

ABAP

Java

2

(SoftwareProvisioning

Manager)

The database migration can be done as integral part of the dual-stack split procedure, as offered for the split of SAP Solution Manager 7.2 by the latest versions of Software Provisioning Manager. The outcome is equivalent to the classic way described of the current standard procedure above. 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) You export the Java stack from your source database.

b) You install a new Java system on the target database using the export file you just created.

c) You remove the Java stack from the old dual-stack system on the source database.


14

The removal of the Java stack is part of the follow-up activities, which are described in section Follow-Up Activities Checklist of the Dual-Stack Split Guide, available in SAP Support Portal at: http://support.sap.com/sltoolset System Provisioning Split Option.

3. You configure your new SAP Solution Manager 7.2 system using SOLMAN_SETUP and perform post

steps. For more information, see SAP Note 2227300.

ABAP

Productionusage

(SOLMAN_SETUP)

Configure5

Java

Productionusage

SolutionManager

7.2

CHOOSING YOUR RIGHT MIGRATION PATH

The following matrix gives an overview of the benefits and considerations of the migration paths described in this document in the previous sections. Upgrade to SAP Solution Manager 7.2 and migration to SAP HANA or SAP ASE

Migration path Description Value proposition Considerations

Current standard procedure

1. Upgrade your dual-stack system

2. Split off the Java stack 3. Optionally migrate one

or both stacks to SAP HANA or SAP ASE

Interim production use is possible after the dual-stack split and configuration of SAP Solution Manager 7.2

Longer downtime

More steps and downtime windows than other procedure

Simplified procedure

1. Upgrade and migrate the ABAP stack of your dual-stack system with DMO of SUM to SAP HANA or SAP ASE

2. Split off and migrate the Java stack to SAP HANA or SAP ASE.

Reduced complexity of the procedure

Reduced downtime for migration

No interim production use possible, since the split and the migration of the Java stack is integrated into one step

After the upgrade with DMO of SUM, 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.



technical path to sap solution manager 7.2 on sap hana

Documents