Create a Connection Contract

When Data Mover acts as a server - meaning it receives files from a partner or makes files available for collection by an actor - a Connection Contract must be configured. This contract defines:

• the actor that sends files to Data Mover or collects them from Data Mover

• the server

• the virtual file system (VFS) and its path.

In input, the Connection Contract defines when Data Mover receives files from the Producer. The Producer, acting as the protocol client, initiates the connection to Data One, which acts as the protocol server​. ​

In output, it defines when the Consumer connects to Data Mover to retrieve the files. The Consumer acts as the protocol client, establishing the connection, while Data Mover remains the protocol server.​

The Connection Contract consists of three main components:

1. Contract Clause. This component establishes the relationship between an Actor, a protocol, and the VFS, specifying the dataflow and access parameters.

2. Associated VFS/Rule. This component links processing rules to VFS instructions, determining whether files are uploaded to or downloaded from the system, and specifies the associated metadata.

3. File Processing Rule. This component outlines the processes a file undergoes during transfer, including tasks such as encoding or compression.