QuickLoadDocID in PrintBOS

What is QuickLoadDocID and How to Use It?

QuickLoadDocID is designed to accelerate the full loading and readiness of "PrintPRS" by preloading 53 mandatory parameters required for precise identification and retrieval of templates for a specific Job request.

These 53 mandatory parameters can be stored locally in an SQLite file (PBAPPPARAMS) or managed through an SQL server.

PrintBOS Template

A collection of components, including FMT, SMT, scripts, images, and other elements.

Example of Use in an Environment

In this environment, there are two PrintBOS servers for load balancing:

• PrintBOS_Server_1 – has a common set of templates and components with PrintBOS_Server_2 – which are stored in a common storage.
• PrintBOS_Server_2 – has a common set of templates and components with PrintBOS_Server_1 – which are stored in a common storage.

How to Use QuickLoadDocID to Improve Performance?

Using a shared "Microsoft SQL Express" is recommended for each PrintBOS server.

Implementation Steps:

1. Open PrintBOS UI and navigate to Server Administrator Settings.
2. In the CFG section, set the QUICKLOADDOCID parameter to 1.
3. In the SET 1 section, add the following value for the DB Connection String:
   PB_USE_REPORT_DB=SQL_SERVER;

4. Save changes by clicking Apply.
5. Fully restart PrintBOS (no need for a full VM reboot).
6. Once the PrintBOS server is operational again, execute Reload Templates.

Important! These steps must be performed on all PrintBOS production servers, but Reload Templates is enough to be performed on only one of them. After these steps are performed, the [PrintBOS].[dbo].[TemplateInfo] table in the PrintBOS Database will be populated. This file contains 53 mandatory parameters for each FMT template.

What Are the Benefits?

Each PrintPRS on each PrintBOS server loads its required set of templates on startup. All PrintBOS servers share a single SQL database for query tracking and statistics.

Critical Note! Any modifications to any PrintBOS project require executing Reload Templates on the machine where the changes were made.