OS4X fetch queue - Revision history

Admin: /* Required license */

2025-09-10T09:04:03Z

Required license

2025-09-10T07:52:44Z

Daemon

2025-09-10T07:52:12Z

Supported protocols

2025-09-10T07:51:31Z

Logging

2025-09-10T07:49:01Z

Protocol specific configuration options

2025-09-10T07:40:51Z

2025-09-09T14:53:46Z

Protocol specific configuration options

2025-09-09T14:53:31Z

Protocol specific configuration options

2025-09-09T14:52:08Z

Configuration

2025-09-09T14:51:34Z

Configuration

@@ Line 3: / Line 3: @@
 = Required license =
 OS4X fetch queue comes in different license models:
-*Stand-alone license (only OS4X fetch queue is licensed)
+*Stand-alone license (only OS4X FetchQ is licensed)
 *Add-on license for OS4X Core
 *Included in OS4X Enterprise

@@ Line 65: / Line 65: @@
 = Daemon =
-The background daemon running OS4X fetch queue is "<code>os4xfqd</code>", which is installed in [[OS4X_Core_configuration#binary_installation_directory|OS4X's binary directory.]]. The daemon can be started and stopped from the top-left icon list:
+The background daemon running OS4X fetch queue is "<code>os4xfqd</code>", which is installed in [[OS4X_Core_configuration#binary_installation_directory|OS4X's binary directory]]. The daemon can be started and stopped from the top-left icon list:
 [[File:Bildschirmfoto 2025-09-09 um 16.10.32.png]]

← Older revision		Revision as of 07:52, 10 September 2025
Line 82:		Line 82:
	*WebDAV (via https)		*WebDAV (via https)

−	'''Why no SCP?''' - Well, the SCP protocol doesn't support a "<code>delete</code>" operation, so fetched files cannot be deleted from the source server, making it impossible to distinguish between already fetched files and new ones.	+	'''Why no SCP?''' - Well, the SCP protocol doesn't support a "<code>delete</code>" operation, so fetched files cannot be deleted from the source server, making it impossible to distinguish between already fetched files and new ones unless OS4X saves this information (which is not planned at the moment of writing).

@@ Line 61: / Line 61: @@
 = Logging =
 The logs in "Logs" -> "Fetch queue log" contain all information about fetching processes. If an OS4X Enterprise job is being created, it is directly viewable via the "info" icon on the left.
 = Daemon =

@@ Line 51: / Line 51: @@
 *SFTP:
 **Key file: instead of a password authentication, a SFTP key file (beware the permissions!) can be used.
 [[File:Bildschirmfoto 2025-09-09 um 16.28.28.png]]

@@ Line 48: / Line 48: @@
 **Key file: instead of a password authentication, a SFTP key file (beware the permissions!) can be used.
 *WebDAV:
-*''none''
+**''none''
 [[File:Bildschirmfoto 2025-09-09 um 16.28.28.png]]

@@ Line 40: / Line 40: @@
 == Protocol specific configuration options ==
-*FTP(S):
+*FTP(S), explicit FTPS:
 **Disable EPVS: passive file transmission will be disabled ("ACTIVE" only")
 **Disable EPRT: Disable the use of the EPRT and LPRT commands when doing active FTP transfers.
 **Disable proxy: no FTP proxy will be used.
 **Force HTTP 1.0 for proxy communication: If a FTP proxy is being used, it will be communication via (obsoleted) HTTP 1.0 only. For ancient environments only, you should really upgrade your environment.
+*SFTP:
+**Key file: instead of a password authentication, a SFTP key file (beware the permissions!) can be used.
 [[File:Bildschirmfoto 2025-09-09 um 16.28.28.png]]

@@ Line 16: / Line 16: @@
 OS4X fetch queue items have several general parameters and some are protocol specific.
-The generic configuration options are:
+== Generic configuration options ==
 *Active: if active, the entry will be picked by the fetch queue daemon.
 *Verbose protocol output: If enabled, the complete protocol input and output will be logged in the fetch queue logs and contained in the dry-run window.
@@ Line 39: / Line 39: @@
 *Next run date: If defined, the next execution date can be configured.
+== Protocol specific configuration options ==
 *FTP(S):
 **Disable EPVS: passive file transmission will be disabled ("ACTIVE" only")

@@ Line 24: / Line 24: @@
 *Server path: The target path on the server to fetch files from. If unsure use "<code>/</code>".
 *Protocol: The selectable protocol.
-*Traget folder prefix for downloaded entities: The target folder for downloaded files. If empty (by default) it will be a subdirectory of [[OS4X_Core_configuration#data_incoming_directory|OS4X's incoming directory]], followed by "<code>os4x-fetchqueue-</code>", the Unix timestamp, followed by a dash ("<code>-</code>") and the actual process ID
+*Target folder prefix for downloaded entities: The target folder for downloaded files. If empty (by default) it will be a subdirectory of [[OS4X_Core_configuration#data_incoming_directory|OS4X's incoming directory]], followed by "<code>os4x-fetchqueue-</code>", the Unix timestamp, followed by a dash ("<code>-</code>") and the actual process ID