Understanding Setup of the Content Management System

The implementation of PeopleSoft Interaction hub Content Management requires the following initial setup steps:

1. Identify how to divide and manage responsibilities.

   Responsibilities are divided by privilege sets. Specific duties, such as adding folders and publishing content, are assigned to privilege sets on the Privilege Sets page. Privilege sets list the actions that a user can perform on a folder or the content that is located in that folder. When you're creating each content management folder, these privilege set definitions are associated with member roles and user IDs.

   Privilege sets are segregated by content management features, and each feature requires a top administrator to create its top folders. The user IDs on the Top Administrators page define who can create the top folders.

   Note: Oracle delivers a number of permission lists to support Content Management-related features. These features are discussed in detail in the PeopleTools: Portal Technology

   See Summary of Delivered Security Data.

2. Identify where document content can be stored.

   Administrators register Content Management storage locations on the Define File Storage page. You can store content on File Transfer Protocol (FTP) file servers or in database binary large objects (BLOBs). The choice of URLs is based on the information from the URL Maintenance page that is found in the PeopleTools > Utilities > Administration > URLs menu path.

   See File Storage Page.

   See PeopleTools: System and Server Administration, “Using PeopleTools Utilities,” Using Administration Utilities, URL Maintenance.

3. Identify where image attachments can be stored.

   PeopleSoft Interaction hub can upload, access, and render image files by way of an FTP service. To render image files as actual images, the FTP service must exist in a web server directory in the PeopleSoft domain.

   Note: The web server directory extension and the FTP service should be installed only on a single web server that is used by the PeopleSoft Interaction hub database. For clustered web servers, all image attachments are rendered and stored on a selected single web server.

See PeopleTools: Security Administration, "Understanding PeopleSoft Security."

See PeopleTools: System and Server Administration, "Using PeopleTools Utilities," Using Administration Utilities.

See PeopleTools: PeopleCode Developer's Guide, "Working With File Attachments," Using File Attachments in Applications, File Attachment Architecture.