SUM Utilities (Extended UI)

The Software Update Manager Utilities (SUM Utilities) extend the SUM user interface and provide an easy way to configure, monitor, and analyze the SUM run.

To open the SUM Utilities, choose Utilities from the More menu on the SUM UI: Menu Bar. A new web browser window opens with an "extended user interface" that offers you various additional options:

The options in detail:

Navigation	Description
SUM Parameters	This option enables you to adapt the configuration of your SAP system by processing the following parameters: SUM Process Parameters (such as the number of ABAP processes, SQL processes, R3trans processes). Further options are: Control of the ABAP batch job execution. That is, you can specify a dedicated server, or you let the system decide where to run the jobs. Decision on the reconfiguration of the temporary instance or the shadow instance. This is especially relevant when you have chosen the scenario strategy Downtime-optimized. The temporary instance is affected when you have selected the downtime-optimized Database Migration Option. The shadow instance, on the other hand, is affected when you work with the near-Zero Downtime Maintenance (nZDM). To monitor the reconfiguration, use the CRR Control Center which is mentioned in the following section Process Control Center. SUM Shadow System Parameters (such as the instance number) SUM Migration Parameters (such as the migration key) SUM Passwords Each dialog with a password request is displayed here again. This can be passwords for user DDIC SAP Service user (SAPServiceSID) shadow system user DDIC database user SYSTEM shadow database user SYSTEM SUM Migration Passwords (such as system user password for the target database. The password concerns the database migration and refers to the password for the database user SYSTEM of the target database) Note In each dialog box, you can enter a new password that overwrites the existing password. Note, however, that you do not change the password in your SAP system, but only the password that the Software Update Manager uses to communicate with your SAP system.
SUM Analysis	SUM Analysis This option visualizes the UPGANA.XML file, which contains detailed information about the update procedure and the runtime of the different phases. See also Using the SUM Analysis Feature.
Process Control Center	For more information, see the following table.
DMO Migration Preparation	This option is relevant if you are executing the database migration option (DMO) of the Software Update Manager. For more information, see the DMO guide.
DMO Migration Post Analysis	This option is relevant if you are executing the database migration option (DMO) of the Software Update Manager. For more information, see the DMO guide.

Process Control Center

With the Process Control Center, you can monitor and handle running processes. It consists of the following options:

Charts Control Center (Process and Load Monitor)

On the view Evolution of Parallel Processes, you can monitor the R3load processes that run in parallel during phase EU_CLONE_MIG_*_RUN. The moving graph shows in real time the number of currently running R3load processes depending on the time. By moving the horizontal slider, you can dynamically increase or decrease the total number of R3load processes.

The following Process Buckets table provides you with information about the status of each R3load process pair, that is, export and import processes. If an R3load process fails, you can analyze the appropriate log file and restart the R3load process pair provided that the issue is solved. For the restart, select the appropriate row and choose Reschedule in the top-right corner of the table.

Note that during the update procedure the SUM UI can inform you about failed buckets by means of the Failed Buckets Notification Flag (see also SUM UI: Flags). The flag disappears after you have restarted failed buckets successfully.

CRR Control Center (Replication Process Monitor)

Shows the current status of the Change Recording & Replay (CRR) procedure during the uptime. For more information about CRR, see Using the Record & Replay Technique in nZDM.

This information is relevant for the Using the near-Zero Downtime Maintenance (nZDM) Feature technology as well as for the downtime-optimized Database Migration Option. For more information about the downtime-optimized DMO, see the Planning section of the DMO Guide.

Current Replication Status

This view gives you an overview of the ABAP-based and the R3load-based replication status. If both the ABAP-based and the R3load-based replication status are used in parallel, the system provides a total CRR status.

If the CRR status is 75% and higher and the indicator Ready for Downtime: displays a Yes, you can enter the downtime and continue with the update.
ABAP Replication Monitor

This monitor displays the number of background processes that are used for the replication in the shadow instance. You can set the number of background processes by using the plus or minus button or by entering a number directly. Afterwards, you must accept the change to save the new number of processes.
Note

The number of background processes is limited to the value of parameter ABAP PROCESSES (UPTIME) that was defined during the Configuration roadmap step. The maximum number of processes that can be used for replication depends on the actual available background processes during the start of the replication.

The list shows all tables currently processed by the ABAP-based replication and gives additional information. It is possible to use predefined filters for Planned, Idle, Running, and Failed table entries. Click the Show Logfile button to get more information about the replication processing.
R3load Replication Monitor

You can start and stop the R3load replication process and dynamically adjust the number of parallel R3load replication processes. The list displays the tables currently being replayed and their status and progress.

Additionally, you see a list of running buckets from which you can navigate to the individual log files. The list also allows you to filter for failed processes to restart them. This feature is described in the DMO guide. Note that with R3load replication, you can restart individual buckets instead of stopping and starting the whole R3load replication.

If there are issues, see Error Handling for the Replication Process Monitor.

Process Control Center (Background Process Monitor)

This view displays all registered background processes and its status. In addition, you can start, stop, or kill such a background process.

The Software Update Manager starts background processes, for example, for the replication. They run in parallel beside the SAPup work process. In general, all registered background processes have the status running.