...
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 who 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.
...
After clicking the display logs button, you will be redirected to the log screen.
| Note |
|---|
In some cases e.g. when the request is running or failed, the logs are not stored in the standard application logs. |
...
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.
| Note |
|---|
We recommend to use using the Background execution for deleting requests with a large amount of data or when deleting more than a few smaller requests. |
In case you proceed and select dialog mode, you will see the following log after the execution of the deletion:
In case any error occurs, you will see it in the logs, and the request together with its data will not be deleted.
If you chose the Background execution, you can find these logs within the standard application logs for GLUE.
| Note |
|---|
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 limitations.
|
...
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.
...
| Note |
|---|
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. |
...
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.
| Note |
|---|
After a 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 a 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), |
...