Service queue - technical note
The WorkZone database has a register service_queue which is used to control the tasks the agents perform.
The following agents may exist in a Captia Web Client installation:
Agent | Description |
---|---|
AgentFIX |
Responsible for the free text indexing of documents and records. |
AgentOCR |
Responsible for producing a textual version of tiff documents. |
AgentSUB |
Responsible for publishing documents. |
Scanjour.Service |
Responsible for scanning documents, importing files and mails into the WorkZone system. |
When a document is imported into Captia Web Client, a job is either queued for the OCR agent to produce an OCR version of the document or a job is queued for the FIX agent requesting the document to be indexed. When cases and records are created in the database, a job to index these is also queued for the FIX agent.
When the Scanjour.Service is used to import documents or mails, these types of jobs are also queued for the agents. To avoid that the scanned documents block the agents' work, initiated by interactive users of Captia Web Client, the database implements a number of tables used by the service_queue. The actual table used depends on the user. In the system 5 users are special because they see a table in a different schema:
User |
Schema and table |
---|---|
Normal users |
sjsysadm.service_queue |
sjserviceagentuser |
sjsysadm.service_queue |
sjserviceagentuser1 |
sjserviceagentuser1.service_queue |
sjserviceagentuser2 |
sjserviceagentuser2.service_queue |
sjserviceagentuser3 |
sjserviceagentuser3.service_queue |
sjserviceagentuser4 |
sjserviceagentuser4.service_queue |
sjserviceagentuser5 |
sjserviceagentuser5.service_queue |
It is possible to start the agents (except AgentSUB) under a special user, the /queue=n (n>=1, n<=5) controls which of the 5 special users above is used, when the agent calls SOM. If no queue is specified, the sjserviceagentuser will be used as default.
The documents inserted into the database will result in new jobs for the OCR or FIX agent - these jobs will end up in sjserviceagentuser1.service_queue. This queue requires that FIX and OCR using queue=1 (and running under sjserviceagentuser1) are installed and running, because these agents will be the only ones able to see the table sjserviceagentuser1.service_queue.
Other scanners or mail importers using Scanjour.Service may be set up to use other queues which will prevent them from blocking the work of each other (and the interactive Captia Web Client users work as well).