Local Holding of Print Jobs

Print jobs can become very large depending on the printer driver. If narrowband long-distance lines are used, it makes sense to store the print jobs locally.

For example, two offices connected by a long-distance line (WAN) can be operated with one IQ4docs installation. By default, a system area is created where the workflow files directory is created. The print jobs are stored here. In the example, the print jobs are therefore transmitted via the (narrowband) long-distance line.

The following solutions avoid this.

A system area is an independent area within the IQ4docs installation. A workflow is processed completely (locally) in a system area. Only one system area (usually the default system area) has its own database (MongoDB), and the other system areas use this database.

Apart from the database, a system area consists of:

  • RabbitMQ (not clustered with a RabbitMQ of another system area - the services of the system area work with this RabbitMQ)

  • PrintService and all other services required to operate IQ4docs

  • WorkflowFiles directory

  • Windows printer queue

Now, when a print job in a system area is sent to the IQ4docs system, the following happens:

  • The user prints via the local printer queue, which points to the local PrintService, see also Printer Driver Installation.

  • The PrintService receives the print job and stores it in the WorkflowFiles directory, which is specified in the system area to which it belongs, see also System Areas.

  • When sending to the device, the PrintService of its own system area is again used.

  • The device itself is also assigned to a system area (in the data record of the device), meaning it also communicates with the local DeviceService.

With a system area, not only print files but all types of workflow files (scan files as well, for example) can be kept locally.

A local PrintService is a Windows service that performs some of the functions of a PrintService. It receives print data - like a print service - and stores it locally. The storage directory is always the WorkflowFiles subdirectory within the installation directory.

When a print@me print job is printed at a device, the local PrintService sends the job to the device.

A PrintService does not necessarily need a server but can also run on a PC (but still accepts print jobs from multiple computers).

The PrintService is not part of the standard installation but is available separately.