OmniPortlet Repository Changes Preconfigured Portlet Producers: Customization Store’s Location

16-14 Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF Table 16–7 describes the handling of navigation parameters of oracle-portlet.xml in the portlet.xml file when you upgrade a portlet producer application. When a JSR 168 portlet producer application is upgraded, the following changes are made while converting oracle-portlet.xmls navigation parameters into public render parameters: ■ If the portlet has any declared supported-public-render-parameter in portlet.xml, all navigation parameters from oracle-portlet.xml are ignored and a warning message is logged. ■ If portlet application-level public-render-parameter descriptions in portlet.xml have the same identifier as the local part of the navigation parameters’ name in oracle-portlet.xml, the navigation parameters that conflict are ignored and a warning message is logged. ■ If any navigation parameters specified in any portlet-extension element in oracle-portlet.xml have different namespace parts but the same local part of the name element, all overlapping navigation parameters except one are ignored and a warning message is logged. Table 16–7 Handling of the navigation-parameters Element available in oracle-portlet.xml navigation-parame ter Element XML Type Handling in portlet.xml of a JSR286 Container name QName The full QName is used as the public-render-parameter QName in portlet.xml at the portlet application-level. The local part of the QName is used as the public-render-parameter identifier at the portlet application-level, and as the supported-public-render-parameter value at the portlet level. type QName Ignored label localizedString Converted to the description element. The label, hint, and usage elements are merged in the given sequence to create the description element of the public-render-parameter in portlet.xml. hint localizedString Converted to the description element. The label, hint, usage elements are merged in the given sequence to create the description element of the public-render-parameter in portlet.xml. usage string Converted to the description element. The label, hint, usage elements are merged in the given sequence to create the description element of the public-render-parameter in portlet.xml. aliases QName Converted to alias declarations on the public-render-parameter declaration in portlet.xml at the portlet application level. A Example: Upgrading and Redeploying SOA Order Booking A-1 A Example: Upgrading and Redeploying SOA Order Booking This appendix provides the step-by-step procedure for upgrading a complex Oracle SOA Suite SOA application from Oracle Application Server 10g Release 3 10.1.3.3 to Oracle Fusion Middleware Release 11 11.1.1.0.0. This procedure is meant to serve as an overall example of the Oracle SOA Suite environment and application upgrade process. Specifically, this appendix contains the following topics: ■ About the SOA Order Booking Application ■ Task 1: Verify That the SOA Order Booking and Its External Partners are Up and Running ■ Task 2: Install and Upgrade the Oracle Fusion Middleware SOA Suite ■ Task 3: Use the Oracle WebLogic Suite Administration Console to Configure Required Resources ■ Task 4: Install Oracle JDeveloper 11g ■ Task 5: Set Up Connections in Oracle JDeveloper Release 11 ■ Task 6: Open the SOA Order Booking Application in Oracle JDeveloper 11g and Migrate the Application Projects ■ Task 7: Compile and Deploy Each of the Application Projects on Oracle Fusion Middleware 11g ■ Task 8: Test the SOA Order Booking Application in Fusion Middleware Control A.1 About the SOA Order Booking Application Oracle provided the SOA Order Booking application with Oracle Application Server 10g Release 3 10.1.3.1.0 as a sample application that demonstrates many of the key features and components of the Oracle Application Server 10g Release 3 10.1.3.1.0 release. The SOA Order Booking application is described in detail in the Oracle SOA Tutorial and in the Oracle SOA Suite Quick Start Guide, which are both available in the Oracle Application Server 10g Release 3 10.1.3.1.0 Documentation Library on the Oracle Technology Network: http:www.oracle.comtechnologydocumentationindex.html