File:Modbus 256x256.png

2026-05-26T13:23:06Z

Dgarratt:

Template:Menu Applications

2026-05-26T13:22:43Z

Dgarratt: /* Applications */

=Applications=

{| cellpadding="8" style="text-align:center"
||[[File:Commander4j_256x256.png|link=[[Commander4j]]|100px]]
====[[Commander4j]]====
|
||[[file:Middleware4j_256x256.png|link=[[Middleware4j]]|100px]]
====[[Middleware4j]]====
|
||[[file:AutoLab4j_256x256.png|link=[[AutoLab4j]]|100px]]
====[[AutoLab4j]]====
|
||[[file:LabelServer4j_256x256.png|link=[[LabelServer4j]]|100px]]
====[[LabelServer4j]]====
|-
||[[file:Menu4j_256x256.png|link=[[Menu4j]]|100px]]
====[[Menu4j]]====
|
||[[file:sftpTransfer_256x256.png|link=[[SFTPTransfer]]|100px]]
====[[SFTPTransfer]]====
|
||[[file:ZPLRenderer_256x256.png|link=[[ZPLRenderer]]|100px]]
====[[ZPLRenderer]]====
|
||[[file:SocketTest_256x256.png|link=[[SocketTest]]|100px]]
====[[SocketTest]]====
|-
||[[file:TreeDoc_256x256.png|link=[[TreeDoc]]|100px]]
====[[TreeDoc]]====
|
||[[file:LaunchPad_256x256.png|link=[[LaunchPad]]|100px]]
====[[LaunchPad]]====
|
||[[file:SFTGet4j_256x256.png|link=[[SFTPGet]]|100px]]
====[[SFTPGet]]====
|
||[[file:SFTPSend4j_256x256.png|link=[[SFTPSend]]|100px]]
====[[SFTPSend]]====
|-
||[[file:XMLViewer_256x256.png|link=[[XMLViewer]]|100px]]
====[[XMLViewer]]====
|
||[[file:Modbus_256x256.png|link=[[ModbusServer]]|100px]]
====[[ModbusServer]]====
|
||[[file:Modbus_256x256.png|link=[[ModbusClient]]|100px]]
====[[ModbusClient]]====
|}

ZPLRenderer

2026-05-07T13:24:37Z

Dgarratt: Updated by push_wiki.py

ZPL Renderer is a desktop application that interprets ZPL (Zebra Programming Language) commands and renders them as a visual preview of what a label will look like when printed on a physical Zebra printer. It is a companion tool to Commander4j, LabelServer4j, and AutoLab4j.

== Purpose ==

ZPL is a text-based command language used to define label layouts, text, graphics, and barcodes for Zebra label printers. The commands are sent directly to the printer as a stream of characters and are not human-readable. ZPL Renderer allows you to:

* Load a ZPL file and see what the label will look like before sending it to a printer
* Listen on a network socket so that any application sending ZPL to that port renders the label on screen in real time
* Zoom in and out to examine label detail
* Preview multiple labels from a single ZPL stream
* Export the rendered label to PDF
* Print the rendered label directly from the application

== Running ZPL Renderer ==

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 25 desktop (Swing) application:

java -jar zplrenderer.jar

On first launch it reads its configuration from <code>xml/config/config.xml</code>.

== Loading a ZPL File ==

Use the '''Open''' toolbar button to load a <code>.zpl</code> text file from disk. The label is rendered immediately. Use '''Refresh''' to reload the file after editing it externally.

Several example ZPL files are included in the <code>examples/</code> directory:

{| class="wikitable"
|-
! File !! Contents
|-
| example1.zpl || Shipping label with QR code, text, and graphics
|-
| example2.zpl || Complex layout with boxes, barcodes, and logo
|-
| barcodes.zpl || Showcase of all supported barcode types
|-
| pallet_labels.zpl || Pallet label examples typical of Commander4j output
|-
| fonts.zpl || Font size and style demonstration
|-
| shipping.zpl || Shipping label sample
|-
| character.zpl || Character set reference
|-
| grid.zpl || Layout grid for alignment reference
|}

