| Oracle® Fusion Middleware Communities Guide for Oracle WebLogic Portal 10g Release 3 (10.3.4) Part Number E14232-02 |
|
|
View PDF |
| Oracle® Fusion Middleware Communities Guide for Oracle WebLogic Portal 10g Release 3 (10.3.4) Part Number E14232-02 |
|
|
View PDF |
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.
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:
Section 7.5, "Setting Delegated Administration Rights on Community Resources"
Section 7.6, "Setting Visitor Entitlements on Community Resources"
Section 7.7, "Creating Localized Community Titles and Descriptions"
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.
Note:
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 Section 7.4, "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.
In the WebLogic Portal, choose Portal > Portal Management.
In the Portal Resources tree, verify that the correct web application is selected. If it is not, click Update WebApp and select the web application you want.
Create a portal if you did not already create one.
In the Portal Resources tree, expand the Portals directory, expand the portal you created, and select the Communities directory.
In the Browse tab, click Create Community. The Create Community wizard appears.
In Step 1 of 5 in the wizard, select the source for your template and click Next.
Use a Community Template – Lets you select an existing Community template to create the Community.
Select resources in the Library – Lets you create a Community using an existing book (or a book you create yourself), an existing shell, and an existing look and feel in the portal Library. Make sure the resources you select were designed to be used in a Community. For example, the shell should contain the Community Tools. See the Oracle Fusion Middleware Portal Development Guide for Oracle WebLogic Portal for more information on library resources and .portal files.
Select a .community or .portal file – Lets you create a Community using an existing .community or .portal file created by your development team. If you use a .portal file, make sure it was designed to be used as a Community.
In Step 2 of 5, click Search or Show all to display the available choices. Select the appropriate resource and click Next.
In Step 3 of 5, enter the following and click Create Community.
Title - The title that appears for the Community in the user interface.
Description - The description that appears when the Community is selected.
Partial URL - The text that serves as the end of the URL for the Community.
Select and enter the remaining properties for the Community, as described in "Community Properties Reference" in the Setting up Community Infrastructure chapter.
You can also click Review Properties to review what you entered.
If you clicked Review Properties in Step 8, review the information and click Create Community. You can also enter the following information:
Set the date that the Community should expire. If you do not want the Community to expire, leave the field blank.
Select the Make this community active now option to make the Community available immediately. If you want to configure and test the Community before making it active, deselect this option.
In Step 5 of 5, click Go to community to view it and then click Finish.
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:
In the Portal Resources tree, select the Community you want to activate by expanding the Portals directory, selecting your Portal's directory, selecting the Communities directory, and selecting your Community.
On the Summary tab, click Status & Expiration.
In the Status & Expiration dialog, select Active from the Status drop-down field and click Update.
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.
In the Portal Resources tree, expand the Portals directory, your portal's directory, the Templates directory, the Community Templates directory, and select your template.
On the Details tab, click any of the links or buttons to modify the template. Refer to the Community Properties Reference section in the Chapter 6, "Setting Up Community Infrastructure" chapter for details.
To delete a Community template, expand the Portals directory, select your Portal's directory, the Templates directory, and select the Community Templates directory. Select the Delete check box next to the template and click Delete. Communities that were based on that template are not affected.
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.
In the Portal Resources tree, expand the Portals directory, select your Portal's directory, select the Communities directory, and select your Community.
On the Summary tab, click any of the links or buttons to modify a property. See Section 6.2, "Community Properties Reference" and Section 7.9, "Managing Community Members" for more information.
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:
In the Portal Resources tree, expand the Portals directory, select your Portal's directory, select the Communities directory, and select your Community.
Select the Custom Properties tab.
Click Add Property.
In the Create Custom Property dialog, enter the property name and value. To add more than one value, click Add Another Value.
Click Save.
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.
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.
In the Portal Resources tree, expand the Portals directory, select your Portal's directory, select the Communities directory, and select your Community.
Select the Title & Description tab and click Add Localized Title.
In the Add a Localized Title & Description dialog, enter:
Language (required) – The two-letter code for the language. For example, zh for Chinese.
Country (optional) – The name of the country.
Variant (optional) – The two-letter language variant in uppercase, such as US for the United States English, or TW for Taiwan Chinese.
Title (required) – The localized title you want to provide.
Description (optional) – The localized description you want to provide.
Click Create.
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:
In the Portal Resources tree, select the Community you want to deactivate.
On the Summary page, click Status & Expiration.
In the Status & Expiration dialog, select Inactive and click Update. Or if you want to deactivate the Community on a specific date, select Active, set the Expiration Date for when it should automatically be deactivated, and click Update.
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:
In the Portal Resources tree, expand the Portals directory, select your Portal's directory, and select the Communities directory.
On the Browse tab, select the Delete check box next to the Community name.
Click Delete.
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 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.
In the Portal Resources tree, expand the Portals directory, select your Portal's directory, the Communities directory, and select your Community.
Select the Members tab.
Click Edit next to the user whose capabilities you want to change.
In the Membership Details dialog, select the capability you want, and click Save.
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 Oracle Fusion Middleware Production Operations Guide for Oracle WebLogic Portal.
|
 Copyright © 2010, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
