Commander4j - Recent changes [en-gb]

User:JiMHXLwVHDqDIDaIYAQoOIcJ

JiMHXLwVHDqDIDaIYAQoOIcJ — Mon, 27 Apr 2026 06:07:55 GMT

User account JiMHXLwVHDqDIDaIYAQoOIcJ was created

File:SFTPTransfer.jpg

Dgarratt — Fri, 24 Apr 2026 17:54:03 GMT

Dgarratt uploaded File:SFTPTransfer.jpg

New page

SFTPTransfer

Dgarratt — Fri, 24 Apr 2026 17:53:51 GMT

← Older revision		Revision as of 19:53, 24 April 2026
Line 6:		Line 6:

	SFTPTransfer automates recurring file transfers between Commander4j and external systems — for example, uploading despatch notifications to a customer portal or downloading order files from a supplier. It runs continuously, polling for new files at a configurable interval, and handles authentication, retry, backup, and archiving without operator involvement.		SFTPTransfer automates recurring file transfers between Commander4j and external systems — for example, uploading despatch notifications to a customer portal or downloading order files from a supplier. It runs continuously, polling for new files at a configurable interval, and handles authentication, retry, backup, and archiving without operator involvement.

			[[File:SFTPTransfer.jpg\|800px]]

	== Startup Modes ==		== Startup Modes ==

ZPLRenderer

Dgarratt — Fri, 24 Apr 2026 16:34:15 GMT

← Older revision		Revision as of 18:34, 24 April 2026
Line 12:		Line 12:
	* Print the rendered label directly from the application		* Print the rendered label directly from the application

	[[File:ZPLRenderer.~~png~~\|800px]]		[[File:ZPLRenderer.jpg\|800px]]

	== Running ZPL Renderer ==		== Running ZPL Renderer ==

File:ZPLRenderer.jpg

Dgarratt — Fri, 24 Apr 2026 15:19:57 GMT

Dgarratt uploaded File:ZPLRenderer.jpg

New page

ZPLRenderer

Dgarratt — Fri, 24 Apr 2026 15:18:39 GMT

← Older revision		Revision as of 17:18, 24 April 2026
Line 11:		Line 11:
	* Export the rendered label to PDF		* Export the rendered label to PDF
	* Print the rendered label directly from the application		* Print the rendered label directly from the application

			[[File:ZPLRenderer.png\|800px]]

	== Running ZPL Renderer ==		== Running ZPL Renderer ==

User:MaudeDriggers

MaudeDriggers — Tue, 14 Apr 2026 22:37:27 GMT

User account MaudeDriggers was created

File:JLaunchPad.png

Dgarratt — Thu, 09 Apr 2026 07:58:13 GMT

Dgarratt uploaded File:JLaunchPad.png

New page

LaunchPad

Dgarratt — Thu, 09 Apr 2026 07:56:11 GMT

Updated by push_wiki.py

← Older revision		Revision as of 09:56, 9 April 2026
Line 1:		Line 1:
	LaunchPad is a macOS application organiser and launcher. It provides a tabbed grid interface for grouping macOS applications (.app bundles) into named categories and launching them with a double-click. It is a companion tool to the Commander4j suite, used to organise the suite's tools and supporting applications in a single place.		LaunchPad is a macOS application organiser and launcher. It provides a tabbed grid interface for grouping macOS applications (.app bundles) into named categories and launching them with a double-click. It is a companion tool to the Commander4j suite, used to organise the suite's tools and supporting applications in a single place.

			[[File:JLaunchPad.png\|thumb\|right\|500px\|JLaunchPad showing the Desktop tab]]

	== Purpose ==		== Purpose ==
Line 7:		Line 9:
	== Running LaunchPad ==		== Running LaunchPad ==

	~~A native macOS install package~~ is available from the [[Downloads]] page and is the ~~preferred installation method~~.		The easiest way to run LaunchPad is to double-click the <code>JLaunchPad.app</code> bundle. This is available from the [[Downloads]] page and launches the application exactly as you would any other macOS application.

	Alternatively, LaunchPad can be run ~~directly~~ from the ~~distribution archive. It is a Java 21 desktop (Swing) application for macOS~~:		Alternatively, LaunchPad can be run from the command line using:

	java -jar JLaunchPad.jar		java -jar JLaunchPad.jar

LabelServer4j Example User Interface

Dgarratt — Sun, 05 Apr 2026 16:05:04 GMT

Updated by push_wiki.py

