UDMG as FTP(S) Server

The UDMG as FTP(S) Server Pipeline type represents a standard FTP(S) transfer scenario where UDMG acts as a server, accepting inbound connections from external clients and storing received files in a local directory.

This Pipeline consists of:

• A Local FTP Server Endpoint that receives incoming FTP(S) connections (used as the Source Endpoint).
• A Local Filesystem Endpoint that stores the received files (used as the Destination Endpoint).
• Pipeline-specific configuration options.

info

Unlike Pipelines in which UDMG acts as a client, transfers in this Pipeline type are automatically triggered by the UDMG Server when a partner performs an action. To enable this, the Pipeline must be assigned to at least one Account Group to grant access to the Account associated with that partner.

Before You Begin

Understanding Paths in FTP(S) Server Pipelines

When configuring a UDMG as FTP(S) Server Pipeline, several path fields determine where files are received and where they are written to the filesystem.

Each path has a specific role and is combined during runtime to build the complete source and destination paths used in transfers.

Bind IP (Listener IP Address) and Port

The Listener IP Address and Port define the local bind address and port where the UDMG Server listens for incoming FTP(S) connections for this Pipeline.

These values are configured in the Local FTP Server Endpoint used as the Source Endpoint.

Depending on your network (load balancer, DNS, firewall/NAT rules, or use of USP), the partner-facing FTP(S) hostname (or public IP) and port may differ from the bind address configured on the Endpoint. In such cases, ensure that the partner is provided with the correct public-facing hostname (or public IP) and port to reach your UDMG FTP(S) Server.

Virtual Path

The Virtual Path defines the directory path that an Account can see and browse when connecting to UDMG FTP(S) Server.

Virtual Paths represent the partner-facing directory structure. They do not need to match the underlying filesystem layout used by the Pipeline.

An Account may see more than one Virtual Path, depending on how many Pipelines (with the same Local FTP(S) Server Endpoint as Source Endpoint) the Account can access. Each Virtual Path is associated with a specific Pipeline.

Domain Chroot

Depends on the domain_chroot argument defined in the Configuration File, which specifies the base path UDMG prepends at runtime. Valid argument values are:

• NONE: No path is added.
• WORKDIR: The file path is resolved relative to the work_directory_path argument defined in the Configuration File.
• WORKDIR+DOMAIN: Same as WORKDIR, but UDMG also prepends the Domain name. For example, if the work_directory_path is /home/udmg/ and the Domain name is primary, the resulting path portion is /home/udmg/primary.

info

• Default value for domain_chroot is WORKDIR+DOMAIN.
• Default value for work_directory_path is /home/udmg/.

Root File Path

Path that establishes the storage hierarchy for all transferred files and provides the critical reference point for enforcing permissions across the file system structure.

It is defined in the Local Filesystem Endpoint used as the Destination Endpoint for this Pipeline.

warning

Must point to a directory that exists on the local UDMG host.

Relative Path

The Relative Path completes the directory where files are written.

It can use Runtime Variables.

Valid formats:

• /
• /[path]
• /[path]/[subdir]/

It is defined in this Pipeline configuration.

warning

Must point to a directory that exists on the local UDMG host.

Runtime Variables

UDMG allows dynamic Relative Paths using variables. The variables are allowed in the Relative Path and are expanded at runtime (when the transfer is starting or when a FTP(S) command is executed).

This allows you to set a common Relative Path folder name for multiple Accounts, which are redirected to a private local directory.

Variable	Description	Category
${SESSION_UUID}	The unique UUID of the current session.	Session
${DOMAIN_ID}	The numeric ID of the Domain associated with the session.	Domain
${DOMAIN_UUID}	The UUID of the Domain associated with the session.	Domain
${DOMAIN_NAME}	The name of the Domain associated with the session.	Domain
${ENDPOINT_NAME}	The name of the Endpoint associated with the session.	Endpoint
${ACCOUNT_ID}	The numeric ID of the Account for the session.	Account
${ACCOUNT_NAME}	The login name of the Account for the session.	Account
${YYYY}	The current year with four digits (e.g., 2024).	Date/Time
${MM}	The current month with two digits (e.g., 09).	Date/Time
${DD}	The current day of the month with two digits (e.g., 12).	Date/Time

