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

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. 15-22 Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF

15.4.3 Performing Post Upgrade Tasks for Portlet Producers

After upgrading portlet producers, you need to migrate customizations of portlet producers other than preconfigured ones and redeploy your portlet producer applications.

15.4.3.1 Migrating Customizations

After upgrading Oracle PDK-Java and WSRP portlet producers, you must migrate their customizations if the customizations are not shared or accessible to the upgraded portlet producers. These customizations are of portlet producers other than the preconfigured portlet producers. To migrate such customizations, you can use the preference store migration utility. For information, see the Portlet Preference Store Migration Utilities section in Oracle Fusion Middleware Developers Guide for Oracle WebCenter.

15.4.3.2 Redeploying a Portlet Producer Application

You can deploy your upgraded portlet producer application to any Oracle WebLogic Server managed server configured to support Oracle WebCenter portlet producers. For deployment, you can use Oracle Enterprise Manager Fusion Middleware Control, Oracle WebLogic Server Administration Console, or Oracle WebLogic Scripting Tool WLST. For information, see the Deploying Portlet Producer Applications section in Oracle Fusion Middleware Administrators Guide for Oracle WebCenter. You can also deploy portlet producer applications to an Oracle WebLogic Server instance directly from a development environment by using JDeveloper, provided you have the required credentials to access the WebLogic server. For information, see the Deploying a Portlet Application to an Oracle WebLogic Managed Server Instance section in Oracle Fusion Middleware Developers Guide for Oracle WebCenter.

15.5 Migrating Data

If your WebCenter 10g application contains WebCenter services that rely on a back-end component, you may need to prepare the back-end component for upgrade, and migrate the data. This section describes how to migrate your WebCenter 10g data to the required servers. It contains the following subsections: ■ Section 15.5.1, Migrating Data from Oracle WebCenter Wiki and Blog Server ■ Section 15.5.2, Migrating Data from Oracle Content DB

15.5.1 Migrating Data from Oracle WebCenter Wiki and Blog Server

In your WebCenter 10g applications, you expose wiki and blog functionality through the Wiki and Blog services. Oracle WebCenter 10g relies on Oracle WebCenter Wiki and Blog Server to provide the wiki and blog functionality. Oracle WebCenter 11g exposes the wiki and blog functionality through the Documents service, and requires Oracle Content Server 11g as the content repository for this purpose. When you upgrade a WebCenter 10.1.3.x application containing the Wiki and Blog services, you must also migrate the wiki data from Oracle WebCenter Wiki and Blog Note: If Oracle WebCenter Wiki and Blog Server is not installed in your WebCenter 10g environment, you can skip this section.