Production Integrations: Local Print Server

Production Integrations: Local Print Server

Introduction
This production integration uses a locally installed software to manage print queues, this works to manage production of any hardware with a windows driver.

Integration Setup
Requirements:
  1. PC with Internet Access
  2. At least 1 Printer that has Windows Drivers
  3. GhostScript PDF Software (v9.26 specifically) contained in the install files attached in the "additional software - install first" folder
  4. Amazon S3 Bucket credentials
  5. USB Barcode scanner that supports Serial over USB *
*The software can be used manually without a barcode scanner but if a barcode Scanner is required, make sure that it supports Serial over USB (this is normally enabled by scanning the relevant Barcode config in the Manual)

The configuration of the Print Server is managed by 2 config files:

CG.PrintServer.UI.exe.config - This is where the Application settings are stored.




PrinterDefinitions.json - Where the Printers and Media Profiles are set.



The file has comments against the first Printer that explain what the settings are.

Only a few values need to be changed:

name: this is the name of the Printer within Windows, this needs to match exactly

Within profiles: (this is what the media in the print.json refers to)
Name: A descriptive name for that profile
Kind: The size of the paper, printable area e.g. A4

Print jobs
The Print Server software will poll an S3 Bucket for new orders from a Jobs_Pending folder
And once it has retrieved the information, these will be placed in the Jobs_Consumed folder


Job Sheets are placed in the root of the Jobs_Pending folder and these will be automatically printed to a specified printer without intervention.


Each Print Job has its own folder containing the artwork and a JSON file: (the filename of the Jobsheet can be set to a preferred format by Northgate we just need to let them know, for testing I have been using the test format.)





The JSON file contains only a few fields:

id: this is the Barcode Number and needs to match what is sent on the Job Sheet
name: this is the name that will be displayed in the Queue 
media: These details need to match a profile that in the PrinterDefinitions.json file, this is how jobs are assigned to specific printers, the fields are type and kind
orientation: depends on the printer settings, whether it prints in landscape or portrait


And this how it is displayed in the Queue:


If a Print Job cannot find a printer or the PrinterDefinitions file or the print.json refers incorrectly, those jobs will automatically move to the Failed Queue:


Right clicking on one will give the options to Reset or Remove that Job.

You can also right click in a blank area below the jobs to clear any Failed items (if you do this and want to rework the job, it would need to be moved back into the Jobs Pending folder on S3

Still Need Help?
You can access our extensive knowledge base or raise a ticket with our technical support teams using the buttons below



    • Related Articles

    • Production Integrations: Cloud RIP

      Cloud RIP Integration Help Introduction A diagram of how the CloudRIP process works is availble here and should be reviewed for background before setting up - https://docs.google.com/drawings/d/1vNp73oGYRgwWfXCSNmOuNQ6vgnJdqZdZjVhsBixh6ms/preview ...
    • Production Integrations: Hotfolder Feed

      Introduction Kornit X have produced a production solution we call Hotfolder Feed. This is made up of the system modules we offer and an local piece of software used to manage queues and move artwork and jobsheets to printing locations. A high level ...
    • Production Integrations: Quick P

      Kornit Quick P Help Note - The Kornit Quick P PRODUCTION INTEGRATION should not be used in conjunction with the RIP INTEGRATION of the same name. The RIP INTEGRATION performs the same functions as the PRODUCTION INTEGRATION and should be used on its ...
    • Production Integrations: Caldera Prime Centre

      Caldera Prime Centre Integration Help Like other production integrations this should be enabled on a PRODUCTION CENTRE company if it is required. For this particular integration all it requires is to be enabled and for you to add your Local Output ...
    • Production Integrations: PrintFactory

      Introduction Kornit X have produced an integration with Print Factory - https://app.printfactory.cloud/ This is a Production Integration as the Production Module allows jobs to be sent to Print Factory which then manages print and production itself. ...