Relative Paths examples:

• /${ACCOUNT_ID}/Input
• /${YYYY}/Processing
• /RelativePath

Staging

During inbound transfers, UDMG first writes incoming files to a temporary staging folder. After the upload completes (and any configured processing, such as ICAP scanning, succeeds), UDMG moves the file to its final destination under the configured Domain Chroot, Root File Path and Relative Path.

The staging folder is configured on the Local Filesystem Endpoint as the Temporary Path. For details and configuration guidelines, see Temporary Path.

Account Authentication

Remote clients connecting to a Local FTP(S) Server Endpoint are authenticated using Accounts, each of which defines a unique set of credentials authorized to access one or more Pipelines. These Accounts can be created internally within UDMG or can be provisioned by an LDAP provider (see Authentication).

For authentication to succeed:

• The client must connect using credentials that match a configured Account.
• The Account must belong to an Account Group.

• The Account Group must be assigned to the Pipeline that will handle the transfer.

This layered approach ensures:

• Only clients with valid, known credentials can access the Local FTP(S) Server.
• Access is restricted to the Pipelines explicitly linked to the client's Account Group.
• Credentials are managed centrally via Account Groups, decoupled from individual Pipelines.

info

For detailed instructions on this topic, refer to the Accounts and Account Groups.

Permissions

The file and folder level permissions Accounts can perform associated with the Relative Path. The permissions are set for the Local Filesystem Endpoint.

The available permissions are:

Permission	Availability
Download/Read File
Upload/Write File
Overwrite File
Delete File
List File
Make Directory
Remove Directory
Rename File
Share File

warning

Partners using an FTP(S) GUI clients should have List File permission to browse the directory properly. If List File is not included, partners may see empty folders, missing files, or inconsistent UI behavior.

Universal Event

UDMG seamlessly integrates with UAC to automate the entire business workflow, ensuring that file transfers become part of a comprehensive, orchestrated process rather than isolated data movements. One way to integrate UDMG into UAC is to enable the UAC Universal Event within a Pipeline. When enabled, a UAC Universal Event is generated each time a file transfer action occurs through the Pipeline on the UDMG Server. This event is used to trigger a Universal Monitor Task for file processing or further actions concerning this transfer within UAC.

The event is published at the end of a receiving file transfer for both successful and failed transfers.

info

For the UAC Universal Event to work, the integration with UAC must be also be enabled within the Pipeline and configured within the Configuration File.

Adding a Pipeline

To add a Pipeline, follow these steps:

1. From the Sidebar, select Configuration > Pipelines.
2. Click Add Pipeline.
3. Complete the Name and Description for the new Pipeline.
4. Select the Source Endpoint with a Local FTP Server Endpoint type and fill out the dynamic fields.
5. Select the Destination Endpoint with a Local Filesystem Endpoint type and fill out the dynamic fields.
6. Click Add.

warning

UDMG does not allow for the creation of identical Pipelines (even with unique names). The Pipeline must pass the Source Endpoint + Destination Endpoint + Permissions + Virtual Path uniqueness check. See Pipelines for more information on Pipeline validation checks.

Field Descriptions

The following table describes the fields that display in the Pipeline Details:

Name	Description	Specifications	Required
Name	Name of the Pipeline. info Using a descriptive name makes the association of Pipelines to Account Groups easier.	Must be unique. Must follow the Standard Naming Pattern. Cannot be modified after creation.	Yes
Description	Description for the Pipeline.		No
Source Endpoint	The Source Endpoint is where files are retrieved, originated, or come from. Allowable Source Endpoints are based on the available Pipeline combinations.	Must reference an already created Local FTP Server Endpoint Cannot be modified after creation. Endpoint type = Local FTP Server	Yes
Destination Endpoint	The Destination Endpoint is where files are delivered to or sent. Allowable Destination Endpoints are based on the available Pipeline combinations.	Must reference an already created Local Filesystem Endpoint Cannot be modified after creation. Endpoint type = Local Filesystem	Yes
Virtual Path	The path that is the directory structure visible to an Account upon login, but it doesn't directly correspond to the physical filesystem structure. info Modifying this path after initial setup will impact associated Accounts.	Format: /	Yes
Relative Path	The path appended to the Root File Path (set on the Endpoint page) to form a complete directory path. info Modifying this path after initial setup will impact associated Accounts.	Format: can start with a / and accepts variables.	Yes
Permissions	The file and folder level permissions associated with the Relative Path. Options: Download/Read File Upload/Write File Overwrite File Delete List List File Make Directory Remove Directory Rename File	Defaulted to Download/Read File, Upload/Write File, Overwrite File, Delete List, List File	Yes
Universal Event	When enabled, a UAC Universal Event is generated based on the Pipeline configuration.	Defaulted to Disabled.	Yes

