Difference between revisions of "OS4X Portal - shared storage"
(Created page with "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:...") |
|||
| (5 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | Storage for portal jobs | + | Storage for portal jobs is 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 portal jobs (from internal to DMZ) | ||
**outgoing job data | **outgoing job data | ||
| Line 7: | Line 7: | ||
The storage can be located anywhere in the DMZ, offering a wide range of protocols usable to be implemented, such as: | The storage can be located anywhere in the DMZ, offering a wide range of protocols usable to be implemented, such as: | ||
| − | *NFS (most common) | + | *NFS (most common, see example below) |
*CIFS | *CIFS | ||
*SSHFS | *SSHFS | ||
*others | *others | ||
| + | |||
| + | The storage must be read/writable by [[OS4X_Core_configuration#run_OS4X_programs_as_user|the user running the daemons]]. | ||
| + | |||
| + | = 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 | ||
| + | |||
| + | = 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) = | ||
| + | The path of the shared directory has to be defined per attached portal server in the corresponding portal configuration in "Configuration" -> "OS4X Enterprise" -> "Portals" -> "Portal server", there in the editing/add window in the field "Base path": | ||
| + | |||
| + | [[File:Bildschirmfoto 2019-04-08 um 13.36.32.png]] | ||
| + | |||
| + | [[Category:OS4X Portal]] | ||
Latest revision as of 07:58, 9 April 2019
Storage for portal jobs is 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
The storage must be read/writable by the user running the daemons.
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":
The path of the shared directory has to be defined per attached portal server in the corresponding portal configuration in "Configuration" -> "OS4X Enterprise" -> "Portals" -> "Portal server", there in the editing/add window in the field "Base path":
