...
| Info | ||
|---|---|---|
| ||
A rule's local, remote, and temporary paths must not be confused with its (virtual) path. The virtual path is only used to identify the rule and not to calculate the actual file paths. |
Let's take the example of an incoming transfer where the UDMG Server acts as a server. The file to be transferred is file.txt.
Depending on the values of the various configurations, the destination path of the file changes as follows:
udmg-server root folder | udmg-server “in” folder | Local Server root folder | Local Server receive folder | Transfer Rule local folder | Final file path |
|---|---|---|---|---|---|
/root | in | /root/in/file.txt | |||
/root | /in | /in/file.txt | |||
/root |
not applicable | server | /root/server/file.txt | ||
/root |
not applicable | /server | /server/file.txt | ||
/root |
not applicable | /server | serv_ |
in | /server/serv_in/file.txt | |
/root |
/in
not applicable | not applicable | /serv_ |
in | /serv_in/file.txt | |
/root |
not applicable | /server | not applicable | rule_local | /server |
/serv_recv
/rule_local/file.txt | |||||
| /root | not applicable | not applicable | not applicable | /rule_local | / |
| rule_local/file.txt |
Outgoing transfers work in a similar way but replace the UDMG Server's in folder with its out folder; and replace the Local Server's receive folder with its send folder.
udmg-server root folder | udmg-server “out” folder | Local Server root folder | Local Server send folder | Transfer Rule local folder | Final file path |
|---|---|---|---|---|---|
/root | out | /root/out/file.txt | |||
/root | /out | /out/file.txt | |||
/root | /out | server | /out/server/file.txt | ||
/root | not applicable | /server | /server/file.txt | ||
/root | not applicable | /server | serv_out | /server/serv_out/file.txt | |
/root | not applicable | not applicable | /serv_out | /serv_out/file.txt | |
/root | not applicable | /server | not applicable | rule_local | /server/rule_local/file.txt |
| /root | not applicable | not applicable | not applicable | /rule_local | /rule_local/file.txt |
Client transfers also work in a similar way, but without the server-specific folders.
Inbound client transfer:
udmg-server root folder | udmg-server “in” folder | Transfer Rule local folder | Final file path |
|---|---|---|---|
/root | in | /root/in/file.txt | |
/root | /in | /in/file.txt | |
/root | not applicable | rule_local | /root/rule_local/file.txt |
| /root | not applicable | /rule_local | /rule_local/file.txt |
Outbound client transfer:
udmg-server root folder | udmg-server “out” folder | Transfer Rule local folder | Final file path |
|---|---|---|---|
/root | out | /root/out/file.txt | |
/root | /out | /out/file.txt | |
/root | not applicable | rule_local | /root/rule_local/file.txt |
| /root | not applicable | /rule_local | /rule_local/file.txt |
Detailed Explanations
UDMG Server folders
...
These folders can be absolute or relative paths. In the latter case, if the UDMG Server is acting as a transfer client, the path is relative to the root. On the other hand, if the UDMG Server is the transfer server, then any relative path is considered to be relative to the local server's root, if it has one, or to the gateway's root if it doesn't have one.
Rule availability and path determination
The effective rules and paths are determined at runtime when a local account or a remote account is accessed.
When a transfer is initiated for a remote partner or when a virtual folder is accessed for a local server, the account is allowed to use a set of Transfer Rules:
- the rules that are authorized for this account,
- the rules that are authorized for the Local Server or the Remote Partner,
- the global rules, that are not assigned to any account, server, or partner.
This is displayed in the Rules tab of the relevant object details pane in the UDMG Admin UI.
For example, this local server has access to the global receiving rule "show_me_the_rules-global_r" and a "private" (or authorized for this server) rule "show_me_the_rules-partner_r".
A test account is assigned to the server:
This account has access to the same rules as the server, but also to a "private" (or authorized for this account) rule "show_me_the_rules-account_r".
| Note | ||
|---|---|---|
| ||
Both the rules that are assigned at account level or at server or partner level are indicated with the card icon ( When updating an account, the server or partner level rules are listed in the Selected Items of the Edit Rules pop-up, but only the account level rules can be removed.
Attempting to deassign a server or partner rule will have no effect, it must be done from the relevant server or partner Rules screen.:
|
