69 Exercise 5: Start the DMO procedure
Task 5: Implement missing SAP Notes
The SUM checks for required SAP Notes, and lists them. You have to download and implement these notes before the procedure can continue. Follow the instruction of the dialog Missing SAP Notes for Tools and apply the missing SAP Notes in the ABAP source system
Note: Not all SAP Notes may be applicable, but even non-applicable notes must be downloaded so that the SUM can check whether they are existing. For this exercise, some SAP Notes were already implemented in the ABAP source system beforehand.
1. Download missing SAP Note(s) in the ABAP source system.
2. Implement downloaded SAP Notes.
3. Continue the DMO procedure.
Solution 5: Start the DMO procedure
Task 1: Start the DMO procedure
Start the DMO procedure and configure the first dialogs.
1. Open the Chrome browser on your server HB-HA250SPS8-### and start the DMO procedure.
a) Use the shortcut on the taskbar to start the Chrome browser.
b) Enter the following URL, replace <sid> with the System-ID of your ABAP source system, and <host> with the host of your ABAP source system:
http://<host>:1128/lmsl/sumabap/<sid>/doc/gui
Note: It is recommended to configure SSL for the SAP Host Agent. The port will then be 1129.
c) Log on using <sid>adm of your ABAP source system.
2. Provide the location of the stack.xml file to the DMO procedure.
a) Use the link Default Pattern to set the default path.
Note: Although the default path is written in Unix syntax, the SAPup will interprete it correct for Windows OS as well.
b) Add the name of the stack.xml file at the end of the pattern (with a preceding slash) so that the path becomes
/usr/sap/<sid>/download/stack.xml
Replace <sid> with the system-ID of your ABAP source system.
c) Choose Next to continue.
The “Work in Progress” icon is shown.
Continued on next page
3. While the “Work in Progress” icon is shown, examine the UI of DMO, and detect the following elements: Tool Tabs; Roadmap steps;
Progress Bar; Work in Progress icon; Menu; Phaselist Toggle. You will examine the areas in detail later.
a) The Tool tabs is the top menu, listing COCKPIT and UTILITIES.
Later you will see that they may have a sub structure (sub menu).
b) The Roadmap steps are shown below the Tool Tabs. There are 6 Roadmap Steps. The current roadmap step is 1 Extraction.
c) The Progress Bar displayes the percentage completed, and the current phase.
d) The Work in Progress icon in the center is animated and illustrates the running process that does not require any input.
e) The Menu shows admin, Help, and a logoff button.
f) The Phase list Toggle is located at the right hand side of the window, and shows the text CURRENT PHASELIST, in horizontal direction, from top to bottom.
4. Display the phase list.
a) Click once on the Phase List Toggle CURRENT PHASELIST.
b) The phases of the current roadmap step are listed in a sidebar area on the right hand side.
c) Phases that have been executed are displayed with a tick mark in front.
The phase currently running is preceded by a C in a green circle.
d) Click once again on the Phase List Toggle CURRENT PHASELIST.
The phaselist gets hidden.
Note: The list displays the phases of the current roadmap step only, not the complete list.
5. Examine the estimation of the progress bar.
a) Move the mouse cursor over the progress bar to get additional information displayed.
b) Moving the mouse away from the progress bar will hide the additional information.
Continued on next page
6. Provide input for the Required System Passwords dialog.
a) Enter the requested passwords for the existing user DDIC (ABAP source system client 800), SAPService<sid>, and <sid>adm.
b) Choose Next to continue.
The Work in Progress icon is shown, and the phase SCANDIR_EPS0 is executed.
Task 2: Check for SAPup processes
Check the process list of the host for SAPup processes.
1. Open the Task Manager on the host of the ABAP source system.
a) Use the existing Remote Desktop Connection to the host of the ABAP source system, or reopen the connection.
b) Open the Task Manager. You may do a right-mouse click on the task bar and choose the option Start Task Manager.
2. In the Task Manager, check the list of processes for SAPup processes.
a) Choose the tab Processes.
b) Sort the processes by naming by clicking on the header of the first column Image Name.
c) Add the column Command Line: use the menu View –> Select Columns ... and scroll down to find the checkbox for Command Line (the columns are not listed alphabetically).
d) Expand the width of the Task Manager and the width of the column Command Line to examine the command line. You should find two SAPup processes, one of them with option gt=httpchannel.
Continued on next page
Task 3: Examine the DMO UI.
Examine further options of the DMO UI.
1. Examine the menu options.
a) At the upper right corner of the browser window, the UI displays three elements.
b) The first element shows the role admin. There is no menu behind this.
Note: The UI currently does not offer other roles (e.g.
observer) like for a classical update / upgrade with the SDT GUI of SUM.
c) The Help menu offers to change the color schema, an About entry, and the option Get Support File. Depending on the SUM version used, the other options are currently not used, or provide access to DMO guide and DMO note.
d) In case of UI issues, it may be required to provide the Support File to SAP support.
e) The third element is the Logout icon. Clicking the icon will display a dialog explaining that you have to close the browser to log off.
2. Examine the Tooltab UTILITIES.
a) Switch to the menu entry UTILITIES.
b) You find the sub menus Logs and Breakpoints.
c) Switch to Breakpoints.
Note: Here, all phases are listed - in contrast to Current Phaselist, where only the phases of the current roadmap step are listed.
3. Set a breakpoint for phase GENBUFFER_TOOLIMP.
a) Use the filter for column Phase Name.
b) Enter a part of the phase name (like _TOOLIMP), and press enter.
c) Mark the checkbox for the phase to set the breakpoint.
Note: You do not have to save the breakpoint settings.
Continued on next page
4. Examine the log SAPUPPHASES.LOG from within the DMO UI.
a) Navigate back to the LOGS menu.
b) You may sort the logs per name by clicking on the column header and choosing Sort Descending.
c) Search for the log SAPUPPHASES.LOG by clicking on the column Log File, entering SAPUP, and pressing enter
d) 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.
e) You may scroll down if necessary to see the complete content of the log.
f) Close the log using the Close button below or the “close icon” above.
Task 4: Continue the configuration.
Continue the configuration of Extraction phase.
1. On the SPAM Version Check, skip the SPAM update.
a) As SPAM level 53 is sufficient, you may skip the update.
b) Choose option Skip SPAM update.
c) Choose Next to continue.
2. On the Database Migration Option dialog, choose Database Type SAP HANAand maintain the migration key.
a) Switch the option DATABASE TYPE to SAP Hana.
b) Enter the migration key. You may copy the key from the content of the file Migration_key.txt, located in folder D:\HA250 on the host of the ABAP source system.
c) Choose Next to continue.
d) The “Work in Progress” icon is shown.
Continued on next page
3. Analyse the breakpoint encountered.
a) As you have set a breakpoint for phase GENBUFFER_TOOLIMP before, the DMO procedure stops here.
b) Examine the options.
c) Select option Continue in single step mode (stop before each phase) and choose Next to continue.
d) The next step is shown as another breakpoint.
e) Choose option End single step mode and continue to next breakpoint.
Choose Next to continue processing without further breakpoints.
4. Verify that the migration option was selected.
a) Open the Current Phaselist section, scroll down to phase 42 PREP_INPUT/MIG2NDDB_INI.
b) Click on the name of the phase to open the corresponding log c) The log should contain a line with
1 ETQ399 Setting target DB type to 'HDB'.
d) Open
D:\usr\sap\T60\SUM\abap\log\SAPupConsole.logon the host 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
Continued on next page
Task 5: Implement missing SAP Notes.
The SUM checks for required SAP Notes, and lists them. You have to download and implement these notes before the procedure can continue. Follow the instruction of the dialog Missing SAP Notes for Tools and apply the missing SAP Notes in the ABAP source system
Note: Not all SAP Notes may be applicable, but even non-applicable notes must be downloaded so that the SUM can check whether they are existing. For this exercise, some SAP Notes were already implemented in the ABAP source system beforehand.
1. Download missing SAP Note(s) in the ABAP source system.
a) Copy the list of SAP Note numbers from the dialog into the clipboard.
b) Switch to the ABAP logon of user admin in client 800 (or logon again with user admin).
c) Start transaction SNOTE.
d) Open the download dialog by using menu Goto –> Download SAP Notes.
e) On the popup Note Assistant: Note download, use the button Multiple Selection.
f) Paste the SAP Note numbers from the clipboard into the popup list.
g) Choose Copy (F8) to return to the fist popup.
h) Choose Execute (F8) to start the download of the SAP Notes.
Continued on next page
2. Implement downloaded SAP Notes.
a) In transaction SNOTE, open the area New under SAP Notes with a single click.
b) Select the first SAP Note with a single click, and choose the first button Implement SAP Note (Ctrl+F1) to start the implementation.
c) Read the information popup (that no valid corrections are contained), and close the popup with Enter.
d) Select the next SAP Note with a single click, and choose the first button Implement SAP Note (Ctrl+F1) to start the implementation.
e) Read the text of the popup Confirmation: SAP Note read, and confirm by choosing Yes.
Note: Of course you should read the content of the SAP Note as well in a real life scenario.
f) Read the information popup (about repairs in foreign namespaces), and close the popup with Enter.
g) On the Prompt for local Workbench request popup, choose the Create Request (F8)button.
h) On the Create Request popup, enter a Short Description (like SAP Notes for DMO). Choose the Save (Enter) button to continue.
i) Back on the Prompt for local Workbench request popup, choose the Continue (Enter)button.
j) Choose enter on all following popups.
k) Repeat the procedure for all SAP Notes listed in the area New.
3. Continue the DMO procedure.
a) Switch to the DMO browser window.
b) If the Session Timeout popup is shown, choose Re-connect to refresh the browser page.
c) On the Missing SAP Notes for Tools dialog, choose Next to continue.
Note: The next dialog is shown: Continue roadmap Configuration. It will be handled in the following exercise.
Lesson Summary
You should now be able to:
• Start the DMO run
Lesson:
80