Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 2 Current »

Universal Data Mover Gateway release 2.0.1.0 - January 20, 2025, contains the following high-level features. For a complete list of all the included features and fixes, please refer to Universal Data Mover Gateway 2.0.x Maintenance.

Protocols

Backlog

Title

Description

B-17141UDMG Admin UI, UDMG Server

Adds support for an outbound HTTP proxy for SFTP client connections.

A Remote Partner can be configured to connect through an HTTP or HTTPS proxy.
Proxy credentials for basic authentication are optional and can be given as a username and password.

User Experience

Backlog

Title

Description

#40899, #40940UDMG Admin UI, UDMG Web Transfer Client 

Adds the option to delete an ad-hoc share record in the Ad-Hoc Activity list.

On Admin UI, the action buttons are revamped to align with the standard style.

On Web Transfer Client, the delete option is added:

#42758UDMG Admin UI

Standardizes the date and hour format across the Admin UI to align with UAC. The date and hour format is yyyy-MM-dd HH:mm:ss xx.

Architecture

Backlog

Title

Description

#43113UDMG Server

Fixes the retry mechanism after a database error. The configurable retry parameters are applied for all database DML statements.

The occurrences of the retry attempts are logged with new messages:

ERROR: Attempt 1/3 failed with error: …
ERROR: Max retries reached. Returning last error: …

This was causing transfer errors when the transaction was chosen as a deadlock victim on a MS SQL Server database.

#43203UDMG ServerFixes the handling for the loss of database connection. Under certain conditions, UDMG Server instance would remain in ACTIVE mode after a disconnection from the database. Connection attempts on the local servers and the REST would fail and the /ping interface would show the active state and prevent a failover by a network load balancer.

The instance will now switch to OFFLINE mode and /ping API will return OFFLINE to allow the switch to another instance by the network load balancer.


  • No labels