Installation - Revision history

Dgarratt: Updated by push_wiki.py

2026-10-15T19:26:52Z

Updated by push_wiki.py

← Older revision		Revision as of 20:26, 15 October 2026
Line 125:		Line 125:
	=== Barcode Labels (ZPL) ===		=== Barcode Labels (ZPL) ===

	Barcode labels — pallet labels, case labels and sample labels — are printed by sending raw ZPL (Zebra Printer Language) commands directly to a ZPL compatible printer. This bypasses the normal print driver rendering pipeline entirely, so the ~~print queue~~ must ~~be configured as~~ a raw / pass-through queue.		Barcode labels — pallet labels, case labels and sample labels — are printed by sending raw ZPL (Zebra Printer Language) commands directly to a ZPL compatible printer. This bypasses the normal print driver rendering pipeline entirely, so the label must reach the printer untouched: either through a raw / pass-through print queue, or by '''Direct Print''', where Commander4j sends the label straight to the printer's IP address and port with no operating system queue at all. Direct Print works on every platform and is described on [[Printer Queues]].

	* '''Windows''' — install the printer using the [https://www.seagullscientific.com/support/downloads/drivers/ Seagull Scientific Generic Label] driver, or configure a ''Generic / Text Only'' queue. Do not use a standard Zebra Windows driver, as this will re-interpret the ZPL rather than passing it through.		* '''Windows''' — install the printer using the [https://www.seagullscientific.com/support/downloads/drivers/ Seagull Scientific Generic Label] driver, or configure a ''Generic / Text Only'' queue. Do not use a standard Zebra Windows driver, as this will re-interpret the ZPL rather than passing it through.
	* '''macOS''' — ~~configure~~ a ~~raw~~ printer queue ~~using~~ a ~~tool such as [https://qz.io QZ Tray] or follow~~ the guidance at [https://qz.io/docs/Setting-Up-A-Raw-Printer-in-OSX qz.io]. ~~A standard~~ macOS ~~printer queue will not work for ZPL output~~.		* '''macOS''' — a standard macOS printer queue will not work for ZPL output. On macOS 26 and earlier a raw queue can be created through the CUPS web interface, following the guidance at [https://qz.io/docs/Setting-Up-A-Raw-Printer-in-OSX qz.io]. From macOS 27 (Golden Gate) Apple has disabled the CUPS web interface, so use Direct Print instead.
	* '''Linux''' — configure a CUPS raw queue pointing at the printer's IP address and port 9100.		* '''Linux''' — configure a CUPS raw queue pointing at the printer's IP address and port 9100.

	If a label is accidentally sent to a standard print queue rather than a raw queue, the printer will output pages of ZPL text commands instead of a label. This is harmless but confirms the queue type needs to be changed.		If a label is accidentally sent to a standard print queue rather than a raw queue, the printer will output pages of ZPL text commands instead of a label. This is harmless but confirms the queue type needs to be changed.

			To use Direct Print, define the printer in [[Label Printers]] with its IP address and port and '''Direct Print''' ticked, then tick '''Direct Print''' on the label's report module in [[Modules]] and make sure Group ID, Printer Type, Language and DPI agree on both. The printer then appears in the Print Queue drop-down of the label screens. See [[Printer Queues]] for the full walk-through.

	See also: [[Zebra_ZPL_Label\|Zebra ZPL Label]], [[Intermec_IPL_Label\|Intermec IPL Label]], [[Label_Template_Syntax\|Label Template Syntax]].		See also: [[Zebra_ZPL_Label\|Zebra ZPL Label]], [[Intermec_IPL_Label\|Intermec IPL Label]], [[Label_Template_Syntax\|Label Template Syntax]].

	[[Category:Commander4j]]		[[Category:Commander4j]]

Dgarratt: Updated by push_wiki.py

2026-09-22T20:46:52Z

Updated by push_wiki.py

← Older revision		Revision as of 21:46, 22 September 2026
Line 21:		Line 21:
	== Install Java ==		== Install Java ==

	* Java 25 ~~is needed if you are installing~~:		The Windows and macOS installers include their own copy of Java, so a normal desktop installation needs nothing extra. You only need to install Java 25 yourself in two cases:
	** The desktop application on a Linux operating system.
	** The web components onto a server using Apache Tomcat.

	The ~~Windows and macOS installers include their own~~ Java, ~~so nothing extra is needed there~~.		* '''The web component''' (the scanner web application) on the server that runs Apache Tomcat. Tomcat itself needs Java to run.
			* '''The desktop application on Linux''', because the Linux installer does not bundle Java.

	'''~~Note that~~ the ~~web applications should be installed~~ on ~~a nominated server machine~~ and ~~not on workstations~~.~~'''~~		In both cases install the '''JDK''' (not the smaller JRE). The Azul Zulu JDK 25 from [https://www.azul.com/downloads/?package=jdk#zulu https://www.azul.com/downloads/?package=jdk#zulu] is recommended; on Windows choose the <code>.msi</code> installer and tick the option to set <code>JAVA_HOME</code>, which the Tomcat installer looks for.

	~~Recommend installing~~ the ~~Azul Zulu JDK from [https://www.azul.com/downloads/#zulu https://www.azul.com/downloads/#zulu]~~.		'''Note that the web application should be installed on a nominated server machine and not on workstations.'''

	== Install Tomcat 11.x ==		== Install Tomcat 11.x ==

	* Download from [~~http~~://tomcat.apache.org/ Apache Tomcat ~~Site~~].		Apache Tomcat 11 is required for the web component. Download it from the [https://tomcat.apache.org/download-11.cgi Apache Tomcat site]. On Windows choose the '''32-bit/64-bit Windows Service Installer''' so that Tomcat runs as a service and starts with the machine. The installer asks for the Java location: point it at the JDK you installed above.

	~~Ensure you download~~ the 32/~~64Bit~~ Windows Service Installer ~~package~~.

	== Configure Tomcat / Web Application ==		== Configure Tomcat / Web Application ==

	The web ~~components~~ of Commander4j ~~are contained in the .war files which you download. You won't need all of them and their names may change with updated releases.~~		The web component of Commander4j is a single file, '''c4j_commander4j_web.war''', included with every release from version 12.75 onwards (it replaced the three separate web applications of earlier releases, which are listed below for sites that still run them). It contains the scanner pages and the REST API they use.

	~~From version 12.75 the separate web applications are combined into~~ a single file, '''c4j_commander4j_web.war''', ~~which is~~ the ~~one to use for a new installation. The~~ three ~~older files~~ are listed for sites that still run them.

	The servlet (.war) files shown below are intended to work on Zebra Mobile Computers which have the Zebra Enterprise Browser installed.		The servlet (.war) files shown below are intended to work on Zebra Mobile Computers which have the Zebra Enterprise Browser installed.
Line 67:		Line 62:
	* If you update the hosts.xml file for a servlet you will need to either restart Apache Tomcat or stop and start the servlet from the [http://localhost:8080/manager/html Apache Tomcat Manager].		* If you update the hosts.xml file for a servlet you will need to either restart Apache Tomcat or stop and start the servlet from the [http://localhost:8080/manager/html Apache Tomcat Manager].
	* If you want to connect to a SQL Server database using Windows Integrated Authentication, copy the appropriate version of the auth DLL from the downloaded MS JDBC drivers (e.g. mssql-jdbc_auth-12.10.0.x64.dll) into the Java bin folder.		* If you want to connect to a SQL Server database using Windows Integrated Authentication, copy the appropriate version of the auth DLL from the downloaded MS JDBC drivers (e.g. mssql-jdbc_auth-12.10.0.x64.dll) into the Java bin folder.

			=== Optional: allow other web servers to call the REST API (CORS) ===

			The scanner pages and the REST API are served from the same web application, so browsers need no special permission to use them. If pages served from '''another''' web server (a different host name or port) need to call the API from the browser, Tomcat must be told to allow cross-origin requests. Tomcat includes a filter for this. Add the following inside the <code><web-app></code> element of <code>conf\web.xml</code> in the Tomcat installation folder, then restart the Tomcat service:

			<pre>
			<filter>
			<filter-name>CorsFilter</filter-name>
			<filter-class>org.apache.catalina.filters.CorsFilter</filter-class>
			<init-param>
			<param-name>cors.allowed.origins</param-name>
			<param-value>*</param-value>
			</init-param>
			<init-param>
			<param-name>cors.allowed.methods</param-name>
			<param-value>GET,POST,PUT,DELETE,HEAD,OPTIONS</param-value>
			</init-param>
			<init-param>
			<param-name>cors.allowed.headers</param-name>
			<param-value>Content-Type,X-Requested-With,Accept,Authorization,Origin,Access-Control-Request-Method,Access-Control-Request-Headers</param-value>
			</init-param>
			<init-param>
			<param-name>cors.exposed.headers</param-name>
			<param-value>Access-Control-Allow-Origin,Access-Control-Allow-Credentials</param-value>
			</init-param>
			</filter>
			<filter-mapping>
			<filter-name>CorsFilter</filter-name>
			<url-pattern>/*</url-pattern>
			</filter-mapping>
			</pre>

			Two things to be aware of. Placing the filter in <code>conf\web.xml</code> applies it to every web application on that Tomcat, including the Tomcat manager, so only do this on a Tomcat dedicated to Commander4j. And because <code>cors.allowed.origins</code> is <code></code>, the filter does not pass the login cookie across origins (Tomcat's <code>cors.support.credentials</code> setting stays at its default of <code>false</code>); a page on another server can therefore only call API functions that do not need a logged-in session. To allow a logged-in session from another server, replace <code></code> with that server's exact origin, for example <code>http://scanner-pages.example.local:8080</code>, and add an <code>init-param</code> setting <code>cors.support.credentials</code> to <code>true</code>.

	== Create Commander4j Services ==		== Create Commander4j Services ==

Dgarratt: Updated by push_wiki.py

2026-09-22T20:13:38Z

Updated by push_wiki.py

Show changes

Dgarratt at 16:50, 10 June 2026

2026-06-10T16:50:00Z

← Older revision		Revision as of 17:50, 10 June 2026
Line 50:		Line 50:
	== Install Java ==		== Install Java ==

	* Java 21 is needed if you are installing:		* Java 25 is needed if you are installing:
	** The desktop application on a Linux operating system.		** The desktop application on a Linux operating system.
	** The web components onto a server using Apache Tomcat.		** The web components onto a server using Apache Tomcat.

Dgarratt: Improved by ClaudeAI documentation bot — expanded content

2026-04-01T09:22:23Z

Improved by ClaudeAI documentation bot — expanded content

Show changes

Dgarratt: /* Configure Tomcat / Web Application */

2025-08-12T07:09:19Z

Configure Tomcat / Web Application

← Older revision		Revision as of 08:09, 12 August 2025
Line 128:		Line 128:
	*You can now confirm that this is working by opening the url '''http://servername:8080/chosen_servlet/'''		*You can now confirm that this is working by opening the url '''http://servername:8080/chosen_servlet/'''
	*If you need to update the hosts.xml file for a servlet you will need to either restart the Apache Tomcat service or stop and start the servlet from the [http://localhost:8080/manager/html Apache Tomcat Manager]		*If you need to update the hosts.xml file for a servlet you will need to either restart the Apache Tomcat service or stop and start the servlet from the [http://localhost:8080/manager/html Apache Tomcat Manager]
			*If you want to connect to a SQL Server database using Windows Integrated Authentication you will need to copy the appropriate version of the auth dll from the downloaded MS JDBC drivers (e.g. mssql-jdbc_auth-12.10.0.x64.dll) into the Java bin folder.

	== Create Commander4j Services ==		== Create Commander4j Services ==

Dgarratt: /* Configure Tomcat / Web Application */

2025-06-09T13:38:06Z

Configure Tomcat / Web Application

← Older revision		Revision as of 14:38, 9 June 2025
Line 111:		Line 111:
	! Servlet !! Purpose !!Environment !! Notes		! Servlet !! Purpose !!Environment !! Notes
	\|-		\|-
	\| '''~~b6web_t10_react~~.war''' \|\| Pallet Transactions \|\| Any Mobile Browser \|\| * Recommended		\| '''c4j_web_react.war''' \|\| Pallet Transactions \|\| Any Mobile Browser \|\| * Recommended
	\|-		\|-
	\| '''~~b6web_t10_android_eb3~~.war''' \|\| ~~Pallet Transactions~~\|\| ~~Zebra Enterprise~~ Browser ~~3.x on Android~~ \|\|		\| '''c4j_web_WS.war''' \|\| Quality - Product Grading \|\| Any Mobile Browser\|\| Only needed for Quality Control \|\|
	\|-		\|-
	\| '''~~b6web_t10_wm_eb18.war''' \|\| Pallet Transactions \|\| Zebra Enterprise Browser 1.8 on Windows Mobile \|\|~~		\| '''c4j_web_Issue.war''' \|\| Issue Pallets to Order & Location \|\| Tablet Mobile Browser\|\| Issue/Return of Stock
	\|-
	~~\| '''c4jWS.war''' \|\| Quality - Product Grading \|\| Any Mobile Browser\|\| Only needed for Quality Control \|\|~~
	\|-
	~~\| '''c4jIssue~~.war''' \|\| Issue Pallets to Order & Location \|\| Tablet Mobile Browser\|\| Issue/Return of Stock
	\|}		\|}

Dgarratt: /* Install Java */

2025-06-09T13:36:01Z

Install Java

← Older revision		Revision as of 14:36, 9 June 2025
Line 45:		Line 45:

	== Install Java ==		== Install Java ==
	* Java 17 is needed if you're installing		* Java 21 is needed if you're installing
	**Desktop Application into a Linux operating system.		**Desktop Application into a Linux operating system.
	**Web components onto a server using Apache Tomcat.		**Web components onto a server using Apache Tomcat.

Dgarratt: /* Install Tomcat 10.x */

2025-06-09T13:35:48Z

Install Tomcat 10.x

← Older revision		Revision as of 14:35, 9 June 2025
Line 53:		Line 53:
	Recommend installing the JDK.		Recommend installing the JDK.

	== Install Tomcat 10.x ==		== Install Tomcat 11.x ==
	* Download from [http://tomcat.apache.org/ Apache Tomcat Site]		* Download from [http://tomcat.apache.org/ Apache Tomcat Site]
	Ensure you download the 32/64Bit Windows Service Installer package.		Ensure you download the 32/64Bit Windows Service Installer package.

Dgarratt: /* Configure Tomcat / Web Application */

2025-01-25T08:28:04Z

Configure Tomcat / Web Application

← Older revision		Revision as of 09:28, 25 January 2025
Line 117:		Line 117:
	\| '''b6web_t10_wm_eb18.war''' \|\| Pallet Transactions \|\| Zebra Enterprise Browser 1.8 on Windows Mobile \|\|		\| '''b6web_t10_wm_eb18.war''' \|\| Pallet Transactions \|\| Zebra Enterprise Browser 1.8 on Windows Mobile \|\|
	\|-		\|-
	\| '''c4jWS.war''' \|\| Quality - Product Grading \|\| Any Mobile Browser\|\| Only needed for Quality Control		\| '''c4jWS.war''' \|\| Quality - Product Grading \|\| Any Mobile Browser\|\| Only needed for Quality Control \|\|
			\|-
			\| '''c4jIssue.war''' \|\| Issue Pallets to Order & Location \|\| Tablet Mobile Browser\|\| Issue/Return of Stock
	\|}		\|}