== Network Socket Mode ==

ZPL Renderer can listen on a TCP/IP port and render any ZPL label stream sent to it. This allows Commander4j, LabelServer4j, or any other application to use ZPL Renderer as a virtual printer — sending ZPL to the socket and seeing the result on screen instead of printing to paper.

The default port is '''9100''' (the standard Zebra raw print port). The IP address and port are configured in <code>config.xml</code>. Enable listening using the '''Network''' button in the toolbar.

ZPL Renderer extracts complete label blocks from the stream, identified by the standard <code>^XA</code> (start of label) and <code>^XZ</code> (end of label) delimiters.

== REST API ==

ZPL Renderer can also expose its rendering engine as a lightweight HTTP service. When REST mode is enabled, any application — including a web browser — can submit ZPL to ZPL Renderer over HTTP and receive back a rendered PNG, a multi-page ZIP of PNGs, or a multi-page PDF.

'''ZPL Renderer must be installed locally and the REST server must be toggled on for any of the URLs in this section to work.'''

=== Enabling REST Mode ===

REST mode is controlled from the toolbar. Alongside the network socket controls, the toolbar provides:

* a '''REST''' toggle button (disconnected icon when off, connected icon when on)
* a '''Port''' field (default '''8080''')

Click the REST button to start the server on the chosen port. Click again to stop it. While the server is running, the port field is locked.

A running REST server accepts requests on:

* <code>http://<host>:<port>/</code> — a small HTML form for pasting ZPL by hand
* <code>http://<host>:<port>/render</code> — the rendering endpoint

=== Endpoints ===

{| class="wikitable"
|-
! Method !! URL !! Body / Parameters
|-
| GET || <code>/render?zpl=...</code> || URL-encoded ZPL in the <code>zpl</code> query parameter (suitable for short payloads or clickable links)
|-
| POST || <code>/render</code> || Raw ZPL request body (any Content-Type other than form-encoded), read as ISO-8859-1
|-
| POST || <code>/render</code> || <code>application/x-www-form-urlencoded</code> body with a <code>zpl</code> field
|-
| GET || <code>/</code> || Returns a built-in HTML form for ad-hoc rendering in a browser
|}

=== Query Parameters ===

All parameters are optional. Where a parameter is omitted, the value falls back to the GUI's current settings.

{| class="wikitable"
|-
! Name !! Description !! Default
|-
| <code>dpi</code> || Printer DPI (e.g. 203, 300, 600) || GUI setting
|-
| <code>width</code> || Label width || GUI setting
|-
| <code>height</code> || Label height || GUI setting
|-
| <code>uom</code> || Unit of measure: <code>cm</code> or <code>inch</code> || GUI setting
|-
| <code>mag</code> || Output magnification (1.0 = full DPI) || 1.0
|-
| <code>page</code> || 1-indexed page selector (only used when <code>format=png</code>) || 1
|-
| <code>format</code> || Output format: <code>png</code>, <code>zip</code> or <code>pdf</code> || <code>png</code>
|}

=== Output Formats ===

{| class="wikitable"
|-
! Format !! Content-Type !! Description
|-
| <code>png</code> || image/png || A single rendered label (the page selected by <code>page</code>). Returns 404 if the page is out of range.
|-
| <code>zip</code> || application/zip || All rendered labels packaged as <code>page_1.png</code>, <code>page_2.png</code>, ...
|-
| <code>pdf</code> || application/pdf || All rendered labels in a single PDF (raster, one image per page).
|}

Every successful response includes an <code>X-Total-Pages</code> header reporting the number of labels found in the submitted ZPL.

The server also adds permissive CORS headers (<code>Access-Control-Allow-Origin: *</code>) so a web page served from anywhere can call the endpoint via JavaScript. <code>OPTIONS</code> preflight requests are handled.

=== Example ===

The link below renders the contents of <code>examples/barcodes.zpl</code> directly in a browser tab using the GET endpoint, with the ZPL inlined as a URL-encoded <code>zpl</code> query parameter:

