Configuring ADF Security Performing Post Upgrade Tasks

15-16 Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF

15.4.1 Determining WebCenter Consumer Application and Portlet Producer Compatibility

In most cases, WebCenter consumer applications or portlet producer applications deployed to Oracle Application Server 10.1.3.x are compatible with applications upgraded to Oracle Fusion Middleware 11g. For example, a WebCenter consumer application that has been upgraded and deployed to Oracle WebLogic Server in Oracle Fusion Middleware 11g may still use portlets from PDK-Java producer applications running on Oracle Application Server 10.1.3.x. Oracle Fusion Middleware 11g supports backward compatibility for WebCenter consumer applications and portlet producer applications. Based on the compatibility supported, you may decide to upgrade only your WebCenter consumer applications, only portlet producer applications, or both. Table 15–3 lists the compatibility between different versions of WebCenter consumer applications and portlet producer applications. Table 15–3 shows that a WebCenter 10.1.3.x consumer application and a PDK-Java or a WSRP 1.0 WebCenter 11g portlet producer application are compatible. In such a case where backward compatibility is supported, you may choose not to upgrade your WebCenter 10.1.3.x consumer application to Oracle WebCenter 11g. The table further shows that a WebCenter 11g consumer application and a PDK-Java or a WSRP 1.0 WebCenter 10.1.3.x portlet producer application are compatible. In such a case, you may choose not to upgrade your 10.1.3.x portlet producer application. Table 15–2 Task Flow for Upgrading Portlet Producers Task SubTask When to Perform the Task? Preparing Your Application Determining WebCenter Consumer Application and Portlet Producer Compatibility Always Upgrading Your Portlet Producer Application Upgrading Portlet Producers Created in JDeveloper If your WebCenter application contains portlets provided by portlet producers developed in JDeveloper 10.1.3.x. Upgrading Portlet Producers Created Outside of JDeveloper If your WebCenter application contains portlets provided by portlet producers developed outside of JDeveloper. Upgrading Preconfigured Portlet Producers If your WebCenter application contains portlets provided by preconfigured portlet producers. Performing Post Upgrade Tasks Migrating Customizations If your WebCenter application contains portlets other than the portlets provided by preconfigured portlet producers. Redeploying a Portlet Producer Application Always Considerations When Upgrading Oracle WebCenter Applications 15-17 However, WebCenter 10.1.3.x consumer applications are not compatible with WSRP 2.0 Oracle WebCenter 11g portlet producer applications. Similarly, WebCenter 11g consumer applications are not compatible with WSRP 2.0 WebCenter 10.1.3.x portlet producer applications. In such cases, all 10.1.3.x WSRP 2.0 applications must be upgraded to Oracle Fusion Middleware 11g for these applications to work together.

15.4.2 Upgrading Portlet Producer Applications

To upgrade portlet producer applications, you may need to perform various tasks depending on the type of portlet producers used in your WebCenter 10.1.3.x application. This section describes those tasks. It contains the following subsections: ■ About Upgrading JSR168 Portlet Producers to JSR286 ■ Upgrading Portlet Producers Created in JDeveloper ■ Upgrading Portlet Producers Created Outside of JDeveloper ■ Upgrading Preconfigured Portlet Producers

15.4.2.1 About Upgrading JSR168 Portlet Producers to JSR286

Oracle WebCenter 10g supports Java portlets based on the Java Portlet Specification, JSR 168; Oracle WebCenter 11g supports Java portlets based on Java Portlet Specification version 2, or JSR 286. JSR 286 is an extension of JSR 168, and is backward compatible with JSR 168. In Oracle WebCenter 10g, Oracle JSF Portlet Bridge is based on and conforms to JSR 301, whereas in Oracle WebCenter 11g, Oracle JSF Portlet Bridge conforms to JSR 329. In JDeveloper 11g, when you open for the first time an existing portlet producer application containing JSR 168 portlets, portlets are automatically upgraded to be JSR 286 compliant. If the application is a portlet bridge application, it is further automatically upgraded to be JSR 329-compliant. In most cases, the upgraded portlets continue to work exactly as they did before. However, there are a few cases in which JSR 168 portlets function differently when Table 15–3 Compatibility Between Different Versions of WebCenter Consumer and Portlet Producer Applications Version of WebCenter Consumer Application 1 1 In this column, 11g refers to a WebCenter consumer application upgraded to or originally created in Oracle WebCenter 11.1.1.4.0. Version of Portlet Producer Application Is this Combination of Applications Supported in Oracle Fusion Middleware 11g? 10.1.3.x PDK-Java 11g Yes 10.1.3.x WSRP 1.0 deployed to Oracle WebLogic Server 11g Yes 10.1.3.x WSRP 2.0 deployed to Oracle WebLogic Server 11g No 11g PDK-Java 10.1.3.x Yes 11g WSRP 1.0 deployed to Oracle Application Server 10.1.3.x Yes 11g WSRP 2.0 deployed to Oracle Application Server 10.1.3.x No 15-18 Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF upgraded to JSR 286; these portlets must invoke a JSR 168 compatibility mode to run under JSR 286. In Oracle WebCenter 10g, a portlet producer application contains the portlet.xml and oracle-portlet.xml files. When you upgrade a portlet producer application, the oracle.portlet.xml file is deleted, and all its details are moved to portlet.xml. The navigation parameters stored in oracle.portlet.xml are converted into public render parameters and are added to portlet.xml. For information about how JSR 168 parameters are handled in an upgraded JSR 286-compliant portlet producer application, see Section 16.4, Migration of JSR 168 Portlet Producers to JSR 286: Handling of Portlet Elements.

15.4.2.2 Upgrading Portlet Producers Created in JDeveloper

If your WebCenter 10.1.3.x application contains portlets and was created by using JDeveloper, you must create a portlet producer application in Oracle WebCenter 11g to upgrade portlet producers. You must also manually add the Portlets project of the WebCenter 10.1.3.x application to the newly created portlet producer application. To upgrade a portlet producer application created in JDeveloper 10.1.3.x:

1. Create a portlet producer application in JDeveloper 11g by using the Portlet

Producer Application template. For information, see the section Creating a Portlet Producer Application in the Oracle Fusion Middleware Developers Guide for Oracle WebCenter.

2. In the newly created portlet producer application, select the Portlets project.

3. From the File menu, choose Delete Project.

4. In the Confirm Delete Project dialog, select the Remove project and delete all of

its contents including source directories radio button and click Yes, as shown in Figure 15–9 . Figure 15–9 Deleting the Portlets Project Note: If your WebCenter 10g application does not contain any portlet producers, its Portlets project will be empty. Note: To complete this procedure, you need a copy of the Portlets directory of your WebCenter 10.1.3.x application.