Windchill System Administrator's Guide

2. Use the following SQL statements to delete existing revaulting rules:
delete FvPolicyRule
delete FVPolicyItem
3. Reassign all storage folders to the vault designated as your cache vault.
4. Delete all vaults except the designated cache vault.
5. Add the following to the wt.properties file. 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, which is discussed elsewhere in this
guide.
wt.fv.forceContentToVault=true
6. Restart the method server
7. Ensure that the designated cache vault is properly configured for a large
number of data sets.
8. Initiate revaulting to the designated cache vault so that any remaining data is
moved from BLOBs to the vault.
Changing from a Multiple Vault to a Single Vault Architecture
The following steps show a method composed of deleting rules and revaulting.
Another approach is to move all folders from vaults that you will delete to a vault
that will remain.
1. Stop all scheduled revaultings.
2. Use the following SQL statements to delete existing revaulting rules:
delete FvPolicyRule
delete FvPolicyItem
3. Create a csv file with new external storage rules and a cache vault chosen to
be the storage location. Comment out the final rule.
4. In wt.properties, comment out the following FvService entry and restart the
method server. 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, which is discussed elsewhere in this guide.
wt.services.service.33 = wt.fv.FvService/wt.fv.StandardFvService
Note: Services numbering has to be sequential, so take the last service and assign
it whatever number FvService had previously);
5. Load the csv file with rules.
6. In wt.properties, restore the FvService entry and restart the method server. If
you are not setting properties through a graphical user interface or in a
3-22 Windchill System Administrator’s Guide