File asset metadata is stored in the PublishingFilesRepository. Actual file assets—WWWFileSystem files, scenarios, targeters, segments, folders, and JSPs—are stored and versioned in a file system. The file system is located by default at:
<ATG2007.3dir>\home\Publishing\versionFileStore\PublishingFiles\fa100\
The fa100 directory contains one or more subdirectories named after integers. For example:
<ATG2007.3dir>\home\Publishing\versionFileStore\PublishingFiles\fa100\0
By default, the 0 directory contains a maximum of 1000 file assets and 30 versions of those assets. If the number of file assets exceeds 1000, a new directory called 1 is created, and so on.
Individual files are stored with a file asset ID that has the root fa100. The version number is appended. For example:
_cricket_0020fan_xproperties._fa100778#2
Note the following:
File metadata is stored in the
epub_file_assettable. If you need to examine any deployment issues with file assets, this table can help you determine which asset might be causing a problem. (File assets are referred to by their ID in deployment errors.)Folder assets are not visible in the file system.
Caution: Be sure to back up file asset directories up at the same time as the ATG Content Administration database. Conflicts between the file store and the database can cause serious errors.
Deleting File Assets from the File System
You should only delete file assets in the context of projects that you create in the ATG Business Control Center. For more information, refer to the ATG Content Administration Guide for Business Users.
Warning: Never move or delete file assets directly by manipulating the file system. Doing so can fatally compromise data integrity.
Changing File Asset Storage Location
The location of the file system used for file assets is determined by the pathPrefix attribute of the content property for the fileAsset item descriptor in the publishingFileRepository. To change the location, create a publishingFiles.xml file with a new pathPrefix attribute that overrides the default, and put the file in your CONFIGPATH.
For example:
<gsa-template>
<item-descriptor name="fileAsset">
<property name="content" xml-combine="append">
<attribute name="pathPrefix"
value="{atg.dynamo.server.home}/Publishing/myFiles"
xml-combine="replace"/>
</property>
</item-descriptor>
</gsa-template>The new location must be on the ATG Content Administration server.
