Vaults can be configured for specific classes of objects by relating the vault to an interface instantiated on the object being vaulted. This interface is not a file interface but one on the object to which the file is attached (for example, ISPFDocumentVersion or ISPFNonSectionedTransmittal).
Once an interface is related to a vault:
-
That vault is valid only for objects that instantiate that interface.
-
Objects that instantiate that interface can no longer be vaulted in any vault that is not related to an interface instantiated on that object.
For example, to force all published documents to use a vault named PlantAVault, the vault could be configured as follows:
|
Name |
PlantAVault |
|---|---|
|
Related owning groups |
None |
|
Related configurations |
PlantA |
|
Related interfaces |
IFDWDocumentRevision |
Once a vault is configured for an interface of an object, that object can only go
to vaults that are related to interfaces that the object instantiates. For example,
if PlantA is configured as shown above, and a document is published for another plant,
PlantB, but a similar vault is not configured for PlantB, the document will not be
published to a vault. To publish to a vault, a PlantB vault must be configured and
related to that interface.