Portlet Development Guide

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Adding a Third-Party Portlet

This chapter discusses special-purpose portlets that are provided by WebLogic Portal partner companies that you can easily incorporate into your portal.

This chapter includes these sections:


Using the Collaboration Portlets

WebLogic Portal provides a set of portlets for adding collaborative features to your portal. You can use these collaboration portlets in any WebLogic Portal desktop.

Note: The Collaboration portlets will not operate correctly when desktop or portlet asynchronous mode is enabled. Async mode is not supported for Collaboration portlets. For information on portlet async mode, see Asynchronous Portlet Content Rendering. For information on desktop async mode, see the WebLogic Portal Portal Development Guide.

This section includes these topics:

What Are Collaboration Portlets?

WebLogic Portal provides the following collaboration portlets that you can use in any WebLogic Portal desktop.

Note: User portlets are portlets that store data on a per-user basis. Common area portlets store data in a common location that can be viewed by all users. The Calendar, Address Book, and Tasks portlets are user portlets by default. In some cases, you might want to reconfigure them to be common area portlets. For example, you might want to configure a corporate events calendar where all users see the same data. See Configuring Collaboration Portlets for a Shared View for details.
Tip: The collaboration portlets are also available for use in communities, such as a GroupSpace Community. For detailed information on creating communities, see the WebLogic Portal Communities Guide. A GroupSpace Community is a community created using the Workshop for WebLogic GroupSpace Template. For information on the WebLogic Portal GroupSpace Community, see the WebLogic Portal GroupSpace Guide. The instructions in this chapter are intended for use of the collaboration portlets outside of a groupspace enabled community.

Adding Collaboration Portlets To Your Portal

This section explains how to add collaboration portlets to your portal and configure them properly. The basic steps are:

Step 1. Add Collaboration Facets

You must add the appropriate facets to both the portal EAR projects and the portal Web projects in which the collaboration portlets will be used.

  1. Add the relevant collaboration portlet facets to your portal EAR project.
    1. In the Navigator view, right-click your portal EAR project and choose Properties.
    2. In the Properties view, select Project Facets, and click Add/Remove Project Facets.
    3. In the Add/Remove window, expand WebLogic Portal Collaboration and select both Collaboration Portlets Application Libraries and Collaboration API.
    4. Click Finish, then OK.
  2. Add the Collaboration Portlets facet to your portal web project.
    1. Perform the same sub-steps above, selecting the WebLogic Portal Collaboration > Collaboration Portlets facet.

After you add the collaboration portlet facets, collaboration portlets themselves must be configured properly, as explained in the following steps. After configuration, they are available to add to a portal desktop.

Step 2: Add Collaboration Repository to Your Domain

If you have not done so, you need to create or extend a domain to includes the Collaboration Repository components.

  1. If you have an existing server and it is running, stop the server.
  2. Start the Configuration Wizard. From the Windows Start menu, choose Oracle Products > WebLogic Server 10.x > Tools > Configuration Wizard.
  3. In the Configuration Wizard, select Create for a new domain or Extend for an existing domain, and click Next.
  4. If you selected Create in step 3 , select WebLogic Portal Collaboration Repository check box and click Next. If you are extending an existing domain, select the domain root directory, and click Next.
  5. Complete the remaining wizard windows.
  6. Restart the server.

Step 3: Create a Role for Collaboration Portlet Users

Users of the collaboration portlets must be entitled to use the repository in which collaboration data is stored. This section explains how to create an new user role.

  1. Start the WebLogic Portal Administration Console and log in.
  2. Create a new enterprise application-scoped visitor entitlement. To do this, select Users, Groups, & Roles > Visitor Entitlement > Browse Roles.
  3. Set the role scope. In the Browse Roles from panel, click Update to bring up the Update Role Scope dialog. In the dialog, select Enterprise Application Scope, and click Update.
  4. Select Visitor Roles > Browse Roles > Create New Role. Enter a name for the new role and save it.

Step 4. (Optional) Configure a Repository

