Seon Core configuration - Revision history

R.pfaff: /* Fetch EERPs for ISDN partners, too? */

2018-09-13T13:07:33Z

‎Fetch EERPs for ISDN partners, too?

Admin: /* Daemon parameters */

2018-05-29T19:21:40Z

‎Daemon parameters

Admin: /* Daemon parameters */

2018-05-29T19:20:01Z

‎Daemon parameters

Admin: /* OFTP2 */

2018-03-01T07:41:06Z

‎OFTP2

Admin: /* TLS server: check client certificate validity */

2018-02-19T15:52:43Z

‎TLS server: check client certificate validity

Admin: /* TLS server: check client certificate validity */

2018-02-19T15:50:43Z

‎TLS server: check client certificate validity

Admin: /* OFTP2 */

2018-02-19T15:16:56Z

‎OFTP2

Admin: /* Seon Enterprise - Basic */

2017-08-22T08:12:51Z

‎Seon Enterprise - Basic

Admin: /* Delete file, if available */

2017-06-02T09:10:46Z

‎Delete file, if available

Admin: /* Cleanup of sent send queue entries */

2017-06-02T09:06:03Z

‎Cleanup of sent send queue entries

@@ Line 1,058: / Line 1,058: @@
 |}
-Since 2016-11-28, by default OS4X only fetches EERPs for TCP/IP and TLS partners (before this release, also ISDN partners are being contacted for missing EERPs). If you activate this checkbox, also ISDN partners are being contacted for missing EERPs (files in the send queue with status "waiting for remote acknowledge). '''Be aware that in combination with the send queue daemon time slice parameter and the EERP timeslice factor, the send queue daemons initiates outgoing sessions which can generate connection costs!'''
+Since 2016-11-28, by default Seon only fetches EERPs for TCP/IP and TLS partners (before this release, also ISDN partners are being contacted for missing EERPs). If you activate this checkbox, also ISDN partners are being contacted for missing EERPs (files in the send queue with status "waiting for remote acknowledge). '''Be aware that in combination with the send queue daemon time slice parameter and the EERP timeslice factor, the send queue daemons initiates outgoing sessions which can generate connection costs!'''
 ==== Don't deactivate dir.scanner entries on error? ====

← Older revision		Revision as of 19:21, 29 May 2018
Line 1,034:		Line 1,034:

	If multiple partner entries match, first one will be used.		If multiple partner entries match, first one will be used.
−
−	~~==== Be absolute RFC restrictive? ====~~
−	~~{\|style="background:white"~~
−	~~\|- style="background:lightgrey;"~~
−	~~\| '''DB configuration name:''' \|\| rfc_conformity~~
−	\|}
−
−	~~This optional parameter enables strict RFC conformity. This enables:~~
−	*Closure of TCP/IP connection after partner closes connection only (no pro-active socket closing)
−	*Sending CD message even if the partner doesn't want to (EFPA['N']). This unwanted "C"hange "D"irection request break OFTP sessions with (at least) Axway products.

	==== Fetch EERPs? ====		==== Fetch EERPs? ====

← Older revision		Revision as of 19:20, 29 May 2018
Line 775:		Line 775:

	Seon will update all file transfer progress information after this value (in seconds). Because it is database driven, some MySQL server will crash if you have too many connects to a database in a very short time (which could occur if you transfer very little files with a combination of a small exchange buffer size). If you experience problems with your database server, try increasing this value.		Seon will update all file transfer progress information after this value (in seconds). Because it is database driven, some MySQL server will crash if you have too many connects to a database in a very short time (which could occur if you transfer very little files with a combination of a small exchange buffer size). If you experience problems with your database server, try increasing this value.
−
−	~~==== default maximum parallel send processes ====~~
−	~~{\|style="background:white"~~
−	~~\|- style="background:lightgrey;"~~
−	~~\| '''DB configuration name:''' \|\| default_max_sendq_sendings_per_partner~~
−	\|}
−
−	You can define the amount of parallel sending processes globally here. There is also a definable column in the partner table (see below) to set this value on a per-partner base. If you don't have such a column, this default value will be used.

	==== allow unsecure OFTP 2 authentification ====		==== allow unsecure OFTP 2 authentification ====

← Older revision		Revision as of 07:41, 1 March 2018
Line 1,488:		Line 1,488:

	This configuration option is used in new certificate signing requests as the common name ("CN") of this OFTP2 system.		This configuration option is used in new certificate signing requests as the common name ("CN") of this OFTP2 system.
		+
		+	==== Activate auto-cleanup of old certificates? ====
		+	{\|style="background:white"
		+	\|- style="background:lightgrey;"
		+	\| '''DB configuration name:''' \|\| configOftp2AutoCleanup
		+	\|}
		+
		+	Since certificates will expire, Seon will warn you about this fact. If you want Seon to clean up expired certificates automatically (so you don't have to do this manually), you can enable this checkbox.
		+
		+	==== Automatically enable disabled certificates? ====
		+	{\|style="background:white"
		+	\|- style="background:lightgrey;"
		+	\| '''DB configuration name:''' \|\| configOftp2AutoEnableInactiveCert
		+	\|}
		+
		+	If an old certificate has been archived by the mechanism above, disabled (say: not yet enabled) certificates can be enabled dynamically. This is also a mechanism for automatic handling during certificate renewal.

	=== Logging ===		=== Logging ===

@@ Line 141: / Line 141: @@
 Summarizing:
-If you have this checkbox disabled (default):
+If you have this checkbox enabled (default):
 *Seon's TLS server asks the remote side, if not already presented, during TLS handshake for a client certificate.
 *This TLS client certificate is checked against the list of trusted certificates in order to verify a valid certificate chain for the certificate.
 *If the certificate chain is trusted, all chain elements are checked against the actually installed certificate revocation lists ("CRLs").
-If you have this checkbox enabled (not the default, not recommended):
+If you have this checkbox disabled (not the default, not recommended):
 *None of the above checks is being executed.
 *Every TLS client can connect to your server without any further client certificate check.

@@ Line 137: / Line 137: @@
 When this option is activated, all incoming TLS connections will be checked for a client certificate and a validity path for them. In case of self-signed certificates from the client, you have to add them manually (by requesting them from the partners) to your trusted certificate pool.
-In case of client sessions, Seon will override a wrong purpose of the server certificate (such as "SSL Server: no").
+In case of client sessions, Seon will override a wrong purpose of the server certificate (such as "SSL client: no").
 ==== Ignore TLS CRL unavailability? ====

← Older revision		Revision as of 15:16, 19 February 2018
Line 1,392:		Line 1,392:

	After successful receipt of an OFTP2 file, you may suppress the automatic sending of an EERP by activating this feature. You should ensure to send an EERP via "[[Seon_Core_binaries#seoneq_.2F_seoneq2\|seoneq]]" with all parameters given in the "[[Seon_Core_event_scripts#end_receive_script\|end receive script]]".		After successful receipt of an OFTP2 file, you may suppress the automatic sending of an EERP by activating this feature. You should ensure to send an EERP via "[[Seon_Core_binaries#seoneq_.2F_seoneq2\|seoneq]]" with all parameters given in the "[[Seon_Core_event_scripts#end_receive_script\|end receive script]]".
		+
		+	==== Send EERP in synchronous session? ====
		+	{\|style="background:white"
		+	\|- style="background:lightgrey;"
		+	\| '''DB configuration name:''' \|\| configOftp2SyncEerp
		+	\|}
		+
		+	In OFTP2, file handling (like decompression, signature verification and decryption) is being processed in an asynchronous, forked process (because this handling can take a very long time in terms of network connections; many minutes are not uncommon). If you have to deal with synchronous data transfers where an EERP '''MUST''' be transfered in the same OFTP2 session, you can enable this option. Beware of the (default: 1MB) size limit of received files for enabling this feature.
		+
		+	==== Maximum size of sync. EERP files (in kB) ====
		+	{\|style="background:white"
		+	\|- style="background:lightgrey;"
		+	\| '''DB configuration name:''' \|\| configOftp2SyncEerpMaxsize
		+	\|}
		+
		+	If the above mentioned synchronous EERP handling for OFTP2 is enabled, you have to define a filesize limit of the transfered file. Files bigger that this limit are not handled by the synchronous EERP process.
		+
		+	==== Add log entry for synchronous EERP handling ====
		+	{\|style="background:white"
		+	\|- style="background:lightgrey;"
		+	\| '''DB configuration name:''' \|\| configOftp2SyncEerpLog
		+	\|}
		+
		+	If synchronous file handling takes place, an optional log entry can be places in the receive log every time this process is activated. '''Warning:''' may increase your receive log massively!

	==== Delete original OFTP2 handled files which have been enqueued by send queue daemon? ====		==== Delete original OFTP2 handled files which have been enqueued by send queue daemon? ====

← Older revision		Revision as of 08:12, 22 August 2017
Line 1,180:		Line 1,180:

	When enabled, the administrative web interface warns an administrator if the configured address code is used by another person in the same company. This is done by marking the input field as invalid, adding a hover mask for a textual information that this address code is used already.		When enabled, the administrative web interface warns an administrator if the configured address code is used by another person in the same company. This is done by marking the input field as invalid, adding a hover mask for a textual information that this address code is used already.
		+
		+	===== Disable automatic addresscode conversion =====
		+	{\|style="background:white"
		+	\|- style="background:lightgrey;"
		+	\| '''DB configuration name:''' \|\| configGuiAddresscodeDontConvert
		+	\|}
		+
		+	When enabled, the administrative web interface doesn't convert the addresscode into upper case, so it's usable for other purposes than ENGDAT routing.
		+
		+	===== Shall errornous sendings abort jobs =====
		+	{\|style="background:white"
		+	\|- style="background:lightgrey;"
		+	\| '''DB configuration name:''' \|\| configEnterpriseAbortJobRejectedFiles
		+	\|}
		+
		+	When enabled, the "end send" event of Seon Core will abort jobs if sending is errornous.
		+
		+	===== Absolute AJAX URL for job restore processes =====
		+	{\|style="background:white"
		+	\|- style="background:lightgrey;"
		+	\| '''DB configuration name:''' \|\| enterprise_archive_restore_url
		+	\|}
		+
		+	For archived jobs, this URL will be called via JSONP in order to restore the job.
		+
		+	===== Name of parameter for restore AJAX call =====
		+	{\|style="background:white"
		+	\|- style="background:lightgrey;"
		+	\| '''DB configuration name:''' \|\| enterprise_archive_restore_parametername
		+	\|}
		+
		+	When restoring Seon Enterprise jobs via the above configured URL, this is the name of the parameter containing the archive ID.
		+
		+	===== Event to be executed for sent non-Enterprise files =====
		+	{\|style="background:white"
		+	\|- style="background:lightgrey;"
		+	\| '''DB configuration name:''' \|\| non_enterprise_send_event
		+	\|}
		+
		+	If you use Seon Core and Seon Enterprise events in parallel, this event will be fired if a "end_send" will be executed for non-Enterprise enqueued files.
		+
		+	===== Name of JSONP callback parameter =====
		+	{\|style="background:white"
		+	\|- style="background:lightgrey;"
		+	\| '''DB configuration name:''' \|\| enterprise_archive_restore_callbackname
		+	\|}
		+	Due to JSONP, this is the name of the required callback function parameter. The default value (if empty) is "<code>callback</code>".

	==== Seon Enterprise - Webaccess ====		==== Seon Enterprise - Webaccess ====

@@ Line 717: / Line 717: @@
   Deleted send queue entry '<virt. filename>' and file '<abs. filename>'
-If this option is disabled, the log message says:
+If this option is disabled or the referenced file doesn't exist, the log message says:
   Deleted send queue entry '<virt. filename>'

@@ Line 698: / Line 698: @@
 |}
-If enabled, the send queue daemon cleans up the send queue for all entries with a given age automatically. Optionally, an event "[[OS4X_Core_event_scripts#Send_queue_cleanup_event|Send queue cleanup event]]" will be executed.
+If enabled, the send queue daemon cleans up the send queue for all entries with a given age automatically (based on the timestamp of "last change"). Optionally, an event "[[OS4X_Core_event_scripts#Send_queue_cleanup_event|Send queue cleanup event]]" will be executed.
 ===== Age of send queue entries for cleanup (days) =====