Posted on

Multiple ways to integrate content into Webcenter Portal

Ways to integrate content into a WebCenter Portal application using any of the following methods:

■ Content data controls. Use JCR adapters to enable read-only access to content in an Oracle Content Server, Oracle Portal, or SharePoint content repository, and
maintain tight control over the way the content displays in a WebCenter Portal application. This functionality is available primarily for backward compatibility
with prior releases, and for requirements outside the capability of Content Presenter or the Documents service and its task flows.

■ Content Management REST APIs. Use CMIS (Content Management Interoperability Services) REST APIs to surface and manage content in Oracle Content Server.

■ Content Presenter. Enables you to precisely customize the selection and presentation of content in a WebCenter Portal application. The Content Presenter
task flow is available only when the connected content repository is Oracle Content Server and your WebCenter administrator has completed the prerequisite configuration. With Content Presenter, you can select an Oracle Site Studio file, a single item of content, multiple content items, query for content, or select content based on the results of a WebCenter Personalization Conductor scenario, and then select a template to render the content on a page in a WebCenter Portal application. Content Presenter has no dependency on the Documents service for
adding or managing the content it displays.

■ Documents service. Provides several task flows that offer a variety of formats to display folders and files on a page. You can choose the task flows appropriate for
your application to provide features for accessing, adding, and managing folders and files; configuring and viewing file and folder properties; and searching file
and folder content in the connected content repositories. The Documents service task flows are available when the connected content repository is Oracle Content
Server, Oracle Portal, or SharePoint, and your WebCenter administrator has completed the prerequisite configuration. Using Documents service task flows and document components (such as links, previews, and images), you can both add content to the application, and provide end users with content and Documents service task flows built into the application to manage, display, and search documents at runtime. The Documents service also supports wikis and blogs.

Posted on

Adding Porlet into Webcenter Application

If you have portlets based on JSR 168 or JSR 286 and you want to add in webcenter 11g application.Oracle WebCenter Framework enables you to consume a portlet by registering its producer either with an application or with the Resource Palette from where you can add it to any application. After you register the producer, its portlets appear under the registered producer’s name under the Connections node in the Application Resources panel or in the Resource Palette.

For this you need to register WSRP portlet producer .If porlets JSR 168 is WSRP 2.0 enabled then it can be usable in webcenter 11g.

Register a WSRP portlet producer:

-> In the Application Resources panel of the Application Navigator, right-click Connections, choose New Connection and then choose WSRP Producer.
-> Use the Register WSRP Portlet Producer wizard , provide information and register .

Adding Portlets to a Page

Placing a portlet on a WebCenter Portal application page is a simple matter of dragging the portlet from the Application Resources panel or Resource Palette and dropping it on the page.
In the Application Navigator, open the application that contains the page (.jspx file) to which you want to add the portlet.
Under the Connections node in the Application Resources panel of the Application Navigator, or in the Resource Palette:
If the producer is a WSRP producer, expand the WSRP Producer node.
If the producer is a PDK-Java producer, expand the Oracle PDK-Java Producer node.

Expand the node for the portlet producer that contains the portlet to add to the page.Under the selected producer, all portlets contained by that producer are listed.
Drag the portlet from the producer node directly onto the page.You should drag the portlet onto a form on the page.

When you add a portlet to a page, a portlet tag (adfp:portlet or adfph:portlet) is added to the page source. This is the tag that represents the portlet component. This tag includes attributes that you can edit using the Property Inspector, or in the page source, to further control the behavior and appearance of the portlet.

The type of portlet tag used is determined by the following:

->If the project is configured for rich client components alone, the adfp:portlet tag is used.
->If the project is configured for Trinidad components alone, the adfph:portlet tag is used.

  <adfp:portlet value="#{bindings.FooterPortlet1_3}"
                            portletType="/oracle/adf/portlet/SamplePortlets_1257247466260/ap/E2default_ba133935_0124_1000_8008_0a093208e9fc"
                            id="portlet18" binding="#{backing_home.portlet18}"
                            displayHeader="false" width="100%"
                            renderPortletInIFrame="false"
                            displayScrollBar="false"/>

You can add the attributes by changing the source code or using property Inspector .