|
If you are using PostgreSQL as your persistence provider, the offline queue is persisted to support failover for ThingWorx high availability.
|
File Transfer Settings
|
Data Type
|
Default
|
Notes
|
---|---|---|---|
Min Threads Allocated to File Transfer Pool
|
NUMBER
|
10
|
|
Max Threads Allocated to File Transfer Pool
|
NUMBER
|
10
|
Asynchronous file transfers could be lost if ThingWorx goes down. For example, this setting has the default value of 10, and 50 long-running file transfers are submitted. If ThingWorx goes down, 40 would be lost.
|
Max Queue Entries Before Adding New Working Thread
|
NUMBER
|
100
|
The maximum number of active transfers allowed at a time.
|
Idle Thread Timeout (sec)
|
NUMBER
|
600000
|
|
FileTransfer Idle Timeout (sec)
|
NUMBER
|
30
|
|
Max FileTransfer block size (bytes)
|
NUMBER
|
128000
|
This variable imposes a maximum block size during file transfer at a system level. EMS configuration still takes precedence, however, if the EMS is configured with a larger buffer_size than what is configured in this variable, then this variable will cap this block size. If larger block sizes (128KB) are configured through EMS, this value must be increased. The maximum compile level is 1MB.
|
Max FileTransfer size (bytes)
|
NUMBER
|
100000000
|
If the source file is larger than this value, the transfer fails and an error message is displayed.
|
Max File Transfers Allowed in Offline Queue
|
NUMBER
|
50000
|
|
Max File Transfers Allowed Per Thing in Offline Queue
|
NUMBER
|
10
|
|
Time to Live (sec) of a Queueable File Transfer
|
NUMBER
|
86400
|
A file transfer will be removed from the offline queue after this specified amount of time.
|
Total Max Edge-Controlled File Transfers Allowed
|
NUMBER
|
500
|
The total concurrent edge-controlled transfers across the platform. The range is 1–1000 transfers. This is separate from the maximum allowed always-on transfers (which are controlled by the Max Queue Entries Before Adding New Working Thread setting.)
|
Total Max Edge-Controlled File Transfers Allowed Per Thing
|
NUMBER
|
2
|
The maximum number of concurrent transfers allowed to or from an edge-controlled Thing. The range is 1–100 transfers. For example, a value of 2 means that one edge-controlled Thing can only have two active transfers (upload or download) at a given time. Subsequent requests to dequeue file transfer egress are rejected until there is capacity.
|
Idle Timeout for Edge-Controlled File Transfers (sec)
|
NUMBER
|
600
|
The maximum time an active job can remain active without being acted on (for example, by data transfer or job state update). The range is 1–3600 seconds. This is similar to the idle timeout for always-on transfer jobs, but it is usually longer to account for the ping cycle of polling devices.
|