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:

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:

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.