LabelServer4j - Revision history

Dgarratt: Updated by push_wiki.py

2026-04-05T15:56:01Z

Updated by push_wiki.py

← Older revision		Revision as of 17:56, 5 April 2026
Line 10:		Line 10:
	\|-		\|-
	\| [[Downloads]] \|\| Download the latest release		\| [[Downloads]] \|\| Download the latest release
			\|-
			\| [[Installation LabelServer4j]] \|\| Installing LabelServer4j and configuring as a Windows service
	\|-		\|-
	\| [[LabelServer4j Configuration]] \|\| Configuring sites, labellers, and database connections		\| [[LabelServer4j Configuration]] \|\| Configuring sites, labellers, and database connections

Dgarratt: Updated by push_wiki.py

2026-04-01T10:26:19Z

Updated by push_wiki.py

← Older revision		Revision as of 12:26, 1 April 2026
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
			\|-
			\| [[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]]

Dgarratt: Replaced content with "{{LabelServer4j}}"

2024-08-28T08:25:02Z

Replaced content with "{{LabelServer4j}}"

← Older revision		Revision as of 10:25, 28 August 2024
Line 1:		Line 1:
	LabelServer is a module of [[Commander4j]] which is designed to send data provided by Commander4j to external Labellers via a script which is just plain text. The script can contain specific printer commands and or data in whatever combination is needed. Therefore the application can accomodate a variety of printer types.		{{LabelServer4j}}

	~~It shares a lot with the [[AutoLab4j]] module but has some important differences as well.~~

	~~Rather than replicate wiki pages across the multiple Commander4j modules - some of the links will take to the relevant wiki page of the referenced program.~~

	AutoLab4j is designed to send data when requested via a Modbus signal and is intended to generate a unique SSCC on each request. This makes the [[AutoLab4j]] program more suitable for [[Pallet Label]].

	The LabelServer application will send data to a labeller when an operator has assigned an order to a production line within the Commander4j application. This is more suitable for [[Case Label]] where the data remains the same (no SSCC).

	~~You should refer to the documentation on [[Production Lines & Labellers]]~~

Dgarratt: Created page with "LabelServer is a module of Commander4j which is designed to send data provided by Commander4j to external Labellers via a script which is just plain text. The script can contain specific printer commands and or data in whatever combination is needed. Therefore the application can accomodate a variety of printer types. It shares a lot with the AutoLab4j module but has some important differences as well. Rather than replicate wiki pages across the multiple Comma..."

2024-08-28T08:20:33Z

Created page with "LabelServer is a module of Commander4j which is designed to send data provided by Commander4j to external Labellers via a script which is just plain text. The script can contain specific printer commands and or data in whatever combination is needed. Therefore the application can accomodate a variety of printer types. It shares a lot with the AutoLab4j module but has some important differences as well. Rather than replicate wiki pages across the multiple Comma..."

New page

LabelServer is a module of [[Commander4j]] which is designed to send data provided by Commander4j to external Labellers via a script which is just plain text. The script can contain specific printer commands and or data in whatever combination is needed. Therefore the application can accomodate a variety of printer types.

It shares a lot with the [[AutoLab4j]] module but has some important differences as well.

Rather than replicate wiki pages across the multiple Commander4j modules - some of the links will take to the relevant wiki page of the referenced program.

AutoLab4j is designed to send data when requested via a Modbus signal and is intended to generate a unique SSCC on each request. This makes the [[AutoLab4j]] program more suitable for [[Pallet Label]].

The LabelServer application will send data to a labeller when an operator has assigned an order to a production line within the Commander4j application. This is more suitable for [[Case Label]] where the data remains the same (no SSCC).

You should refer to the documentation on [[Production Lines & Labellers]]