Page History
| Panel | |||||||||
|---|---|---|---|---|---|---|---|---|---|
|
Introduction
Using an external Session Manager or using the default one decides what type of temporary persistence strategy will be used.
This article documents the different persistent strategy used by each case for storing temporary files
As a simplification, these are the general rules that apply for persisting a temporary file
| Coonection type | Persistence | Clustered | Notes |
|---|---|---|---|
| Memory | Temporary | No | The file is stored temporarily for the duration of the current request. At the end of the request the file is deleted. Memory connections and temporary persistence should be used when an uploaded/received file is immediately sent to a 3rd party system during the same request. |
| Memory | Temporary | Yes | |
| Other / FileSystem | Temporary | No | The file is stored temporarily for the duration of the current session. At the end of the session the file is deleted. |
| Other / FileSystem | Temporary | Yes | The file is stored temporarily for the duration of the current session and a Quartz job is scheduled to delete the file. |
Note: It is possible to enter a file size in the file upload container that is larger than accepted by the system (network or server settings for example). In that case the network/server setting will overrule this size.
Temporary memory
The Blueriq Runtime stores the file inside the Runtime's memory, no matter if it is running as a single environment or in a clustered environment.
| Note |
|---|
If the file is larger than the heap size on the system, the user will receive an error. |
If a connection type memmory is set and the persistence is permanent, the runtime will throw an exception
Temporary file store
Container / Services
Overview
Content Tools