Difference between revisions of "OS4X Portal"
Jump to navigation
Jump to search
| Line 27: | Line 27: | ||
For a functional OS4X Portal communication, the following communication protocols needs to be enabled between internal to external zone: | For a functional OS4X Portal communication, the following communication protocols needs to be enabled between internal to external zone: | ||
*[[OS4X Portal - shared storage|shared storage]] (like NFS, CIFS or others) | *[[OS4X Portal - shared storage|shared storage]] (like NFS, CIFS or others) | ||
| − | *http(s) communication via a defined port (80 | + | *http(s) communication via a defined port (TCP ports 80 or 443 by default) |
[[Category:OS4X Portal]] | [[Category:OS4X Portal]] | ||
Revision as of 19:38, 7 April 2019
Product purpose
OS4X Portal is a portal solution for transferring files between an internal and external server for a secure data exchange with external communication partners, who typically don't have an own solution for managed data transfers.
Definition
- OS4X Portal server: a server in the DMZ
- OS4X Portal daemon: software handling portal jobs, running in the internal network zone
Components
OS4X Portal consists of several components being used:
Internal
- Special portal license
- Portal definition
- User management and synchronization
- OS4X Portal daemon
- Portal send plugin
- Portal receive plugin
- shared storage
External
- Special portal license
- OS4X client daemon
- Portal configuration
- shared storage
Required communication ports
For a functional OS4X Portal communication, the following communication protocols needs to be enabled between internal to external zone:
- shared storage (like NFS, CIFS or others)
- http(s) communication via a defined port (TCP ports 80 or 443 by default)