Data generated by collaboration portlets is stored in a content repository. By default, collaboration portlets are configured to store data in the repository subfolder /Communities_Repository/Collaboration.

If you wish, you can use any WLP content repository for storing collaboration portlet data. Note that library services must be disabled for the repository. Collaboration portlet data is not supported for third party repositories, such as Documentum repositories. See the Content Management Guide for detailed information on content repositories. It is a good practice to create a subfolder in the repository in which to store the data, as explained in this section.

Tip: A general best practice is to create a custom repository for collaboration data. See Configuring Additional WLP Repositories in the Content Management Guide for details.

To create a subfolder in which to store collaboration portlet data, do the following:

  1. Select Content > Content Management. In the Repository View, select your repository.
  2. Click Add Folder and add a new folder to the repository of your choice.

In a later step, you will configure individual collaboration portlets to point to the repository folder of your choice, which is an option if the default location is not desirable.

Step 5. Entitle the Collaboration Data Repository

You must properly entitle the repository folder in which collaboration portlet data will be stored. Only entitled users can use the collaboration portlets.

  1. Select the subfolder you created or targeted to store collaboration data.
  2. Select the Entitlements tab for the subfolder.
  3. Click Add Role and add the new user role you created for the collaboration portlets. Entitle the role with the capabilities Create, View, Update, and Delete.

Step 6. Add Users to the New Role

You must add any users who will use the collaboration portlets to the new role. Select the role and click Add Users to Role. Use the dialog to add users to the role.

Tip: Be sure to add any new users to the role if you want them to use the collaboration portlets. To create new users, select Users, Groups, & Roles > User Management. After you create a new user, add it to the role.

Step 7. Configure the Collaboration Portlets

Configure the collaboration portlets so that they are aware of the repository that you configured. To do this, you edit certain portlet preferences.

  1. Select Portal > Portal Management.
  2. Expand the Portal Resources > Library > Portlets folder.
  3. For each collaboration portlet that you wish to use, do the following:
    1. Select a portlet to configure. For example, click Discussion to configure the Discussion portlet.
    2. Click Portlet Preferences.
    3. Edit collaboration.personal_repository.path and set its value to the designated collaboration data folder in your repository. For example, if you created a folder named MyCollaborationData in the repository called MyCollaborationRepository, set the value to: /MyCollaborationRepository/MyCollaborationData.
    4. Edit collaboration.personal_repository.name and set its value to the name of the repository you are using for collaboration data. For example, if you are using a repository called MyCollaborationRepository, set the value to MyCollaborationRepository.

Step 8. Add Collaboration Portlets to Your Desktop

Now that you have configured your collaboration portlets, you can add them to a desktop.

Note: Collaboration portlets only work if the user is authenticated. Your desktop must include a login portlet. For more information on authentication, see the Security Guide.

If you configured everything properly, authorized users can access the collaboration portlets after logging in. Folders will be created in the collaboration repository as they are needed. For example, Figure 11-1 shows the repository structure for an example discussion forum on beekeeping.

Figure 11-1 Repository Structure for a Discussion Forum

Repository Structure for a Discussion Forum

Configuring Collaboration Portlets for a Shared View

This section explains how to reconfigure user portlets to be common area portlets. User portlets restrict the portlet’s data to individual users, while common area portlets allow entitled users to share a the same view of the portlet’s data.

Overview of User and Common Area Portlets

Collaboration portlets fall into two categories: common area portlets and user portlets: Typically, common area portlets are recommended for use cases where all users need to share the same view of the portlet’s data. For example, you could create a calendar that displays corporate events to all users. In this case, you would need to configure the Calendar portlet (which is a user portlet by default) to be a common area portlet.

Configuring a Common Area Portlet

This section explains how to reconfigure user portlets to be common area portlets. Note that by default, the Calendar, Address Book, Tasks, and Mail portlets are user portlets.

