Difference between revisions of "OS4X Portal - shared storage"
Jump to navigation
Jump to search
| Line 21: | Line 21: | ||
= Configure shared storage (DMZ) = | = Configure shared storage (DMZ) = | ||
| + | The path of the shared folder has to be defined in "Configuration" -> "OS4X Enterprise" -> "Portals" -> "Base directory for portal": | ||
| + | [[File:Bildschirmfoto 2019-04-08 um 13.34.47.png]] | ||
= Configure shared storage (internal) = | = Configure shared storage (internal) = | ||
[[Category:OS4X Portal]] | [[Category:OS4X Portal]] | ||
Revision as of 11:36, 8 April 2019
Storage for portal jobs are typically provided by the DMZ, making communication possible from the internal zone to the DMZ. The shared storage saves the following information:
- Outgoing portal jobs (from internal to DMZ)
- outgoing job data
- Incoming portal jobs
- incoming job data
- incoming job XML information
The storage can be located anywhere in the DMZ, offering a wide range of protocols usable to be implemented, such as:
- NFS (most common, see example below)
- CIFS
- SSHFS
- others
NFS example
On OS4X portal server side (DMZ), export a directory. Configuration file:
/etc/exports
Content (example):
/nfs 192.168.2.1(rw,sync,no_root_squash,no_subtree_check)
Activate export on DMZ side:
exportfs -a
The path of the shared folder has to be defined in "Configuration" -> "OS4X Enterprise" -> "Portals" -> "Base directory for portal":
