Requirements
System Requirements for Linux
Linux x64 (kernel 3.10 and later, glibc 2.17-78 and later), x86_64 based or Debian based
NGINX web server (1.20 and later)
PostgreSQL database (12 and later) or MySQL (8 and later)
UDMG distribution files for the different modules:
UDMG Admin UI
UDMG Authentication Proxy
UDMG Server
UDMG Agent Proxy, this module is optional
- An account with administrative privileges for the installation.
- Network connectivity via TCP/IP.
- Approximately 100 megabytes of disk space for the installation. More disk space is required for log files.
- A dedicated account for the execution of the UDMG components, with write access to the storage location for the files that will be managed by UDMG.
System Requirements for Windows
Windows Server 2012 R2 (or Windows 8.1) and later
NGINX web server (1.20 and later)
PostgreSQL database (12 and later)
UDMG distribution files for the different modules:
UDMG Admin UI
UDMG Authentication Proxy
UDMG Server
UDMG Agent Proxy, this module is optional
- An account with administrative privileges for the installation.
- Network connectivity via TCP/IP.
- Approximately 100 megabytes of disk space for the installation. More disk space is required for log files.
- A dedicated account for the execution of the UDMG components, with write access to the storage location for the files that will be managed by UDMG.
WinSW (https://github.com/winsw/winsw/releases/tag/v2.11.0) for service management, optional.
Database Space Requirements
Following the initialization of the Universal Data Mover Gateway database, the initial table space size will be approximately 10MB.
Based on calculations using data from all transfer types, each file transfer consumes approximately 2KB of database space. You should estimate space requirements for your data based on your expected number of file transfers per day and the duration for retaining history and activity data before purging.
Working Space Requirement
UDMG allows to define a complex folder structure for the storage of the local files. The final and temporary location of a file for a given transfer scenario can be set by means of the global configuration, or at the Server level, or by the transfer rule which itself depends on the combination of partner/server, account and the requested target path. This allows to split into different folder and/or filesystems according to the business cases, for security requirements, or access speed, or space management. For more details please refer to the UDMG Server configuration file, the creation and update of Server entities, and the creation and update of Transfer Rules.
The Temp Directory (also denoted as 'tmpReceiveDir') is only utilized for file transfer where UDMG is on the receiving end (either by actively downloading a file as a client, or by being pushed a file as a server). This is were the partial content is stored until the completion of the file data exchange between server an client. At the end of the transfer, the temporary file is moved to its target location that was defined by the transfer rule Local Directory (or the default value from the Server entity Receive Directory, or in turn by the default from UDMG Server global configuration).
All the final and temporary folder locations must be large enough to accommodate the expected volume of files and their retention period (to be handled outside of UDMG). For example, let's assume a transfer scenario with a daily download of a 1.5 Tb file, a weekly retention is setup with the removal of file older that 7 days, a setup where the temporary and final storage are on different filesystems. Considering solely this scenario, the temp storage must be greater than 1.5Tb and the final storage greater than 11 Tb. Ideally, both would require to be at least the double in size, to allow for transfer failures and retries.
Note that having the temp and final on the same filesystem would avoid the need for additional space and usually speed up the moving (intra-filesystem move operation versus inter-filesystem copy and delete)