Extractor Request Monitor serves as a tool for monitoring ongoing or past extraction processes.

You can access it via GLUE cockpit, transaction /DVD/GLUE → Tools → Request monitor.

After accessing Request monitor, a filter for requests comes up where you can specify your selection based on the following fields:

Extraction process - name of the extractor or extraction process of Extractor 2.0
GLUE request - number of GLREQUEST
Status - status of a request (success, error, warning, running, failed)
Username - name of the user which executed the extraction
As of Date - date data is displayed from
As of Time - time data is displayed from
Maximum no. of hints - maximum number of records displayed

After clicking on the Execute button, the request monitor displays all records according to the selection.

Records are sorted by the date and time of an extraction (newest first).

Monitor screen functionalities

On the monitor screen you can:

Refresh the results for a real-time monitoring
Display logs for each request, using a button in the Logs column
Delete request together with data on the target storage
Clean request metadata resulting in deletion of GLUE request metadata while keeping data on the target storage
Display selection used for data extraction
Restart failed requests in case these were executed via Extractor 2.0 Mass Execution capabilities
Standard ALV functionalities like displaying details of the row, sorting and filtering
Redirect to standard SAP transactions like Job monitor, Process overview, SAP servers

Refresh

You can refresh the monitor by using Refresh button shown in the next image:

The Refresh button causes monitor to load the latest state of the GLUE requests while keeping the selection you specified.

Display logs

In order to keep information about the execution of the extraction, each GLUE request keeps execution logs. You can see this logs by double-clicking on the row belonging to a particular request in the request monitor.

After the double-click you will be redirected to the log screen.

In some cases e.g. when the request is running or failed, the logs are not stored in the standard application logs.
Therefore, you will be redirected to the joblog of SM37 where you can find similar information about the execution of the extraction.

Delete request

The request monitor allows you to delete the data of particular GLUE request. Using this option both metadata and data on the target storage will be deleted.
This functionality requires the field GLREQUEST to be present in the target structures and will display an error message in case it's not.

In order to delete the particular GLUE requests, select these in the ALV grid of the monitor and press delete button, shown on the next image.

After clicking on the Delete button the following dialog will pop-up:

In order to continue, select yes. After that you should see the pop-up allowing you to select between the dialog or background execution.

We recommend to use Background execution for deleting requests with large amount of data or when deleting more than a few smaller requests.
When using Background execution, you will have to press refresh button to see the requests being deleted.

In case you proceed and select dialog mode, you will see the following log after the execution of the deletion:

In case any error occur, you will see it in the logs and the request together with it's data will not be deleted.
If you chose the Background execution, you can find these logs within the standard application logs for GLUE.

If you are deleting the requests in a state running, you will see one additional message.

You can proceed to the deletion by selecting Yes but please be aware of a few limitation.

In case you are deleting the request that runs in a background job, the program attempts to stop the job in order to keep the data consistency.
If this fails (e.g. due to insufficient privileges) the request won't be deleted.
In case you are deleting the request that runs in dialog, the program has no way to stop the job and therefore this action might lead to data inconsistencies on the target storage.
Therefore, we recommend you not to delete the running requests that are executed in dialog.

Clean request metadata

This functionality is similar to Delete request functionality. However, it keeps the data on the target storage and deletes the only the metadata in GLUE.

In order to delete metadata for particular requests, select these in the ALV grid of the monitor and press Clean request metadata button, as shown in the image:

After pressing the Clear request metadata button, you will see the following pop-up:

To continue select Yes. After that you should see the log informing you about metadata deletion.

If you are deleting metadata for running requests, you will see one additional message.

You can proceed to metadata deletion by pressing Yes. However, such an action is not recommended unless you know what you are doing.
Deleting metadata of running requests won't stop the running jobs, neither touch the data on the target storage and might lead to data inconsistencies on the target.
The only proper use of the deletion of the running request is in case when the request stuck in the running state (e.g. unexpected error in custom code).

Display selection

This functionality allows you to browse the selection that was used for execution of a particular request.

To display the selection, click the Display selection button on ALV grid, within the line of the request you want to see selection for.

After executing the Display selection, you will see the pop-up with used selection or the message informing you about the fact that the process has no selection filled in case no selection was used for the particular extraction.

Restart failed requests

The Extractor 2.0 introduces the new Mass Execution capabilities see (Glue-2005) Mass Execution page.
If the request was created via Mass Execution and for some reason failed to extract the data, you are able to restart it directly from the monitor screen using the button that is displayed in the column Action.

You need to press the Restart button in order to re-execute the failed request. After that you will see the pop-up informing you about the restart of the request.

After successful restart, the new request will be created and the possibility to restart the original one is removed. It means that you can restart the request (with particular request number) only once.

In case the new request would fail as well, you will be able to restart this request using the same logic however as the new request (different request number),

Browser not supported