Because different ATG Content Administration clusters can deploy to the same VFS repository, it is possible for file system assets on these clusters to share the same paths and names. Using cluster identifiers, deployment agents on the target site can keep track of deployed file ownership; this enables them to differentiate between files from different clusters whose paths are otherwise identical.

In order to enable deployment of files assets from multiple ATG Content Administration clusters, you must configure a target site in two ways:

Enable Tracking of File Ownership

In order to enable file ownership in a virtual file system, ownerCacheEnabled must be set to true in the target site’s VFS configuration. Depending on your configuration, this property is set in one or more of the following VFS configuration files:

Note: In all configuration properties files, uncomment the ownerCacheEnabled property.

When ownerCacheEnabled is set to true, the target site deployment agent caches file ownership data. For online deployment, the owner cache file path is explicitly set in the VFS configuration’s property ownerCacheDataFile. For switch deployments, SwitchableLocalFileSystem components do not have this property; instead, they write the owner cache data to the following locations:

The owner cache contents can help answer deployment questions related to file ownership. The following example shows a fragment from the owner cache file for the WWWFileSystem component. It shows three files that are stored in the local WWWFileSystem and their path. The cache file also identifies each file’s cluster owner as CA1 or CA2.:


Given these file owners, an attempt by cluster CA1 to deploy About_Us\execProfiles.txt triggers an ownership conflict, which is resolved according to the ownerStrategy that is configured for the target site (see below).

Set a Strategy for Handling Ownership Conflicts

You can choose one of several strategies to handle potential file conflicts during deployment, by setting three properties on the target component /atg/deployment/file/DeploymentConfiguration:

ownerStrategy controls how to handle file ownership conflicts. You can set this property to one of the following values:

ownerStrategy setting



On any file conflict, throw an error and stop deployment. This setting is appropriate when you wish to exercise complete manual oversight over all possible file ownership conflicts.


Give precedence to one cluster over all others in the event of a conflict. If you use this setting, you must specify the cluster by also setting ownerSpecificWinnerId. Attempts by other clusters to deploy this file are ignored and yield a warning if ownerWarning is true.

This setting is appropriate for automating ownership conflict resolution.


Use the most recent file, regardless of its owner. The overwritten file is owned by the latest deploying cluster. If ownerWarning is true, changes to file ownership yield a warning.


Allow deployment of a file only from its latest cluster owner. Attempts by other clusters to deploy this file are ignored and yield a warning if ownerWarning is true.

Attempts to deploy conflicting file assets are ignored unless you set ownerStrategy to RESOLVE_ERROR, where all file deployments fail in the event of any conflict, or RESOLVE_CLOBBER, where all deployments succeed. RESOLVE_ERROR and RESOLVE_SPECIFIC provide the greatest levels of control for resolving file ownership conflicts.

ownerSpecificWinnerId specifies the identifier of the cluster to take precedence if ownerStrategy is set to RESOLVE_SPECIFIC. If ownerStrategy is set to another value, this property is ignored.

Set this property to the same string value used to Set the Cluster Name property clusterName.

ownerWarning specifies whether to print warnings on ownership conflicts to the deployment agent. The default setting is true.