About Upgrading JSR168 Portlet Producers to JSR286

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

3. In the New Gallery dialog, expand General, select Applications, then Application

from EAR File , and click OK. 4. Select Application from EAR File, and click OK. 5. On the Welcome page in the Create Application from EAR File wizard, click Next. 6. On the Location page, in the EAR File field, enter the path to the EAR file. 7. Select the Copy Files to Application checkbox. 8. Select Finish to create the application in JDeveloper. 9. Save the application. 10. Save a backup copy of the application. 11. Open JDeveloper 11g. 12. Open the WebCenter 10.1.3.x application that you created from the EAR file. 13. Follow the instructions to upgrade the application to JDeveloper 11g. 14. Save the application. The application can now be redeployed.

15.4.2.3.2 Creating a JDeveloper Application from a WAR File To create a JDeveloper file

from a JSR 168 or a PDK-Java application packaged as a WAR file: 1. Open JDeveloper 10.1.3.x.

2. From the File menu, choose New.

3. In the New Gallery dialog, expand General, select Applications, then

Application , and click OK.

4. In the Create Application wizard, click OK.

5. In the Create Project wizard, click Cancel so that no new project is created in the

application.

6. In the Application Navigator, select the newly created application.

7. From the File menu, choose New.

8. In the New Gallery, expand General, select Project, then Project from WAR File,

and click OK. 9. On the Welcome page in the Create Project from WAR File wizard, click Next. 10. On the WAR Location page, in the WAR File field, specify the path to the WAR file.

11. Click Finish to create the project.

12. Save the application. 13. Back up your application. 14. Open JDeveloper 11g. 15. Open the WebCenter 10.1.3.x application that you created from the WAR file. Note: You must use JDeveloper 10.1.3.x to prepare the WAR file for upgrade. Considerations When Upgrading Oracle WebCenter Applications 15-21 16. Follow the instructions to upgrade the application in JDeveloper 11g. 17. Save the application. The application can now be redeployed.

15.4.2.4 Upgrading Preconfigured Portlet Producers

Oracle WebCenter 11g provides various preconfigured portlet producers. These include OmniPortlet, Web Clipping, WSRP Parameter Form Portlet, sample WSRP portlet producers, and sample PDK-Java portlet producers. Oracle WebCenter enables you to customize portlets. Customizations can include preferences such as user data and portlet and producer settings. Customizations can be stored in a database or a file system. Customizations related to preconfigured portlet producers are saved in the customization store of these producers, and not within your application projects. By default, in Oracle WebCenter 10g, customizations for preconfigured portlet producers are stored at the following location: 10.1.3.x_jdev_install_dir portalportletdata Where, 10.1.3.x_jdev_install_dir refers to the JDeveloper 10.1.3.x installation directory. So, when you upgrade a WebCenter application containing portlets provided by preconfigured portlet producers, you must ensure that portlet customizations are also migrated.

15.4.2.4.1 Migrating Customizations from the Default Location After installing JDeveloper

11g, when you start it the first time, it prompts whether you want to migrate settings from a previous release. If you select Yes, portlet customizations of preconfigured portlet producers, along with other JDeveloper system properties, are automatically migrated from a previous JDeveloper installation to JDeveloper 11g. However, this migrates portlet customizations only from the default location, 10.1.3.x_jdev_ install_dir portalportletdata. If you choose not to migrate portlet customizations and select No, you must migrate customizations later manually. The manual procedure involves copying the 10.1.3.x_jdev_install_dir portalportletdata directory to the 11g_ jdev_install_dir jdeveloperportalportletdata directory.

15.4.2.4.2 Migrating Customizations from a Nondefault Location You may choose to store

portlet customizations at a different location instead of the default location, 10.1.3.x_jdev_install_dir portalportletdata. To migrate customizations from a nondefault location, you must perform either of the following tasks: ■ Migrating customizations to a new location: Copy the customization store directory to the required path and configure your upgraded portlet producer to point to the new location of the customization store. If customizations are stored in a database, configure your upgraded portlet producer to access that database. ■ Using customizations from the existing location: Configure your upgraded portlet producer to access the customization store from the old location. For information about storing customizations at a nondefault location, see Section 16.3, Preconfigured Portlet Producers: Customization Store’s Location.