In the live production environment, portal administrators and end-users create Communities based on the Community templates created in the Staging phase, and Community members with administrative rights manage Communities. Portal administrators can also modify visitor entitlements, delegated administration, content management types, configure cache for performance management, and other relevant tasks. If you are creating a GroupSpace Community, rather than a custom Community, you should configure the ActiveMenus tag in the Production phase. See Using Tag Libraries in Your Community for more information.
Portal administrators can also use the WebLogic Portal propagation tools to propagate Community templates and other portal data back to the staging environment for testing against production conditions.
This chapter includes the following sections:
As a portal administrator, you can create Communities with the WebLogic Portal Administration Console. In order for end users to create their own Communities, at least one Community must exist that includes the Community Tools. The Community Tools provide the menu that lets administrative Community members create new Communities.
You must create Communities in the production environment rather than in the staging environment, because the WebLogic Portal propagation tools do not propagate Community instances.
When a user creates a Community, that user automatically becomes the Community creator and owner with full management rights in the Community.
|Tip:||If you make a Community inactive when you create it, you or any Community member with administrative rights can test and configure the Community before you activate it. If your Community functionality depends on the presence of custom Community properties, also define those before activating a Community. (See Creating Custom Community Properties.)|
This section describes how to create a Community with the WebLogic Portal. The steps are similar if you create a Community using the Community tools inside of a Community.
One reason to create a Community with the WebLogic Portal Administration Console is to provide an initial Community that contains the Community tools, where end users can create their own Communities.
.portalfile created by your development team. If you use a
.portalfile, make sure it was designed to be used as a Community.
To view your new Community, you can also select it in the Portal Resources tree and click View Community.
To activate an inactive Community, which allows users to access the Community:
When you modify a template, new Communities created with that template take on the new template properties and characteristics. However, existing Communities that were created with the original template do not change. If you want the changes to apply to existing Communities, you must modify those Communities directly.
Communities should use a shell that contains the Visitor Tools.
After you have created a Community, you can modify its properties in the WebLogic Portal. After your modifications, the Community immediately uses the new settings.
Communities should use a shell that contains the Visitor Tools.
After you create a Community, you can add custom properties to it to uniquely identify the Community and its characteristics. Your developers can then develop programmatic functionality using those properties.
To create a custom Community property:
You can also modify or delete a custom property by clicking Edit or selecting the Delete check box and clicking Delete next to the property.
You can control administrative access to Community resources by assigning delegated administration roles to resources, the same way you do for portal desktop resources.
You can control end user access to Community resources by assigning visitor entitlement roles to resources, the same way you do for portal desktop resources.
|Note:||Be careful when setting entitlements on Community resources. Entitlements applied to components (books, pages and portlets) of the Community desktop at the definition level may result in some or all of the components not being visible to Community members.|
You can provide localized text for the title and description of your Communities. When you provide localized text, and a browser is set to use a language you provide, the localized title and description of that Community appear in that browser, either in the WebLogic Portal or in the Community itself. For example, in GroupSpace, localized titles appear in the GroupSpace header. For more information, see the GroupSpace Guide.
If you want to use double-byte characters, such as Chinese, make sure your system is configured to support this.
You can also use this feature to provide an alternative Community name and description in English, changing them as often as you like.
If you want to modify an existing title and description, such as changing the English text, click the language link and modify the title and description.
If you want to prevent users from accessing a Community, either deactivate or delete the Community. Deleting a Community permanently removes it from the database. Deactivating a Community lets administrators access it for configuration, archive, or reactivation in the future.
To deactivate an active Community, which prevents users from accessing the Community:
The callback class assigned to the Community determines what occurs when the Community is deactivated. For example, notifications can be sent to users when a Community is deactivated.
Deleting a Community permanently removes it from the database.
Perform the following steps to delete a Community:
If you belong to more than one GroupSpace Community, you can log in once and access Communities you have joined, Communities to which you are invited to join, and public Communities that anyone can join.
Perform the following steps to access the GroupSpace Communities to which you belong and view any invitations:
You can modify the capability rights of members or remove members from Communities in the WebLogic Portal.
Capabilities, such as creator, owner, contributor, and viewer, dictate the level of access members have to Community resources. You can change the capabilities of Community members. For example, to give a user administrative access to a Community, change the user’s capability to owner. The creator and owner capabilities are provided automatically in all Communities. Any additional capabilities are provided by your development team.
You can use the MemberPicker portlet that ships with WebLogic Portal in your non-GroupSpace Community. You can use the User Picker portlet outside of a Community, in a portal desktop. A Portal System Administrator has the ability to see all users in a portal desktop.
The following procedures show you how to manage members with the WebLogic Portal.
Removing a member does not delete the member from the user store—it only removes the member from the Community. On the Members tab, select the Remove check box next to the member you want to remove, and click Remove.
You cannot propagate a Community back to the Staging or Development phases. You can only propagate Community templates.
For information on deployment and propagation, see the Production Operations Guide.