Supported File Locations from File Listeners in On Premise Environment
Hi all
We are on premise environment and currently working with Local data storage for File listeners.
As per the below article Local File system is deprecated for Cloud .
Hi all
We are on premise environment and currently working with Local data storage for File listeners.
As per the below article Local File system is deprecated for Cloud .
- Can we still use the same for On Premise?
- If yes will it still work when we will move to containerisation deployments ?
| Repository type | On-premises systems | Pega Cloud Services | Configuration notes |
| Pega Cloud File Storage | Not applicable | Default | Pega Cloud File Storage is the default repository configured and ready to use in applications running in Pega Cloud Services environments. |
| Amazon S3, Microsoft Azure, JFrog Artifactory | Supported | Supported | These repository types are not configured by default in Pega Platform. Configure a new repository. For more information, see Creating a repository. |
| Local file system | Supported (recommended only when using a shared network storage) | Not supported | Local storage on nodes in Cloud is ephemeral. Therefore, data that is stored in Cloud can be lost.
For more information, see Creating a repository. |
Accepted Solution
Updated: 22 Jan 2024 4:50 EST
Pegasystems Inc.
US
You asked the following:
- Can we still use an on premise environment that currently works with Local data storage for File listeners?
- Answer: Yes, there is nothing stopping you from configuring local data storage. Pega just acknowledges that cloud environments would require a repository.
- If yes will it still work when we will move to containerisation deployments ?
- Yes, moving to a containered deployed (like Kubernetes) should not change the local share point.
There is documentation below that outlines how to setup and configure on premise file systems. This could also be applied to listeners. There is a cavet in there stating that, "You should only use local file system repositories with a shared or network storage, or for development-time experimentation." This is best practices and you should try to adhere to this recommendation.
https://docs-previous.pega.com/data-management-and-integration/87/adding-premises-file-system-legacy?
Pegasystems Inc.
US
To expand with some additional information, the following link describes persistent volumes in kubernetes that would enable all nodes to access a standard mount point and behave like local storage. This would require a shared network storage in the volume configuration.