Tip: Because mail is usually intended to be used by specific users rather than shared among many users, it is typically not necessary to reconfigure the Mail portlet to be a common area portlet.
  1. Copy the portlets you want to configure to your local project. To do this:
    1. Open the Merged Projects View in Workshop for WebLogic. (To open the Merged Projects view, select Window > Show View > Merged Projects.)
    2. Right-click each portlet (located in the portlets/collaboration folder) and select Copy to Project. See Portlets in J2EE Shared Libraries for information on the Copy to Project feature.
  2. Rename each copied portlet. For example, change Tasks.portlet to Tasks-Team.portlet.
  3. In a text editor, open each .portlet file and change the definition label and title. For example:
  4. Before:

    <netuix:portlet definitionLabel="task" title="My Task"


    <netuix:portlet definitionLabel="task_team" title="Team Task"

  5. Also in the text editor, for each portlet, change the <netuix:meta> tag containing the AccountListenerImpl to use the CmAccountListener instead of the PersonalAccountListener. For example:
  6. Before:

    <netuix:meta name="collaboration.portlet.AccountListenerImpl"


    <netuix:meta name="collaboration.portlet.AccountListenerImpl"

  7. Save each .portlet file.

Using the Collaboration Portlets

For detailed information on how to use the collaboration portlets, see the “Using the GroupSpace Portlets” chapter of the WebLogic Portal GroupSpace Guide. All of the collaboration portlets listed previously in this section are described in that chapter.

Using the Collaboration Portlet Source Code

Source code for the collaboration portlets is available to WebLogic Portal developers, as explained in this section.

Copying the Source Code to Your Project

To use the source code, you must first copy it from a J2EE Shared Library to your workspace.

Source code for the collaboration portlets is located in the J2EE Shared Library wlp-collab-portlets-web-lib. To use this source code, you need to copy it from the shared library to your project workspace. See Portlets in J2EE Shared Libraries for information on the Copy to Project feature.

Java source code for the collaboration portlets is copied to WEB-INF/src/portlets. Javadoc for the collaboration portlet code is copied to WEB-INF/src/javadoc.zip.

Source Code Disclaimers

If you modify any of the source code for the collaboration portlets, be aware of the following disclaimers:


Third-Party Portlets

WebLogic Portal partner companies create special-purpose portlets that you can easily incorporate into your portal; these companies include Autonomy, Documentum, and MobileAware.

The following sections provide more information about third-party portlets:

Autonomy Portlets

WebLogic Portal includes an embedded license of Autonomy-based search capabilities. You can use these capabilities to integrate enterprise-class search into your portal; common use cases include integration with content management systems, relational databases, and external web sites. You can expose these sources of information for searches using portlets that some with WebLogic Portal, and developers can use Autonomy APIs as they author new portlets and business logic for integrating search into your portal as well.

In WebLogic Portal 9.2, the proprietary search APIs were deprecated; we recommend that you use Autonomy APIs to implement search capabilities.

For more information about Autonomy, see Integrating Search.

Documentum Portlets

EMC Documentum has partnered with Oracle to offer EMC Documentum Content Services for Oracle Weblogic Portal. This product provides a packaged set of Documentum functionality exposed through the Oracle WebLogic Portal infrastructure, allowing users to access and interact with all types of enterprise content including web pages, documents, and rich media such as audio and video.

From a portlet development perspective, a key feature of this product is the inclusion of Documentum portlets—application components that expose standardized, enhanced content management user functions through the portal interface.

Documentum portlets expose four key applications:

See the Documentum web site for more information on Documentum portlets for WebLogic Portal

MobileAware Portlets

Oracle Communication and Mobility Server provides a standards-based, non-proprietary environment that extends Oracle WebLogic deployments to offer multichannel mobile services in significantly reduced time frames. Enterprises can broaden the effectiveness of business-critical systems for employees and customers, and mobile carriers can rapidly deploy new, data-centric services, without the need for re-training and re-tooling.

For more information about Oracle Communication and Mobility Server and how to use it with WebLogic Portal, see the product documentation on the e-docs web site.

  Back to Top       Previous  Next