Configuring a User’s Preferred Vault

A user’s Default Vault is the vault server where all files saved by the user are saved. For systems configured for Vault Replication, it is also the preferred vault from which files are retrieved for a given user, unless specific Read Priority vaults are set. Vaults can be specified and prioritized for each user by setting one or more vaults, including the User’s Default Vault, on the ‘Read Vaults’ relationships tab for a User.

When a user gets a file, Aras Innovator determines all the vaults with copies of the file, and selects the vault to send the file based on:

1. if it is the vault with the highest Read Priority (lowest numeric value),
2. it is the user’s default vault (if that vault is not in the Read Priority list),
3. it is another vault.

Setting the Read Vaults should be done for users to improve performance accessing files, based on latency, bandwidth, server load and other considerations.

A User’s Default Vault and Read Vault priority is also significant in triggering Replication. The user’s Default Vault sets, where a file is first saved or changed, so Replication Rules must be set on that vault to generate onChange Replication Transactions. The Read Priority, and the vault location(s) of the the file, determines which vault Aras Innovator chooses to send the file, and Replication Rules must exist on the chosen vault to generate onDemand Replication Transactions. Replication Rules are described in the next chapter.