File system governors
In cloud environments, the file system access is restricted. Cloud-ready extensions must comply with those restrictions.
Extensions are restricted to certain folders in the BSE. Outside those folders data cannot be read or written. The LN standard software can read outside those folders but can only write in a restricted number of folders. End users cannot choose all locations to put their files that are output of their sessions.
Extensions are also restricted in writing files with certain file extensions. For example, writing a file with a .exe file extension is not allowed.
If you develop extensions in an on-premises environment with the Extensions Ready for Cloud option switched on, you can change the values in the $BSE/lib/extensibility/config.<package combination> file:
Resource | Default | Remark |
---|---|---|
user_writable_dirs
|
appdata, tmp | Within $BSE. |
not_trusted_object_accessible
|
appdata, tmp | Within $BSE. |
forbidden_filename_extensions
|
exe,vb*,com |
Adding folders or extensions to those resources results in extensions that are not ready for the cloud. These extensions may not run after they are moved to the cloud.