Overview LabelServer4j - Revision history

Dgarratt: Updated by push_wiki.py

2026-04-01T10:26:15Z

Updated by push_wiki.py

@@ Line 1: / Line 1: @@
-[[Category:LabelServer4j]]
+LabelServer4j is a background label printing service that acts as a bridge between Commander4j and physical label printer devices on a production line. It monitors for incoming label requests, processes them through configurable scripts, and communicates with printers over TCP/IP.
-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.
+== Multi-Site and Multi-Printer ==
-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.
+LabelServer4j supports multiple sites (each with its own <code>labellers.xml</code>) and runs each configured printer in an independent background thread. Multiple printers operate simultaneously without interfering with one another.
-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]].
+== Database Integration ==
-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).
+LabelServer4j can connect directly to the Commander4j database to perform SQL queries during script execution. This allows label content to be dynamically enriched with data that is not included in the CSV file — for example, querying the current status of an order or looking up a reference value.
-You should refer to the documentation on [[Production Lines & Labellers]]
+See also: [[LabelServer4j Configuration]], [[LabelServer4j Operation]], [[LabelServer4j Dataset CSV]], [[Production Lines & Labellers]]
-[[file:ManualLabAutomated2.gif|link=|800px]]
+[[Category:LabelServer4j]]

Dgarratt at 09:24, 1 September 2024

2024-09-01T09:24:46Z

← Older revision		Revision as of 11:24, 1 September 2024
Line 11:		Line 11:

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

			[[file:ManualLabAutomated2.gif\|link=\|800px]]

Dgarratt at 11:12, 31 August 2024

2024-08-31T11:12:29Z

← Older revision		Revision as of 13:12, 31 August 2024
Line 1:		Line 1:
			[[Category:LabelServer4j]]
	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.		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.

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:25:15Z

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]]