Skip Headers
Oracle® Fusion Middleware Developer's Guide for Oracle WebCenter
11g Release 1 (11.1.1.5.0)

Part Number E10148-16
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

12 Adding Resources to Your Portal

When building up the content of your WebCenter Portal application, you can bring in content from various resources, including:

Adding content to your WebCenter Portal application is no different from adding content to any other web application.

This chapter includes the following sections:

12.1 Adding Pages to Your Portal

A portal is made up of pages that provide the structure of the portal and expose the content. If you create your portal using the WebCenter Portal Application template, a home page and several other pages are created for you. You can create your own pages to construct the rest of your portal.

For more information, see Section 5.2.2, "Adding Pages to the Portal."

After creating the pages, you can organize them into a page hierarchy to determine the structure of the pages. The page hierarchy also determines the security for those pages.

For more information, see Section 67.6, "Using the Page Hierarchy Security Editor."

If you want users to be able to edit pages at runtime, you can add Oracle Composer components to the pages.

For more information, see Chapter 19, "Enabling Runtime Editing of Pages Using Oracle Composer."

12.2 Adding Service Task Flows to Your Portal

WebCenter services enrich portals and web sites with enterprise 2.0 capabilities, including social computing services, personal productivity services, online awareness and communications, content integration, and web analytics. WebCenter services expose their functionality through task flows. For more information about WebCenter services and task flows, see Section 2.4, "Introducing Oracle WebCenter Services,"

If you create your portal using the WebCenter Portal Application template, all the appropriate WebCenter service connection wizards and tag libraries are readily visible and available in the New Gallery and Component Palette. When you consume a WebCenter service task flow or component, the necessary libraries are automatically added to the project. Depending on the service you plan to consume, your application must meet certain prerequisites. For example, if the service must know the identity of users, then your application must provide some level of security with user authentication. For more information, see Chapter 7, "Preparing Your Application for Oracle WebCenter Services."

For more information about the individual WebCenter services and their task flows, refer to Table 12-1.

12.3 Adding Custom Task Flows to Your Portal

Task flows, like pages, are containers in which you can add components such as portlets, content, and other task flows. You can add task flows to pages or other task flows. Task flows created in JDeveloper can be included in Resource Catalogs so that users can add them to pages or other task flows at runtime.

You can drag and drop a custom task flow into a Resource Catalog so that it is available to users to add to pages or task flows at runtime. For more information, see Section 15.2.3.7, "Dragging and Dropping a Resource into the Catalog." When you deploy the application, the task flow is also deployed to the target instance.

For detailed information about creating different types of ADF task flows, see "Creating ADF Task Flows" in Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework.

Exposing Task Flows Created in JDeveloper to a Deployed Application

If you created a custom task flow in JDeveloper and want to expose it in an already deployed application, you must deploy the project containing the task flow as an ADF shared library to the runtime application. Once the library containing the task flow is accessible to the application, it is displayed in the runtime Resource Registry and can be added to custom Resource Catalogs from there.

Note:

Permissions to view or edit a task flow are not provisioned by default when you create the task flow. To ensure that a task flow is visible at runtime, prior to deploying as a shared library, you must grant at least the View privilege on the task flow. For more details, see Section 23.6.1, "Granting Permissions on Task Flows."

For the steps to deploy an application to a WebCenter Portal application, see "Deploying the Application to a WebLogic Managed Server" in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter. However, while running the Install Application Assistant, on the Choose targeting style page, select Install this deployment as a library.

For the steps to deploy an application to a WebCenter Spaces instance, see Section 53.2.3, "Rebuilding the WebCenter Spaces Shared Library List."

12.4 Adding Content from Oracle Content Server to Your Portal

To provide access to the content in your Oracle Content Server content repository, you must create a connection to the Oracle Content Server. For more information, see Section 26.2.1, "How to Create a Content Repository Connection Based on the Oracle Content Server Adapter."

