Moving Resource Catalogs from an Applications MDS to a Project Directory

Considerations When Upgrading Oracle WebCenter Applications 15-15 set to support this style of security. If this flag is not set, then anyone who has page access can view attributes and rowsets and invoke methods because in Oracle WebCenter 11g the permission check is performed only on pages and task flows. The flag must be set for each application in the adf-config.xml file, as shown in the following example: sec:adf-security-child xmlns=http:xmlns.oracle.comadfsecurityconfig JaasSecurityContext initialContextFactoryClass=oracle.adf.share.security.JAASInitialContextFactory jaasProviderClass=oracle.adf.share.security.providers.jps.JpsSecurityContext authorizationEnforce=true contextEnv name=oracle.adf.security.metadata value=false CredentialStoreContext credentialStoreClass= oracle.adf.share.security.providers.jps.CSFCredentialStore credentialStoreLocation=....srcMETA-INFjps-config.xml sec:adf-security-child You must also ensure that there are no duplicate JaasSecurityContext and CredentialStoreContext elements in the adf-config.xml file.

15.3.3.5 Upgrading Producer Registrations of Preconfigured Portlet Producers

During application upgrade, the port numbers of all preconfigured portlet producers such as Web Clipping and OmniPortlet are updated. All producer registrations from preconfigured portlet producers that existed in Oracle Application Server 10.1.3.x environment with port 6688 are migrated to port 7101. If you did not use default port numbers in your Oracle Application Server 10.1.3.x environment, you must manually change those port numbers to appropriate port numbers. When you upgrade a WebCenter application, port changes are not made to registrations of portlet producers other than preconfigured portlet producers.

15.3.3.6 Redeploying Your Applications

After upgrading your application to Oracle WebCenter 11g, you must recompile the application. To prepare your application for redeployment, create a WebLogic Managed Server instance and provision it with a required set of shared libraries. Also, create and register the Metadata Service MDS repository for your application on the WebLogic Domains Administration Server instance. You must then redeploy the application and verify that it has been deployed properly. For information, see the Deploying WebCenter Applications chapter in Oracle Fusion Middleware Administrators Guide for Oracle WebCenter.

15.4 Upgrading Portlet Producers

If your WebCenter 10.1.3.x application uses portlets, then in addition to upgrading your WebCenter consumer application, you may need to upgrade portlet producers to Oracle WebCenter 11g. Table 15–2 lists the tasks involved in upgrading portlet producers used by your WebCenter 10.1.3.x applications. 15-16 Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF

15.4.1 Determining WebCenter Consumer Application and Portlet Producer Compatibility

In most cases, WebCenter consumer applications or portlet producer applications deployed to Oracle Application Server 10.1.3.x are compatible with applications upgraded to Oracle Fusion Middleware 11g. For example, a WebCenter consumer application that has been upgraded and deployed to Oracle WebLogic Server in Oracle Fusion Middleware 11g may still use portlets from PDK-Java producer applications running on Oracle Application Server 10.1.3.x. Oracle Fusion Middleware 11g supports backward compatibility for WebCenter consumer applications and portlet producer applications. Based on the compatibility supported, you may decide to upgrade only your WebCenter consumer applications, only portlet producer applications, or both. Table 15–3 lists the compatibility between different versions of WebCenter consumer applications and portlet producer applications. Table 15–3 shows that a WebCenter 10.1.3.x consumer application and a PDK-Java or a WSRP 1.0 WebCenter 11g portlet producer application are compatible. In such a case where backward compatibility is supported, you may choose not to upgrade your WebCenter 10.1.3.x consumer application to Oracle WebCenter 11g. The table further shows that a WebCenter 11g consumer application and a PDK-Java or a WSRP 1.0 WebCenter 10.1.3.x portlet producer application are compatible. In such a case, you may choose not to upgrade your 10.1.3.x portlet producer application. Table 15–2 Task Flow for Upgrading Portlet Producers Task SubTask When to Perform the Task? Preparing Your Application Determining WebCenter Consumer Application and Portlet Producer Compatibility Always Upgrading Your Portlet Producer Application Upgrading Portlet Producers Created in JDeveloper If your WebCenter application contains portlets provided by portlet producers developed in JDeveloper 10.1.3.x. Upgrading Portlet Producers Created Outside of JDeveloper If your WebCenter application contains portlets provided by portlet producers developed outside of JDeveloper. Upgrading Preconfigured Portlet Producers If your WebCenter application contains portlets provided by preconfigured portlet producers. Performing Post Upgrade Tasks Migrating Customizations If your WebCenter application contains portlets other than the portlets provided by preconfigured portlet producers. Redeploying a Portlet Producer Application Always