Editing a Pipeline

To edit a Pipeline, follow these steps:

1. From the Sidebar, select Configuration > Pipelines.
2. Click the Name of the Pipeline you want to edit.
3. Click the Edit button above the Pipeline details.
4. Edit details for the Pipeline.
   • The Source Endpoint and Destination Endpoint cannot be changed after creation.
5. Click Update.

warning

Upon Pipeline update, UDMG checks for Endpoint Source + Endpoint Destination + Configuration + Virtual Path uniqueness, as well as Endpoint Destination + Virtual Path uniqueness across all Pipelines already associated with Account Groups and Accounts.

info

Pipeline changes are reflected immediately only for new connections. Ongoing client sessions are not affected until they reconnect.

Managing a Pipeline

All Pipelines support the ability to view the complete Pipeline and linked Endpoint details, including Account Group information.

Viewing Pipeline Details

To view the details of a Pipeline, follow these steps:

1. From the Sidebar, select Configuration > Pipelines.
2. Click the Name of the Pipeline you want to view.
3. Click the Overview Tab or Account Groups Tab to see additional Pipeline, Endpoint, and Account Group details.

Pipeline Metadata

Pipeline details include all parameters given in the Field Descriptions table, plus the following read-only metadata:

Name	Description
UUID	Universally Unique Identifier of this Pipeline.
Version	Version number of the configuration. Every change increases the number.
Enabled	Pipeline's Enabled status. If enabled, field is set to True.
Created	Date and time this Pipeline was created.
Updated	Date and time this Pipeline was last updated.

Enabling and Disabling Pipelines

Pipelines can be Enabled or Disabled to control their active status and ability to participate in file transfers. The status is defaulted to Enabled and can be changed after creation. The Configuration Item's Disabled status does not impact whether it can be configured. Also, Disabled Endpoints can be added to a Pipeline.

• Enabled (default): The Pipeline is active and allows file transfers.
• Disabled: The Pipeline is inactive and does not allow file transfers.

To enable or disable a Pipeline, follow these steps:

1. From the Sidebar, select Configuration > Pipelines.
2. Click the Name of the Pipeline you want to enable or disable.
3. Click the Enable or Disable button above the Pipeline details.
4. If the Pipeline is Disabled, then the button displays Enabled. If the Pipeline is Enabled, then the button displays Disabled.
5. Click Update.

info

Changes to a Pipeline's Enabled/Disabled status take effect immediately for **new** connections. Existing client sessions continue unaffected until they reconnect.

Deleting a Pipeline

To delete a Pipeline, follow these steps:

1. From the Sidebar, select Configuration > Pipelines.
2. Click the Name of the Pipeline you want to delete.
3. Click the Delete button above the Pipeline details.
4. You will be asked to confirm the deletion. Click Delete.

warning

UDMG prevents the deletion of a Configuration Item if it is currently referenced by another Configuration Item (i.e., Account Group). The Configuration Item must be edited or the reference removed before you can delete the Pipeline. Deletion cannot be undone.

Monitoring a Pipeline

To monitor and determine the status of a Pipeline, the Transfers page and Endpoints page must be monitored to track incoming Transfers and the Source and Destination Endpoints' individual statuses, respectively. If an Endpoint (Local FTP Server) goes down (Endpoint Status <> Running), then all of the associated Pipelines, Account Groups, and Accounts are impacted.

On the Transfers page, the following fields indicate the type of Local Transfer.

• Is Schedule: If No, then the Transfer was a Local Transfer.
• Is Send:
  • If No, then the Account uploaded a file to UDMG
  • If Yes, then the Account downloaded a file from UDMG.