1.5
Page 18
No. of Pages
1
%5
Number of pages of the
job
Number of pages of the
job
No. of Copies
1
%6
Number of copies set by
the user
Number of copies set by
the user
Domain Name
1
%7
The Domain Name
"na"
Machine Name
1
%8
The Machine Name
"na"
1
) These values originate from the Printer Driver machine.
The variables can and should be used to create dynamic file and folder names for each print job.
This enables separating "licensed" and "unlicensed" jobs and/or storing the files by domain,
machine and even user name.
File extension
If the output file name does not include an extension, the default extension “.ps” is added
automatically. The plug-in will also create a Workflow metadata file with the same name
containing basic information about the job.
Main steps in using OLCS
If OLCS is unlicensed, the plug-in stores the incoming job in the target folder using the specified
file name, but it does not save any information in the database. The client will receive a message
in its SysTray confirming the unlicensed status, and the printer driver will not request another
web page.
In licensed mode, the plug-in will store all relevant information about each job in the database.
This database is a HSQLDB and is installed automatically. Subsequent Workflow processes can
use the information in the database for additional processing.
The main steps in using OLCS are:
1.
A user prints a document to a printer using the OLCS printer driver.
2.
The print job is captured by the printer driver code, zipped up, and if applicable, split into
multiple chunks.
3.
These chunks are transferred to the
Workflow
process and received by the OL Connect
Send plug-in.
4.
The plug-in communicates with the printer driver to ensure that all data has been received
correctly.
5.
The plug-in combines all the chunks into a .7z and then unpacks it to the original print job.
This is a Postscript file.
6.
The plug-in stores the print job at a specified location with a specified name.
7.
The plug-in creates a Workflow metadata file for the print job, containing basic job
information. (See License Modes – Basic Mode, below.)
8.
The plug-in (if licensed) stores all job related info in a database.
9.
The plug-in returns a status message to the client, indicating a successful or failed job
transfer.
10.
The plug-in sends the license status to the Printer Driver.