As an Administrator, you are responsible for creating top-level folders and defining the overall structure of the folder hierarchy. Many considerations go into deciding how to set up folders, but the most immediate has to do with assigning user roles. When you admit users to Publisher, you grant them permission to perform predetermined tasks by assigning roles, and you assign them roles by folder. For example, you can allow a user to access content in some folders but not others.
By default, when you create a content item within a folder in Publisher, the folder structure is mirrored in the destination Web server when the content item is published.
You can change the folder structure created on the Web server by editing the publishing targets of the folder. You can put the generated folder in a different location on the same server or in an entirely different server. You can also set the publishing target so that the folder hierarchy is not mapped to the Publisher hierarchy in the Web server, instead, the contents of the folder are flattened into a single folder in the Web server.
Publishing targets are available at all levels in the folder tree, including the root folder. At publication time, the destination of the generated file for an object is determined by the nearest ancestor, including the object in question, that has a publishing target set. You could have 10 first level folders all pointing to different Web servers.
For detailed information about setting up and securing the Publisher folder hierarchy, see the Administrator Guide for AquaLogic Interaction Publisher (available on edocs.bea.com).
Related Topics: