31 Integrating Wikis and Blogs

31.3.1 What You Should Know About the Document Explorer Task Flow

To provide your application users with the ability to add and manage wiki documents at runtime, you need to add the Document Explorer task flow to your 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 30.7.2, "Document Explorer Task Flow Parameters."

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

To prepare your 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 31.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 Content Server.

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

   For information, see Section 7.2.1.1, "Implementing Security for Services."

2. Create or open the JSF page in which you want to provide the wiki functionality (see Section 5.3, "Adding Pages to a Portal").

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 30.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 30.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 30.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 31-1. Application users can create a wiki document by clicking New Wiki Document.

   Figure 31-1 Creating a New Wiki Document

   
   

31.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 service task flow. For information, see Section 30.6, "Modifying Content Task Flow Parameters." For information about the specific parameters that you can modify, see Section 30.7.2, "Document Explorer Task Flow Parameters."

31.3.4 What Happens at Runtime

At runtime, an authenticated user can create wiki documents in a 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. Application users can create a wiki document by clicking New Wiki Document (Figure 31-4), which opens the Rich Text Editor (RTE) (Figure 31-3), displaying a blank wiki document.

Figure 31-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 31-3).

Figure 31-3 Rich Text Editor Displaying New Wiki Document

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

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

At runtime, users can also choose to display a wiki document using Content Presenter.

The runtime procedures for adding and managing wiki documents in a Framework application are the same as those in a space in WebCenter Portal: Spaces. For generic information, refer to the chapter "Working with Wiki Documents" in Oracle Fusion Middleware User's Guide for Oracle WebCenter Portal: Spaces.

31.3.5 Displaying Wiki Page Links Within Content Presenter

At runtime, 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 such links within Content Presenter.

To open the links present in a wiki document within Content Presenter:

1. Open the adf-config.xml file. This file is located under Descriptors/ADF META-INF in 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.

31.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 31-1 lists and describes the blog task flows:

31.4.2 Adding a Blog to a Page

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

1. Ensure that you have completed the requirements listed in Section 31.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 Content Server.

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

   For information, see Section 7.2.1.1, "Implementing Security for Services."

2. Create or open a page in your application where you want to expose the blog functionality (see Section 5.3, "Adding Pages to a Portal").

3. Before you add a blog task flow to your page, consider whether or not you want to allow your application users to edit the task flow. To enable runtime editing of the page, see Chapter 19, "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 individual blog task flows:

   • Section 31.4.2.1, "Adding a Default Blog Using an Existing Folder"

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

31.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 31.4.2.1, "Adding a Default 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 31.4.2.2, "Adding a Custom Blog to a Page Using the Blog Task Flows," then the name of the folder that you specify 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 you specify in the Title parameter of the Blog Banner task flow.

In a Framework application, any authenticated user can create blog posts, and the posts are displayed on the blog page. Users can perform tasks such as edit, download, comment on blog posts, and so on.

On the default blog page (Figure 31-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 31-8 A Default Blog Page

Description of "Figure 31-8 A Default Blog Page"

A blog displays various details for each blog post. These include the profile photo of the user who added the blog post, the blog post title, the 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 31-9), providing controls to manage the blog post.

Figure 31-9 A Blog Post

Description of "Figure 31-9 A Blog Post"

When public users (not logged in) view a blog post in a WebCenter 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 68-2, "Automated Security Grants for WebCenter Portal Services"). Your system administrator can use the grantPermission WLST command (see "grantPermission" in Oracle Containers for J2EE Security Guide) 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 Framework application are the same as those for managing blogs in a space in WebCenter Portal: Spaces. For information, see the "Working with Blogs" chapter in Oracle Fusion Middleware User's Guide for Oracle WebCenter Portal: Spaces.

31.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 service task flow. For information, see Section 30.6, "Modifying Content Task Flow Parameters." For information about the parameters that you can modify, see Section 31.4.5, "Blog Task Flow Parameters."

31.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 31.4.5.1, "Blog Archives Task Flow Parameters"

• Section 31.4.5.2, "Blog Banner Task Flow Parameters"

• Section 31.4.5.3, "Blog Digest Task Flow Parameters"

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

• Section 31.4.5.5, "Blogs Task Flow Parameters"