All project files are replicated/transferred between MMs using a project flow definition.
A flow can either be:
| • | An In Flow, i.e. files are transferred from a remote MM to your MM via an In Flow. This particularly true of the Master MM of a project. On a client MM the project In Flow will reflect the same settings, but as the remote MM is indeed a client of the project an In Flow assigned to it actually means files will transfer away from the client MM and to the master MM. |
| • | An Out Flow, i.e. files are transferred from the local MM to the remote client MM assigned to the flow. Once again, a client MM will also see the Out Flow assigned to it, but will actually be transferring files to the itself from the remote master MM. |
NOTE: You can only assign flows to client MMs which have connected to you at least once.
You can add a new flow by:
| 1. | Right-clicking the Flows folder and typing a name for the flow in the Add edit box and pressing Enter |
| 2. | Now double click the new flow and setup it's properties |
Property |
Comments |
Name |
This is an unique Flow name within your project. It will automatically reflect this name at any remote MirrorMaster which connect to you as a client for the project and to which the flow has been assigned. The name is only important for humans to distinguish between flows, as your MM uniquely identifies flows by an unique flow GUID. |
Description |
Any description you which to add to the flow. |
Ownership |
The flow's ownership, i.e. for an In Flow this will mean who is responsible for the files of the flow's files (from where are files copied to your MM). For an Out Flow this means the remote MM that will be receiving part or all of the project's files. NOTE: You can only pick and set MirrorMasters that have connected to your MM at least once. |
Definition |
Here you can setup a filtering conditions for the specific flow. One condition per line is allowed and the filter criteria is applied to relative directory and filenames of all files in the project. See Understanding Flow Criteria below. |
If the flow's file limit is reached during a replication session, then this email address(es) will be notified of the fact. More than one email address is allowed and should be comma-delimited. |
|
Status |
You can disable this flow so that your MM will not include it, or any related files, in it's replication session to the responsible MM. |
Flow File Limit |
This is the flow's file limit, i.e. the maximum number of files transferred during a single session. By default it has a limit of 2 billion files, but can be set to any number, even 0. If 0, this implies that no files will ever be transferred and the email notifications will be send if any files differs between master and client MMs. |
Understanding Flow Criteria:
Each flow is defined as an in or out flow, meaning, files adhering to the flow criteria will either be downloaded from the Master MirrorMaster or be uploaded to it during replication. Each flow can contain multiple flow criteria, each on it's own line in the Definition property of a flow. A flow criteria follows the same searching format as for any files in Windows (since MS-DOS in the 1980s), i.e.:
| • | Literal characters must match exactly (but is case-insensitive) |
| • | "*"-character matches zero or more of any characters |
| • | "?"-character matches exactly one of any character |
Criteria are applied only to relative directory and file names, ex. If your project root directory, is: "c:\myproject" and it contains a folder and file called "c:\myproject\mydir1\myfile.txt", then only "\mydir1\myfile.txt" is used to match against the criteria.
Some criteria examples:
| • | "*.*" - Is the default criteria for a flow and matches all files in the project root folder and below. |
| • | "*.txt" - Matches all text files in the project root folder and below. |
| • | "\mydir1\*.txt" - Matches all text files in the project's "mydir1" subfolder only. |
| • | "*\mydir1\?*.txt" - Matches all text files with at least a 1 character name length in all folders in the project which is named "mydir1". |
| • | "*mydir1\?*.txt" - Matches all text files with at least a 1 character name length in all folders in the project of which the foldername ends with "mydir1". |
| • | "\mydir1\myfile.txt" - Matches exactly 1 file |