Forcing Content to Vault
With the increasing capability of certain applications comes a possibility that the increased number of vaults and file vault policy rules may become unmanageable. You can use the wt.fv.forceContentToVault to control this. If this property is set to false, which is the default setting, it has no effect. If this property set to true, the property forces vaulting to be accomplished through a single vault in the following way:
• The method server does not start if more than one master vault is present in the system. Therefore, you need to remove all master vaults but one before enabling this property. A message appears in the method server log describing the problem.
• If users attempt to create more than one master vault, they receive an error message stating that they cannot create more than one master vault.
• If revaulting is scheduled on the existing vault, all content that can be vaulted is moved to this vault.
• When content is uploaded to the master vault, all content that can be vaulted goes to the existing vault. Therefore, this vault must be designated as the cache vault.
|
|
A write-enabled cache vault is required to create a document or CAD document in Windchill.
|
• File vaulting policy rules are ignored.
If you are not setting properties through a graphical user interface or in a mapping rules file, you add or edit properties with the xconfmanager utility. For more information, see
Using the xconfmanager Utility.
