30 Integrating Wikis and Blogs

30.3.1 About Integrating Wikis

To provide your end users with the ability to add and manage wiki documents at runtime, you need to add the Document Explorer task flow to your Portal Framework application. When you add this task flow at design time, it is built into the application for end users, and enables them to work with wiki documents at runtime.

The Document Explorer task flow has associated parameters. For information, see Section 29.7.2, "Document Explorer Task Flow Parameters."

30.3.2 Adding the Document Explorer Task Flow to Provide the Wiki Functionality

To prepare your Portal Framework application and add the Document Explorer task flow for enabling the wiki functionality:

1. Ensure that you have completed the requirements listed in Section 30.2, "Requirements for Wikis and Blogs."

   Note:

   While setting up the connection, you must choose an authentication method. If you choose identity propagation, you must implement ADF security in your application and configure secure socket layer (SSL) on WebCenter Content.

   If you choose external application, you must specify the external application you want to use for authenticating users to WebCenter Content.

   For information, see Section 4.2.1.1, "Implementing Security for Tools and Services."

2. Create or open the JSF page on which you want to provide the wiki functionality (see Section 15.2, "Creating Pages in a WebCenter Portal Framework Application").

3. Choose a method for adding the Document Explorer task flow to the page:

   • To add the Document Explorer task flow prepopulated with a selected folder or file, see Section 29.4, "Adding a Selected Folder or File to a Page."

   • To add the Document Explorer task flow standalone as an "empty" task flow that you can populate using the task flow menus and actions, see Section 29.5, "Adding a Content Task Flow to a Page."

   For information about the parameters that you can set for the Document Explorer task flow, see Section 29.7.2, "Document Explorer Task Flow Parameters."

   When you run the page, the Document Explorer task flow displays in your default browser, as shown in Figure 30-1. End users can create a wiki document by clicking New Wiki Document. For more information, see Section 30.3.4, "What Happens at Runtime."

   Figure 30-1 Creating a New Wiki Document

   
   Description of ''Figure 30-1 Creating a New Wiki Document''
   
   

30.3.3 Modifying Document Explorer Task Flow Parameters

The way you modify parameters of a Document Explorer task flow is the same as any other documents task flow. For information, see Section 29.6, "Modifying Content Task Flow Parameters." For information about the specific parameters that you can modify, see Section 29.7.2, "Document Explorer Task Flow Parameters."

30.3.4 What Happens at Runtime

At runtime, authorized users can create wiki documents in a Portal Framework application in which the wiki functionality has been exposed. Users can also edit, download, rename, share, and subscribe to a wiki document and view its history and properties.

At runtime, the folder that you exposed through the Document Explorer task flow is shown as the root folder. End users can create a wiki document by clicking New Wiki Document (Figure 30-2), which opens the Rich Text Editor (RTE) (Figure 30-3), displaying a blank wiki document.

Figure 30-2 Creating a New Wiki Document

Description of ''Figure 30-2 Creating a New Wiki Document''

Users can add and edit wiki content using the Rich Text Editor (RTE), which is a fully-integrated HTML text editor (Figure 30-3).

Figure 30-3 Rich Text Editor Displaying New Wiki Document

Description of ''Figure 30-3 Rich Text Editor Displaying New Wiki Document''

By default, all wiki documents are created directly under the root folder (Figure 30-4).

Figure 30-4 Wiki Document Created Using New Wiki Document Action

Description of ''Figure 30-4 Wiki Document Created Using New Wiki Document Action''

The runtime procedures for adding and managing wiki documents in a Portal Framework application are the same as those in WebCenter Portal. For generic information, refer to the "Working with Wikis" chapter in Using Oracle WebCenter Portal.

30.3.5 Displaying Wiki Page Links Within Content Presenter

At runtime, users can choose to display an existing wiki document using Content Presenter, as described in the "Adding a Selected Folder or File to a Page" section in Building Portals with Oracle WebCenter Portal.

When a wiki document is displayed using a Content Presenter display template, by default the links present in the wiki document render in the Document Viewer. You can configure your application to display link targets within Content Presenter.

To open the targets of links present in a wiki document within Content Presenter rather than the Document Viewer:

1. Open the adf-config.xml file. This file is located under Descriptors/ADF META-INF in the Application Resources section of the Application Navigator.

2. Update the Namespace entry as follows:

   xmlns:wpsC="http://xmlns.oracle.com/webcenter/framework/service" 
   

3. Update the ResourceActionHandler entry as follows:

   <wpsC:adf-service-config
   xmlns="http://xmlns.oracle.com/webcenter/framework/service">
         <resource-handler
   class="oracle.webcenter.portalframework.sitestructure.handler.NavigationResourceActionHandler"/>
   </wpsC:adf-service-config>
   

4. Save adf-config.xml.