← Older revision		Revision as of 18:05, 5 April 2026
Line 6:		Line 6:

	The native install package includes <code>LabelServer.exe</code>, a service-mode launcher that manages the Windows service directly. All commands must be run from an elevated command prompt (Run as Administrator).		The native install package includes <code>LabelServer.exe</code>, a service-mode launcher that manages the Windows service directly. All commands must be run from an elevated command prompt (Run as Administrator).

			The default service name is '''LabelService'''. A custom name can be passed as an optional second parameter — if used, the same name must be supplied to all subsequent commands.

	{\| class="wikitable"		{\| class="wikitable"
Line 11:		Line 13:
	! Command !! Effect		! Command !! Effect
	\|-		\|-
	\| <code>LabelServer.exe /install</code> \|\| Register ~~the service~~ with automatic startup on boot		\| <code>LabelServer.exe /install</code> \|\| Register as '''LabelService''' with automatic startup on boot
	\|-		\|-
	\| <code>LabelServer.exe /install-demand</code> \|\| Register ~~the service~~ with manual startup only		\| <code>LabelServer.exe /install "My Label Service"</code> \|\| Register with a custom service name
			\|-
			\| <code>LabelServer.exe /install-demand</code> \|\| Register with manual startup only
	\|-		\|-
	\| <code>LabelServer.exe /start</code> \|\| Start the service		\| <code>LabelServer.exe /start</code> \|\| Start the service

Interface Service

Dgarratt — Sun, 05 Apr 2026 16:05:03 GMT

Updated by push_wiki.py

← Older revision		Revision as of 18:05, 5 April 2026
Line 39:		Line 39:

	All service commands must be run from an elevated command prompt (Run as Administrator).		All service commands must be run from an elevated command prompt (Run as Administrator).

			The default Windows service name is '''Service4j''' (the launcher name defined in the installer). You can specify a different name as an optional second parameter. If a custom name is used at install time, that same name must be passed to every subsequent command.

	{\| class="wikitable"		{\| class="wikitable"
Line 44:		Line 46:
	! Command !! Effect		! Command !! Effect
	\|-		\|-
	\| <code>Service4j.exe /install</code> \|\| Register ~~the Windows service~~ with automatic startup on boot		\| <code>Service4j.exe /install</code> \|\| Register as '''Service4j''' with automatic startup on boot
	\|-		\|-
	\| <code>Service4j.exe /install-demand</code> \|\| Register ~~the service~~ with manual startup only		\| <code>Service4j.exe /install "Commander4j Interface"</code> \|\| Register with a custom service name
			\|-
			\| <code>Service4j.exe /install-demand</code> \|\| Register with manual startup only
	\|-		\|-
	\| <code>Service4j.exe /start</code> \|\| Start the service		\| <code>Service4j.exe /start</code> \|\| Start the service
Line 58:		Line 62:
	\| <code>Service4j.exe /uninstall</code> \|\| Remove the service registration		\| <code>Service4j.exe /uninstall</code> \|\| Remove the service registration
	\|}		\|}

			If a custom service name was used at install time, append it to all subsequent commands:

			Service4j.exe /start "Commander4j Interface"
			Service4j.exe /stop "Commander4j Interface"
			Service4j.exe /uninstall "Commander4j Interface"

	Once installed, the service also appears in the Windows Services management console (<code>services.msc</code>).		Once installed, the service also appears in the Windows Services management console (<code>services.msc</code>).

SFTPTransfer

Dgarratt — Sun, 05 Apr 2026 16:05:02 GMT

Updated by push_wiki.py

← Older revision		Revision as of 18:05, 5 April 2026
Line 116:		Line 116:

	All service commands must be run from an elevated command prompt (Run as Administrator).		All service commands must be run from an elevated command prompt (Run as Administrator).

			The default Windows service name is '''sftpTransfer_Service''' (the launcher name defined in the installer). You can specify a different name as an optional second parameter — useful if you need to run multiple instances on the same machine. If a custom name is used at install time, that same name must be passed to every subsequent command.

	{\| class="wikitable"		{\| class="wikitable"
Line 121:		Line 123:
	! Command !! Effect		! Command !! Effect
	\|-		\|-
	\| <code>sftpTransfer_Service.exe /install</code> \|\| Register ~~the Windows service~~ with automatic startup on boot		\| <code>sftpTransfer_Service.exe /install</code> \|\| Register as '''sftpTransfer_Service''' with automatic startup on boot
	\|-		\|-
	\| <code>sftpTransfer_Service.exe /install-demand</code> \|\| Register ~~the service~~ with manual startup only		\| <code>sftpTransfer_Service.exe /install "My SFTP Service"</code> \|\| Register with a custom service name
			\|-
			\| <code>sftpTransfer_Service.exe /install-demand</code> \|\| Register with manual startup only
	\|-		\|-
	\| <code>sftpTransfer_Service.exe /start</code> \|\| Start the service		\| <code>sftpTransfer_Service.exe /start</code> \|\| Start the service
Line 135:		Line 139:
	\| <code>sftpTransfer_Service.exe /uninstall</code> \|\| Remove the service registration		\| <code>sftpTransfer_Service.exe /uninstall</code> \|\| Remove the service registration
	\|}		\|}

			If a custom service name was used at install time, append it to all subsequent commands:

			sftpTransfer_Service.exe /start "My SFTP Service"
			sftpTransfer_Service.exe /stop "My SFTP Service"
			sftpTransfer_Service.exe /uninstall "My SFTP Service"

	Once installed, the service also appears in the Windows Services management console (<code>services.msc</code>).		Once installed, the service also appears in the Windows Services management console (<code>services.msc</code>).

Installation Middleware4j

Dgarratt — Sun, 05 Apr 2026 16:05:01 GMT

Updated by push_wiki.py

← Older revision		Revision as of 18:05, 5 April 2026
Line 55:		Line 55:

	All service commands must be run from an elevated command prompt (Run as Administrator).		All service commands must be run from an elevated command prompt (Run as Administrator).

			The default Windows service name is '''Middleware Service''' (the launcher name defined in the installer). You can specify a different name as an optional second parameter — useful if you need to run multiple instances on the same machine. If a custom name is used at install time, that same name must be passed to every subsequent command.

	{\| class="wikitable"		{\| class="wikitable"
Line 60:		Line 62:
	! Command !! Effect		! Command !! Effect
	\|-		\|-
	\| <code>Middleware_Service.exe /install</code> \|\| Register ~~the Windows service~~ with automatic startup on boot		\| <code>Middleware_Service.exe /install</code> \|\| Register as '''Middleware Service''' with automatic startup on boot
	\|-		\|-
	\| <code>Middleware_Service.exe /install-demand</code> \|\| Register ~~the service~~ with manual startup only		\| <code>Middleware_Service.exe /install "My Middleware"</code> \|\| Register with a custom service name
			\|-
			\| <code>Middleware_Service.exe /install-demand</code> \|\| Register with manual startup only
	\|-		\|-
	\| <code>Middleware_Service.exe /start</code> \|\| Start the service		\| <code>Middleware_Service.exe /start</code> \|\| Start the service
Line 74:		Line 78:
	\| <code>Middleware_Service.exe /uninstall</code> \|\| Remove the service registration		\| <code>Middleware_Service.exe /uninstall</code> \|\| Remove the service registration
	\|}		\|}

			If a custom service name was used at install time, append it to all subsequent commands:

			Middleware_Service.exe /start "My Middleware"
			Middleware_Service.exe /stop "My Middleware"
			Middleware_Service.exe /uninstall "My Middleware"

	Once installed, the service also appears in the Windows Services management console (<code>services.msc</code>).		Once installed, the service also appears in the Windows Services management console (<code>services.msc</code>).

Installation LabelServer4j

Dgarratt — Sun, 05 Apr 2026 16:05:00 GMT

Updated by push_wiki.py

← Older revision		Revision as of 18:05, 5 April 2026
Line 68:		Line 68:

	All service commands must be run from an elevated command prompt (Run as Administrator).		All service commands must be run from an elevated command prompt (Run as Administrator).

			The default Windows service name is '''LabelService''' (the launcher name defined in the installer). You can specify a different name as an optional second parameter — useful if you need to run multiple instances on the same machine. If a custom name is used at install time, that same name must be passed to every subsequent command.

	{\| class="wikitable"		{\| class="wikitable"
Line 73:		Line 75:
	! Command !! Effect		! Command !! Effect
	\|-		\|-
	\| <code>LabelServer.exe /install</code> \|\| Register ~~the Windows service~~ with automatic startup on boot		\| <code>LabelServer.exe /install</code> \|\| Register as '''LabelService''' with automatic startup on boot
	\|-		\|-
	\| <code>LabelServer.exe /install-demand</code> \|\| Register ~~the service~~ with manual startup only		\| <code>LabelServer.exe /install "My Label Service"</code> \|\| Register with a custom service name
			\|-
			\| <code>LabelServer.exe /install-demand</code> \|\| Register with manual startup only
	\|-		\|-
	\| <code>LabelServer.exe /start</code> \|\| Start the service		\| <code>LabelServer.exe /start</code> \|\| Start the service
Line 87:		Line 91:
	\| <code>LabelServer.exe /uninstall</code> \|\| Remove the service registration		\| <code>LabelServer.exe /uninstall</code> \|\| Remove the service registration
	\|}		\|}

			If a custom service name was used at install time, append it to all subsequent commands:

			LabelServer.exe /start "My Label Service"
			LabelServer.exe /stop "My Label Service"
			LabelServer.exe /uninstall "My Label Service"

	Once installed, the service also appears in the Windows Services management console (<code>services.msc</code>) and can be started and stopped from there.		Once installed, the service also appears in the Windows Services management console (<code>services.msc</code>) and can be started and stopped from there.

Interface Service

Dgarratt — Sun, 05 Apr 2026 16:01:24 GMT

Updated by push_wiki.py

New page

The Commander4j Interface Service is a background process that handles all automated integration between Commander4j and external systems. It monitors for incoming XML messages from ERPs and other systems, generates outbound XML messages, triggers scheduled reports, and drives automatic labelling. It is designed to run continuously on a server as a Windows service.

The service is a separate optional component — the main Commander4j desktop application does not need to be running for the Interface Service to operate.

== What the Service Does ==

When started, the Interface Service logs into the Commander4j database using the built-in <code>interface</code> account and starts five background threads:

{| class="wikitable"
|-
! Thread !! Purpose
|-
| '''Inbound Message Thread''' || Monitors the configured inbound directory for XML message files from external systems. Processes each file against the appropriate message handler and writes results to <code>SYS_INTERFACE_LOG</code>.
|-
| '''Outbound Message Thread''' || Picks up XML messages queued in the database for transmission to external systems and writes them to the configured outbound directories.
|-
| '''Recovery Thread''' || Monitors the recovery path for messages that failed processing and re-attempts them on a schedule.
|-
| '''Reporting Thread''' || Fires scheduled reports at their configured times and distributes the output.
|-
| '''Auto Labeller Thread''' || Drives automatic pallet labelling triggers that are not handled by [[AutoLab4j]] or [[LabelServer4j]].
|}

At a configured daily housekeeping time the service gracefully stops all threads, performs maintenance tasks, and restarts. Email notifications are sent on startup, shutdown, and housekeeping if configured.

== Prerequisites ==

=== Host Configuration ===

The Interface Service identifies which database to connect to by looking for a host entry in <code>hosts.xml</code> with a <code>uniqueId</code> of <code>service</code>. This host entry must be created using [[Setup4j]] before the service will start. Without it, the service logs an error and exits immediately.

=== Interface User Account ===

The service logs into Commander4j using the application account <code>interface</code> with password <code>interface</code>. This account must exist and be enabled in the Commander4j user list. It is created automatically when the schema is initialised, but verify it has not been disabled or had its password changed.

== Installing as a Windows Service ==

The native install package includes <code>Service4j.exe</code>, a service-mode launcher built with install4j. This executable manages the Windows service directly — no additional wrapper is required.

All service commands must be run from an elevated command prompt (Run as Administrator).

{| class="wikitable"
|-
! Command !! Effect
|-
| <code>Service4j.exe /install</code> || Register the Windows service with automatic startup on boot
|-
| <code>Service4j.exe /install-demand</code> || Register the service with manual startup only
|-
| <code>Service4j.exe /start</code> || Start the service
|-
| <code>Service4j.exe /stop</code> || Stop the service (waits for graceful shutdown)
|-
| <code>Service4j.exe /restart</code> || Restart the service
|-
| <code>Service4j.exe /status</code> || Query status (exit code: 0 = running, 3 = stopped)
|-
| <code>Service4j.exe /uninstall</code> || Remove the service registration
|}

Once installed, the service also appears in the Windows Services management console (<code>services.msc</code>).

=== Testing Before Installing as a Service ===

Before committing to service installation, run the Interface Service in a visible console window using:

Interface4j.exe

This runs the same application code and all log output is written to the console window. Use this mode to confirm that the correct host is found, the <code>interface</code> account logs in, and all threads start successfully.

== Email Notifications ==

If configured, the service sends email alerts at key lifecycle events:

{| class="wikitable"
|-
! Event !! Trigger
|-
| Startup || Service has connected to the database and all threads are running
|-
| Shutdown || Service has stopped all threads and disconnected
|-
| Housekeeping || Daily maintenance cycle has run
|-
| Statistics || Daily statistics summary (if enabled)
|}

Email notification is controlled by the system key <code>INTERFACE EMAIL NOTIFY</code> (true/false) and the recipient list in <code>INTERFACE ADMIN EMAIL</code>. Both are configured in the Commander4j system keys administration screen.

== Monitoring ==

All activity is written to the Log4j log file in the <code>logs/</code> directory. The [[Interface Log]] screen in the Commander4j desktop application provides a searchable view of every message processed — inbound and outbound — including status, error details, and message content.

Failed messages can be resubmitted for reprocessing from the Interface Log screen without re-sending the original file.

See also: [[Interface Log]], [[Interface Message Formats]], [[Setup4j]], [[AutoLab4j]], [[LabelServer4j]]

[[Category:Commander4j]]

Clone4j

Dgarratt — Sun, 05 Apr 2026 16:01:21 GMT

Updated by push_wiki.py

New page

'''Clone4j''' is a database copy utility included with Commander4j. It copies the entire contents of one Commander4j database into another, and supports copying between different database types — for example from SQL Server to MySQL or from MySQL to Oracle.

Clone4j is launched from the <code>Clone4j.exe</code> executable in the Commander4j installation directory. It requires administrator privileges (the launcher requests elevation on Windows).

== When to Use Clone4j ==

Typical uses include:

* Copying a live production database to a test or development environment
* Migrating data when moving a site from one database platform to another
* Creating a full backup copy of the database in a different database instance

== Prerequisites ==

Before running Clone4j:

* Both the source and destination databases must be defined as hosts in <code>hosts.xml</code> (use [[Setup4j]] to configure host connections)
* Both databases must be on the '''same schema version''' — Clone4j will refuse to proceed if the schema versions differ
* Both databases must have the same number of tables — they must be on identical schema revisions with no partial upgrades applied
* The destination database will have '''all its data erased''' and replaced with the source data

== Using Clone4j ==

# Launch <code>Clone4j.exe</code>
# The window shows two lists populated from <code>hosts.xml</code> — select the '''source''' database on the left and the '''destination''' database on the right
# Click '''Clone Database'''
# A confirmation prompt warns that all data in the destination will be erased — confirm to proceed
# Clone4j copies every table in sequence, updating a progress bar as it works
# On completion, the status bar reports the outcome

The Clone button is only enabled when both a source and a destination have been selected and they are not the same host.

== Limitations ==

* Clone4j copies data row by row — it is not a structural migration tool. Both databases must already have matching schemas (same schema version, same table count).
* It is not designed for continuous replication. It is a one-time full copy.
* Large databases may take several minutes to clone depending on row count and network speed.

See also: [[Setup4j]], [[Installation]], [[Upgrading]]

[[Category:Commander4j]]

LabelServer4j

Dgarratt — Sun, 05 Apr 2026 15:56:01 GMT

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

Installation AutoLab4j

Dgarratt — Sun, 05 Apr 2026 15:56:00 GMT

Updated by push_wiki.py

← Older revision		Revision as of 17:56, 5 April 2026
Line 78:		Line 78:
	== Starting AutoLab4j ==		== Starting AutoLab4j ==

	~~If you installed using the native package, start AutoLab4j using the shortcut or service entry created by the installer.~~		=== Windows — Native Package ===

	If running ~~from~~ the ~~distribution archive:~~		The native install package creates <code>AutoLab4j_Startup.exe</code> in the installation directory. Double-click this launcher, or create a shortcut to it, to start AutoLab4j. It enforces single-instance operation — a second launch will signal the running instance to shut down before the new one starts.

	=== Windows ===		AutoLab4j is a GUI application and does not include a built-in Windows service launcher. To run it automatically at boot without an interactive session, use a service wrapper such as WinSW configured to launch <code>AutoLab4j_Startup.exe</code>.

			=== Windows — Distribution Archive ===

			If running from the extracted archive rather than the native package:

	java -jar AutoLab.jar		java -jar AutoLab.jar

	~~AutoLab4j can be installed as a Windows service using a wrapper such as WinSW so that it starts automatically on boot.~~

	=== Linux / macOS ===		=== Linux / macOS ===
Line 92:		Line 94:
	java -jar AutoLab.jar		java -jar AutoLab.jar

	Use systemd, launchd, or nohup for production deployment.		Use systemd, launchd, or nohup for production deployment as a background process.

	When running, AutoLab4j appears in the system tray with one icon per production line. The System Log window shows startup progress.		When running, AutoLab4j appears in the system tray with one icon per production line. The System Log window shows startup progress.

SFTPTransfer

Dgarratt — Sun, 05 Apr 2026 15:55:54 GMT

Updated by push_wiki.py

@@ Line 20: / Line 20: @@
 |}
-On Windows the service mode can be managed using a wrapper such as WinSW. On Linux/macOS, use systemd, launchd, or nohup.
+On Windows, the native install package includes <code>sftpTransfer_Service.exe</code>, which manages the Windows service directly — see [[#Installing as a Windows Service|Installing as a Windows Service]] below. On Linux/macOS, use systemd, launchd, or nohup.
 == Configuration Files ==
@@ Line 110: / Line 110: @@
 SMTP settings for error notification emails. When a transfer failure occurs and email notification is enabled, SFTPTransfer sends an alert to the configured address. Fields include SMTP host, port, sender address, recipient address, and AES-encrypted SMTP password.
 == Authentication ==

LabelServer4j Example User Interface

Dgarratt — Sun, 05 Apr 2026 15:55:53 GMT

Updated by push_wiki.py

← Older revision		Revision as of 17:55, 5 April 2026
Line 3:		Line 3:
	== Starting LabelServer4j ==		== Starting LabelServer4j ==

	=== Windows ===		=== Windows — Running as a Service ===

	LabelServer4j can be installed as a Windows service so that it starts automatically when the server boots and restarts automatically if it crashes. Once installed as a service it is managed through the standard Windows Services management console (<code>~~services~~.~~msc~~</code>~~) or~~ the command ~~line:~~		The native install package includes <code>LabelServer.exe</code>, a service-mode launcher that manages the Windows service directly. All commands must be run from an elevated command prompt (Run as Administrator).

	~~net~~ start ~~LabelServer4j~~		{\| class="wikitable"
	~~net~~ stop ~~LabelServer4j~~		\|-
			! Command !! Effect
			\|-
			\| <code>LabelServer.exe /install</code> \|\| Register the service with automatic startup on boot
			\|-
			\| <code>LabelServer.exe /install-demand</code> \|\| Register the service with manual startup only
			\|-
			\| <code>LabelServer.exe /start</code> \|\| Start the service
			\|-
			\| <code>LabelServer.exe /stop</code> \|\| Stop the service (waits for graceful shutdown)
			\|-
			\| <code>LabelServer.exe /restart</code> \|\| Restart the service
			\|-
			\| <code>LabelServer.exe /status</code> \|\| Query status (exit code: 0 = running, 3 = stopped)
			\|-
			\| <code>LabelServer.exe /uninstall</code> \|\| Remove the service registration
			\|}

	~~It can~~ also ~~be started directly from a command prompt for testing:~~		Once installed, the service also appears in the Windows Services management console (<code>services.msc</code>).

	~~start_labeller~~.~~cmd~~		=== Windows — Testing in a Console Window ===

			Before installing as a service, use the debug launcher to run LabelServer4j with all output visible in the console:

			LabelServerDebug.exe

			This runs the same application code and is the most convenient way to verify that labellers connect and that the configuration is correct before committing to service deployment.

	=== Linux / macOS ===		=== Linux / macOS ===

Installation Middleware4j

Dgarratt — Sun, 05 Apr 2026 15:55:52 GMT

Updated by push_wiki.py

Show changes

Installation LabelServer4j

Dgarratt — Sun, 05 Apr 2026 15:55:35 GMT

Updated by push_wiki.py

New page

This page covers deploying LabelServer4j on a server or PC connected to the production network.

== Requirements ==

* Network access to each label printer (TCP/IP — Zebra port 9100, Logopak port 9100 or as configured)
* Network access to the Commander4j server (to receive CSV request files)
* Windows, Linux, or macOS
* Java 21 — required only when running from the distribution archive; the native install package bundles its own Java runtime

== Installation ==

Native install packages for Windows, macOS, and Linux are available from the [[Downloads]] page and are the preferred installation method. The installer creates the application directory, copies all configuration templates, and handles the Java runtime dependency automatically.

Alternatively, a distribution archive can be extracted to a suitable directory, for example:

C:\Commander4j\LabelServer4j\ (Windows)
/opt/commander4j/labelserver4j/ (Linux)

The extracted directory contains:

LabelServer.jar
LabelServer.exe (Windows — service launcher)
LabelServerDebug.exe (Windows — console launcher for testing)
start_labeller.cmd (Windows — fallback start script)
start_labeller.sh (Linux/macOS — start script)
lib/
xml/config/
labeller_files/
labeller_requests/
labeller_cmd/
labeller_backups/
logs/

== Configuration Before First Run ==

Before starting LabelServer4j, complete the following configuration steps.

=== 1. Site and Labeller Definitions ===

Edit <code>xml/config/config.xml</code> to set the active site identifier. Then create or edit the <code>labellers.xml</code> file for that site in <code>xml/config/</code>. Each labeller entry defines:

* The labeller name (must match the name used in Commander4j)
* The printer IP address and TCP port
* The path to the command script
* The input directory where Commander4j writes CSV files

See [[LabelServer4j Configuration]] for the full XML structure.

=== 2. Command Scripts ===

Place the command script files (plain text <code>.txt</code> files) for each labeller in the <code>labeller_cmd/</code> directory. The script filename is referenced in <code>labellers.xml</code>.

=== 3. Label Files (Logopak only) ===

If using Logopak printers with stored label templates, place the binary label files in the appropriate subdirectory of <code>labeller_files/</code>. LabelServer4j can upload these to the printer using the <code>SEND_FILE_INTELHEX</code> command.

=== 4. Database Connection (Optional) ===

If the command scripts use <code>DB_QUERY</code> to enrich label data from the Commander4j database, configure the database connection in <code>xml/config/config.xml</code> with the JDBC URL, username, and AES-encrypted password.

=== 5. Email Notifications (Optional) ===

To receive alerts on print failures or service events, configure <code>xml/config/email.xml</code> with SMTP server details and recipient addresses.

== Installing as a Windows Service ==

The native install package includes <code>LabelServer.exe</code>, a service-mode launcher built with install4j. This executable manages the Windows service directly — no additional wrapper (such as WinSW) is required.

All service commands must be run from an elevated command prompt (Run as Administrator).

{| class="wikitable"
|-
! Command !! Effect
|-
| <code>LabelServer.exe /install</code> || Register the Windows service with automatic startup on boot
|-
| <code>LabelServer.exe /install-demand</code> || Register the service with manual startup only
|-
| <code>LabelServer.exe /start</code> || Start the service
|-
| <code>LabelServer.exe /stop</code> || Stop the service (waits for graceful shutdown)
|-
| <code>LabelServer.exe /restart</code> || Restart the service
|-
| <code>LabelServer.exe /status</code> || Query status (exit code: 0 = running, 3 = stopped)
|-
| <code>LabelServer.exe /uninstall</code> || Remove the service registration
|}

Once installed, the service also appears in the Windows Services management console (<code>services.msc</code>) and can be started and stopped from there.

=== Testing Before Installing as a Service ===

Before committing to service installation, run LabelServer4j in a visible console window using the debug launcher:

LabelServerDebug.exe

This runs the same application code with all log output written to the console window. Use this mode to confirm that labellers connect to their printers and that the configuration is correct before installing as a service.

== Starting on Linux / macOS ==

Use the provided shell script:

./start_labeller.sh

Or directly:

java -cp ./LabelServer.jar:./lib/devonly/i4jruntime.jar com.commander4j.labeller.Service

The process runs in the foreground. For production deployment, use a process manager (systemd, launchd, or nohup) to run it as a background service.

== Verifying the Installation ==

After starting LabelServer4j:

# Check <code>logs/c4jLabelServer.log</code> — there should be startup and thread initialisation messages.
# Verify that each labeller thread reports a successful TCP connection to its printer.
# Place a test CSV file in a labeller's input directory to trigger an end-to-end print cycle.
# Confirm the CSV file is consumed (deleted on success, or moved to the error directory on failure).

== Log Files ==

All activity is written to <code>logs/c4jLabelServer.log</code>. Log files rotate at 10 MB and are retained for 14 days.

See also: [[Overview LabelServer4j]], [[LabelServer4j Operation]], [[LabelServer4j Configuration]], [[LabelServer4j Example User Interface]]

[[Category:LabelServer4j]]

AutoLab4j Folder Structure

Dgarratt — Wed, 01 Apr 2026 15:28:46 GMT

Updated by push_wiki.py

← Older revision		Revision as of 17:28, 1 April 2026
Line 29:		Line 29:
	=== AutoLab.jar ===		=== AutoLab.jar ===

	The main application JAR. ~~Start~~ AutoLab4j ~~by running~~ <code>java -jar AutoLab.jar</code>.		The main application JAR. When running from the distribution archive, start AutoLab4j with <code>java -jar AutoLab.jar</code>. If installed using the native package, use the shortcut or service entry created by the installer.

	=== lib/ ===		=== lib/ ===

Installation AutoLab4j

Dgarratt — Wed, 01 Apr 2026 15:28:45 GMT

Updated by push_wiki.py

← Older revision		Revision as of 17:28, 1 April 2026
Line 3:		Line 3:
	== Requirements ==		== Requirements ==

	* Java 21 (JRE or JDK)
	* Network access to the Modbus I/O device on each production line (TCP port 502 by default)		* Network access to the Modbus I/O device on each production line (TCP port 502 by default)
	* Network access to each Zebra printer (TCP port 9100)		* Network access to each Zebra printer (TCP port 9100)
	* Network access to the Commander4j server (to receive CSV dataset files)		* Network access to the Commander4j server (to receive CSV dataset files)
	* Windows, Linux, or macOS		* Windows, Linux, or macOS
			* Java 21 (JRE or JDK) — required only when running from the distribution archive; the native install package bundles its own Java runtime

	== Installation ==		== Installation ==

	~~Download~~ the ~~AutoLab4j~~ distribution from the [[Downloads]] page and ~~extract it~~ to a suitable directory, for example:		Native install packages for Windows, macOS, and Linux are available from the [[Downloads]] page and are the preferred installation method. The installer creates the application directory, registers it with the operating system, and handles the Java runtime dependency automatically.

			Alternatively, a distribution archive can be downloaded from the [[Downloads]] page and extracted to a suitable directory, for example:

	C:\Commander4j\AutoLab4j\ (Windows)		C:\Commander4j\AutoLab4j\ (Windows)
Line 75:		Line 77:

	== Starting AutoLab4j ==		== Starting AutoLab4j ==

			If you installed using the native package, start AutoLab4j using the shortcut or service entry created by the installer.

			If running from the distribution archive:

	=== Windows ===		=== Windows ===

XML Viewer

Dgarratt — Wed, 01 Apr 2026 15:28:44 GMT

Updated by push_wiki.py

← Older revision		Revision as of 17:28, 1 April 2026
Line 7:		Line 7:
	== Running XML Viewer ==		== Running XML Viewer ==

	XML Viewer is a Java 21 desktop (Swing) application:		Native install packages for Windows, macOS, and Linux are available from the [[Downloads]] page and are the preferred installation method.

			Alternatively, XML Viewer can be run directly from the distribution archive. It is a Java 21 desktop (Swing) application:

	java -jar xmlviewer.jar [optional path to XML file]		java -jar xmlviewer.jar [optional path to XML file]

TreeDoc

Dgarratt — Wed, 01 Apr 2026 15:28:43 GMT

Updated by push_wiki.py

← Older revision		Revision as of 17:28, 1 April 2026
Line 7:		Line 7:
	== Running TreeDoc ==		== Running TreeDoc ==

	TreeDoc is a Java 21 desktop (Swing) application:		Native install packages for Windows, macOS, and Linux are available from the [[Downloads]] page and are the preferred installation method.

			Alternatively, TreeDoc can be run directly from the distribution archive. It is a Java 21 desktop (Swing) application:

	java -jar Tree.jar		java -jar Tree.jar

Menu4j

Dgarratt — Wed, 01 Apr 2026 15:28:41 GMT

Updated by push_wiki.py

← Older revision		Revision as of 17:28, 1 April 2026
Line 7:		Line 7:
	== Running Menu4j ==		== Running Menu4j ==

	Menu4j is a Java 21 desktop (Swing) application:		Native install packages for Windows, macOS, and Linux are available from the [[Downloads]] page and are the preferred installation method.

			Alternatively, Menu4j can be run directly from the distribution archive. It is a Java 21 desktop (Swing) application:

	java -jar JMenu.jar		java -jar JMenu.jar

LaunchPad

Dgarratt — Wed, 01 Apr 2026 15:28:41 GMT

Updated by push_wiki.py

← Older revision		Revision as of 17:28, 1 April 2026
Line 7:		Line 7:
	== Running LaunchPad ==		== Running LaunchPad ==

	LaunchPad is a Java 21 desktop (Swing) application for macOS:		A native macOS install package is available from the [[Downloads]] page and is the preferred installation method.

			Alternatively, LaunchPad can be run directly from the distribution archive. It is a Java 21 desktop (Swing) application for macOS:

	java -jar JLaunchPad.jar		java -jar JLaunchPad.jar

ZPLRenderer

Dgarratt — Wed, 01 Apr 2026 15:28:39 GMT

Updated by push_wiki.py

← Older revision		Revision as of 17:28, 1 April 2026
Line 14:		Line 14:
	== Running ZPL Renderer ==		== Running ZPL Renderer ==

	ZPL Renderer is a Java 21 desktop (Swing) application:		Native install packages for Windows, macOS, and Linux are available from the [[Downloads]] page and are the preferred installation method.

			Alternatively, ZPL Renderer can be run directly from the distribution archive. It is a Java 21 desktop (Swing) application:

	java -jar zplrenderer.jar		java -jar zplrenderer.jar

SocketTest

Dgarratt — Wed, 01 Apr 2026 15:28:29 GMT

Updated by push_wiki.py

← Older revision		Revision as of 17:28, 1 April 2026
Line 12:		Line 12:
	== Running SocketTest ==		== Running SocketTest ==

	SocketTest is a Java 21 desktop (Swing) application:		Native install packages for Windows, macOS, and Linux are available from the [[Downloads]] page and are the preferred installation method.

			Alternatively, SocketTest can be run directly from the distribution archive. It is a Java 21 desktop (Swing) application:

	java -jar SocketTest.jar		java -jar SocketTest.jar

Installation AutoLab4j

Dgarratt — Wed, 01 Apr 2026 11:35:25 GMT

Updated by push_wiki.py

New page

This page covers deploying AutoLab4j on a server or PC connected to the production network.

== Requirements ==

* Java 21 (JRE or JDK)
* Network access to the Modbus I/O device on each production line (TCP port 502 by default)
* Network access to each Zebra printer (TCP port 9100)
* Network access to the Commander4j server (to receive CSV dataset files)
* Windows, Linux, or macOS

== Installation ==

Download the AutoLab4j distribution from the [[Downloads]] page and extract it to a suitable directory, for example:

C:\Commander4j\AutoLab4j\ (Windows)
/opt/commander4j/autolab4j/ (Linux)

The extracted directory contains:

AutoLab.jar
lib/
xml/
labels/
logs/
interface/
running/

== Configuration Before First Run ==

Before starting AutoLab4j, complete the following configuration steps.

=== 1. Production Lines ===

Edit <code>xml/config/config.xml</code> and define each production line. For each line you need:

* The Modbus device IP address and port
* The coil address that signals a pallet complete event
* The coil address for semi-pallet detection
* The printer name (must match the name used in Commander4j)

See [[AutoLab4j Configuration]] for the full XML structure.

=== 2. SSCC Sequence Files ===

Create one SSCC sequence file per printer in <code>xml/sscc/</code>. The filename must match the printer name configured in <code>config.xml</code>. For example, for a printer named <code>PRINTER 1</code>:

xml/sscc/PRINTER 1.xml

The file must contain the SSCC prefix, starting sequence number, warning limit, and upper limit. Your GS1 member organisation will provide the prefix. Example:

<?xml version="1.0" encoding="UTF-8"?>
<sscc>
<prefix>384133182</prefix>
<sequence>00000001</sequence>
<checkDigit>0</checkDigit>
<upperlimit>00009999</upperlimit>
<warninglimit>00009000</warninglimit>
</sscc>

=== 3. Label Templates ===

Copy the ZPL label template files into the <code>labels/</code> directory. The filename for each template is specified in the CSV dataset file in the <code>REPORT_FILENAME</code> field. See [[Zebra ZPL Label]] for information on ZPL label authoring.

=== 4. Dataset Directory ===

Ensure the directory configured as <code>dataSet path</code> in <code>config.xml</code> is accessible. This is where Commander4j writes the CSV files when an operator assigns a process order to a labeller. The directory can be a local path or a network share.

=== 5. Output Directory ===

Ensure the directory configured as <code>output path</code> in <code>config.xml</code> exists and is writable. AutoLab4j writes Production Declaration XML files here after each pallet is printed.

=== 6. Email Notifications (Optional) ===

If you want email alerts for SSCC warnings and service start/stop events, configure <code>xml/config/email.xml</code> with your SMTP server details and distribution lists.

== Starting AutoLab4j ==

=== Windows ===

java -jar AutoLab.jar

AutoLab4j can be installed as a Windows service using a wrapper such as WinSW so that it starts automatically on boot.

=== Linux / macOS ===

java -jar AutoLab.jar

Use systemd, launchd, or nohup for production deployment.

When running, AutoLab4j appears in the system tray with one icon per production line. The System Log window shows startup progress.

== Exclusive Runtime ==

AutoLab4j uses a TCP port (default: 8000) as an exclusive runtime lock. Only one instance can run at a time. If you start a second instance, it sends a shutdown signal to the running instance and waits for it to stop before starting. The watchdog port can be changed in <code>config.xml</code>.

== Verifying the Installation ==

After starting AutoLab4j:

# Check the system tray — there should be one icon per enabled production line.
# Open the System Log window (right-click the system tray icon).
# Verify that each production line shows a Modbus connection attempt in its log window.
# Place a test CSV file in the dataset directory and trigger the Modbus coil to confirm end-to-end operation.

== Log Files ==

All activity is written to <code>logs/AutoLab.log</code>. Log files rotate at 10 MB and are retained for 14 days. Review this file if any production line fails to connect or if labels are not printing.

See also: [[AutoLab4j Configuration]], [[Overview AutoLab4j]], [[AutoLab4j Operation]]

[[Category:AutoLab4j]]

AutoLab4j Folder Structure

Dgarratt — Wed, 01 Apr 2026 11:35:23 GMT

Updated by push_wiki.py

← Older revision		Revision as of 13:35, 1 April 2026
Line 1:		Line 1:
			This page describes the directory layout of an AutoLab4j installation and the purpose of each folder.

			== Directory Layout ==

			AutoLab4j/
			├── AutoLab.jar
			├── lib/
			├── xml/
			│ ├── config/
			│ │ ├── config.xml
			│ │ ├── email.xml
			│ │ └── log4j2.xml
			│ └── sscc/
			│ └── PRINTER NAME.xml
			├── labels/
			├── interface/
			│ ├── input/
			│ │ └── dataset/
			│ └── output/
			│ └── ProdDec/
			├── remote_dataset/
			├── remote_labels/
			├── labelary/
			├── logs/
			└── running/

			== File and Folder Descriptions ==

			=== AutoLab.jar ===

			The main application JAR. Start AutoLab4j by running <code>java -jar AutoLab.jar</code>.

			=== lib/ ===

			Third-party library JARs required by AutoLab4j (referenced in the JAR manifest classpath). Do not modify this directory.

			=== xml/config/config.xml ===

			The main configuration file. Defines production lines, Modbus connection details, pallet quantities, batch format patterns, and file paths. See [[AutoLab4j Configuration]] for the full structure.

			=== xml/config/email.xml ===

			SMTP and distribution list settings for email notifications. Used for SSCC warning alerts and service start/stop notifications.

			=== xml/config/log4j2.xml ===

			Log4j2 logging configuration. Controls log file location, rotation size, and retention period.

			=== xml/sscc/ ===

			Contains one XML sequence file per printer, named after the printer (for example <code>PRINTER 1.xml</code>). Each file stores the current SSCC prefix, sequence number, check digit, warning limit, and upper limit. AutoLab4j reads and updates these files atomically each time a new SSCC is generated. Back up this directory regularly — it records how far through the SSCC sequence each printer has progressed.

			=== labels/ ===

			ZPL label template files. The filename of the template to use for each order is specified in the <code>REPORT_FILENAME</code> field of the CSV dataset file. Templates contain ZPL commands with field placeholders such as <code><MATERIAL></code> and <code><SSCC></code>.

			=== interface/input/dataset/ ===

			The directory AutoLab4j monitors for incoming CSV dataset files from Commander4j. When Commander4j assigns a process order to a production line, it writes a CSV file here named <code>LINE_NAME_PRINTER_NAME.CSV</code>. This directory is configured as <code>dataSet path</code> in <code>config.xml</code>.

			=== interface/output/ProdDec/ ===

			Production Declaration XML files are written here after each pallet is printed — one file per SSCC. These files record the SSCC, product, batch, shelf life, and other details for downstream integration. This directory is configured as <code>output path</code> in <code>config.xml</code>.

			=== remote_dataset/ ===

			An optional secondary location for CSV dataset files, used when the dataset files are delivered from a remote source and need to be synchronised locally before processing. Configured as <code>dataSet path</code> if remote synchronisation is in use.

			=== remote_labels/ ===

			An optional source directory for label template files. The LabelSync thread copies label files from this directory into <code>labels/</code> at a configurable interval. Used when label templates are maintained centrally and need to be distributed to multiple AutoLab4j instances. Configured as <code>labelSync path</code> in <code>config.xml</code>.

			=== labelary/ ===

			Cache directory for label preview images fetched from the Labelary API. Each ZPL label that is previewed produces a PNG file here. The cache is used to avoid re-fetching the same label image on repeat prints.

			=== logs/ ===

			Application log files. The main log file is <code>AutoLab.log</code>. Log files rotate at 10 MB and are retained for 14 days. Review this directory when diagnosing Modbus connection issues, print failures, or SSCC sequence problems.

			=== running/ ===

			Temporary runtime flag files created by AutoLab4j while it is running. These files are created on startup and removed on clean shutdown. If they remain after an unexpected exit, AutoLab4j will clear them on the next start. Do not modify or delete these files while the service is running.

			See also: [[AutoLab4j Configuration]], [[Installation AutoLab4j]], [[Overview AutoLab4j]]

	[[Category:AutoLab4j]]		[[Category:AutoLab4j]]

	~~Commander4j AutoLab~~
	~~├── images~~
	~~│ ├── Icons~~
	~~│ │ └── AutoLab4j_Icons~~
	~~│ │ └── MyIcon.iconset~~
	~~│ ├── linux~~
	~~│ ├── mac~~
	~~│ └── windows~~
	~~├── interface~~
	~~│ ├── input~~
	~~│ │ └── dataset~~
	~~│ └── output~~
	~~│ └── ProdDec~~
	~~├── labelary~~
	~~├── labels~~
	~~├── layout~~
	~~├── lib~~
	~~│ ├── devonly~~
	~~│ └── modbus~~
	~~├── licences~~
	~~├── logs~~
	~~├── remote_dataset~~
	~~│ └── Backup~~
	~~├── remote_labels~~
	~~├── running~~
	~~└── xml~~
	~~├── config~~
	~~│ ├── Example Config~~
	~~│ └── Example Email~~
	~~└── sscc~~
	~~└── Example SSCC~~

AutoLab4j Dataset CSV

Dgarratt — Wed, 01 Apr 2026 11:35:22 GMT

Updated by push_wiki.py

@@ Line 1: / Line 1: @@
-[[Category:AutoLab4j]]
+When an operator assigns a [[Process Orders|Process Order]] to a production line in Commander4j, a CSV data file is written to the dataset directory monitored by AutoLab4j. This file contains all the product and order information AutoLab4j needs to generate and print labels.
-The example CSV data shown below is automatically exported when someone assigns a Process Order to a Production line in the Pallet Label screen within Commander4j.
-AutoLab4j expects the filename of the CSV to be constructed from the name of the production line and printer separated by an underscore.
+The <code>fieldNamesLookup</code> section in <code>config.xml</code> can map CSV field names to different template placeholder names if the CSV field names do not match the placeholder names in the template. The <code>clone</code> section can copy a field value under an additional name, and the <code>formats</code> section can apply numeric formatting to a field before substitution.
-===CSV Dataset===
+== SSCC Field ==
-[[file:AutoLab4j_CSV_Dataset.png|link=|800px]]
+See also: [[AutoLab4j Operation]], [[AutoLab4j Configuration]], [[Zebra ZPL Label]], [[Label Template Syntax]]
-The above image is the same data as the CSV in a format which is a little easier to understand.
+[[Category:AutoLab4j]]

AutoLab4j Operation

Dgarratt — Wed, 01 Apr 2026 11:35:21 GMT

Updated by push_wiki.py

@@ Line 1: / Line 1: @@
-[[Category:AutoLab4j]]
+This page describes the end-to-end operational workflow of AutoLab4j — from an operator assigning a process order in Commander4j through to a label being printed on the production line.
-The easiest way to work with the AutoLab4j application is to drive it from the Commander4j desktop software. In the screen below you will see the Pallet Labelling screen. The operator selects the order and then uses the "Assign to Labeller" button. They can then choose the production line which the order data is sent to. This data is exported via the Commander4j Interfaces in CSV format. The autolab program retains a copy of this data and will use it to generate a label (and declare a pallet as being produced) in response to a Modbus signal.
-More information on label printing can be found in the Commander4j wiki in the [[Production Declaration]] and [[Pallet Label]] pages. The data exported from the Commander4j is written to the folder defined within the [[Production Lines & Labellers]] screen.
+See also: [[Overview AutoLab4j]], [[AutoLab4j Configuration]], [[AutoLab4j Dataset CSV]], [[Installation AutoLab4j]]
-[[file:AutoLab_Operation1.png|link=|800px]]
+[[Category:AutoLab4j]]

Overview AutoLab4j

Dgarratt — Wed, 01 Apr 2026 11:35:20 GMT

Updated by push_wiki.py

@@ Line 1: / Line 1: @@
-[[Category:AutoLab4j]]
+AutoLab4j is an automated label printing and SSCC generation service for production lines. It monitors Modbus digital signals from production equipment, reads product data from CSV files exported by Commander4j, generates ZPL labels, sends them to networked Zebra printers over TCP/IP, and produces Production Declaration XML documents for each pallet printed.
-=Overview=
-AutoLab4j is a program which has been developed to enable automatic label printing based on a trigger signal from a modbus device.
+AutoLab4j communicates with printers using ZPL (Zebra Programming Language) over raw TCP/IP sockets. Any printer that accepts raw ZPL on a configurable IP address and port is supported.
-It was created to compliment the Commander4j application but in theory could be used with other systems.
+== Multi-Line Support ==
-This application is quite similar in role to the [[LabelServer]] program. The main difference is that AutoLab4j runs as a forground application with tray icon and has a visual component including a label preview, whereas the LabelServer program runs as a service and is normally run on a server.
+AutoLab4j supports multiple production lines simultaneously. Each line runs its own independent set of threads (dataset monitor, Modbus poller, print handler) and has its own system tray icon showing the current status.
-AutoLab4j would typically be installed on a workstation next to the production line/labeller and as such you may have multiple copies running on a site. LabelServer handles mutiple printers from a central location but does not have any visual user interface.
+== Label Preview ==
-[[file:AutoLab4j_Animation.gif|800px]]
+If enabled, AutoLab4j calls the Labelary web API to render each ZPL label as a PNG image and displays it on screen before sending to the printer. This provides a visual confirmation that the correct label is being printed.
-[https://www.flaticon.com/free-icons/conveyor-belt Image from FlatIcon created by vectorsmarket15]
+After each pallet is printed, AutoLab4j writes an XML Production Declaration file to the configured output directory. This document records the SSCC, product, batch, shelf life, and other details for downstream integration.
-[[file:AutoLab4j_3.png|800px]]
+[[Category:AutoLab4j]]

TreeDoc

Dgarratt — Wed, 01 Apr 2026 11:29:49 GMT

Updated by push_wiki.py

← Older revision		Revision as of 13:29, 1 April 2026
Line 1:		Line 1:
	TreeDoc ~~was created to make the process of documenting~~ folder ~~structures easier. You can~~ select ~~the folder structure root that you want to display~~ and it ~~will generate~~ a text ~~representation of the folder structure~~. ~~You~~ can ~~then copy it~~ to the clipboard or ~~save to~~ a file.		TreeDoc is a desktop utility that generates an ASCII directory tree from a folder you select and displays it in a scrollable text window. The output can be copied to the clipboard or saved as a plain text file.

	~~[[File~~:~~TreeDoc1~~.~~png~~\|~~link~~=\|~~border~~\|~~800px~~]]		== Purpose ==

			TreeDoc is useful for producing a human-readable snapshot of a folder structure — for example, documenting a Commander4j installation layout, comparing the contents of two directories, or quickly exploring an unfamiliar project. The output uses box-drawing characters (├──, └──, │) to show the hierarchy clearly in any monospace environment.

			== Running TreeDoc ==

			TreeDoc is a Java 21 desktop (Swing) application:

			java -jar Tree.jar

			The window opens at 900 × 750 pixels.

			== Generating a Tree ==

			# Click '''Browse''' to choose the root folder, or type a path directly into the folder field.
			# Adjust '''Max Depth''' and '''Max Entries''' if needed (see below).
			# Check '''Include Files''' if you want files shown alongside directories.
			# Click '''Refresh''' to generate the tree.

			The output appears in the central text area. The status bar at the bottom shows the total number of entries printed, and indicates if the output was truncated.

			== Options ==

			{\| class="wikitable"
			\|-
			! Option !! Default !! Description
			\|-
			\| Max Depth \|\| 9999 \|\| Maximum folder depth to traverse. Set to a small number (e.g. 3) to get a high-level overview of a deep tree.
			\|-
			\| Max Entries \|\| 10,000 \|\| Maximum number of lines to print. Prevents the output from becoming unmanageable for very large trees.
			\|-
			\| Include Files \|\| Off \|\| When off, only directory names are shown. When on, files are listed inside their parent directory.
			\|}

			== Output Format ==

			The output is plain UTF-8 text using box-drawing characters:

			project/
			├── src/
			│ ├── main/
			│ └── test/
			├── docs/
			└── build.xml

			Directories are always included. Files appear indented under their parent directory when '''Include Files''' is enabled.

			=== What is Excluded ===

			The following are always omitted regardless of settings:

			* Hidden files and folders (system hidden flag)
			* <code>.DS_Store</code> and <code>.localized</code> (macOS metadata)
			* <code>.app</code> bundles (macOS application packages)
			* Symbolic links (skipped to prevent infinite loops)

			== Saving and Copying Output ==

			The right sidebar provides:

			* '''Save''' — save the output as a <code>.txt</code> file (default filename: <code>tree.txt</code>, UTF-8 encoded)
			* '''Clipboard''' — copy the entire output to the system clipboard
			* '''Clear''' — clear the output area

			== Configuration ==

			TreeDoc saves your last-used folder path and the Include Files checkbox state to <code>xml/config/config.xml</code> automatically on exit. These are restored the next time the application opens.

			If the saved folder path no longer exists, TreeDoc prompts you to choose a new folder on startup.

			== Log Files ==

			Activity is written to <code>logs/TreeDoc.log</code>. Log files rotate at 10 MB and are retained for 14 days.

			See also: [[XML Viewer]], [[Menu4j]], [[Downloads]]

			[[Category:Commander4j]]

Menu4j

Dgarratt — Wed, 01 Apr 2026 11:29:48 GMT

Updated by push_wiki.py

Show changes

LaunchPad

Dgarratt — Wed, 01 Apr 2026 11:29:47 GMT

Updated by push_wiki.py

← Older revision		Revision as of 13:29, 1 April 2026
Line 1:		Line 1:
	~~This~~ application is a ~~functionally equivalent program~~ to the ~~MacOS LaunchPad~~.		LaunchPad is a macOS application organiser and launcher. It provides a tabbed grid interface for grouping macOS applications (.app bundles) into named categories and launching them with a double-click. It is a companion tool to the Commander4j suite, used to organise the suite's tools and supporting applications in a single place.

	=~~Getting Started~~=		== Purpose ==

	~~Download~~ the ~~installer for the appropriate Apple hardware, either Intel~~ or ~~Apple Silicon~~.		LaunchPad replaces cluttered Dock folders and aliases with a structured, tabbed grid. Each tab is a named category and each cell in the grid holds one application. Applications are added by browsing or dragging from Finder.

	~~Run the installer and select the folder that you want to install into.~~		== Running LaunchPad ==

	~~[[file~~:~~LaunchPad_Install1.png\|link=[[LaunchPad]]\|100px]]~~		LaunchPad is a Java 21 desktop (Swing) application for macOS:

	~~[[file:LaunchPad_Install2~~.~~png\|link=[[LaunchPad]]\|500px]]~~		java -jar JLaunchPad.jar

	~~When~~ the ~~application is installed you should run it and you will see~~ the ~~default empty launchpad~~.		The window opens at 1300 × 900 pixels. Tabs are listed on the left edge; the grid fills the rest of the window.

	~~Unlike the MacOs the launchpad will not be populated with all your applications at startup.~~		== Adding Applications ==

	~~What I recommend it that you use the + button to create your Categories first. You may want to create a category called "Imported" or "Temp" as well.~~		=== Single Application ===

			Click the '''Add App''' toolbar button. A file chooser opens, defaulting to <code>/Applications</code> and your home directory. Select any <code>.app</code> bundle. If you select <code>/Applications</code>, LaunchPad also scans <code>/System/Applications</code> and <code>/System/Applications/Utilities</code> automatically.

	~~[[file:LaunchPad_Install3.png\|link~~=~~[[LaunchPad]]\|500px]]~~		=== Importing a Folder ===

	~~When these categories have been created (~~and ~~you can add/edit/remove them later) You have 3 ways to add the~~ applications ~~to your launchpad~~.		Click '''Import Folder''' to scan a directory recursively for application bundles. LaunchPad filters out uninstall helpers, login item helpers, and background-only bundles, adding only user-facing applications.

	~~Option 1)~~		=== Drag and Drop ===

	~~With Launchpad open, use the Macos~~ Finder ~~to drag and drop~~ the ~~application want to the appropriate catergory/~~tab ~~on the left of the LaunchPad~~. ~~You~~ only ~~need to drop it on the "title" or name of the category and it will be added to it automatically~~.		Drag a <code>.app</code> bundle from Finder directly onto the grid or onto a tab. An application can only appear once across all tabs — dragging a duplicate has no effect.

	~~[[file:LaunchPad_Install4.png\|link~~=~~[[LaunchPad]]\|500px]]~~		== Grid Layout ==

	~~[[file:LaunchPad_Install5~~.~~png\|link=[[LaunchPad]]\|500px]]~~		Each tab contains a 7-column grid of 150 × 150 pixel cells. Each cell displays the application icon (120 × 120 pixels) and the application's display name. Click '''Pack Icons''' to remove empty cells from the current tab, compacting the grid.

	~~Option 2)~~		Applications can be reordered within the grid by dragging from one cell to another. The same drag operation works between tabs.

	Use the button on the toolbar to the left to import applications from a folder. Select your "Applications" folder and let the LaunchPad application create icons for all the programs it finds. They will be imported into whatever the Category you have selected. You may therefore find it useful to select the "Import" or "Temp" category before you do this. You can then drag and drop all the imported programs from this tab into the required category.		== Tab Management ==

	~~[[file~~:~~LaunchPad_Install6.png\|link=[[LaunchPad]]\|500px]]~~		The toolbar provides buttons for:

	~~[[file:LaunchPad_Install7.png\|link=[[LaunchPad]]\|500px]]~~		* '''Add Tab''' — create a new named category
			* '''Edit Tab''' — rename the selected tab
			* '''Delete Tab''' — remove the selected tab (with confirmation)
			* '''Move Up / Move Down''' — reorder tabs

	~~[[file:LaunchPad_Install8.png\|link~~=~~[[LaunchPad]]\|500px]]~~		== Launching Applications ==

	~~Option 3)~~		Double-click any application icon to launch it. LaunchPad uses the macOS <code>open</code> command to launch the bundle, so the application opens exactly as if you had double-clicked it in Finder.

	~~Use the option to import a single app using the same technique as above.~~		== Cell Context Menu ==

	Things to be aware of. If you have some applications installed which are inherently designed for IOS they may not get the appropriate icon create. You may have a default folder icon or blank. This is due to how the appl bundle is constructed and the fact that the LaunchPad application is Java based. As a workaround, you can right click on any ~~of these applications and manually select an Icon that you have created~~ or ~~downloaded.~~		Right-click any cell or application to access:

	[[file~~:LaunchPad_Install9~~.png~~\|link=~~[[~~LaunchPad~~]]~~\|500px~~]]		* '''Assign Custom Icon...''' — replace the icon with any PNG, JPG, GIF, or ICNS image
			* '''Remove App''' — clear the cell
			* '''Reveal in Finder''' — open the application's location in Finder

			== Icon Resolution ==

			When an application is added, LaunchPad attempts to extract its icon automatically. It tries the following in order:

			# The <code>.icns</code> file named in the app's <code>Info.plist</code>
			# PNG icons listed in <code>Info.plist</code> under <code>CFBundleIcons</code>
			# The app's <code>Assets.car</code> (rendered via QuickLook)
			# A generic system icon as a last resort

			Extracted icons are scaled to 120 × 120 pixels and cached to <code>images/appIcons/</code> on disk. On subsequent launches the cached PNG is used unless the app itself has been updated.

			== Configuration ==

			LaunchPad saves its state automatically on exit and restores it on the next launch.

			=== launchpad.xml ===

			Located at <code>xml/config/launchpad.xml</code>. This file records all tabs, their names, and the path of each application in the grid. It is written automatically — you do not need to edit it manually.

			=== images/appIcons/ ===

			The icon cache directory. Each application has a <code><BundleName>.png</code> file here. If you use '''Assign Custom Icon...''', the cache file for that application is overwritten with your chosen image.

			See also: [[Menu4j]], [[ZPLRenderer]], [[Downloads]]

			[[Category:Commander4j]]

SocketTest

Dgarratt — Wed, 01 Apr 2026 11:29:46 GMT

Updated by push_wiki.py

@@ Line 1: / Line 1: @@
-SocketTest is a simple program which can act as a client or server. You can use it to connect to a device including barcode printers to send direct commands. When in server mode you can also receive data from another program and see what is being sent.
+SocketTest is a TCP/IP network testing utility with a graphical interface. It acts as both a TCP client and a TCP server, allowing you to send and receive arbitrary data over a socket connection, debug protocol implementations, and simulate network endpoints. It is a companion tool to LabelServer4j, AutoLab4j, and ZPL Renderer, which all communicate with devices over raw TCP/IP sockets.
-== Client Mode ==
+== Purpose ==
-[[File:SocketTest_Client.png|border|800px]]
+SocketTest is useful when:
-Connect to a remote device in client mode.
+* Testing whether a printer or other device is accepting connections on a given IP address and port
-== Server Mode ==
+== Running SocketTest ==
-[[File:SocketTest_Server.png|border|800px]]
+SocketTest is a Java 21 desktop (Swing) application:
-Receive data from another device and see what is being sent.
+ java -jar SocketTest.jar
 == Proxy Mode ==
-[[File:SocketServer_Proxy_Mode.png|border|800px]]
+The '''Proxy''' button on the server tab enables transparent data relay. When proxy mode is active, data received on the server side is automatically forwarded to whatever the client tab is connected to, and vice versa. This allows SocketTest to sit between a client and a real device and relay all traffic in both directions, which is useful for capturing a complete protocol conversation.
-Use Client and Server mode. Data received by the server is forwarded to the device which the client is connected to.
+[[Category:Commander4j]]

XML Viewer

Dgarratt — Wed, 01 Apr 2026 11:29:26 GMT

Updated by push_wiki.py

New page

XML Viewer is a desktop application for exploring XML documents as an interactive, expandable tree. It supports configurable display modes, multi-language element name translation, and adjustable tree expansion depth. It is designed for viewing structured XML files such as SAP IDoc messages, Commander4j configuration files, and production schedule exports.

== Purpose ==

XML Viewer makes it practical to inspect complex XML files that are difficult to read as raw text. Element names can be translated into plain-language descriptions (for example, the SAP field code <code>ABWKZ</code> becomes "Deviation indicator" in the English translation), and the tree can be expanded to a specific depth to give a high-level overview without showing every leaf value.

== Running XML Viewer ==

XML Viewer is a Java 21 desktop (Swing) application:

java -jar xmlviewer.jar [optional path to XML file]

If a file path is provided on the command line, that file is opened immediately on launch. Otherwise, the last-opened file from the configuration is loaded.

== Loading a Document ==

Click the '''Open XML Document''' button in the right sidebar, or pass a file path on the command line. Only well-formed XML files are supported. Click '''Reload XML Document''' to re-read the current file after it has been changed externally.

== Display Modes ==

=== Standard Mode ===

The XML hierarchy is displayed exactly as it appears in the file — elements nest within their parent elements, forming a tree that mirrors the XML structure.

=== Flat Mode ===

Leaf elements (those containing only text, no child elements) are collapsed into their parent's row rather than appearing as separate tree nodes. Only elements that contain child elements appear as tree nodes. This produces a more compact view of documents with many small leaf values.

Toggle between modes using the '''View Mode''' button in the right sidebar.

== Tree Expansion Control ==

The top toolbar provides four buttons:

* '''Expand All''' — expand every node in the tree
* '''Expand Selected''' — expand only the selected subtree
* '''Collapse Selected''' — collapse the selected subtree
* '''Collapse All''' — collapse everything to root level

The '''−''' and '''+''' buttons in the toolbar adjust the current expansion level (shown as a number between the buttons). Clicking '''Refresh''' after changing the level re-expands the tree to that depth.

The expansion level is saved in the configuration and restored on next launch.

== Translation ==

XML Viewer can replace technical XML element names and values with plain-language descriptions from a translation file.

=== Enabling Translation ===

Toggle translations using the '''View Translations''' button. The '''Translation''' dropdown at the bottom of the window selects which translation file to use. The '''Language''' dropdown selects the language within that file.

=== Built-in Translation Files ===

{| class="wikitable"
|-
! File !! Contents
|-
| matmas05.xml || SAP MATMAS05 IDoc field translations
|-
| zmatmas03.xml || SAP ZMATMAS03 IDoc field translations
|-
| productionschedule.xml || Production schedule export field translations
|-
| config.xml || Commander4j configuration element translations
|-
| default.xml || Generic fallback translations
|}

=== Languages ===

The default installation includes English, French, German, and Italian. The active language can be changed at any time from the Language dropdown.

=== Adding Translations ===

Translation files are XML documents located in <code>xml/translations/</code>. Each file maps element names, attribute names, element values, and attribute values to their translated equivalents for each language. Elements without a translation entry are shown using their original name from the XML file.

== Other Display Options ==

{| class="wikitable"
|-
! Button !! Effect
|-
| View Icons || Show or hide the icon column next to each tree node
|-
| View Brackets || Wrap element values in <code>[ ]</code> brackets to distinguish them from element names
|}

== Configuration ==

=== config.xml ===

Located at <code>xml/config/config.xml</code>. Stores the last-opened file path, selected translation file, selected language, current expansion level, and the state of all four display toggles (mode, translations, brackets, icons). Updated automatically on exit.

=== log4j2.xml ===

Located at <code>xml/log/log4j2.xml</code>. Controls logging to <code>logs/XML_View.log</code>. Log files rotate at 10 MB and are retained for 14 days.

=== fonts.xml / icons ===

Icons are loaded from <code>images/xmlIcons/</code>. If an icon file referenced by a translation is not found, the icon column is left blank for that element without an error.

See also: [[TreeDoc]], [[Middleware4j]], [[Label Template Syntax]]

[[Category:Commander4j]]

SFTPTransfer

Dgarratt — Wed, 01 Apr 2026 10:31:55 GMT

Updated by push_wiki.py

Show changes

LabelServer4j

Dgarratt — Wed, 01 Apr 2026 10:26:19 GMT

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

LabelServer4j Example User Interface

Dgarratt — Wed, 01 Apr 2026 10:26:18 GMT

Updated by push_wiki.py

← Older revision		Revision as of 12:26, 1 April 2026
Line 1:		Line 1:
			LabelServer4j is a headless background service — it has no graphical user interface. All interaction with the service is through configuration files, log files, and (on Windows) the Windows Services control panel.

			== Starting LabelServer4j ==

			=== Windows ===

			LabelServer4j can be installed as a Windows service so that it starts automatically when the server boots and restarts automatically if it crashes. Once installed as a service it is managed through the standard Windows Services management console (<code>services.msc</code>) or the command line:

			net start LabelServer4j
			net stop LabelServer4j

			It can also be started directly from a command prompt for testing:

			start_labeller.cmd

			=== Linux / macOS ===

			Start from the terminal using the provided shell script:

			./start_labeller.sh

			Or directly:

			java -cp ./LabelServer.jar:./lib/devonly/i4jruntime.jar com.commander4j.labeller.Service

			The process runs in the foreground. Use a process manager (systemd, launchd, or nohup) for production deployment.

			== Monitoring ==

			Since there is no GUI, the primary monitoring tool is the log file:

			logs/c4jLabelServer.log

			The log records every event in detail:

			* Service startup and configuration loading
			* Each labeller thread starting
			* Every CSV file detected and processed
			* Every command sent to a printer and every response received
			* File operations (upload, download, backup, delete)
			* Errors and exceptions with full context

			Log files rotate at 10 MB and are retained for 14 days.

			=== What to Look For ===

			{\| class="wikitable"
			\|-
			! Situation !! What to check in the log
			\|-
			\| Label not printing \|\| Look for the CSV filename being detected; if absent, check the input path in labellers.xml
			\|-
			\| Printer not responding \|\| Look for TCP connection errors or timeout messages for that labeller's IP and port
			\|-
			\| Wrong data on label \|\| Check the variable substitution log lines to see what values were sent
			\|-
			\| Script error \|\| Look for the script line number and command that caused the failure
			\|-
			\| File stuck in input directory \|\| File renamed to <code>.in</code> means the script is running or failed — check for a <code>.error</code> file
			\|}

			== Configuration Changes ==

			To change a labeller's IP address, port, command script, or input path, edit the relevant <code>labellers.xml</code> file and restart the service. Changes to configuration files are not picked up at runtime.

			To switch site, edit <code>xml/config/config.xml</code> and change the <code>site id</code> attribute, then restart.

			== Thread Architecture ==

			When running, LabelServer4j maintains the following threads:

			* One main service thread (lifecycle management)
			* One server thread (configuration and orchestration)
			* Per enabled labeller: one labeller thread, one TCP receive thread, one TCP transmit thread

			The thread count grows with the number of configured printers. A site with six printers typically runs around 20 threads in total.

			== Graceful Shutdown ==

			Sending a termination signal (Ctrl+C on Linux/macOS, or stopping the Windows service) triggers the shutdown hook. LabelServer4j signals all labeller threads to stop, waits for any in-progress print jobs to complete, then exits cleanly.

			See also: [[Overview LabelServer4j]], [[LabelServer4j Configuration]], [[LabelServer4j Operation]], [[Install Interface Services]]

	[[Category:LabelServer4j]]		[[Category:LabelServer4j]]

	The LabelServer application is designed to run as a background process (Service) and as such does not have a user interface, however you can run is as a Terminal program or view it's activity via the Log files.

LabelServer4j Operation

Dgarratt — Wed, 01 Apr 2026 10:26:16 GMT

Updated by push_wiki.py

@@ Line 1: / Line 1: @@
-[[Category:LabelServer4j]]
+This page describes the end-to-end operational workflow of LabelServer4j — from an operator assigning a process order in Commander4j through to a label being printed on the production line.
-The easiest way to work with the LabelServer application is to drive it from the Commander4j desktop software. In the screen below you will see the Pallet Labelling screen. The operator selects the order and then uses the "Assign to Labeller" button. They can then choose the production line which the order data is sent to. This data is exported via the Commander4j Interfaces in CSV format. The LabelServer program reads this data and sends it to the labellers which are defined in the configuration.
+Each configured labeller runs in its own background thread. All labellers poll and execute simultaneously. A site with six printers runs six independent threads, each managing its own TCP connection and input directory.
-More information on label printing can be found in the Commander4j wiki in the [[Production Declaration]] and [[Pallet Label]] pages. The data exported from the Commander4j is written to the folder defined within the [[Production Lines & Labellers]] screen.
+See also: [[Overview LabelServer4j]], [[LabelServer4j Configuration]], [[LabelServer4j Dataset CSV]], [[LabelServer4j Folder Structure]], [[Production Lines & Labellers]]
-[[file:AutoLab_Operation1.png|link=|800px]]
+[[Category:LabelServer4j]]

Overview LabelServer4j

Dgarratt — Wed, 01 Apr 2026 10:26:15 GMT

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

ZPLRenderer

Dgarratt — Wed, 01 Apr 2026 10:22:02 GMT

Updated by push_wiki.py

Show changes

Middleware4j

Dgarratt — Wed, 01 Apr 2026 10:17:26 GMT

Updated by push_wiki.py

← Older revision		Revision as of 12:17, 1 April 2026
Line 1:		Line 1:
	{{~~Middleware4j~~}}		'''Middleware4j''' is a file-based message transformation and routing engine developed as a companion to [[Commander4j]]. It has no dependencies on Commander4j and can be used independently for any system integration requirement.

			Its primary purpose is to link systems that use incompatible data formats. It monitors directories for incoming files, transforms them using configurable XSLT stylesheets, and delivers the results to one or more output destinations in the required format — running continuously in the background as a service.

			For a full explanation of how the application works, see [[Overview_Middleware4j]].

			== Getting Started ==

			{\| class="wikitable" style="width:100%"
			\|-
			\| [[Overview_Middleware4j]] \|\| What Middleware4j does and how it works
			\|-
			\| [[Downloads]] \|\| Download the latest release
			\|-
			\| [[Installation_Middleware4j]] \|\| How to install and deploy as a Windows service
			\|}

			== User Guide ==

			{\| class="wikitable" style="width:100%"
			\|-
			\| [[Maps]] \|\| Configuring transformation pipelines (the core concept)
			\|-
			\| [[Connectors]] \|\| Available input and output connector types
			\|-
			\| [[Middleware4j_Example_Configuration]] \|\| Complete worked configuration example
			\|-
			\| [[EMAIL]] \|\| Email connector and SMTP configuration
			\|}

			== Connector Reference ==

			{\| class="wikitable" style="width:100%"
			\|-
			\| [[ASCII]] \|\| Fixed-column flat file input and output
			\|-
			\| [[CSV]] \|\| Delimiter-separated file input and output
			\|-
			\| [[XML]] \|\| XML document input and output with XSLT transformation
			\|-
			\| [[RAW]] \|\| Copy or move files without transformation
			\|-
			\| [[EMAIL]] \|\| Send files as email attachments or receive via email
			\|-
			\| [[SOCKET]] \|\| Transmit data to devices over TCP/IP
			\|-
			\| [[PDF_PRINT]] \|\| Automatically print PDF files to a named printer queue
			\|}

			[[Category:Middleware4j]]

PDF PRINT

Dgarratt — Wed, 01 Apr 2026 10:17:25 GMT

Updated by push_wiki.py

@@ Line 1: / Line 1: @@
-[[Category: Middleware4j]]
+The PDF_PRINT connector monitors a directory for incoming PDF files and automatically sends them to a printer. It provides a simple way to automate printing of reports, labels, or documents that are generated as PDF files by Commander4j or any other application.
-=PDF_PRINT Map Configuration=
-'''config.xml'''
+== How It Works ==
 <syntaxhighlight lang="xml">
-      <map>
+<input>
-         <id>Map06</id>
+  <id>in1</id>
-         <enabled>true</enabled>
+  <type>PDF_PRINT</type>
-         <description>Print PDF Document</description>
+  <url>
-         <enableEmailNotifications>true</enableEmailNotifications>
+    <path>./interface/input/Map06 PDF to PRINT</path>
-         <connectors>
+    <mask/>
-            <input>
+    <pollingInterval>1000</pollingInterval>
-               <id>in1</id>
+  </url>
-               <description>Read PDF Document</description>
+</input>
 </syntaxhighlight>
-This Connector is designed to automatically print PDF files whenever they are found in the nominated directory.
+== Output Configuration ==
 <syntaxhighlight lang="xml">
- <queueName>HP8600</queueName>
+<output>
 </syntaxhighlight>

RAW

Dgarratt — Wed, 01 Apr 2026 10:17:24 GMT

Updated by push_wiki.py

@@ Line 1: / Line 1: @@
-[[Category: Middleware4j]]
+The RAW connector copies or moves files from one location to another without any format conversion, transformation, or interpretation of the file contents. Unlike other [[Connectors|connectors]], it does not convert the file into an internal XML representation — the bytes are passed through unchanged.
-The other connectors will load the input file and convert into a XML representation so you can apply XSL transformations and convert into different file formats. This has a memory and cpu overhead.
+== When to Use RAW ==
-The RAW connector bypasses this step and just moves the file.
+Use the RAW connector when you need to:
-You might to this if you want to poll and remote file share and move files to a local folder for import into an application without modification.
+* Transfer files between directories or network shares without modifying them
 <syntaxhighlight lang="xml">
-      <map>
+<path>./interface/output/Map07 Path1;./interface/output/Map07 Path2;\\server\share\output</path>
 </syntaxhighlight>

Connectors

Dgarratt — Wed, 01 Apr 2026 10:17:23 GMT

Updated by push_wiki.py

@@ Line 1: / Line 1: @@
-[[Category: Middleware4j]]
+Connectors are the components within Middleware4j responsible for reading from and writing to specific file formats and protocols. Each [[Maps|Map]] has one input connector and one or more output connectors. The connector type determines how the data is read, written, or transmitted.
-The Middleware application has a selection of them already and this list is likely to grow.
+== How Connectors Work ==
-* [[ASCII|ASCII Connector]]
+When a file arrives in an input directory, the input connector reads it and converts the data into an internal XML representation. This XML is then optionally transformed by an XSLT stylesheet before being passed to each output connector. The output connector converts the XML back into the required format and writes it to the destination.
-* [[CSV|CSV Connector]]
-* [[EMAIL|EMAIL Connector]]
+== Available Connectors ==
-* [[EXCEL|EXCEL Connector]]
-* [[IDOC|IDOC Connector]]
+=== [[ASCII]] ===
-* [[MQTT|MQTT Connector]]
-* [[PDF_PRINT|PDF_PRINT Connector]]
+Reads or writes fixed-column flat files. The key configuration is the '''pattern''' attribute, which specifies which column ranges to extract from (input) or write to (output). For example, <code>1-10,12-21,23-32</code> extracts three fields from columns 1–10, 12–21, and 23–32.
-* [[RAW|RAW Connector]]
-* [[SOCKET|SOCKET Connector]]
+Use this connector when integrating with legacy systems that produce or consume fixed-width files.
-* [[XML|XML Connector]]