After you configure XBOUND to import documents, you can track what is happening.
If the XBOUND Collect Service is installed and running correctly, the batch is imported into XBOUND automatically, typically within a few seconds. You can see this happening when the file extension of the trigger file changes from .rdy to .bsy and then to .imp. These extensions come from the collector configuration, and you can specify different extensions if that is helpful.
You can see import progress from the extension of the trigger file:
.rdy (or other extension that you specified): The batch is ready for import.
.bsy (or other extension): The batch is being imported right now.
.imp (or other extension): The import of the batch is finished.
.err (or other extension): An error occurred while importing the batch. You can find information on the cause of error in the Windows Event Viewer or the log file of the Collect Service.
If the extension of the trigger file remains unchanged at .rdy,
ensure that the Collect Service is running (how?) and
that the application server is configured correctly (see Installing
XBOUND).
Now you can display the documents in the Process Monitor.
Tracking and adjusting document processing