30.4.1 Understanding the Blog Task Flows

If you want to include a blog on a page, along with other page components, you can use the blog task flows to add one or more elements of a blog to a page. Table 30-1 lists and describes the blog task flows:

30.4.2 Adding a Blog to a Page

To add a blog to a page in your Portal Framework application:

1. Ensure that you have completed the requirements listed in Section 30.2, "Requirements for Wikis and Blogs."

   Note:

   While setting up the connection, you must choose an authentication method. If you choose identity propagation, you must implement ADF security in your application and configure secure socket layer (SSL) on WebCenter Content.

   If you choose external application, you must specify the external application you want to use for authenticating users to WebCenter Content.

   For information, see Chapter 4, "Implementing Security for Tools and Services."

2. Create or open a page in your application where you want to expose the blog functionality (see Section 15.2, "Creating Pages in a WebCenter Portal Framework Application").

3. Before you add a blog task flow to your page, consider whether or not you want to allow your end users to edit the task flow. To enable runtime editing of the page, see Chapter 18, "Enabling Runtime Editing of Pages Using Composer."

4. Add a blog to the page using an existing folder to create a default blog page, or by creating a custom blog by selecting component blog task flows:

   • Section 30.4.2.1, "Adding a Blog Using an Existing Folder"

   • Section 30.4.2.2, "Adding a Custom Blog to a Page Using the Blog Task Flows"

30.4.3 What Happens at Runtime

At runtime, the folder specified by the resourceID parameter for the blog task flow is exposed as a blog on the page:

• If you created a blog as described in Section 30.4.2.1, "Adding a Blog Using an Existing Folder," then the name of the folder that you exposed as a blog is displayed as the name of your blog in the blog banner.

• If you created a blog as described in Section 30.4.2.2, "Adding a Custom Blog to a Page Using the Blog Task Flows," then the name of the folder that you specified in the resourceID parameter of the blog task flow is the name of your blog internally; however, the name visible on the page is the value that you specified in the Title parameter of the Blog Banner task flow.

Authorized users can create blog posts, and the posts are displayed on the blog page. Users can perform tasks such as edit, download, comment upon blog posts, and so on.

On the default blog page (Figure 30-8), and in the Blog Archives task flow, the Archives section provides links to blog posts by year and by month. Clicking a month displays all blog posts created during that month.

Figure 30-8 A Default Blog Page

Description of ''Figure 30-8 A Default Blog Page''

A blog displays various details for each blog post. These include the blog post title, the blog post content, date of creation or modification, name of the user who created or last modified the post, and the number of comments on the blog post. Authorized users can click the Edit Post icon to edit a post, and click the Post comments link to enter comments on a blog post.

Clicking a blog post title opens the blog post to occupy the entire the blog page (Figure 30-9), providing controls to manage the blog post.

Figure 30-9 A Blog Post

Description of ''Figure 30-9 A Blog Post''

When public users (not logged in) view a blog post in a Portal Framework application, they will not see the profile photos associated with each blog post because the anonymous-role that is assigned to public users is not granted permission to view profiles by default (see Table 74-2, "Automated Security Grants for Portal Framework Applications"). Your system administrator can use the grantPermission WLST command (see the "grantPermission" section in the WebLogic Scripting Tool Command Reference) to allow public users to view profile photos for blog posters. For example:

grantPermission(appStripe=<app-name>, 
  principalClass="oracle.security.jps.internal.core.principals.JpsAnonymousRoleI mpl", 
  principalName="anonymous-role",
  permClass="oracle.webcenter.peopleconnections.profile.security.ProfilePermission", 
  permTarget="/oracle/webcenter/peopleconnections/profile/s8bba98ff_4cbb_40b8_beee_296c916a23ed/.*", 
  permActions="view")

The procedures for managing blogs at runtime in a Portal Framework application are the same as those for managing blogs in WebCenter Portal. For information, see the "Working with Blogs" chapter in Using Oracle WebCenter Portal.

30.4.4 Modifying Blog Task Flow Parameters

The procedure for modifying the parameters of a Blogs task flow is the same as any other documents task flow. For information, see Section 29.6, "Modifying Content Task Flow Parameters." For information about the specific parameters that you can modify, see Section 30.4.5, "Blog Task Flow Parameters."

30.4.5 Blog Task Flow Parameters

Each blog task flow has its own set of parameters. You can configure these values when you add the task flow to your page, or modify the values at any time.

The following sections describe the parameters for the blog task flows:

• Section 30.4.5.1, "Blog Archives Task Flow Parameters"

• Section 30.4.5.2, "Blog Banner Task Flow Parameters"

• Section 30.4.5.3, "Blog Digest Task Flow Parameters"

• Section 30.4.5.4, "Blog Recent Posts Task Flow Parameters"

• Section 30.4.5.5, "Blogs Task Flow Parameters"