All Pega Cloud 2 clients who use local file system repositories must refactor to refer to the Pega Cloud File storage repository as soon as possible. The refactoring must be complete before beginning the update to Pega Cloud 3 or before the end of June 2025, whichever comes first. Pega Cloud 3 does not support local file system repositories. Pega Cloud 2 will also no longer support local file system repositories by the end of June 2025. All code that still refers to local file system repositories after the update to Pega Cloud 3 or after June 2025 on Pega Cloud 2 may experience errors until you refactor to the Pega Cloud File storage repository.
Steps to refactor to Pega Cloud File storage repository
- Search for “sync-data” across your applications in Pega Platform.
- Wherever “sync-data” appears in a file path, replace the file path up to and including "sync-data" with “file://pegacloudrepository:” or “file://pegacloudfilestorage:/sftp”. Any subfolders after "sync-data" should remain the same. For example:
- "/usr/local/tomcat/work/sync-data" becomes "file://pegacloudrepository:" or “file://pegacloudfilestorage:/sftp”.
- "/usr/local/tomcat/work/sync-data/bix/" becomes “file://pegacloudrepository:/bix” or “file://pegacloudfilestorage:/sftp/bix”.
- Exception: If “sync-data” appears in a Pega rule labeled “Final” in your search, just ignore it. Do not change it. This happens most often with pzCheckIsInValidSource.
- Search for “/pegafiletransfer/” across your Pega Platform applications and in client applications that access the Pega Cloud file storage repository.
- Wherever “/pegafiletransfer/” appears in a file path, replace just “/pegafiletransfer/” with “/”.
If the searches yield no results, you are not using local file system repositories and do not need to take any further action. For more information about file storage, see Using Pega Cloud File storage.