* [http://127.0.0.1:8080/render?zpl=%5EXA%0A%5ELT0010%0A%5EFX%20EAN%208%0A%5ECF0%2C30%0A%5EFO120%2C10%5EFH%5EFDEAN%208_7e%5EFS%0A%5ECF0%2C25%0A%5EBY3%2C2%2C270%0A%5EFO50%2C40%5EB8N%2C100%2CY%2CN%5EFD1234567%5EFS%0A%0A%5EFX%20EAN%2013%0A%5ECF0%2C30%0A%5EFO550%2C10%5EFDEAN%2013%5EFS%0A%5ECF0%2C25%0A%5EBY3%2C2%2C270%0A%5EFO450%2C40%5EBEN%2C100%2CY%2CN%5EFD123456789012%5EFS%0A%0A%5EFX%20Interleaved%202%20of%205%0A%5ECF0%2C30%0A%5EFO100%2C220%5EFDInterleaved%202%20of%205%5EFS%0A%5ECF0%2C25%0A%5EBY3%2C2%2C290%0A%5EFO40%2C250%5EB2N%2C100%2CY%2CN%2CY%5EFD12345678%5EFS%0A%0A%5EFX%20Code%2039%0A%5ECF0%2C30%0A%5EFO550%2C220%5EFDCode%2039%5EFS%0A%5EFX%20Third%20section%20with%20bar%20code.%0A%5ECF0%2C25%0A%5EBY3%2C2%2C270%0A%5EFO400%2C250%5EB3N%2CY%2C100%2CY%2CN%5EFD12345678%5EFS%0A%0A%5EFX%20pdf%20417%0A%5ECF0%2C30%0A%5EFO170%2C410%5EFDPDF%20417%5EFS%0A%5EFX%20Third%20section%20with%20bar%20code.%0A%5ECF0%2C25%0A%5EBY2%2C2%2C100%0A%5EFO40%2C440%5EB7N%2C25%2C3%2C6%2C11%2CN%5EFD12345678%5EFS%0A%0A%5EFX%20Code%20128%0A%5ECF0%2C30%0A%5EFO540%2C600%5EFDCode%20128%5EFS%0A%5EFX%20Third%20section%20with%20bar%20code.%0A%5ECF0%2C25%0A%5EBY2%2C2%0A%5EFO460%2C630%0A%5EBCN%2C100%2CY%2CN%2CY%2CA%5EFD20250809ABC%5EFS%0A%0A%5EFX%20Code%2011%0A%5ECF0%2C30%0A%5EFO550%2C410%5EFDCode%2011%5EFS%0A%5EFX%20Third%20section%20with%20bar%20code.%0A%5EFO450%2C440%0A%5ECF0%2C25%0A%5EBY3%2C2%2C270%0A%5EB1N%2CN%2C100%2CY%2CN%5EFD12345678%5EFS%0A%0A%5EFX%20EAN%20128%0A%0A%5ECF0%2C30%0A%5EFO330%2C780%5EFDEAN%20128%5EFS%0A%5EFO80%2C810%0A%5EBY2%2C2%0A%5EBCN%2C100%2CY%2CN%2CY%2CN%0A%5ECF0%2C20%2C15%0A%5EFD%3E%3B%3E80207613036650397200715270131374752%3E8105212093365%5EFS%0A%0A%5EFX%20Aztec%0A%5ECF0%2C30%0A%5EFO160%2C980%5EFDAztec%5EFS%0A%5EFX%20Third%20section%20with%20bar%20code.%0A%5EFO140%2C1010%0A%5ECF0%2C25%0A%5EB0R%2C5%2CN%2C35%2CN%2C1%2C0%5EFDThis%20is%20a%20Test%20Barcode%5EFS%0A%0A%5EFT400%2C1120%0A%5EBQN%2C2%2C4%2CM%2C7%0A%5EFDMAhttps%3A%2F%2Fwww.commander4j.com%5EFS%0A%0A%5EXZ Render barcodes.zpl in your browser]

To render the same file by uploading it as a POST body (more practical for large payloads), use any HTTP client. With <code>curl</code>:

curl --data-binary @examples/barcodes.zpl \
"http://127.0.0.1:8080/render?format=pdf" \
-o barcodes.pdf

For ad-hoc rendering without crafting a URL by hand, open the built-in form:

* [http://127.0.0.1:8080/ http://127.0.0.1:8080/]

== Zoom ==

Use the zoom controls in the toolbar to scale the rendered label between 0.10× and 2.00×. The default zoom is configured in <code>config.xml</code> (default: 0.5×). This is useful for examining barcode detail or checking overall label proportions.

== Multiple Labels ==

When a ZPL file or network stream contains multiple labels, ZPL Renderer displays them as pages. Navigation controls allow stepping through each label. The maximum number of pages displayed is configurable (default: 3).

== Export and Print ==

* '''PDF Export''' — saves the rendered label as a vector PDF using Apache PDFBox
* '''Print''' — sends the rendered label to a system printer

== Supported ZPL Commands ==

ZPL Renderer supports over 100 ZPL commands. Key categories:

=== Label Setup ===
{| class="wikitable"
|-
! Command !! Description
|-
| ^XA || Start of label
|-
| ^XZ || End of label
|-
| ^LL || Label length
|-
| ^LH || Label home (origin offset)
|-
| ^LT || Label top offset
|-
| ^PQ || Print quantity
|-
| ^CD || Change delimiter character
|-
| ^CC || Change caret character
|}

=== Text and Fields ===
{| class="wikitable"
|-
! Command !! Description
|-
| ^FO || Field origin (X,Y position from top-left)
|-
| ^FT || Field typeset (X,Y position from bottom-left)
|-
| ^FD || Field data (the text content)
|-
| ^FS || Field separator
|-
| ^FR || Field reverse (inverted colours)
|-
| ^FW || Field orientation/rotation
|-
| ^FX || Comment (ignored in output)
|}

=== Fonts ===
{| class="wikitable"
|-
! Command !! Description
|-
| ^A0–^AZ || Select font by ID
|-
| ^CF || Change default alphanumeric font
|-
| ^CI || Change international character set/encoding
|}

=== Graphics ===
{| class="wikitable"
|-
! Command !! Description
|-
| ^GB || Graphic box (rectangle)
|-
| ^GC || Graphic circle
|-
| ^GD || Graphic diagonal line
|-
| ^GE || Graphic ellipse
|-
| ^GF || Graphic field (embedded image data)
|-
| ^GS || Graphic symbol
|}

=== Barcodes ===
{| class="wikitable"
|-
! Command !! Description
|-
| ^BC || Code 128 / GS1-128 (EAN-128)
|-
| ^BE || EAN-13
|-
| ^B8 || EAN-8
|-
| ^B3 || Code 39
|-
| ^B2 || Interleaved 2 of 5
|-
| ^B1 || Code 11
|-
| ^BQ || QR Code
|-
| ^B7 || PDF417
|-
| ^B0 / ^BO || Aztec
|-
| ^BY || Bar code field defaults (width, ratio, height)
|}

Barcode rendering uses the OkapiBarcode library. GS1 application identifiers are interpreted from <code>xml/config/gs1_app_defs.xml</code>.

== Configuration ==

=== config.xml ===

Located at <code>xml/config/config.xml</code>:

{| class="wikitable"
|-
! Setting !! Description
|-
| Input folder || Default directory for ZPL file loading (default: <code>./examples</code>)
|-
| Port || Network socket port to listen on (default: 9100)
|-
| Default magnification || Starting zoom level (default: 0.5)
|-
| Max pages || Maximum number of label pages to display (default: 3)
|}

=== fonts.xml ===

Located at <code>xml/config/fonts.xml</code>, this file maps ZPL font IDs (0, A–Z) to TrueType font files and defines their pixel dimensions. This allows ZPL Renderer to simulate the fonts installed in a physical Zebra printer.

Included fonts: Bitstream Vera, Anonymous Pro, ATTriumvirate.

If your labels use fonts that differ from the defaults, edit <code>fonts.xml</code> to match the font metrics of your target printer.

== Relationship to Commander4j ==

Commander4j generates ZPL label streams for pallet and case labels. ZPL Renderer allows you to preview these labels before deploying them to production printers, and to verify that label templates produce the correct output after making changes to the template syntax. See [[Label Template Syntax]] and [[Zebra ZPL Label]] for information on ZPL label authoring within Commander4j.

See also: [[Zebra ZPL Label]], [[Label Template Syntax]], [[Printer Queues]], [[Production Lines & Labellers]]

[[Category:Commander4j]]

File:SFTPTransfer.jpg

2026-04-24T17:54:03Z

Dgarratt:

SFTPTransfer

2026-04-24T17:53:51Z

Dgarratt:

SFTPTransfer is a background file transfer service that moves files between a local filesystem and a remote SFTP server. It is a standalone Java application that runs either as a headless background service or as a desktop application with a minimal GUI, and supports both uploading (PUT) and downloading (GET) in independent threads.

SFTPTransfer replaces the earlier sftpSend and sftpGet tools with a unified, configurable service.

== Purpose ==

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

SFTPTransfer supports two startup modes selected at launch time:

{| class="wikitable"
|-
! Mode !! Behaviour
|-
| '''Start desktop''' || Opens a small GUI window. Transfer threads start in a paused state; the operator must click Start in the interface to begin polling. Useful for testing configuration.
|-
| '''Start service''' || Headless — no GUI window. Transfer threads start immediately on launch. Suitable for production deployment as a background service or scheduled task.
|}

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

All configuration is held in XML files under the <code>xml/config/</code> directory. Changes require a service restart unless hot-reload is triggered (see below).

=== sftp_common.xml ===

Shared settings used by all transfer threads:

{| class="wikitable"
|-
! Setting !! Description
|-
| Poll interval || How often (in seconds) each thread checks for new files. Default: 10 seconds.
|-
| Backup retention || Number of days to keep backed-up files before automatic deletion.
|-
| Log level || Logging verbosity passed to Log4j.
|}

=== sftp_put.xml ===

Configures one or more PUT (upload) profiles. Each profile defines:

{| class="wikitable"
|-
! Setting !! Description
|-
| Enabled || Whether this profile's thread is active.
|-
| Local path || Local directory to watch for outbound files.
|-
| File mask || Wildcard pattern to match files (e.g. <code>*.xml</code>, <code>order_*.csv</code>). Uses Apache Commons IO WildcardFileFilter.
|-
| Remote host || SFTP server hostname or IP address.
|-
| Remote port || SFTP port (default: 22).
|-
| Remote path || Target directory on the remote server.
|-
| Username || SFTP login username.
|-
| Password || AES-encrypted password (see [[#Password Encryption|Password Encryption]]).
|-
| Private key path || Path to SSH private key file (alternative to password authentication).
|-
| Backup path || Local directory where successfully uploaded files are moved.
|-
| Error path || Local directory where files that failed to upload are moved.
|}

=== sftp_get.xml ===

Configures one or more GET (download) profiles. Each profile defines:

{| class="wikitable"
|-
! Setting !! Description
|-
| Enabled || Whether this profile's thread is active.
|-
| Remote host || SFTP server hostname or IP address.
|-
| Remote port || SFTP port (default: 22).
|-
| Remote path || Directory on the remote server to poll for incoming files.
|-
| File mask || Wildcard pattern matched against the remote file listing (server-side ls).
|-
| Local path || Local directory where downloaded files are saved.
|-
| Username || SFTP login username.
|-
| Password || AES-encrypted password.
|-
| Private key path || Path to SSH private key file.
|-
| Delete after download || Whether to delete the remote file after successful download.
|-
| Backup path || Local directory where a copy of each downloaded file is kept.
|}

=== jsch_properties.xml ===

Advanced SSH session parameters passed directly to the JSch library. Used to control host key checking, preferred algorithms, and connection timeouts. In most deployments this file can be left at its defaults.

=== email_properties.xml ===

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.

== Installing as a Windows Service ==

The native install package includes <code>sftpTransfer_Service.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).

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"
|-
! Command !! Effect
|-
| <code>sftpTransfer_Service.exe /install</code> || Register as '''sftpTransfer_Service''' with automatic startup on boot
|-
| <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 /stop</code> || Stop the service (waits for graceful shutdown)
|-
| <code>sftpTransfer_Service.exe /restart</code> || Restart the service
|-
| <code>sftpTransfer_Service.exe /status</code> || Query status (exit code: 0 = running, 3 = stopped)
|-
| <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>).

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

The native install package also provides two alternatives for testing:

{| class="wikitable"
|-
! Launcher !! Mode !! Use case
|-
| <code>sftpTransfer_Console.exe</code> || Console (headless) || Runs the service logic in a visible console window — useful for watching log output during initial configuration
|-
| <code>sftpTransfer.exe</code> || Desktop GUI || Opens the GUI window in Start desktop mode — transfer threads start paused, allowing configuration to be verified before enabling transfers
|}

== Authentication ==

SFTPTransfer supports two authentication methods, configured per profile:

{| class="wikitable"
|-
! Method !! How to configure
|-
| Password || Set the <code>Password</code> field in the profile to an AES-encrypted value. Leave the private key path empty.
|-
| SSH private key || Set the <code>Private key path</code> field to the path of a PEM-format private key file. The password field is ignored.
|}

Both methods use the JSch 2.x SSH library with Bouncy Castle as the cryptographic provider.

=== Password Encryption ===

Passwords stored in configuration files are AES-encrypted. Plain-text passwords are never stored on disk. To encrypt a password, use the password utility included with Commander4j (the same utility used for database passwords in Commander4j's own configuration).

== File Transfer Behaviour ==

=== PUT (Upload) ===

# SFTPTransfer polls the local input directory every 10 seconds (configurable).
# Files matching the file mask are selected for upload.
# Each file is uploaded to the remote path using a temporary name with a <code>.tmp</code> extension.
# On successful transfer, the remote file is renamed to its final name (atomic rename — the remote system never sees a partial file).
# The local source file is moved to the backup directory.
# If the transfer fails, the file is moved to the error directory and an error is logged.

=== GET (Download) ===

# SFTPTransfer lists the remote directory every 10 seconds (configurable).
# Files matching the file mask are selected for download.
# Each file is downloaded to the local path using a <code>.tmp</code> extension.
# On successful download, the local file is renamed to its final name.
# If configured, the remote file is deleted after download.
# A backup copy is optionally saved to the local backup directory.

== Thread Architecture ==

When running, SFTPTransfer maintains the following threads:

{| class="wikitable"
|-
! Thread !! Purpose
|-
| TransferPUT || One thread per enabled PUT profile, each managing its own SFTP connection.
|-
| TransferGET || One thread per enabled GET profile, each managing its own SFTP connection.
|-
| EmailThread || Sends error notification emails asynchronously.
|-
| ArchiveThread || Periodically purges backup files older than the configured retention period.
|}

== Hot Configuration Reload ==

SFTPTransfer supports a configuration reload mode (<code>Mode_CONFIG_UPDATE</code>). When this mode is triggered, running threads re-read their configuration files without requiring a full service restart. This allows profile changes — such as updating a remote path or rotating credentials — to be applied with minimal disruption.

== Logging ==

All activity is written to the Log4j log file. The log records:

* Service startup and configuration loaded
* Each thread starting and its profile settings
* Every file detected, transfer attempted, and outcome
* Every remote connection attempt and disconnect
* File move operations (to backup or error directories)
* Errors and exceptions with full context

Log rotation and retention are configured in the Log4j configuration file included in the distribution.

== Dependencies ==

{| class="wikitable"
|-
! Library !! Version !! Purpose
|-
| JSch || 2.27.9 || SSH/SFTP client
|-
| Bouncy Castle || current || Cryptographic provider for JSch
|-
| Apache Commons IO || current || WildcardFileFilter for local file matching
|-
| Log4j || 2.25.3 || Logging
|}

See also: [[LabelServer4j]], [[Middleware4j]], [[Production Lines & Labellers]]

[[Category:Commander4j]]