To make My Content portlet available for administrators to create and manage content, you much perform the following tasks:
Before you begin this process, it is assumed that you already have a portal application with a portal project (web application) that it is running on a WebLogic Server. For more information on creating a portal application, see Creating a Portal Application and Portal Web Project.
Import or copy this | to this directory (create if necessary) |
<WEBLOGIC_HOME>\samples\portal\portalApp\ sampleportal\portlets\content\ |
<PORTAL_APP>\<project>\portlets\ |
Note: The My Content portlet requires that users be logged in to determine the rights each user has on certain content. Consider importing the “Login to Portal” portlet as well. To do this, import the folder “login” and the file “includes/Login.portlet” from the same location as the “content” folder above.
Note: Only the BEA Repository is visible until you add content.
You can set up user access to the My Content Portlet two ways:
Delegated Administration provides a way for WebLogic Administration Portal to propagate privileges down a hierarchy of roles. A Delegated Administration role is a dynamic classification of users based on user name, group membership or by the user's characteristics (or expressions), such as user profile values or time.
The rights you set up in the Administration Portal determine the content users can see and manage in My Content Portlet. Users must be in the PortalSystemAdministrators group to manage content with My Content portlet, and you can set this up two ways:
To set up Delegated Administration Rights for content in the Administration Portal you will follow this general process:
A portlet preference is a property in a portlet that can be customized by either an administrator or a user. The My Content Portlet provides you with a way to grant users access to content by using a special Portlet Preference called cm_homefolders. You can modify values of the cm_homefolders Portlet Preference using either the Administration Portal or WebLogic Workshop.
For example, your company provides each employee with his or her own private space for content on the corporate network. If you’ve got 10,000 employees, setting up Delegated Administration rights on each of those 10,000 folders individually would be very time consuming. The cm_homefolders Portlet Preference provides a way to quickly grant rights to content based on string substitution of users’ username, group names, or role names.
If each user’s private content area is represented by a folder that matches their username:
Corporate Repository
Employees
…jan_hjane_djoe_pjohn_d…
To grant each user access to their folder, you add a value to the cm_homefolders Portlet Preference like /Corporate Repository/Employees/%username%. Now when jan_h logs in, she will have access to /Corporate Repository/Employees/jan_h and when joe_p logs in he will have access to /Corporate Repository/Employees/joe_p.
The My Content portlet supports three primary types of string substitution variables:
The %username% variable can be used to provide individual users access to the appropriate part of the content directory. The access is granted by adding %username% to a path in a repository. For example, /BEA Repository/%username%. If BEA Repository contains immediate children named Bob and Jane, the user named Jane would have access to /BEA Repository/Jane and its children while the user Bob would have access to /BEA Repository/Bob and its children.
Note: Users and groups are scoped to the users and groups that are set up in the Administration Portal. Roles are scoped to visitor entitlements.
You can set up portlet preferences in the Administration Portal or you can start the process in the Administration Portal and finish it in WebLogic Workshop.
Use the following instructions to set up portlet preferences:
For more information about portlet preferences in the Administration Portal, see Creating Portlet Preferences.