Request Queue: Difference between revisions
Created page with " link=|700px" |
No edit summary |
||
| Line 1: | Line 1: | ||
When you use one of the transactions within the application which has a output message defined for it the application will put a request in a queue. This queue holds a list of all the unprocessed messages and is polled by the Interface process. When the interface process is running the queue is normally empty. However if the interfaces are not running then all requests for output messages will be held in this queue until the interfaces are started again. | |||
[[file:Interface_Request_Queue.png|link=|700px]] | [[file:Interface_Request_Queue.png|link=|700px]] | ||
Revision as of 21:28, 26 August 2024
When you use one of the transactions within the application which has a output message defined for it the application will put a request in a queue. This queue holds a list of all the unprocessed messages and is polled by the Interface process. When the interface process is running the queue is normally empty. However if the interfaces are not running then all requests for output messages will be held in this queue until the interfaces are started again.
