14-14 Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF
operation name=onResult soap:operation style=document soapAction=onResult
input soap:body use=literal namespace=http:services.otn.com
input operation
binding service name=UnitedLoan
port name=UnitedLoanPort binding=tns:UnitedLoanBinding soap:address
location=http:stadg55.us.oracle.com:7001soa-infraservices defaultUnitedLoan1.005ed6481-93e6-4b46-b2d7-a21fa27a36a9
UnitedLoan_client port
service definitions
Example 14–3 Example of WSDL Code Modified So It Can Be Used by a SOAP Processor
That Does Not Support WS-Addressing 1.0
?xml version=1.0 encoding=UTF-8 ? definitions
name=UnitedLoan targetNamespace=http:services.otn.com
xmlns=http:schemas.xmlsoap.orgwsdl xmlns:plnk=http:schemas.xmlsoap.orgws200305partner-link
xmlns:soap=http:schemas.xmlsoap.orgwsdlsoap xmlns:s1=http:www.autoloan.comnsautoloan
xmlns:wsdl=http:schemas.xmlsoap.orgwsdl xmlns:wsa=http:www.w3.org200508addressing
xmlns:tns=http:services.otn.com plnk:partnerLinkType name=UnitedLoan
plnk:role name=UnitedLoanProvider plnk:portType name=tns:UnitedLoan
plnk:role plnk:role name=UnitedLoanRequester
plnk:portType name=tns:UnitedLoanCallback plnk:role
plnk:partnerLinkType types
schema xmlns=http:www.w3.org2001XMLSchema import namespace=http:www.autoloan.comnsautoloan
schemaLocation=http:stadg55.us.oracle.com:7001 soa-infraservicesdefault
UnitedLoan1.005ed6481-93e6-4b46-b2d7-a21fa27a36a9 UnitedLoan_client?XSD=AutoLoanTypes.xsd
schema schema xmlns=http:www.w3.org2001XMLSchema
import namespace=http:www.w3.org200508addressing schemaLocation=http:www.w3.org200603
addressingws-addr.xsd schema
types message name=UnitedLoanResultMessage
part name=payload element=s1:loanOffer message
message name=UnitedLoanRequestMessage part name=payload element=s1:loanApplication
message
Upgrading Other Oracle SOA Suite Technologies 14-15
message name=WSAMessageIDHeader part name=MessageID element=wsa:MessageID
message message name=WSAReplyToHeader
part name=ReplyTo element=wsa:ReplyTo message
message name=WSARelatesToHeader part name=RelatesTo element=wsa:RelatesTo
message portType name=UnitedLoanCallback
operation name=onResult input message=tns:UnitedLoanResultMessage
operation portType
portType name=UnitedLoan operation name=initiate
input message=tns:UnitedLoanRequestMessage operation
portType binding name=UnitedLoanBinding type=tns:UnitedLoan
soap:binding transport=http:schemas.xmlsoap.orgsoaphttp operation name=initiate
soap:operation style=document soapAction=initiate input
soap:header message=tns:WSAReplyToHeader part=ReplyTo
use=literal soap:header message=tns:WSAMessageIDHeader
part=MessageID use=literal
soap:body use=literal namespace=http:services.otn.com input
operation binding
binding name=UnitedLoanCallbackBinding type=tns:UnitedLoanCallback
soap:binding transport=http:schemas.xmlsoap.orgsoaphttp operation name=onResult
soap:operation style=document soapAction=onResult input
soap:header message=tns:WSARelatesToHeader part=RelatesTo
use=literal soap:body use=literal namespace=http:services.otn.com
input operation
binding service name=UnitedLoan
port name=UnitedLoanPort binding=tns:UnitedLoanBinding soap:address location=http:stadg55.us.oracle.com:7001
soa-infraservicesdefault UnitedLoan1.005ed6481-93e6-4b46-b2d7-a21fa27a36a9
UnitedLoan_client port
service definitions
14-16 Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF
15
Considerations When Upgrading Oracle WebCenter Applications 15-1
15
Considerations When Upgrading Oracle WebCenter Applications
This chapter describes how to upgrade Oracle WebCenter 10.1.3.x applications to Oracle WebCenter 11g.
For information about the high-level tasks required to upgrade any Oracle SOA, Oracle WebCenter, and ADF application, see
Chapter 8, Overview of Upgrading Oracle SOA Suite, WebCenter, and ADF Applications.
Use the following sections to understand tasks specific to upgrading Oracle WebCenter applications:
■
About Upgrading WebCenter Applications
■
Prerequisites for Upgrading WebCenter Applications
■
Upgrading WebCenter Consumer Applications
■
Upgrading Portlet Producers
■
Migrating Data
15.1 About Upgrading WebCenter Applications
This section lists the high-level upgrade tasks and provides an overview of the different WebCenter application templates.
15.1.1 Tasks Involved in Upgrading WebCenter Applications
Based on the functionality of your WebCenter 10.1.3.x applications, and the WebCenter services that they are configured to use, you may need to perform the following tasks
to upgrade your applications to Oracle WebCenter 11g:
■
Upgrade WebCenter consumer applications by using Oracle JDeveloper
■
Upgrade WebCenter portlet producer applications and their customizations, if WebCenter applications contains portlets.
■
Migrate the data related to WebCenter services, if your WebCenter consumer applications use these services.
Note: In this chapter, Oracle Fusion Middleware 11g, Oracle
JDeveloper 11g, and Oracle WebCenter 11g refers to the Release 1 11.1.1.4.0 version.
15-2 Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF
15.1.2 About WebCenter Application Templates
Oracle WebCenter 10.1.3.x applications and Oracle WebCenter 11g applications are based on different application templates. An understanding of various templates is
important before you attempt to upgrade your WebCenter applications.
In JDeveloper 10.1.3.x, WebCenter applications are created using the WebCenter Application [Portlet, Content Repository, JSF]
application template. Both WebCenter consumer applications and portlet producer applications are based on the same
template.
By contrast, Oracle WebCenter 11g applications are based on a WebCenter Portal Application
template for consumer applications, or a Portlet Producer Application
template for portlet producer applications.
In JDeveloper 10.1.3.x, WebCenter applications consist of three projects: Model, Portlets
, and ViewController. In JDeveloper 11g, applications created by using the WebCenter Portal Application
template contain the Portal project which includes features like site navigation and page hierarchies and the PortalWebAssets project
which includes static application resources like HTML and image files. Applications created by using the Portlet Producer Application template contain only one project,
Portlets
, scoped for creation of JSR 286 standards-based and Oracle PDK-Java portlets.
15.2 Prerequisites for Upgrading WebCenter Applications
Before you attempt to upgrade your WebCenter 10.1.3.x applications, perform the following tasks:
1. Verify that the application is running successfully on Oracle Application Server
10g. For information, see
Section 8.2, Task 2: Verify that the Applications Are Up and Running Successfully on Oracle Application Server 10g.
2. Verify that your Oracle WebCenter 10.1.3.x environment is upgraded to the Oracle
WebCenter 11g environment. For information, see
Section 8.4, Task 4: Verify That You Have Upgraded Your 10g Environment to 11g.
3. Install Oracle JDeveloper 11g.
For information, see Section 8.5, Task 5: Install and Start Oracle JDeveloper 11g.
4. Install the Oracle WebCenter extension.
To work with WebCenter applications, you must install the Oracle WebCenter extension. The Oracle WebCenter extension is a JDeveloper add-in that provides
all WebCenter capabilities in JDeveloper.
To install Oracle WebCenter 11g extension:
Note: In this chapter, a WebCenter consumer application refers to an
application that provides the user interface and contains JSP pages and components required by the application. A portlet producer
application refers to an application that contains Oracle WebCenter server-side producer components and the portlets that can be
consumed by a WebCenter consumer application.
Considerations When Upgrading Oracle WebCenter Applications 15-3
a.
Start JDeveloper 11g.
b. If the Select Role dialog displays, select Default Role to enable all
technologies, and click OK. c.
If this is the first time you started JDeveloper 11g, it prompts you to import preferences from a previous version of JDeveloper.
In the Confirm Import Preferences dialog, use the Search icon to select the JDeveloper version from which you want to copy preferences. Then, click Yes
to automatically migrate portlet customization data of preconfigured portlet producers like OmniPortlet and Web Clipping, from the older JDeveloper
version listed in the dialog. You can choose a different JDeveloper version by clicking the Show All Installations button and then selecting the required
version.
If you select No, be aware that portlet customizations are not migrated from the previous version of JDeveloper. In this case, you must manually migrate
customizations. For information about migrating customizations manually from the default location, see
Section 15.4.2.4.1, Migrating Customizations from the Default Location.
Note: If you intend to upgrade application settings from JDeveloper
10.1.3.x, be sure to close and remove your WebCenter applications from the IDE in JDeveloper 10.1.3.x before you start JDeveloper 11g.
This gives you more control in deciding when your applications will get migrated, and will not invoke application migration during
JDeveloper startup.
You can remove applications from the IDE by right-clicking an application name in the Application Navigator and selecting Delete
from the shortcut menu. Removing an application removes it only from the IDE and not from your local storage system.
15-4 Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF
d. From the Help menu, select Check for Updates.
e. On the Welcome page of the Check for Updates wizard, click Next.
f. On the Source page, select Search Update Centers and click Next.
g.
On the Updates page, search for the WebCenter extension, select it, and click Finish
.
h. Click Yes when prompted to restart JDeveloper 11g.
i. In the Confirm Import Preferences dialog, click Yes when asked if you want to
import preferences from a previous version of JDeveloper. These preferences include the portlet customization data.
JDeveloper is now configured to create WebCenter Portal and Portlet Producer applications.
15.3 Upgrading WebCenter Consumer Applications
Table 15–1 lists the tasks involved in upgrading a WebCenter 10.1.3.x consumer
application to Oracle WebCenter 11g.
Note: The JDeveloper migration utility migrates portlet
customizations only for preconfigured portlet producers from the default location, 10.1.3.x_jdev_install_
dir portalportletdata.
If you used a nondefault location to store customizations of preconfigured portlet producers, you must manually migrate the
customizations. To migrate customizations of portlet producers other than preconfigured portlet producers, you need to use the preference
store migration utility.
For information about:
■
Migrating preconfigured portlet producers’ customizations manually from the default location, see
Section 15.4.2.4.1, Migrating Customizations from the Default Location.
■
Migrating preconfigured portlet producers’ customizations from a nondefault location, see
Section 15.4.2.4.2, Migrating Customizations from a Nondefault Location.
■
Migrating customizations for portlet producers other than preconfigured portlet producers, see
Section 15.4.3.1, Migrating Customizations.
Note: For more information about obtaining and installing Oracle
WebCenter extension, see the Oracle WebCenter page on Oracle Technology Network OTN at:
http:webcenter.oracle.com
