Deploying Portlet Producer Applications Using Fusion Middleware Control

24-2 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter ■ Resources are web applications registered with the Pagelet Producer. Registering a resource allows the proxy to map internal applications to external URLs, manage authentication, and transform applications. Registering a web application as a Pagelet Producer resource allows you to do the following: ■ Proxy internal web applications to external addresses. ■ Manage authentication, both at the proxy level and at the resource level. ■ Transform proxied web applications, including URL rewriting. ■ Pagelets are sub-components of a web page accessed through the Pagelet Producer that can be injected into any proxied application. Any application on a Pagelet Producer resource that returns markup can be registered as a pagelet, which can then be displayed in Oracle WebCenter. Data can be passed to pagelets using pagelet parameters or the pagelet payload. The former passes name-value pairs attributes to the pagelet application, while the latter is any text, including XML. ■ All post deployment connection configuration is stored in the Oracle Metadata Services MDS repository. For more information, see Section 1.3.5, WebCenter Configuration Considerations. For detailed information about MDS, see the chapter Managing the Oracle Metadata Repository in the Oracle Fusion Middleware Administrators Guide. Pagelet Producer stores all configuration data on a separate partition in the MDS schema of RCU. Typically, this schema is installed as part of the Oracle WebCenter installation. This configuration data does not conflict with data that belongs to other services. When the Pagelet Producer domain template is deployed, the wizard prompts for connectivity information to the database in which the schema has been created. The names that the Pagelet Producer expects are: – Datasource Name: mds-PageletProducerDS – JNDI name: jdbcmdsPageletProducerDS – MDS partition name: pageletproducer ■ Pagelet Producer registration is dynamic. Additions and updates to existing producers are immediately available; it is not necessary to restart the WebCenter application or the managed server. ■ In the current release, only a single administrator can modify Pagelet Producer administrative settings at any given time. Concurrent edits will result in only one edit succeeding. However, data integrity will always be preserved.

24.2 Registering the Pagelet Producer

This section describes how to register the Pagelet Producer using Fusion Middleware Control and WLST commands. This section includes the following subsections: ■ Section 24.2.1, Registering the Pagelet Producer for WebCenter Applications Using Fusion Middleware Control ■ Section 24.2.2, Registering the Pagelet Producer for WebCenter Applications Using WLST