The Business Administrator determines what the vault is for, while the System Administrator defines where the vault is located on the network. Vaults should use actual host and path names, not mounted directories. Paths must be exported on the host to all users who require access to the vaults. In addition to the business object vaults created by the System Administrator, a vault called the Administration vault is created automatically when the 3DEXPERIENCE platform is installed on your system. The Administration vault is used for administrative purposes only and serves as the master definition vault. The Administration vault is used for definitions only. You cannot use it for storing business objects. All vaults contain a complete set of definitions. These definitions identify the characteristics of items such as persons, roles, types, formats, and so on. When you make changes to a definition (such as add, modify, or delete), all definition copies must be updated to reflect the change. This update of the vaults occurs simultaneously if all the copies are available. If any of the copies are not available (a vault is not available), you cannot alter the definitions. This prevents partial alteration of the definitions. For example, assume that you want to add a new format definition. After you enter the Add Format command, the system attempts to add the definition. If the definition is valid (no errors), all copies of the definitions are changed to include this new format. But assume that a vault resides on a host that is currently offline. In this case, no changes to the definitions are made. If changes were allowed, the one vault would not be updated to contain the change. Therefore, you should ensure that all defined vaults are available before modifying the definitions. For large databases, you can define an optional path vault. Because all business object, relationships, and paths consume an ID in a single table, keeping all of these items in the same vault can eventually cause performance issues for large databases. If you define a path vault, the system stores all path elements, path attributes, path descriptions, and path interfaces, which are usually stored in the object vault, in the path vault. If you do, path elements are stored in the path vault, and the related primary objects are stored in the object vault. For more information, see vault Command. | |||||||