Descripción: This certification exam verifies that the candidate has the knowledge required in the SAP NetWeaver Business Intelligence solution area. This certificate builds on the basic knowledge gained by a B...
Adm540 en Col15
s4h01 en Col03 Ilt Fv Co a4Full description
Descrição: Ha400 en Col12 Ilt Fv Co a4
SAP Activate Methodology ACT100
SAP MM certificate course content for inventory management, Physical inventoryFull description
Bw462 en Col13 Ilt Fv Co a4
BOIT
Ha100
BOIT
HA250 Migration to SAP HANA Using DMO
. .
INSTRUCTOR HANDBOOK INSTRUCTOR-LED TRAINING . Course Version: 11 Course Duration: 2 Day(s) Material Number: 50119249
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://global http://global12.sap.com/corpora 12.sap.com/corporate-en/leg te-en/legal/ al/ copyright/index.epx for copyright/index.epx 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 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 companies at any t ime 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 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.
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://global http://global12.sap.com/corpora 12.sap.com/corporate-en/leg te-en/legal/ al/ copyright/index.epx for copyright/index.epx 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 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 companies at any t ime 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 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.
Typographic Conventions American English is the standard used in this handbook. The following typographic conventions are also used.
This information is displayed in the instructor’s presentation
LESSON OVERVIEW This lesson discusses the benefits of DMO compared to the classical migration. Business Example As a member of the implementation team for a system migration, you need to know more about DMO.
LESSON OBJECTIVES After completing this lesson, you will be able to: ●
List the benefits of the DMO procedure
DMO benefits The following list provides an overview of the database migration option (DMO):
DMO Overview
You want to migrate your existing ABAP-based SAP s ystem to SAP HANA DB. You choose the inplace-migration avoiding landscape changes (SID, host name, …), so you need an update of your SAP system. Classical migration is complex and requires several steps to be considered.
Use the database migration option (DMO) of the Software Update Manager (SUM).
●
●
Migration steps are simplified. System update, Unicode conversion, and database migration are combined in one tool.
●
Business downtime is reduced.
●
The well known tool SUM is used, with an improved UI.
Migrating your existing SAP system to the SAP HANA database, means switching the SAP system to a new database that is running on a new host, as SAP HANA is an appliance.
Note: Although the following example explains the principle for an SAP Business Suite system, the same applies for an SAP Business Warehouse (SAP BW) system.
Classical migration is the sequence of an SAP software update (using Software Update Manager, SUM) and heterogeneous system copy (using Software Provisioning Manager, SWPM). DMO simplifies the migration and is often referred to as the one-step procedure to SAP HANA.
Figure 2: DMO Simplifies Migration
Running an SAP system on a SAP HANA database requires a specific SAP software level. This means that the SAP system has to be updated before the migration takes place.
Note: Update can be an update, in terms of EHP implementation, or an upgrade (re lease switch). If the SAP system is updated, this may result in requirements for the database host software, especially the database software release. So for some scenarios, the source database software has to be updated before the SAP system is updated. As with the SAP HANA database, non-Unicode systems are no longer supported. So the migration procedure may have to cover the Uni code conversion as well. Now with the database migration option (DMO) of the Software Update Manager (SUM), the procedure is simplified. SAP system update and database migration are combined in one tool, in one procedure. If required, the Unicode conversion may be included as well. For some source database types, it is not required to update the source database software for the migration. The figures above illustrate a process where the SAP application server is separate from the database host, which is referred to as a distributed installation. The DMO procedure works independently of the installation type. It can be used for a central installation, in which the database runs on the same host as the SAP application server. The benefits of DMO are as follows:
DMO Benefits
●
Reduces business downtime (TCO)
●
Less regression tests necessary
●
Low impact on system landscape, as only the database server is new
LESSON OVERVIEW This lesson provides a more technical introduction to DMO. Business Example As an administrator, you want to learn more about the technical basics of DMO.
LESSON OBJECTIVES After completing this lesson, you will be able to: ●
List information sources for DMO
●
Explain DMO from a technical perspective
Introduction to Technical Aspects of Database Migration Option (DMO) Lets begin with some remarks on naming:
Remarks on Naming
SUM is the standard tool for updating SAP systems. It is based on SAP NetWeaver.
DMO is an option of SUM for a migration scenario. It is not a tool.
The Software Provisioning Manager is a tool for syste m installation, copying, and renaming. It is a dual-stack split (fka SAPinst), that is mainly used for the heterogeneous system copy, or classical migration. The relevant information sources for DMO are as follows:
Relevant Information Sources for DMO ●
SAP Note: See 2198483 Database Migration Option with SUM 1.0 SP 16. This is the relevant information source for the topics that follow, such as start releases.
●
DMO documentation: see help.sap.com/sltoolset and go to System Maintenance.
For the heterogeneous system copy, a certification is required. For DMO, this is different. The differences are as follows:
DMO and Certification ●
No certification is required for consultants using DMO of SUM.
No migration check service is required for DMO on productive systems.
●
A migration key has to be entered during DMO run: R3load requires the key.
●
Certification training TADM70 (SAP System: OS and DB Migration) is useful.
DMO is a new option inside of SUM. Currently, it does not cover all possible start releases. You have to consider the supported start releases for DMO, as follows:
Supported Start Releases for DMO ●
SAP R/3 4.6C
●
SAP ECC 5.0
●
SAP ECC 6.0 (or above)
●
SAP Business Suite 7 (or above)
●
SAP BW 7.0 (or above)
●
SAP NetWeaver 7.0 systems (or above)
Note: Check the relevant SAP Note on DMO for details.
SP17 is required for all systems based on Software Component Version SAP_BASIS 7.0. The reason for this is that for lower levels, the report SMIGR_CREATE contains syntax errors.
The required start release levels are described in the respective SAP Note on DMO (listed above). Open the attachments to the respective SAP Note and explain the possible start releases. SAP BW 7.3 runs on SAP HANA as well, but is not supported as a target release for DMO.
Check the SAP Note for DMO for information on which database types require an update for DMO and which do not. Some scenarios are not possible with DMO:
Rules for DMO ●
DMO supports a migration to SAP HANA DB (& SAP ASE, MS SQL on request). A homogenous migration is not supported, for example, SAP HANA
●
→
SAP HANA.
DMO can only be started for a maintenance. You need to apply at least one SP, for example, for ST-PI.
●
SAP HANA requires a single stack. DMO only works for AS ABAP based systems. There is no dual-stack split option in DMO. DMO keeps the application server and SID. No switch is possible.
Note: For a target system based on SAP NetWeaver 7.50 (such as SAP ECC 6.0 EHP 8), the source system has to be on Unicode already (see SAP Note 2033243). For this scenario, even DMO is not able to cover the Unicode conversion.
The dual-stack split is relevant for systems combined in a dual-stack, like SAP ERP with SAP Enterprise Portal. DMO cannot be used for SAP Solution Manager for SAP NetWeaver PI (classical installation as dual-stack). The following figure illustrates a brief overview of the DMO phases that are executed by the SUM tool.
Figure 3: Introduction of DMO Phases
Step 1 includes some preparations that are done, like providing stack.xml, passwords, download folder. On the SAP HANA database, the DMO procedure only creates required users and schema. Step 2 includes the creation of the shadow repository on the source database. This is still uptime processing, so the system is available for end users. The shadow repository is then copied to the SAP HANA database. Step 3 is the switch to the downtime. The system is no longer available. The source database is still running, but is no longer used to store new or changed data. Step 4 is the migration of application data. Step 5 finalizes the upgrade and migration, like switching the SAP system to the new kernel. Step 6 starts the SAP system, which is now running on the new database and on the new SAP software release.
During the complete procedure, the source database continues to run. The DMO procedure offers an easy reset in case this may be required. As the source database was not changed, the reset is fast and does not require manual interactions. The DMO reset deletes the shadow repository from the source database, and all other artefacts are reset as well.
Business Example You have to check the status of the ABAP source system prior to a DMO procedure. Check the status, number of instances, and the release of the ABAP source system. Log on to the operating system (OS) of your source system host. Use the SAP Microsoft Management Console (SAP MMC) to check the system status, the number of instances, and the number of work processes. Log on to the ABAP source system and check the component and software component versions. Check the level of SPAM/SAINT .
Business Example You have to check the status of the ABAP source system prior to a DMO procedure. Check the status, number of instances, and the release of the ABAP source system. Log on to the operating system (OS) of your source system host. Connect to the Common Training WTS. From within the Common Training WTS, open a remote desktop connection to connect to your system landscape TH-HA250SPSxx-###. Log on with train-## . From within TH-HA250SPSxx-###, open a remote desktop connection to the host of the ABAP source system. Log on with user adm and the password provided by your instructor. Use the SAP Microsoft Management Console (SAP MMC) to check the system status, the number of instances, and the number of work processes. Open the SAP Microsoft Management Console on the ABAP source system host, by using the shortcut on the desktop for example. Check that the system is running. If the system is listed with a green icon, the system is running. If the system is not running, start the system using the context menu with the systemID icon, and choose All Tasks Start ..... You will have to provide the password of the adm user. →
Check the number of instances listed. In the left area of the screen, below Console Root SAP Systems , there is only one instance listed: 0. →
→
Note: has to be replaced by the host name of your ABAP source system.
Check the number of work processes of type Dialog (DIA) and Batch (BTC), by using the menu entry AS ABAP WP Table. There are 10 DIA and 10 BTC work processes. Log on to the ABAP source system and check the component and software component versions.
Start the SAP Logon from the Start menu of the server TH-HA250SPSxx-###. Use the existing logon entry to log on to client 800 with user admin. Use the System/Status menu to open the system information popup. Check that the component version is listed as EHP7 for SAP ERP 6.0. Check that the database system is listed as SYBASE 15.7.0.135. Use the button below the Component Version to display the Software Component Version list. Check that SAP_BASIS is listed as 740. Check that SAP_APPL is listed as 617 , which is equivalent to the product version Enhancement Package 7 for SAP ERP 6.0. Use the Installed Product Versions button to see product EHP7 for SAP ERP 6.0 listed. Check the number of instances listed in transaction SM51. There is only one instance listed, as in the SAP MMC. Check the level of SPAM/SAINT . Start transaction SPAM .
SPAM/SAINT is started, and available functions are displayed (as you have started SPAM in a different client to 000). The title lists SPAM/SAINT version 7.40/00
.
Optionally, check in SAP Service Marketplace for the latest patch version for SPAM/ SAINT.
Unit 1 Exercise 2 Check the Status of the SAP HANA Database 13
Business Example As an administrator, you are responsible for a DMO procedure and have to monitor the SAP HANA database. Start the SAP HANA studio, and configure access to the SAP HANA database. Start the SAP HANA studio on your server TH-HA250SPSxx-###. Configure general settings for the SAP HANA studio, like Active provider=Direct for Network Connections, and Internet Explorer for External Browser. Add an entry for the SAP HANA database H00 in the Administration Console, in a new folder H00 SYSTEM. Check the version of SAP HANA database H00. Check the status of the SAP HANA database H00.
Unit 1 Solution 2 Check the Status of the SAP HANA Database 14
Business Example As an administrator, you are responsible for a DMO procedure and have to monitor the SAP HANA database. Start the SAP HANA studio, and configure access to the SAP HANA database. Start the SAP HANA studio on your server TH-HA250SPSxx-###. From the Windows Start area, start the SAP HANA studio on your server THHA250SPSxx-###. Confirm the popups. The Overview page is shown, and the popup Secure Storage is displayed. Read the text of the popup, and choose No to close it. Configure general settings for the SAP HANA studio, like Active provider=Direct for Network Connections, and Internet Explorer for External Browser. On the Overview page, choose the menu Window
→
Preferences.
The Preferences popup is displayed. Open the first General section. Select the entry Network Connections. In the drop down menu for Active Provider, switch from Native to Direct. Choose Apply to apply the change. In the General section, select the entry Web Browser. Switch the first option (radio button) from Use internal web browser to Use external web browser . In the External web browser list, select the Internet Explorer checkbox. Choose Apply, to apply the change, and OK to close the popup. Add an entry for the SAP HANA database H00 in the Administration Console, in a new folder H00 SYSTEM. Switch to the Administration Console, either by choosing the first link on the Overview page, or by using the menu Window Open Perspective SAP HANA Administration Console. →
In the field Folder Name: below, enter H00 SYSTEM . Choose Finish to close the popup. On the folder H00 SYSTEM, use the context menu Add System ... and right click to open the System popup. Specify the Host Name as wdflbmt7215, Instance Number as 00, Description H00 as target for DMO. Keep the Mode option to Single Container. Choose Next. Keep the option Authentication by database user. Enter the username SYSTEM and the password. Choose Finish to create the system entry. The system is listed, with a folder structure below. Check the version of SAP HANA database H00. In your folder H00 SYSTEM, use the context menu on your system entry H00, and choose Properties. The Properties popup is shown. In the menu on the left of the screen, select Version History. The Version History lists the version, such as 1.00.111.00.xxx, and optionally earlier versions. Check the status of the SAP HANA database H00. In your folder H00 SYSTEM, use the context menu on your system entry H00, and choose Administration.
Note: Double clicking the H00 system entry will do the same.
The System Overview page is shown. Check if Database Used Memory and Disk Usage are shown in green.
1. What are the advantages of the DMO procedure? Choose the correct answers.
X
DMO combines several steps into one procedure.
X
DMO allows a lower target release on SAP HANA database.
X
DMO allows an easy reset during the procedure.
X
DMO is an inplace procedure, keeping the application server host.
DMO does combine several steps, offers an easy rest, and it is an inplace procedure. But the requirements concerning the target release on SAP HANA are not changed by DMO.
Ensuring DMO prerequisites are fullfilled on the host
LESSON OVERVIEW This lesson explains the required steps on the host to prepare a DMO procedure. Business Example You have the task to prepare a DMO procedure and need to know the required steps.
LESSON OBJECTIVES After completing this lesson, you will be able to: ●
List the required steps and files to prepare a DMO procedure
●
Prepare the archives for a DMO procedure
Fulfilling the Prerequisites for DMO The required considerations for DMO are as follows:
Required Considerations for DMO ●
The SAP HANA appliance has to be available.
●
The Dual-stack has to be split beforehand.
●
The OS/DB software may need to be updated.
●
The Stack.xml file and software files have to be downloaded, see the MOpz or Maintenance Planner.
●
A Web browser update may have to be applied.
●
SAP BW housekeeping needs to be considered, NLS, and BW-PCA. (See SCN blog: http://scn.sap.com/docs/DOC-46824)
Hint: See SAP Note 1829728 on BW Housekeeping Task List.
DMO Specifics For a DMO procedure, you will have to select both the kernel files for the source database and the target database, as the DMO procedure will require and use both of them. This is explained further in a separate section.
Lesson: Ensuring DMO prerequisites are fullfilled on the host
Figure 4: Maintenance Planner: Selecting Kernel Files for DMO
Hint: See SAP Note 1795851, which details the report in SAP Solution Manager on how to copy an existing stack.xml (from the previous system maintenance).
Useful SAP Notes ●
SAP Note 1912445: ABAP custom code mi gration for SAP HANA
●
SAP Note 1872170: Suite on HANA memory siz ing report
●
SAP Note 1736976: Sizing report for BW on HANA
Only pure ABAP systems can be migrated onto the SAP HANA database. In case the system is a dual-stack system (both ABAP and Java stacks on one database, one System-ID), the dual-stack has to be split beforehand.
Note: The dual-stack split procedure is now part of the Software Provisioning Manager. There are no plans to include the dual-stack split procedure in the DMO procedure.
Note: With SAP NetWeaver 7.40 SP03 (and above), it is possible to operate an SAP system based on AS Java (for example, BI-Java) on an SAP HANA database.
With SUM SP10, the DMO procedure allows for the inclusion of the Unicode Conversion (for single-code-page systems).
Depending on the update path, the ope rating system and the database software may have to be updated prior to the DMO procedure. For specific source databases, the DMO procedure has lower requirements than the classical migration. The DMO documentation lists the latest requirements.
This was already discussed in a previous lesson (Maintenance Optimizer in SAP Solution Manager, or Maintenance Planner).
The user interface (UI) of the DMO procedure is based on SAPUI5 and requires a specific internet browser version. The DMO documentation lists the latest requirements. The supported Web browser versions for DMO are as follows: ●
Internet Explorer 9 or higher (not using compatibility view)
●
Chrome 28 or higher
●
Firefox 21 or higher
●
Refer to the DMO documentation for latest update.
The required software download from SAP Service Marketplace for DMO is as follows:
Required Software Download for DMO ●
SPAM/SAINT update for SAP source release has to be downloaded.
●
Software Update Manager (SUM) latest version has to be downloaded.
●
SAP Host Agent 7.21 latest patch has to be downloaded.
●
SAP HANA Client installation files have to be downloaded.
●
Migration key has to be requested.
●
SAP license file for target system has to be requested.
Preparation Task List The latest update for the source release is not included in the MOpz, so the file has to be downloaded separately. The SUM requires specific functionality in the ABAP stack to prepare the source system and to create the shadow system. This functionality is not shipped with the SUM, it is part of the SPAM/SAINT. : Move the SPAM update archive into the download folder.
Although for some scenarios the MOpz will add the SUM into the download basket, it is recommended to always check for the latest update of the SUM in SAP Service Marketplace. This includes the latest patch level for a SUM SP version as well. Use the quick link: help.sap.com/sltoolset in SAP Service Marketplace to navigate to the SUM patches. : Extract the SUM archive into the system folder.
Lesson: Ensuring DMO prerequisites are fullfilled on the host
Although the MOpz will add the SAP Host Agent into the download basket, it is recommended to always check for the latest update of the SAP Host Agent in SAP Service Marketplace. Use the quick link /patch in SAP Service Marketplace to navigate to the SAP Host Agent patches.
Hint: The path to SAP Host Agent patches is as follows: http://service.sap.com/ patch Browse download catalog SAP Technology Components AGENT SAP HOST AGENT 7.21 →
→
→
SAP HOST
→
: Execute a self update. The SUM will establish a connection to the SAP HANA database and requires the SAP HANA client for this. The installation files have to be provided, and the SUM will ask for the location of these files during the DMO procedure. : Extract the SAP HANA Client ins tallation archive.
For a heterogeneous database migration, a migration key is required. The kernel tool R3load is used for the migration and requires this migration key. The DMO procedure will ask for the key and provide it to the R3load tool. Use the link support.sap.com/ migrationkey in SAP Support Portal to request the migration key for your SAP system. : Provide the migration key when the DMO procedure asks for it.
The SUM will have to install a new license on the target system. The DMO procedure will ask for the license file. Use the quick link /licensekey in SAP Service Marketplace to request the license file for your SAP system. : Provide the license file location when the DMO procedure asks for it. The above task list is summarized below:
Preparation Task List: Summary Move the stack.xml file into the download folder. Move the SPAM update archive into the download folder. Extract the SUM archive into the system folder. Execute a self update for SAP Host Agent. Extract the SAP HANA Client installation archive. Keep the migration key ready (DMO procedure asks for it). Keep the SAP license file ready (DMO procedure asks for it). The following figure shows the folder D:\HA250 that has been prepared on the host in the training landscape.
Unit 2 Exercise 3 Ensure DMO Prerequisites are Fulfilled 27
Business Example A colleague has already prepared the DMO procedure by downloading required files, such as a license file. You have to check the location of the files.
Note: Some of these actions are optional, but serve to understand the special requirements for DMO, especially the additional files required, and additional steps compared to a standard update/upgrade using the SU M.
Note: You will have to replace with the system-id of the ABAP source system assigned to you, for example T60 or T64.
Check the host of the ABAP source system for required files and folders. Check the content (files and folders) provided in the folder D:\HA250\. Examine the system folder D:\usr\sap\\. Check if a SUM folder already exists. Prepare the required files and folders on the host of the ABAP source system. Extract the Software Update Manager archive into the system folder using SAPCAR . Move the stack.xml file into the download folder. Move the download folder into the system folder. Extract the SAP HANA Client installation archive.
Unit 2 Solution 3 Ensure DMO Prerequisites are Fulfilled 28
Business Example A colleague has already prepared the DMO procedure by downloading required files, such as a license file. You have to check the location of the files.
Note: Some of these actions are optional, but serve to understand the special requirements for DMO, especially the additional files required, and additional steps compared to a standard update/upgrade using the SUM.
Note: You will have to replace with the system-id of the ABAP source system assigned to you, for example T60 or T64.
Check the host of the ABAP source system for required files and folders. Check the content (files and folders) provided in the folder D:\HA250\. Switch to the Remote Desktop Connection on your ABAP source system host. Open a Windows Explorer window, and navigate to the folder D:\HA250\. Check the content of the folder for the following files and folders:
Note: On your host, some of the files may have a slightly different name suffix.
●
●
●
download: This folder contains software and kernel files, which were downloaded from the download basket (in SAP Service Marketplace), provided by Maintenance Optimizer (MOpz, in SAP Solution Manager) or Maintenance Planner. IMDB_CLIENT100_1xx_0-10009664.SAR: This folder contains installation files for the SAP HANA client, which had to be downloaded separately from SAP Service Marketplace. SAPHOSTAGENT0x_x-20009417.SAR: SAP Host Agent archive with the latest patch.
Lesson: Ensuring DMO prerequisites are fullfilled on the host
●
●
●
stack.xml: The definition file for the SUM, downloaded directly from Maintenance Optimizer (in SAP Solution Manager) or Maintenance Planner. SUM10SP16_x_20006676.SAR: Software Update Manager (SUM) archive, downloaded either from SAP Service Marketplace (/sltoolset), or provided by MOpz in the download basket. _multiple.txt: License file for the target system, created separately.
Examine the system folder D:\usr\sap\\. Check if a SUM folder already exists. Open a second Windows Explorer window. Navigate to the folder D:\usr\sap\\.
Note: This folder is referenced as the system folder in this training material.
The system folder does not yet contain a SUM folder. Keep this folder open, as we will work in it later.
Prepare the required files and folders on the host of the ABAP source system. Extract the Software Update Manager archive into the system folder using SAPCAR . Open a command prompt window on the host of the ABAP source system, from the shortcut on the desktop for example. Execute sapcar.exe using the option -R to specify the target directory. The exact statement depends on the location and name of your SUM archive, see step above. Use the following command to execute the SUM archive into the system folder D:\usr \sap\\: SAPCAR.EXE -xvf D:\HA250\SUM10SP16_x_20006676.SAR -R D:\usr\sap\\
Note: Replace the x in the name with the actual patch level of the SUM archive.
Check if the SUM folder was created in the system folder. Use the existing Windows Explorer window for this. Optionally, you may open the SUM folder to check for the abap folder, among other folders. Move the stack.xml file into the download folder. Switch to the Windows Explorer window, showing the content of D:\HA250\. Move the stack.xml file into the download folder.
Note: For a DMO procedure for a standard maintenance with SUM, it is required that the stack.xml is located in the download folder, as the SUM only asks for the stack.xml file and presumes that it is located in the download folder.
Move the download folder into the system folder. Move D:\HA250\download\ to D:\usr\sap\\.
Note: The download folder may have a different name. But it is common to name it download and place it into the system folder.
Extract the SAP HANA Client installation archive. Switch to the command prompt window. Switch to the directory D:\HA250 cd D:\HA250 Extract the SAP HANA Client installation archive IMDB_CLIENT100_1xx_0-10009664.SAR using the following command: SAPCAR.EXE -xvf D:\HA250\IMDB_CLIENT100_1xx_0-10009664.SAR
Note: You may have to adapt the name of the archive to the actual name.
Unit 2 Lesson 2 Configuring SAP Host Agent for DMO 33
LESSON OVERVIEW This lesson explains the necessary preparation steps to configure the SAP Host Agent for a DMO run. The role of SAP Host Agent and the required preparation steps shall be motivated.
Business Example You are responsible for preparing a DMO run, so you have to prepare the communication between the SAP Host Agent and the SUM.
LESSON OBJECTIVES After completing this lesson, you will be able to: ●
Update SAP Host Agent
●
Configure SAP Host Agent to start SAPup
●
Check SAPup processes in the process list
Collaboration between SAP Host Agent and SUM The Software Update Manager (SUM) is the tool for system maintenance of SAP systems, based on SAP NetWeaver. For the DMO procedure, a new way of starting the tool and a new user interface (UI) was introduced. The following figure illustrates the different approach of the classical way of starting and using SU M, compared to the DMO way of starting and using SUM.
The same tool SUM can be used for a system maintenance, or for a DMO procedure. The DMO procedure was the first SUM use case to use the new UI, which is based on SAPUI5.
Note: SAPUI5 is based on jQuery, a javascript library You use a browser window to start the SUM for a DMO procedure, by sending an appropriate HTTP request to the SAP Host Agent. The URL that you use contains the information for the SAP Host Agent about what to do. http://:/lmsl/sumabap/doc/sluigui
Note: LMSL is the abbreviation for ifecycle
anagement oftware ogistics.
is the hostname of the primary application server of the source system. is the port of the SAP Host Agent (1129, or 1128 for plain HTTP). has to be replaced with the System-ID of the source system. Before the SAP Host Agent starts the SUM, it requests the user and password of an adm user. This is required to start the SUM.
Figure 8: Starting SUM via SAP Host Agent
Note that if you enter a wrong password or a wrong URL, you will get an error message which depends on the browser type. Some browser output will state: “File cannot be found”. With the user and password of an adm user, the SAP Host Agent starts the SAPup. The SAPup is the part of the SUM that is responsible for the ABAP stack. As DMO is only working
on ABAP systems, the SAPup is used for the DMO procedure (and some SUM scripts, as described below). The SAPup process is started with option gt=httpchannel , it acts as a kind of dispatcher, as it handles all requests coming from the SAP Host Agent. This SAPup process will start a second SAPup, which triggers additional tools li ke R3load or tp.
Figure 9: SAP Host Agent Starts SAPup
Both SAPup processes are visible in the process list of the PAS host.
Figure 10: SAPup Processes Visible on OS level
In the unlikely situation that you want to end the SAPup process the hard way, you will have to end the process tree for the SAPup with mode httpchannel. The HTTP communication between SUM and SAP Host Agent requires a minimum patch level for SAP Host Agent. That is why it is important to know how to update the SAP Host Agent. In addition, the SAP Host Agent has to be configured, so that for starting the SUM, it knows the location of SUM.
Required preparation steps for SAP Host Agent The required steps to configure the SAP Host Agent for a DMO run are as follows:
Required steps for SAP Host Agent Configuration ●
Checking the patch level of SAP Host Agent
●
Upgrading SAP Host Agent (if required)
●
Configuring SAP Host Agent for starting SUM
Checking and upgrading SAP Host Agent For a Windows host, the SAP Host Agent is installed in C:\Program Files\SAP\hostctrl\exe. The -version option allows you to check the version: saphostexec.exe -version. The SAP Host Agent archive is typically part of the download folder. Still, it makes sense to check for a newer patch in SAP Service Marketplace. You do not have to unpack the archive of the new SAP Host Agent, as the upgrade option can use an archive as well. To upgrade the existing saphostexec.exe, use the -upgrade option and reference the archive with the new SAP Host Agent with the -archive option , as illustrated in the figure below: saphostexec.exe -upgrade -archive \SAPHOSTAGENT.SAR.
Figure 11: Self update for SAP Host Agent
Hint: The existing SAP host Agent needs patch level 134 (or higher) to support the direct upgrade from an archive. For lower patch levels, you will have to unpack the archive first. The operation should return in a success statement, such as: [OK] SAPHostExec / SAPHostControl successfully upgraded .
You may need to check the version of the SAP Host Agent afterwards again to ensure the upgrade worked.
Configuring SAP Host Agent for starting SUM The SAP Host Agent needs to know the location of SUM to be able to start the SUM (triggered by an appropriate HTTP request from the browser). This information is stored in a configuration file called sumabap.conf . You do not have to create or edit this file on your own, as the SUM has an option to create the file for you: STARTUP confighostagent The interconnection is illustrated in the figure below.
Figure 12: Creating SAP Host Agent Configuration File for Starting SUM
Note: The option confighostagent does not start the SUM or SAPup permanently, only for the short time it takes to create the file. The operation should return a success message, such as: Registering SUM in SAP Host Agent finished. The configuration file is created in a new sub directory operations.d. You may check the configuration file using Notepad, but do not c hange the content of the file.
Figure 13: Examining SAP Host Agent Configuration File
Note: Do not replace the placeholder terms in square brackets, as they are interpreted by SAP Host Agent. You have to be able to check whether the file exists. If it does not exist, the SAP Host Agent will return an error message when you try to start the DMO process from within a browser window.
Unit 2 Exercise 4 Configure SAP Host Agent for DMO 39
Business Example As an administrator, you are responsible for preparing a DMO procedure. You have to ensure that the SAP Host Agent fulfills the requirements.
Note: You will have to replace with the actual System-ID of your ABAP source system, such as T60.
Check the version of the SAP Host Agent and update it to a newer patch level. Check the version of the actual SAP Host Agent. Use the self-update function of the SAP Host Agent. Create the configuration file for the SAP Host Agent for starting the SUM.
Unit 2 Solution 4 Configure SAP Host Agent for DMO 40
Business Example As an administrator, you are responsible for preparing a DMO procedure. You have to ensure that the SAP Host Agent fulfills the requirements.
Note: You will have to replace with the actual System-ID of your ABAP source system, such as T60.
Check the version of the SAP Host Agent and update it to a newer patch level. Check the version of the actual SAP Host Agent. Switch to the Remote Desktop Connection on your ABAP source system host. Switch to the command prompt window on the host of your ABAP source system. Change to the directory of the actual SAP Host Agent. C: cd C:\Program Files\SAP\hostctrl\exe Use the -version option of saphostexec.exe to check the version: saphostexec.exe -version The console shows patch number 187, which is not sufficient for the DMO procedure. Use the self-update function of the SAP Host Agent. Use the -upgrade option to do a self-upgrade, referencing the archive with the -archive option: C:\Program Files\SAP\hostctrl\exe>saphostexec.exe
-upgrade
-archive D:\HA250\SAPHOSTAGENT0x_x-20009417.SAR (replace x with the actual patch level). You should get a success message such as: [OK] SAPHostExec / SAPHostControl successfully upgraded You may have to press enter to end the command. Check if the upgrade worked: saphostexec.exe -version It should write the applied patch level. Create the configuration file for the SAP Host Agent for starting the SUM.
Check if the actual directory of the SAP Host Agent contains an operations.d folder (check in the Windows Explorer window, or use the command dir in the command prompt). The operations.d folder does not yet exist. In the command prompt, switch to the D drive, and navigate to the SUM folder: D: cd D:\usr\sap\\SUM Use the confighostagent option of the SUM to create the configuration file for the SAP Host Agent: D:\usr\sap\\SUM>STARTUP.BAT confighostagent
Note: There is no minus sign required in front of the confighostagent option.
You should get a success message, such as: You are using SAP Host Agent version: .... Please check the central SUM note ... Verify that the actual directory of the SAP Host Agent now contains an operations.d folder with a sumabap.conf file . Optional: you may open the file sumabap.conf in Notepad.exe to check the content. It contains the command: D:\usr\sap\$[SID:#required]\SUM\abap\SUMSTART.BAT where the part $[SID:#required] will be replaced by the SAP Host Agent to start SUMSTART.BAT when requested.
LESSON OVERVIEW This lesson introduces the DMO UI. Business Example As an administrator, you have to configure the DMO procedure and need to know about the new UI and its features.
LESSON OBJECTIVES After completing this lesson, you will be able to: ●
Use the DMO UI
DMO UI DMO UI is Based on SAPUI5 ●
SAPUI5 is an SAP library used in apps and offered for own development.
●
The standard SUM use cases are also based on SAPUI5.
●
SAPUI5 is based on a javascript library (including jQuery).
The admin role is the only role that currently exists, so you cannot switch the roles. There is no role model, as there would be for a standard maintenance in SUM with administrator and observer . The Help menu contains links to the DMO guide and to the SAP Note on DMO. The last option Get Support File is discussed below. If you choose the Logoff button, you will be notified that you have to close the browser to log off. Some browsers do close the window, others do not.
1. The configuration of SAP Host Agent to start SAPup is optional, as the SAPup can be started without SAP Host Agent. Determine whether this statement is true or false.
1. The configuration of SAP Host Agent to start SAPup is optional, as the SAPup can be started without SAP Host Agent. Determine whether this statement is true or false.
X
True
X
False
The configuration of SAP Host Agent to start SAPup is not optional, as the SAP Host Agent serves as entry point for the HTTP requests from the browser. So a configuration file is required, for example to start SAPup.
LESSON OVERVIEW This lesson explains how to start the DMO run. Business Example As an administrator, you are responsible for starting and executing the DMO procedure.
LESSON OBJECTIVES After completing this lesson, you will be able to: ●
Start the DMO run
Start the DMO run You start the DMO procedure with an HTTP request from a browser.
Hint: The following figure illustrates that the browser is opened on the WTS, not on the host of the ABAP source system.
You have to supply the adm user and password, because the SAP Host Agent needs these to start the SAPup. The first DMO dialog is the specification of the stack.xml file.
Figure 23: First DMO Dialog: Stack Configuration File
If you want to provide a SPAM update after the DMO procedure has started, you will have to extract the archive manually, and place the update into the EPS\in directory.
Caution: Do not forget to set the first option to SAP HANA , otherwise only the system update will be executed.
Hint: Target database types SAP ASE and MS SQL are only available on request, and therefore not shown per default (specific configuration required).
Table comparison as part of DMO SUM conducts a count* for each table, counting the table rows. With SUM 1.0 SP11, the option to compare the tables based on checksums was introduced:
Table comparison as part of DMO ●
●
●
●
●
DMO always compares the number of rows (count*). The table comparison compares the content of rows. Tool checks the content of source and target database tables, using cyclic redundancy checksums (CRC). Tool generates checksums for every 10000 rows, for example, on source and target side. It then compares these. Tool digs deeper where checksums do not match, until conflicting rows are found. Tool stops after discovering more than 200 differences, for example, -> points to systematic errors.
Using table comparison ●
Any decisions are made in the Database Migration Option dialog, and can't be switched off later.
●
Checking all tables is for test systems only, due to performance load.
●
Checking happens in parallel for one table and multiple tables, via table splits.
●
Checking is for application tables only, repository tables are not allowed.
●
Runs during downtime, configuring downtime processes.
●
Checksum discrepancies are shown as errors.
●
Ignoring errors possible (use file MIGRATE_CHECK_CHECKDIFF.LST as proposed by tool) and repeat.
SUM SP10 (and above) offers an automatic setup of Landscape Reorganization for a SAP HANA Scale-out scenario. You will have to check the option in this dialog for the Landscape Reorganization to be executed later. You may have to use transaction SNOTE to apply SAP Notes required by SUM. SUM will now display the status of SPDD and SPAU. You should confirm all obsolete notes, and reset all not-adjusted objects with active SAP-version to SAP-standard.
Business Example As an administrator, you are responsible for executing the DMO procedure. You will start the DMO procedure, configure the phases of the first step Extraction, and get familiar with the new UI that the SUM offers exclusively for the DMO procedure. Start the DMO procedure and configure the first dialogs. Open the Chrome browser on your server TH-HA250SPSxx-### and start the DMO procedure. Provide the location of the stack.xml file. While the Work in Progress icon is shown, examine the UI of DMO, and detect the following elements: Legend, More menu, Roadmap Steps and Progress Bar, Tasklist and Logs and Breakpoints. You will examine the areas in detail later. Display the task list. Provide input for the Required System Passwords dialog. Check the process list of the host for SAPup processes. Open the Task Manager on the host of the ABAP source system. In the Task Manager, check the list of processes for SAPup processes. Examine further options of the DMO UI. Examine the menu options. Examine the Breakpoints. Set a breakpoint for phase GENBUFFER_TOOLIMP. Examine the SAPUPPHASES.LOG log from within the DMO UI. Continue the configuration of the Extraction phase. On the SPAM Version Check, skip the SPAM update. On the Database Migration Option dialog, choose Database Type On the Migration Parameters dialog, enter the migration key. Analyze the breakpoint encountered.
Verify that the migration option was selected by analyzing the log files. Handle the Open actions dialog in transaction SPDD and SPAU.
Note: In a real DMO run, you should follow the recommendations and adjust the obsolete and non-adjusted notes. But as the exercises will not reach the phase of required SPDD and SPAU, you can skip this step in the exercise.
Handle the roadmap switch from Extraction to Configuration.
Business Example As an administrator, you are responsible for executing the DMO procedure. You will start the DMO procedure, configure the phases of the first step Extraction, and get familiar with the new UI that the SUM offers exclusively for the DMO procedure. Start the DMO procedure and configure the first dialogs. Open the Chrome browser on your server TH-HA250SPSxx-### and start the DMO procedure. Use the shortcut on the taskbar to start the Chrome browser. Enter the following URL, replace with the System-ID of your ABAP source system, and with the host of your ABAP source system: http://:1128/lmsl/sumabap//doc/sluigui
Note: It is recommended to configure SSL for the SAP Host Agent. The port would then be 1129.
Log on using adm of your ABAP source system host. Provide the location of the stack.xml file. Specify the path and the name of the stack.xml file D:\usr\sap\\download\stack.xml Replace with the system-ID of your ABAP source system. Choose Next to continue. The Work in Progress icon is shown. While the Work in Progress icon is shown, examine the UI of DMO, and detect the following elements: Legend, More menu, Roadmap Steps and Progress Bar, Tasklist and Logs and Breakpoints. You will examine the areas in detail later. The Legend is listed up above right hand side. It explains the icons used on the user interface. The More menu offers several options that are used later. The Roadmap stepsshow 6 Roadmap Steps. The current roadmap step 1 Extraction is highlighted. The Progress Bar below the Roadmap Steps displays the percentage completed. The name of the current phase is listed below the Progress Bar. The Tasklist and the Logs are located at the right hand side of the window.
Display the task list. Click once on TASKLIST . The phases of the current roadmap step are listed in a sidebar area on the right hand side. Phases that have been executed are displayed with a green box. Click once again on TASKLIST . The list gets hidden.
Note: The list displays the phases of the current roadmap step only, not the complete list.
Provide input for the Required System Passwords dialog. Enter the requested passwords for the existing user DDIC (ABAP source system client 800), and SAPService. Choose Next to continue. The Work in Progress icon is shown. Check the process list of the host for SAPup processes. Open the Task Manager on the host of the ABAP source system. Use the existing Remote Desktop Connection to the host of the ABAP source system, or reopen the connection. Open the Task Manager. Right click on the task bar and choose the option Start Task Manager. In the Task Manager, check the list of processes for SAPup processes. Choose the Processes tab. Sort the processes by name, by clicking on the header of the first column Image Name. Add the column Command Line: use the menu View Select Columns ... and scroll down to find the Command Line checkbox. The columns are not listed alphabetically. →
Expand the width of the Task Manager and the width of the Command Line column to examine the command line. You should find two SAPup processes, one of them with option gt=httpchannel. Examine further options of the DMO UI. Examine the menu options. At the upper right corner of the browser window, the More menu displays. The menu offers various options like toggle the color schema, links to SUM guide and SUM SAP Note, the option Get Support File, and others. In case of UI issues, it may be required to provide the support file to SAP support. Examine the Breakpoints.
Note: Here, all phases are listed - in contrast to Tasklist, where only the phases of the current roadmap step are listed.
Set a breakpoint for phase GENBUFFER_TOOLIMP. Use the filter for the Description column. Enter a part of the phase name (like _TOOLIMP), and press enter. Mark the checkbox for the phase to set the breakpoint.
Note: You do not have to save the breakpoint s ettings.
Examine the SAPUPPHASES.LOG log from within the DMO UI. Open the LOGS area. You may sort the logs by name by clicking on the column header and choosing Sort Descending. Search for the SAPUPPHASES.LOG log by clicking on the Description column , entering SAPUP, and pressing enter. You can open the log by clicking on the name link SAPUPPHASES.LOG.
Note: SAPUPPHASES lists all phases of the procedure. SAPupConsole.log includes all inputs done during the SUM procedure.
You may scroll down if necessary to see the complete content of the log. Close the log using the Close button below or the close icon above. Continue the configuration of the Extraction phase. On the SPAM Version Check, skip the SPAM update. As SPAM level 60 is sufficient, you may skip the update. Choose option Skip SPAM update. Choose Next to continue. On the Database Migration Option dialog, choose Database Type
→
SAP HANA.
Switch the option DATABASE TYPE from No migration to SAP HANA. Choose Next to continue. The Work in Progress icon is shown.
On the Migration Parameters dialog, enter the migration key. Keep the option TABLES set to Do not compare table contents. Enter the migration key. Copy the key from the content of the Migration_key.txt file, located in the D:\HA250 folder on the host of the ABAP source system. You may enable the Test cycle option, but the exercises will not reach this point of processing. Choose Next to continue. The Work in Progress icon is shown. Analyze the breakpoint encountered. As you have set a breakpoint for phase GENBUFFER_TOOLIMP before, the DMO procedure stops here. Examine the options. Select option Continue in single step mode (stop before each phase) and choose Next to continue. The next step is shown as another breakpoint. Choose option End single step mode and continue to next breakpoint. Choose Next to continue processing without further breakpoints. Verify that the migration option was selected by analyzing the log files. First possibility, from within the UI, open the Log section and set filter for phase name. MIG2NDDB_INI. Click on the name of the phase to open the corresponding log. Open the log. It should contain a line with: 1 ETQ399 Setting target DB type to 'HDB'. Second possibility, on the host, open D:\usr\sap\\SUM\abap\log \SAPupConsole.log and search for Database Migration Option . You should find the option 02 with an asterisk: =========== Database Migration Option =========== Enter the target database type: 01)
-
No target database.
02)
*
SAP HANA
DATABASE TYPE: SAP HANA
Note: At the beginning of the DMO procedure, SAPupConsole.log cannot be displayed in the LOGS section of the UI. But it will be possible later during the procedure.
Handle the Open actions dialog in transaction SPDD and SPAU.
The dialog lists the objects of non-adjusted notes and modified objects. Choose Next to continue.
Note: In a real DMO run, you should follow the recommendations and adjust the obsolete and non-adjusted notes. But as the exercises will not reach the phase of required SPDD and SPAU, you can skip this step in the exercise.
Handle the roadmap switch from Extraction to Configuration. The roadmap switch dialog is shown, and the log for Checks.txt is displayed in a popup. Check the log for error information. Close the log popup, and choose Next to continue.
LESSON OVERVIEW This lesson explains further configuration steps in DMO. Business Example As an administrator, you are responsible for configuring the DMO procedure.
LESSON OBJECTIVES After completing this lesson, you will be able to: ●
Configure DMO Configuration phase
Configuring DMO Configuration Phase The roadmap step Configuration starts with the choice of the preconfiguration mode.
Hint: For DMO, the preconfiguration mode Single System is not offered. It would not work, as the shadow system is required. If you see the option, then you did not choose the migration to SAP HANA on the Database Migration Option dialog.
Note: If the dialog for your DMO run offers the option Single System, then you did not select the migration option before. You will have to reset your run and start again.
The difference between Standard and Advanced mode is only the number of processes assigned to the tools. These numbers are maintained in the next dialog.
Figure 30: Parameters for Procedure
So you may choose preconfiguration mode Standard, and then increase the number of processes to have the same values as preconfiguration mode Advanced.
Hint: The SUM option near-Zero Downtime Maintenance (nZ DM) is not available for a DMO procedure. The following figure provides an overview of the process parameters and their relevance during uptime and downtime processing of DMO.
Hint: The downtime shown in the figure is only the technical downtime processing of SUM. Downtime is longer and includes times where the SUM is not running, but the system cannot yet be used productively.
Figure 31: SUM Preprocessing Modes
Hint: Configuring a number of 12 R3load processes means that 6 R3load pairs will be used for the migration. Additional parameters can be set, but they are not DMO specific. The SUM option ICNV is not available for DMO.
You can adapt the number of processes later during the DMO procedure, even during the migration:
Changing Processing Parameters During Runtime ●
●
Use the More / Utilities menu Utilities menu , then choose SUM Parameters / Process Parameters. Parameters. A new browser window displays with a URL containing slui gui_ext. Access via a browser in a separate window: http://:1128/lmsl/sumabap//set/procpar
●
Use the Command Prompt: SAPup set procpar gt=scroll
●
For all 3 ways: SAPupParameterConsole.log SAPupParameterConsole.log log log is written. During the next exercise, the command prompt option will be used. The browser access shows a non-SAPUI5 design. For both, you may show that an additional (third) SAPup process is started.
Hint: The system-ID of the SAP HANA DB is different to the system-ID of the ABAP source system. This does not mean that the ABAP system changes its systemID.
Business Example As an administrator, you have to configure the DMO steps. Configure the DMO procedure and spec ify parameters about the SAP HANA database. In the Tool Configuration dialog, examine the preconfiguration mode for DMO. Compare the number of processes for Standard and Advanced mode. Disable SGEN. Check SAPupConsole.log to verify that you have switched off the ABAP load generation (SGEN). On the Hana Database Client Installer dialog, provide the path to the installation files. On the Required System Passwords dialog, provide the password for the adm user on your host. Provide input for the Database Migration Initialization dialog. On the Required Migration Specific Passwords dialog, provide the password for the SYSTEM user on SAP HANA database. Optionally, specify the password for the new user DBACOCKPIT.
Note: This dialog is only shown if the user does not yet exist. If the DMO procedure of another training group is migrating to the same SAP HANA database, the user may already haven been created.
Specify the password for the new user SAPSID. Change the R3load uptime parameter to 8, usi ng the Utilities option. Open the Utilities window from the More menu. Open the Process Parameters within the Utilities window. Continue to configure the DMO Configuration phase. Handle the DMO dialog Include Change Request. Handle the DMO dialog Modification Adjustment. Handle the roadmap switch from Configuration to Checks.
Business Example As an administrator, you have to configure the DMO steps. Configure the DMO procedure and spec ify parameters about the SAP HANA database. In the Tool Configuration dialog, examine the preconfiguration mode for DMO. Compare the number of processes for Standard and Advanced mode. Disable SGEN. The preconfiguration mode offers two options, and option Standard is preselected. Keep this option.
Caution: If your dialog shows the option Single System, you did not select the migration option before. DO NOT CONTINUE here, but reset the run and start from the beginning.
Keep the two checkboxes (archiving and expert mode) unselected. Choose Next to continue. On the next dialog Parameters for procedure, examine the parameters, especially the number of R3load processes. Scroll down and choose Back to return to the previous dialog. The previous dialog Tool Configuration is displayed again. Now choose the second option Advanced, and choose Next to continue. Keep the checkbox Reinitialize dependent values on next screen selected, otherwise you will not see the impact of choosing the Advanced mode. The dialog Parameters for procedure is displayed again. Examine the parameters again, especially the number of R3load processes. Switch the Execution mode for SGEN to the first option Do not start ABAP load generation during the uptime.
Caution: Be sure that SGEN will not be started, as this would take so long that you will not be able to execute the following exercise steps.
Check SAPupConsole.log to verify that you h ave switched off the ABAP load generation (SGEN). Switch to the operating system of your ABAP host. Open log file D:\usr\sap\\SUM\abap\log\SAPupConsole.log with Notepad. Search for the string SGEN to find your selection on the dialog: Choose an execution strategy for transaction SGEN 01)
*
Do not start ABAP load generation during the update.
The star * indicates your choice. On the Hana Database Client Installer dialog, provide the path to the installation files. Specify the path (to the installation files for hdbclient) to the directory in which you have extracted the archive, for example: D:\HA250\SAP_HANA_CLIENT Choose Next to continue. On the Required System Passwords dialog, provide the password for the adm user on your host. Enter the password for the user adm user on your ABAP host. Choose Next to continue. Provide input for the Database Migration Initialization dialog. Specify the host name of the SAP HANA database as wdflbmt7215. Set the Hana SID to H00.
Note: This is the system-ID of the SAP HANA database itself. It does not mean that the ABAP system will get a new system-ID.
Keep the default value 00 for the Hana Instance Number. Set the Target System License field to: D:\HA250\_multiple.txt.
Note: For the license file name, you have to replace with the system-ID of your ABAP source system.
Choose Next to continue. On the Required Migration Specific Passwords dialog, provide the password for the SYSTEM user on SAP HANA database. Enter the password for the existing user SYSTEM on SAP HANA database. Choose Next to continue. Optionally, specify the password for the new user DBACOCKPIT.
Note: This dialog is only shown if the user does not yet exist. If the DMO procedure of another training group is migrating to the same SAP HANA database, the user may already haven been created. Enter a password that is in line with the SAP HANA DB password restrictions, for example, W3lcome123. Enter the same password in the second entry field, and check if the icon turns green. Choose Next to continue. Specify the password for the new user SAPSID. Enter a password that is in line with the SAP HANA DB password restrictions, for example, W3lcome123. Enter the same password in the second entry field, and check if the icon turns green. Choose Next to continue. Change the R3load uptime parameter to 8, usi ng the Utilities option. Open the Utilities window from the More menu. On the DMO browser window, use More / Utilities menu. A second browser window opens. Open the Process Parameters within the Utilities window. Select the menu entry SUM Parameters in the list on the left-hand side. Select the area Process Parameters in the list on the right-hand side. You may have to scroll to the right to see this area. Scroll down to find the text field R3LOAD PROCESSES (UPTIME) with the parameter value 12. This is according to the Advanced Mode, but the value may be too high for the small training system. Change the value to 8. Scroll up to the upper part of the window, and choose Next to save the adapted value.
Continue to configure the DMO Configuration phase. Handle the DMO dialog Include Change Request. As we do not want to include a change request, do not add a line, and leave the list empty. Choose Next to continue. Handle the DMO dialog Modification Adjustment. As we do not have a modification adjustment, do not provide input for the two e ntry fields.
Choose Next to continue. Handle the roadmap switch from Configuration to Checks. The dialog Continue roadmap Checks is shown, and the CHECKS.TXT log is shown in a popup. Check the log for error messages. Close the popup and choose Next to continue.
Handle the DMO dialog Parameters for BI-Specific reports. Keep the default values for the amount of data to be deleted. Choose Next to continue. Handle the roadmap switch from Checks to Preprocessing. The dialog Continue roadmap Preprocessing is shown, and the CHECKS.TXT log is shown in a popup. Check the log for error messages. Close the popup and choose Next to continue.
Unit 3 Lesson 3 Configuring DMO step Preprocessing 84
LESSON OVERVIEW This lesson covers some configuration steps for DMO step Preprocessing. Business Example As an administrator, you have to configure the DMO procedure.
LESSON OBJECTIVES After completing this lesson, you will be able to: ●
Configure roadmap preprocessing
DMO Step Preprocessing
Figure 43: BI specific reports Scr
Note that data deleted will not be restored by the DMO reset.
Depending on the SAP Notes you had to implement, you may be asked to release the associated transport requests.
Hint: The dialog about open repair is only shown if the transport includes objects that are affected by the update of the system. After some time, the DMO procedure proposes to lock the development environment.
After a while, the SUM asks to prepare the table partitioning for the scale up scenario.
Note: Scale up is proposed if the Execute Landscape reorg option (Scale out) was not selected on the Migration Parameters for DMO dialog. The following steps after this dialog are covering migration, and they are discussed in the next lesson. As the downtime migration (migration of the application tables) are not covered in the exercises, the required actions of this dialog for scale-up are not required for the course systems. The steps after the migration are not DMO specific, and take a long time. That is why they are not covered in this course.
Steps for using the SUM Observer Mode Use the latest SAP Host Agent, incl. configuration (STARTUP confighostagent). Create OS user obs on the Application Server. Use a specific URL with that user: https://:1129/lmsl/sumobserver// monitor/index.html.
Note: Port 1128 has to be used if SSL is not configured
Unit 3 Solution 7 Configure Roadmap Preprocessing 90
Business Example As an administrator, you are responsible for configuring the DMO procedure.
Handle the Lock Development Environment dialog. The Lock Development Environment dialog displays. It only allows continuation after the development environment is locked by the SUM.
Note: The lock for the development environment does not hinder end users to continue their business work on the system.
Choose Next to continue. After this dialog, the SUM creates the shadow repository on the source database. The DMO procedure will continue until the next dialog, but this will take quite a while.
As an administrator, you want to check a l ong running SUM procedure, so you choose the SUM Observer Mode for this. Create OS user obs on the Application Server. Open the SUM Observer Mode, using the new user.
As an administrator, you want to check a long running SUM procedure, so you choose the SUM Observer Mode for this. Create OS user obs on the Application Server. On the OS of your ABAP host, open Control Panel
→
User Accounts.
Choose Manage another account, then Create a new account. Specify the New account name as obs (where SID is either T60 or T64), keep the option Standard user, and choose Create Account. On the list of existing accounts, scroll down to find the new user obs. Click on the user name to get options displayed, then choose Change the password. Enter the new password W3lcome123 twice. Choose Change password to save the new password. Open the SUM Observer Mode, using the new user. Open a new browser window, and use the URL http://:1128/lmsl/
sumobserver//monitor/index.html Log on with the new user obs. The SUM Observer Monitor displays. The SUM Observer Monitor can be used on a smart device as well. In the training environment, this cannot be shown.
LESSON OVERVIEW This lesson gives an overview of the general steps of the DMO procedure. Use the explanation of the steps to motivate why additional files are required for the DMO procedure (compared to a standard maintenance like a system update).
Business Example You are responsible for the execution of a DMO procedure, and you have to explain to the upper management how the DMO procedure works, and why the procedure can easily be reset.
LESSON OBJECTIVES After completing this lesson, you will be able to: ●
List the general steps of the DMO procedure
●
Explain why additional kernel files are required for the DMO procedure
DMO procedure steps The DMO procedure consists of some general steps. It is important to understand these to prepare the DMO procedure, and to properly monitor the procedure. The DMO procedure has to be prepared, so that the latest Software Update Manager (SU M) is available, and the SAP Host Agent has been updated to the latest version. The figure below shows the SAP HANA database that has to be organized beforehand as well. The following figures show the Primary Appli cation Server only (PAS — formerly known as Central Instance), because the SUM has to be located on the PAS. The system is running, the existing kernel executables that are comprised in an instance (such as work processes) are running on the application server, based on the source release. The database consists of the application data and the repository (such as programs). The repository is abbreviated as PRD REP to emphasize that it is the productive repository, used by the system. The DMO procedure is started from within a browser, sending an HTTP reque st to the SAP Host Agent, as shown below.
The SAP Host Agent requests authorization from the browser, this user is used to start the SUM. As the DMO procedure is only working on AS ABAP based systems (for which the SAPup is the relevant SUM part), the SAPup is started. After some basic configuration settings, such as checking the stack.xml, the SAPup will start to create the shadow system. The shadow system consists of a shadow repository and a shadow instance. The shadow repository is created on the source database, in a separate section. It contains the basic tables and some customizing tables, which will already be updated to the target release during uptime. The shadow repository does not influence the PRD repository. The system is still running, and end users may work in the system and use functionality (like a transaction) that may change application data on the database. The shadow instance is running on the PAS host, and is based on the shadow kernel. The shadow kernel is the kernel for the source database, but for the target release.
The shadow system requires additional database space, and resources on the application server host. The SAPup will check the status, and ask for additional resources if required. As the shadow repository is being built up on the target release, changes on the PRD repository are no longer allowed, as they would not be considered on the shadow repository. This is why in this phase, the system is running and available for end users (uptime processing), but the development environment is locked. After the shadow repository has been built up completely, it is copied onto the target database, the SAP HANA database.
The kernel executable R3load is triggered by SAPup to execute the copy of the shadow repository.
Hint: You can see in the figure above that two additional kernels are required for the DMO procedure, both on the new SAP release, but one for the source database, and one for the target database. Now the application tables have to be updated to the new release, so the system has to be shutdown to prevent changes on the application tables. The downtime migration is executed, in which the target kernel is used in addition: it is the kernel for the new database (SAP HANA DB) and for the target release.
Figure 53: Downtime Migration
For the migration of the application data, two R3load processes are running in parallel. The first R3load of the shadow kernel exports the data from the source database, and the second R3load process imports the data into the target database (SAP HANA). Both R3load processes are running on the PAS host. The DMO configuration includes configuring the number of R3load pair processes to run in parallel.
After the migration of the application data, the shadow instance is removed. The target kernel is now used for the system, and the system is started. The system is still in downtime because it cannot be used by end users. Now the application tables are updated to the target release.
Figure 55: Update of Application Tables
Finally, the DMO procedure is finished. The system is now migrated to the target database, and updated to the target release.
R3load modes The DMO procedures uses R3load for the migration, like the classical migration based on the Software Provisioning Manager (formerly known as SAPinst) does. For the typical classical migration, the R3load file mode is used.
Figure 56: R3load for Classical Migration with File Mode
The file mode means that the export files are created, and imported later. Meanwhile, it is also possible to use a parallel export and import for the classical migration. Another possibility for the classical migration is to use the R3load socket mode, which transfers the files using a socket connection.
Figure 57: R3load for classical migration with socket mode
With the DMO procedure, both R3load processes are executed on the same host, the PAS host. This allows the use of the R3load pipe mode which transfers the data using the main memory of the host. No files are created, and so no directory has to be prepared to host all export files.
Figure 58: R3load for DMO Using Pipe Mode
In case the R3load stops, the SAPup will restart the process without the need of manual intervention of a user. The SUM can be configured to use the R3load file mode instead of the pipe mode. In this case, only temporary files are created. As soon as a file has been processed by the R3load import process, the file is deleted. With SUM 1.0 SP13 and higher, the pipe mode is used for all cases. Discuss aspects of the DMO procedure
FACILITATED DISCUSSION Of which two components does the shadow system consist of?
FACILITATED DISCUSSION What is the advantage of using a shadow system?
FACILITATED DISCUSSION Why is the source database available for an easy reset even after the DMO procedure reaches the end?
LESSON OVERVIEW This lesson explains the table split and migration procedure. Business Example As an administrator, you are responsible for the DMO procedure and you would like to analyze how the SAPup is migrating the tables.
LESSON OBJECTIVES After completing this lesson, you will be able to: ●
List the DMO steps relevant for table migration
DMO Migration Procedure The migration to SAP HANA DB takes place partially in uptime (UT) processing and partially in downtime (DT) processing of SAPup.
The shadow repository is created on the source database (on target release) and then copied to the SAP HANA DB.
The application tables are migrated (on source release) to SAP HANA DB, and converted to the target release later (in phase PARCONV_UPG).
Transport of tables into SAP HANA based on files in directory.
Hint: In error case, there is no need to adapt files. SAPup is recreating a valid *.TSK file by itself. After the table creation on SAP HANA DB, the DMO procedure shows a dialog proposing the Landscape Reorganization. The sequence of the migration phases is as follows:
DMO migration step phase sequence ●
EU_CLONE_MIG_UT_SIZES
●
EU_CLONE_MIG_DT_SIZES
●
REQ_SCALEUP_PREREQ (scale up, if scale out not chosen)
●
EU_CLONE_MIG_UT_CREATE
●
EU_CLONE_MIG_DT_CREATE
●
EU_CLONE_MIG_UT_PRP
●
EU_CLONE_MIG_UT_RUN (end of exercise)
●
EU_CLONE_MIG_DT_PRP (DT starts afterwards)
●
EU_CLONE_MIG_DT_RUN
Only the migration of the application data is done during downtime (phase EU_CLONE_MIG_DT_RUN).
Hint: Some phases with DT in the name are executed during uptime processing.
Relevant directories for migration are:
Relevant folders for migration
Creation of repository tables.
Prep and run of repository table content migration.
Prep and run of application table content migration.
Log files as described below.
Hint: For the create parts, the folder creation and e xecution are handled together in one phase (no split into prep and run).
DMO table splitting Big tables have to be handled in several buckets, so they have to be split. For table splitting in DMO, the following applies:
DMO table splitting ●
●
SAPup decides what to split. No manual table selection required. Technically, R3ta is not used to generate split conditions. SAPup uses its own logic for table splitting.
●
Tables and table parts are organized in buckets. A bucket is executed by an R3load pair.
●
Big tables are split into segments.
●
The number of segments per table is number of buckets per table.
●
No need for manual configuration.
The relevant log files for migration are as follows:
Relevant log files for migration
Number of buckets, total size: 1 ETQ399 Command file 'MIGRATE_UT.BUC': 1373 tables in 52 tasks, size 21893.9 MB (estimated as 90375.4 MB). Details of R3load process execution: 3 ETQ123 (1): PID x exited with status 0 (time 0.000 real) 3 ETQ123 (0): PID y exited with status 0 (time 0.000 real) 3 ETQ399 ============= , Progress z MB/21894 MB (xx.yy%) Summary on migration speed: 2 ETQ399 Summary (export+import): time elapsed 37:36, total size x MB, x.yz MB/sec ( x.yz GB/hour). With SUM 1.0 SP 16 (and higher), the Utilities window offers a new area to monitor the R3load processes. It is even possible to reschedule a process that is in status error. That way, you do not have to wait until all the packages are processed and an error message is displayed on the
SL UI. The Process Buckets monitor also lists the export and import duration, and offers easy access to the log file of the respective process. Note that some new tables are only imported, so there is only one R3load working on that bucket (instead of two). This is visible in the Process Bucket monitor, as only the import duration is listed, and only the import log is made available.
Figure 60: Process Bucket Monitor
Tables in SAP HANA in row and column store For a target release 7.40 (and above), the information about row or column store is part of the dictionary. For customer tables, this information has to be set manually in the shadow repository after it has been created on the source database. For a target release 7.31, SUM will use a file that contains the row/column information (SUM \abap\bin\ROWSTORELIST_DMO.txt ). Customer tables can be added manually into this file to provide the row or column store assignment.
Unit 3 Exercise 9 Monitor the Uptime Migration 107
Business Example As an administrator, you want to monitor the migration progress of the DMO procedure. Analyze the log files of a DMO migration procedure.
Note: The DMO procedure does not require you to work with the control files or the log files, but you may be interested in gaining some insight into checking the log files.
On the Perform Scale Up (Single Node) dialog, continue the procedure. Open the DMO Migration Control Center, and switch on Automatic Refresh for the Process Buckets section. After the phase EU_CLONE_MIG_UT_PRP has finished, analyze the log file EUMIGRATEUTPRP.LOG to determine the overall number of Process Buckets for uptime migration. Check SAPupStat.log for estimated end of submodule. Check log file EUMIGRATEUTRUN.LOG for percentage completed. Think about how many Process Buckets you expect to run at a time. Check the Process Bucket monitor in the DMO Migration Control Center for the current R3load pairs. Check the performance of the host. In case the phase EU_CLONE_MIG_UT_RUN finished with several failed packages, this may be caused by a systematic error. Then align with your partner group (using the same target SAP HANA DB in the same landscape) if it is required to stop and start the SAP HANA target database (using Putty), and when to do s o. After that, repeat the migration step from within the UI.
Note: After the phase is finished, the Preparations for Downtime dialog is displayed (see figure, Sequence of Following Exercises). Do not proceed on this dialog.
If the phase EU_CLONE_MIG_UT_RUN finished without failed packages, check for the migration rate.
Unit 3 Solution 9 Monitor the Uptime Migration 108
Business Example As an administrator, you want to monitor the migration progress of the DMO procedure. Analyze the log files of a DMO migration procedure.
Note: The DMO procedure does not require you to work with the control files or the log files, but you may be interested in gaining some insight into checking the log files.
On the Perform Scale Up (Single Node) dialog, Node) dialog, continue the procedure. Choose Next to Next to continue the procedure. Open the DMO Migration Control Center, Center, and switch on Automatic on Automatic Refresh for Refresh for the Process Buckets section. Buckets section. In the UTILITIES window, UTILITIES window, choose DMO Migration Control Center, Center, then Charts Control Center. Center. The Charts Control Center will Center will only show data once the migration phase has started. Collapse the sections Realtime Migration Graph and Graph and SAP HANA Server Load. Load. Keep the section Process Buckets open, Buckets open, as you will monitor the running R3load processes here later. Set the display to Automatic to Automatic Refresh with Refresh with the second icon (in the line of the header). After the phase EU_CLONE_MIG_UT_PRP EU_CLONE_MIG_UT_PRP has has finished, analyze the log file EUMIGRATEUTPRP.LOG to EUMIGRATEUTPRP.LOG to determine the overall number of Process Buckets for uptime migration. Return to the main DMO process browser window. Open the LOGS section. LOGS section. Filter the Description column Description column by log file name EUMIGRATEUTPRP.LOG EUMIGRATEUTPRP.LOG.. Open the EUMIGRATEUTPRP.LOG EUMIGRATEUTPRP.LOG log log file by selecting the log file name. Scroll down to the end of the log file and look for a line starting with “Command file”: 1 ETQ399 Command file 'MIGRATE_UT.BUC': 1373 tables in 52 tasks, size 21893.9 MB (estimated as 90375.4 MB). 52 tasks are equivalent to 52 buckets. Note that the number of tasks may be different for your configuration.
Optionally, the log file MIGRATE_UT.BUC is not part of the log folder, log folder, so it is not offered on the UI. To check it, switch to the remote desktop connection for connection for your host. Open the log file from within windows explorer: explorer: D:\usr\sap\\SUM\abap\migrate_ut \MIGRATE_UT.BUC. \MIGRATE_UT.BUC. Two sync points are included in MIGRATE_UT.BUC to MIGRATE_UT.BUC to separate name tabs, column store, and row s tore tables. Check SAPupStat.log for SAPupStat.log for estimated end of submodule. On the More / Log Tail menu, Tail menu, select SAPupStat.log. SAPupStat.log. The display will be refreshed automatically. Check log file EUMIGRATEUTRUN.LOG EUMIGRATEUTRUN.LOG for for percentage completed. Open the LOGS section. LOGS section. Filter the Description column Description column by log file name EUMIGRATEUTRUN.LOG EUMIGRATEUTRUN.LOG.. Open the log file EUMIGRATEUTRUN.LOG EUMIGRATEUTRUN.LOG by by selecting the log file name. Scroll down to the end of the log file and look for the last entry with the following pattern. Check the percentage shown in brackets (xx.yy%). 3 ETQ123
