LabelServer4j: Difference between revisions
Replaced content with "{{LabelServer4j}}" Tag: Replaced |
Updated by push_wiki.py |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{LabelServer4j}} | '''LabelServer4j''' is a background label printing service that bridges Commander4j and physical label printer devices on a production line. When an operator assigns a [[Process Orders|Process Order]] to a production line, Commander4j exports a data file which LabelServer4j picks up, processes through a configurable script, and uses to drive the printer over TCP/IP. | ||
LabelServer4j supports Zebra ZPL printers, Logopak labellers, and any device that accepts raw TCP/IP text commands. It runs as a headless background service with no graphical interface, and can manage multiple printers simultaneously in independent threads. | |||
== Getting Started == | |||
{| class="wikitable" style="width:100%" | |||
|- | |||
| [[Overview LabelServer4j]] || What LabelServer4j does and how it differs from AutoLab4j | |||
|- | |||
| [[Downloads]] || Download the latest release | |||
|- | |||
| [[Installation LabelServer4j]] || Installing LabelServer4j and configuring as a Windows service | |||
|- | |||
| [[LabelServer4j Configuration]] || Configuring sites, labellers, and database connections | |||
|- | |||
| [[LabelServer4j Folder Structure]] || Directory layout and purpose of each folder | |||
|} | |||
== User Guide == | |||
{| class="wikitable" style="width:100%" | |||
|- | |||
| [[LabelServer4j Operation]] || End-to-end workflow from order assignment to label printed | |||
|- | |||
| [[LabelServer4j Dataset CSV]] || Fields available in the CSV data file from Commander4j | |||
|- | |||
| [[LabelServer4j Example User Interface]] || Deployment, startup, monitoring, and log file reference | |||
|} | |||
== Related Pages == | |||
{| class="wikitable" style="width:100%" | |||
|- | |||
| [[Production Lines & Labellers]] || Configuring production lines in Commander4j | |||
|- | |||
| [[Process Order Assign to Labeller]] || Assigning orders to labellers from Commander4j | |||
|- | |||
| [[Zebra ZPL Label]] || ZPL label template syntax reference | |||
|- | |||
| [[Label Template Syntax]] || Commander4j label template language | |||
|- | |||
| [[ZPLRenderer]] || Tool for previewing ZPL labels before printing | |||
|} | |||
[[Category:LabelServer4j]] | |||
Latest revision as of 17:56, 5 April 2026
LabelServer4j is a background label printing service that bridges Commander4j and physical label printer devices on a production line. When an operator assigns a Process Order to a production line, Commander4j exports a data file which LabelServer4j picks up, processes through a configurable script, and uses to drive the printer over TCP/IP.
LabelServer4j supports Zebra ZPL printers, Logopak labellers, and any device that accepts raw TCP/IP text commands. It runs as a headless background service with no graphical interface, and can manage multiple printers simultaneously in independent threads.
Getting Started
| Overview LabelServer4j | What LabelServer4j does and how it differs from AutoLab4j |
| Downloads | Download the latest release |
| Installation LabelServer4j | Installing LabelServer4j and configuring as a Windows service |
| LabelServer4j Configuration | Configuring sites, labellers, and database connections |
| LabelServer4j Folder Structure | Directory layout and purpose of each folder |
User Guide
| LabelServer4j Operation | End-to-end workflow from order assignment to label printed |
| LabelServer4j Dataset CSV | Fields available in the CSV data file from Commander4j |
| LabelServer4j Example User Interface | Deployment, startup, monitoring, and log file reference |
Related Pages
| Production Lines & Labellers | Configuring production lines in Commander4j |
| Process Order Assign to Labeller | Assigning orders to labellers from Commander4j |
| Zebra ZPL Label | ZPL label template syntax reference |
| Label Template Syntax | Commander4j label template language |
| ZPLRenderer | Tool for previewing ZPL labels before printing |