By default, the /atg/epub/file/PublishingFileRepository is configured to support file assets that are deployed to the following virtual file systems on a target site:
/atg/epub/file/ConfigFileSystem: ATG personalization assets such as scenarios and targeters./atg/epub/file/WWWFileSystem: static Web assets such as JSPs.
You extend the /atg/epub/file/PublishingFileRepository to support additional item types only if you require additional deployment destinations on a target site. If the asset destination is a Web application where you wish to deploy JSPs, refer to the previous section, Configure JSP File Asset Support. For all other asset destinations, follow the process described in this section.
You extend the PublishingFileRepository in the following steps:
Extend the PublishingFileRepository Definition to support new item types.
Extend the SecuredPublishingFileRepository Definition to support the new item types.
Configure a Custom VFS to Expose New Item Types in the content development environment.
Optionally, Configure TypeMapping Components for New Item Types to support file imports with the Repository Loader.
Customize the Business Control Center to Support New Item Types.
Note: The sections that follow illustrate each step with an example, where the PublishingFileRepository is extended to support a new VFS asset destination /mycompany/FtpFileSystem, which is located on a production machine that is running an FTP server.
