From the Implementation Style list, select WSRP for your WSRP provider. Click Next to display the Define Connection page

Creating Java Portlets 6-29 Figure 6–21 Registration Confirmation Page 16. Your portlet should now be available for adding to pages just as any other portlet in the Portlet Repository. To add your portlet to a page, follow the instructions in the Oracle Fusion Middleware Users Guide for Oracle Portal.

6.3.5 Registering WSRP Producers in Enterprise Configurations

When you register a WSRP producer in an Enterprise configuration, you must create a Web Seringyvices Definition Language WSDL document manually, then register the WSRP producer using that WSDL. This is because the dynamically generated WSDL creates URLs using the HTTPS protocol and the HTTPS port while WSRP producers use HTTP. To create a WSDL document manually, perform the following tasks: 1. View the dynamically generated WSDL through your browser preferably Internet Explorer. To view the WSDL for our WSRP samples, go to: http:host:external http portportletappportlets?WSDL 2. Save the file from the browser to any externally available location. For our WSRP Samples, save the file from the browser into the following directory: ORACLE_HOMEj2eehomeapplicationsportletappwsrp-samples Save the file as wsrpsamples.wsdl. 3. Edit the file, replacing https with http and correcting the ports to be the external http ports. 4. View the file through a browser. For example, for our WSRP Samples use the following URL: http:host:external http portportletappwsrpsamples.wsdl 5. Use the URL to your .wsdl file such as the URL under Step 4 when you register the WSRP producer. For more information about Enterprise configurations, see the Oracle Fusion Middleware Enterprise Architecture and Deployment Guide. Note: A producer for WSRP portlets is analogous to a provider for PDK-Java portlets. 6-30 Oracle Fusion Middleware Developers Guide for Oracle Portal

6.4 Introduction to Oracle PDK-Java

Oracle PDK-Java gives you a framework to simplify the development of Java portlets by providing commonly required utilities and allowing you to leverage existing development skills and application components such as JSPs, servlets, and static HTML pages. Oracle PDK-Java also enables you to create portlets without having to deal directly with the complexity of communications between Oracle Portal and providers. The Oracle PDK-Java framework is divided into the following areas: ■ The Provider Adapter insulates the developer from the HTTP syntax defined by Oracle Portal for communication with Web providers. It translates the information passed between Oracle Portal and your Java Web provider. Without an adapter, your provider would not only manage portlets, but it would also have to communicate this information directly to Oracle Portal in the expected language. The adapter eliminates the need for your Web provider to understand the portal language and vice-versa. ■ The Provider Interface defines the APIs functions required by your Java implementation to integrate with the Provider Adapter. The Provider Adapter receives messages from the portal, translates them into calls to the Provider Interface, and translates the providers response into a format that the portal can understand. The Provider Interface contains a set of Java classes that define the methods your provider needs to implement and, in many cases, provides a standard implementation. Some of the primary classes are as follows: – ProviderDefinition oracle.portal.provider.v2.ProviderDefinition – ProviderInstance oracle.portal.provider.v2.ProviderInstance – PortletDefinition oracle.portal.provider.v2.PortletDefinition – PortletInstance oracle.portal.provider.v2.PortletInstance – ParameterDefinition oracle.portal.provider.v2.ParameterDefinition – EventDefinition oracle.portal.provider.v2.EventDefinition ■ The Provider Runtime provides a base implementation that follows the specification of the Provider Interface. The Provider Runtime includes a set of default classes that implement each one of the Provider Interfaces and enables you to leverage the rendering, personalization, and security frameworks provided with PDK-Java. These classes and the associated frameworks simplify the development of a provider by implementing common functions for Oracle Portal requests and providing a declarative mechanism for configuring the provider. Using the Provider Runtime, you can focus your development efforts on the portlets themselves rather than the infrastructure needed to communicate with the portal. If the standard behavior of the Provider Runtime does not meet your requirements, you can easily extend or override specific behaviors. Some of the primary classes are as follows: – DefaultProviderDefinition oracle.portal.provider.v2.DefaultProviderDefinition – DefaultProviderInstance oracle.portal.provider.v2.DefaultProviderInstance – DefaultPortletDefinition oracle.portal.provider.v2.DefaultPortletDefinition – DefaultPortletInstance oracle.portal.provider.v2.DefaultPortletInstance – PortletRenderer oracle.portal.provider.v2.render.PortletRenderer