You use the Watch Queues function in the TREX admin tool in the SAP system (transaction TREX_ADMIN) to monitor queues. You can track the processing of documents and check to see whether errors have occurred. In particular, you can check whether the system cannot preprocess, index, or optimize documents. If such problems occur, you can get more information on individual documents using the Get Entries/Documents function.
A table displays the following information:
Information |
Purpose |
Queue ID |
Queue ID |
Queue State |
Current status of the queue (see What Does the Status of a Queue Mean?). |
Last index/optimize |
Time at which the queue server last triggered indexing or optimization. |
Return Code |
Return value that the index server sends to the queue server. Meaning:
|
Delayed ... Invalid |
Overview of how many documents have each status (see What Does the Status of a Document Mean?). The values in the column Invalid have the following meanings:
|
When you next display the queue, fewer documents may have the status OK. This can occur if the application sends documents that have already been indexed to TREX again. These documents are subjected to an entire processing run again. The queue server therefore changes the document status back from OK to To Be Preprocessed.