From the File menu, select New.

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. Considerations When Upgrading Oracle WebCenter Applications 15-23 Server to Oracle Content Server 11g. You can migrate the wiki and blog data any time after upgrading the middle tier. For information about how to migrate the wiki and blog data from Oracle WebCenter Wiki and Blog Server to Oracle Content Server 11g, refer to the section Migrating Your Oracle Wiki Pages and Blogs in Oracle Fusion Middleware Patching Guide.

15.5.2 Migrating Data from Oracle Content DB

If your WebCenter 10g applications rely on Oracle Content DB, you must use Oracle Content Server version 10.1.3.5.1 or 11g as your content repository. You can migrate Content DB data any time after upgrading the middle tier. To migrate Oracle Content DB data to Oracle Content Server 10.1.3.5.1 by using a WebDav client: 1. Open the following WebDAV locations with a user account that has access to all relevant content: ■ Location on Oracle Content DB: http:server:hostcontentdav ■ Location on Oracle Content Server: http:server:hostcontent-server-rootidcplgwebdav 2. Copy the content from the Oracle Content DB location to the Oracle Content Server location. When you migrate content by using WebDav, be aware of the following: ■ The Trash folder gets copied. ■ For the versioned documents, only the latest version gets copied. ■ Metadata and access control setting are not preserved for the copied content. Note: You cannot directly migrate data from Oracle Content DB to Oracle Content Server 11g. If you want to use Oracle Content Server 11g as your content repository, you must first migrate Content DB data to Oracle Content Server 10.1.3.5.1, and then upgrade to Oracle Content Server 11g. For information about upgrading from Oracle Content Server 10g to 11g, refer to Oracle Fusion Middleware Upgrade Guide for Enterprise Content Management.