In the Default Expiry Conditions section, select: Click Next to display the Initialization Parameters page

6-24 Oracle Fusion Middleware Developers Guide for Oracle Portal – packagename.portletnameBundle.java contains all the translation strings for the portlet ■ portlet.xml ■ oracle-portlet.xml ■ web.xml Figure 6–17 Application Navigator

6.3.2 Adding Portlet Logic to Your JSR 168 Portlet

After you create the default implementation of your portlet, you can extend the sample code with your own business logic to implement the desired functionality and features. See the JPS or Javadoc for more information on adding functionality and features.

6.3.3 Deploying Your JSR 168 Portlet to the Oracle WebLogic Server

After you finish the wizard and successfully generate your portlet, you are ready to deploy it to the Oracle WebLogic Server. To create and deploy a WAR file, perform the following steps:

1. In the Application Navigator, right-click the project that contains your portlet and

select New. 2. In the New Gallery, expand General and select Deployment Profiles. 3. In the Items list, select WAR File and click OK. The Create Deployment Profile -- WAR File dialog box opens.

4. In the Deployment Profile Name field, enter a meaningful name for the

deployment profile for example, webapp.

5. Click OK.

The Edit WAR Deployment Profile Properties dialog box opens. 6. Under Web Application’s Context Root, select Specify J2EE Web Context Root and enter the context root in the corresponding field, for example my-portlet.

7. Click OK.

The Project Properties dialog box opens. 8. Click OK. Creating Java Portlets 6-25

9. In the Application Navigator, right-click your project and select Deploy, then

select the deployment profile, next select to, and finally select the IntegratedWLSConnection .

10. In the Select deployment type dialog box, select Yes and click OK.

11. When the Deployment Finished message displays in the Deployment Log at the

bottom of Oracle JDeveloper, verify that no errors occurred. 12. Construct the WSDL URL for your JPS-compliant portlet as follows: http:host:portcontext-rootportletswsrp2?WSDL where host is the server to which your producer has been deployed. port is the Oracle Web Cache HTTP Listener port from the Ports tab of the Application Server Control Console main page. context-root is the Web Applications Context Root, which is found in the WAR Deployment Profile Properties under General. 13. In a Web browser, enter the WSDL URL from the previous step to ensure that it is working. If the WSDL definition does not appear in the browser, then the deployment of your WAR file must have failed. Refer to Appendix B.2, Diagnosing Java Portlet Problems . 14. If you are using SSL HTTPS, you must modify your WSDL URL before registering the producer with Oracle Portal. If you are not using SSL, you may skip to the next step now. To modify your WSDL URL, perform the following steps: a. In a Web browser, enter the HTTPS WSDL URL. For example: http:host:portcontext-rootportletsWSRPBaseService?WSDL Each port in the definition should be displayed with an HTTPS location, for example: wsdl:port binding=bind:WSRP_v1_Markup_Binding_SOAP name=WSRPBaseService soap:address location=https:host:portcontext-rootportletsWSRPBaseService wsdl:port b. If the ports are not listed with HTTPS locations, you must change them manually before proceeding. You can do this by saving the XML to a file from the browser and opening it in a text editor. c. Save a copy of the WSDL definition to a file on your application server in a location where it can be accessed externally over HTTP. For example, the htdocs directory of your Apache installation. When you register the producer in Oracle Portal, use the location of this WSDL for your WSDL URL on the Define Connection page of the registration. Note: In order for HTTPS to work with a producer, you must have previously configured the server certificate in the infrastructure server certificate store as described in the Oracle Fusion Middleware Administrators Guide for Oracle Portal.