Pipelines
Pipelines in UDMG define a file transfer path between two Endpoints—a source and a destination. Pipelines provide the following features:
- Flexibility and Reusability: By defining a few standardized Endpoints, they can be configured in multiple ways through Pipeline-specific configurations. This means you don't have to build new Endpoints from scratch every time you have a new transfer scenario—you can mix and match existing components.
- Protocol Versatility: Supporting both server and client SFTP scenarios means UDMG can adapt to your partners' existing infrastructure rather than forcing them to change their setup. Whether you need to receive files, push them out, or pull them from remote systems, you can create a Pipeline type that fits.
- Scalable Organization: The hierarchical structure (Pipelines → Account Groups → Accounts) makes it easy to manage permissions and access at scale. You can set up Pipelines once and apply them to multiple Accounts, or create partner-specific variations as needed.
- Enforced Data Integrity: UDMG automatically validates Pipeline configurations to prevent file path conflicts that could cause data loss or overwrites, ensuring clean separation between transfer scenarios.
Pipeline Types
UDMG supports multiple Pipeline types, grouped by the role it plays in each file transfer scenario.
UDMG as Server
When UDMG acts as a Server, external partners connect to it using supported protocols such as AS2, FTP(S), HTTPS, or SFTP.
| Pipeline Name | Source Endpoint | Destination Endpoint | Description | Transfer Triggered By |
|---|---|---|---|---|
| UDMG as AS2 Server | Local AS2 Server | Local Filesystem | File transfer configuration where UDMG receives messages as the server. | Partner's AS2 client |
| UDMG as FTP(S) Server | Local FTP Server | Local Filesystem | File transfer configuration where UDMG acts as the server. | Partner's FTP(S) client |
| UDMG as HTTPS Server | Local HTTPS Server (WTC) | Local Filesystem | File transfer configuration where UDMG exposes the Web Transfer Client (WTC) interface, allowing partners to securely upload, download, and manage files and folders through a browser. | Partner actions performed through the WTC |
| UDMG as SFTP Server | Local SFTP Server | Local Filesystem | File transfer configuration where UDMG acts as the server. | Partner's SFTP client |
UDMG as Client
When UDMG acts as a Client, it initiates file transfers to remote servers.
These transfers are triggered with the Transfers Scheduled API and are not assigned to any Account Group or Account.
| Pipeline Name | Source Endpoint | Destination Endpoint | Description | Triggered By |
|---|---|---|---|---|
| UDMG as AS2 Client | Local Filesystem | Remote AS2 Server | File transfer configuration where UDMG sends messages as the client. | UDMG's Transfers Scheduled API |
| UDMG as FTP(S) Client (Push Scenario) | Local Filesystem | Remote FTP(S) Server | File transfer configuration where UDMG acts as the client pushing files to a partner's FTP(S) Server in a push scenario. | UDMG's Transfers Scheduled API |
| UDMG as FTP(S) Client (Pull Scenario) | Local Filesystem | Remote FTP(S) Server | File transfer configuration where UDMG acts as the client in a pull scenario. | UDMG's Transfers Scheduled API |
| UDMG as SFTP Client (Push Scenario) | Local Filesystem | Remote SFTP Server | File transfer configuration where UDMG acts as the client pushing files to a partner's SFTP Server in a push scenario. | UDMG's Transfers Scheduled API |
| UDMG as SFTP Client (Pull Scenario) | Remote SFTP Server | Local Filesystem | File transfer configuration where UDMG acts as the client in a pull scenario. | UDMG's Transfers Scheduled API |
Configuration Structure
Each Pipeline consists of:
- Source Endpoint: where files are retrieved, originated, or come from. Selected from a list of all available Endpoints created.
- Destination Endpoint: where files are delivered to or being sent. Selected from a list of allowable Endpoints, which is based on the selected Source Endpoint and available Pipeline Types.
- Endpoint-specific Configuration (Pipeline Configuration): required and optional Endpoint-specific fields (i.e., file and folder permissions, virtual path). This allows you to reuse a minimal set of Endpoints in a variety of Pipeline scenarios, giving you flexibility without having to reconfigure the base Endpoint configuration multiple times.
Account Authentication
UDMG as Server Pipelines are integrated with the Account and Account Group model to control access:
In this scenario, UDMG acts as a server. Accounts connect to UDMG using protocol-specific credentials, and access is controlled by the Account Groups they belong to. Each Account Group is associated with one or more Pipelines, which define the available file transfer paths.
This integration ensures that:
- Only authenticated Accounts can initiate connections.
- Each Account can only access the Pipelines explicitly assigned through its Account Groups.
- Access control is enforced at the file transfer level without requiring external firewall or directory-based restrictions.
UDMG as Client Pipelines are not Account-based and do not integrate with the Account and Account Group model. These Pipelines are triggered using UDMG's Transfers Scheduled API. The required authentication credentials are added directly to the Pipeline and are dictated by the authentication methods required by the external server.
Pipeline Validation
UDMG enforces validation checks on Pipelines to ensure file paths don't conflict. The Pipeline validation checks occur on creation and then throughout the configuration process to ensure configuration integrity.
- When a Pipeline is created:
Checks for Source Endpoint + Destination Endpoint + Endpoint-specific Configuration + Virtual Path uniqueness. - When a Pipeline is associated with an Account Group:
Checks for Destination Endpoint + Virtual Path uniqueness across all Pipelines within an Account Group. - When an Account is associated with an Account Group:
Checks for Destination Endpoint + Virtual Path uniqueness across all Pipelines associated with an Account's Account Groups.
If a conflict is identified, then the Configuration Item is blocked from being created or associated, or a detailed error message is displayed.