| Panel | |
|---|---|
|
For the UDMG Web Transfer Client, please refer to UDMG Web Transfer Client for Linux Installation.
Upgrading Universal Data Mover Gateway
Upgrading UDMG refers to the increase of a currently installed pre-2.0.x Version, Release, or Modification level of UDMG (1.5.x, 1.4.x, 1.3.x, 1.2.x) to UDMG 2.0.x.
| Note | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||
If you are upgrading an installation of UDMG from any release prior to 1.3.0.0, you must uninstall the older version before installing the new version.
It may be required to modify the work and data directories ownership or access rights and to update UDMG Server transfer rules to use paths that are accessible by the 'udmg' user. The configuration files must be reviewed and compared between the old and new locations. Special attention is required for the AESpassphrase parameter for UDMG Server. It must be the path for the file that was used by the previous release and must be accessible by the new service user. It is recommended to set an absolute path in the configuration file. |
| Note | ||
|---|---|---|
| ||
Starting with UDMG version 2.0, a license key must be provided to enable file transfers. Contact your Stonebranch representative or Customer Support to receive the license key prior to upgrading to version 2.0 or later. |
| Anchor | ||||
|---|---|---|---|---|
|
Pre-Installation / Upgrade Backups
The installation process overwrites the current files (exception: the configuration files are kept), this may affect your modifications.
Backing up the configuration files optimizes the time it takes you to get up and running after installing or upgrading.
/opt/udmg/etc/udmg/nginx/udmg.conf/opt/udmg/etc/udmg/agent/client.toml/opt/udmg/etc/udmg/agent/server.toml/opt/udmg/etc/udmg/auth-proxy/config.toml/opt/udmg/etc/udmg/web-transfer/config.toml/opt/udmg/etc/udmg-server/server.ini
After upgrading RPM or DEB packages, review the new configuration file templates (with the extension .rpmnew or .dpk-new) and edit the current configuration files to add new parameters or remove deprecated parameters.
Anchor db_migration db_migration
Release Migration
The UDMG release version is stored in the database to ensure the data structure is compatible with the version of the UDMG components.
...
Upgrading with Linux Software Packages
Step 1 | Contact your Stonebranch representative or Customer Support to receive the software package for the intended operating system. | |||||
|---|---|---|---|---|---|---|
Step 2 | Perform the recommended backup of configuration files. | |||||
Step 3 | Stop the components services. The exact steps depend on the system architecture and the deployed components, for example:
| |||||
Step 4 | Upgrade the UDMG packages (RPM or DEB), for example:
| |||||
| Step 5 | Review the component configuration files. Note that new configuration file templates (with the extension .rpmnew or .dpk-new) that contain all the allowed parameters are added during the software package upgrade.
| |||||
| Step 6 | Perform the release migration. | |||||
| Step 7 | Start the components services. The exact steps depend on the system architecture and the deployed components, for example:
|
...
Step 1 | Contact your Stonebranch representative or Customer Support to receive the software package for the intended operating system. |
|---|---|
Step 2 | Perform the recommended backup of configuration files. |
Step 3 | Stop the components services. The exact steps depend on the system architecture and the deployed components, for example:
|
Step 4 | Replace the component binaries:
Change ownership/permissions on new files:
Upgrade the Admin UI:
|
| Step 5 | Review the component configuration files. Refer to each component installation section below for the list of parameters. |
| Step 6 | Perform the release migration. |
| Step 7 | Start the components services. The exact steps depend on the system architecture and the deployed components, for example:
|
Installing and Configuring the Components
| Note | ||
|---|---|---|
| ||
Starting with UDMG version 2.0, a license key must be provided to enable file transfers. Contact your Stonebranch representative or Customer Support to receive the license key prior to installing the version 2.0 or later. |
| Anchor | ||||
|---|---|---|---|---|
|
...
Performing a manual installation
| Note | ||
|---|---|---|
| ||
Starting with UDMG version 2.0, a license key must be provided to enable file transfers. Contact your Stonebranch representative or Customer Support to receive the license key prior to installing the version 2.0 or later. |
UDMG Admin UI
| Note |
|---|
The following steps require root privilege, so make sure that you have the correct access before continuing. |
...
| Anchor | ||||
|---|---|---|---|---|
|
Security-Enhanced Linux (SELinux) is enabled by default on modern RHEL and CentOS servers. Each operating system object (process, file descriptor, file, etc.) is labeled with an SELinux context that defines the permissions and operations the object can perform. In RHEL 6.6/CentOS 6.6 and later, NGINX is labeled with the httpd_t context.
When SELinux is enabled, the UDMG Admin UI shows "403 access denied" and "404 page not found" errors on the landing page and permission errors are reported in the NGINX log files:
| Panel |
|---|
|
...