With a connection to Oracle Content Server established, you can use the Documents service, which includes task flows that provide a user-friendly interface to manage, display, and search documents at runtime. For more information, see Chapter 29, "Integrating the Documents Service."

Next, add one of the content task flows to your portal to expose the content from Oracle Content Server. Content task flows include Content Presenter and the Documents service task flows:

For more information about the Content Presenter task flow, see Section 30.1, "Understanding the Content Presenter Task Flow." For more information about the Documents service task flows, see Section 30.2, "Understanding the Documents Service Task Flows."

If you use the Content Presenter task flow, you may also want to create your own Content Presenter display templates. Content Presenter display templates define how content repository items should be rendered on a page. For more information, see Chapter 28, "Creating Content Presenter Display Templates."

12.5 Adding Portlets to Your Portal

A portlet is a reusable web component that can draw content from many different sources. Portlets provide a way of presenting data from multiple sources in a meaningful and related way. For more information about portlets, see Chapter 57, "Overview of Portlets."

To add a portlet to your portal, you must first register the portlet's producer with the WebCenter Portal application. For more information, see Section 63.2, "Registering Portlet Producers with a WebCenter Portal Application."

After you have registered the portlet producer, you can then simply drag and drop any portlets that you want to include in your portal onto the appropriate page. For more information, see Section 63.3, "Adding Portlets to a Page."

For information about how to create portlets, see Chapter 59, "Creating Portlets with the Portlet Wizard."

12.6 Adding Pagelets to Your Portal

A pagelet is similar to a portlet, but while portlets are designed specifically for portals, pagelets are designed to run on any web page.

For more information about adding pagelets to your portal, see Section 62.1, "Using Pagelets in Web Applications."

12.7 Adding External Applications to Your Portal

If the resources you add to your portal require access to applications that define their own authentication processes, you can add external applications to replicate a single sign-on experience for users.

For example, your portal might include portlets that point to applications that require a separate login. Or, if your portal includes the Mail service, you must identify an external application to map the mail server user to the portal user so that the user does not have to log in separately every time.

The first time a portal user accesses the external application, he or she is prompted for a user name and password for the application. These credentials are then mapped to the portal user and stored securely in a credential store. The credential store subsequently supplies these credentials during authentication to the external application. Unless the external application's credentials change, the user supplies the credentials only once as the mapped information is read from the credential store for future requests.

For more information, see Section 67.13, "Working with External Applications."

12.8 Adding Data Controls to Your Portal

Data controls are used to retrieve information from different data sources and create user interface (UI) components within your WebCenter Portal application. A data control provides you with easy-to-use methods that you can drag and drop onto JSF pages to publish content as ADF components, such as URLs, files, and folders. To add content from the data sources to JSF pages, you must first create connections to the data sources, then use the connections to create data controls based on the repositories.

You can create custom data controls to connect different data sources and add them to your application pages or task flows. For detailed information about data controls, see Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework.

Some WebCenter services provide data controls for creating customized visualizations of the services. For information about consuming these data controls in your application, see Section 7.1.3, "Using WebCenter Data Controls."

Exposing Data Controls for Consumption in an Already Deployed Application

The runtime Resource Registry in a WebCenter Portal application or WebCenter Spaces application contains a Design Time Data Controls folder by default. This folder exposes the seeded WebCenter services data controls and any other data controls that were added to the application before it was deployed. To expose a new data control in an already deployed WebCenter Portal or Spaces application, you must deploy the project containing the data control as an ADF shared library to the runtime application. Once the library containing the data control is accessible to the application, it is displayed in the runtime Resource Registry and can be added to custom Resource Catalogs from there.

For the steps to deploy an application to a WebCenter Portal application, see "Deploying Applications Using the WLS Administration Console" in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter. However, while running the Install Application Assistant, on the Choose targeting style page, select Install this deployment as a library.

For the steps to deploy an application to a WebCenter Spaces instance, see Section 53.2.3, "Rebuilding the WebCenter Spaces Shared Library List."