Portlet Tag Changes Attribute Changes

Additional Oracle WebCenter Upgrade Details 16-9 Figure 16–2 Content Repository Connection Configuration of an Upgraded Application Figure 16–3 Public Credentials Specified for an External Application 16-10 Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF

16.3 Preconfigured Portlet Producers: Customization Store’s Location

By default, customizations related to preconfigured portlet producers are stored at the following location in Oracle WebCenter 11g: 11g_jdev_install_dir jdeveloperportalportletdata You may choose to store portlet customizations at a location different. This section describes how to change the location of a customizations store for various preconfigured portlet producers. It contains the following subsections: ■ WSRP Portlet Producers ■ Web Clipping Portlet Producer ■ OmniPortlet and other PDK-Java Portlet Producers ■ OmniPortlet Repository Changes

16.3.1 WSRP Portlet Producers

To specify a file preference store location for portlet customizations of your WSRP portlet producers, update your producers WEB-INFweb.xml with the following entry: env-entry env-entry-nameoracleportalwsrpserverfileStoreRootenv-entry-name env-entry-typejava.lang.Stringenv-entry-type env-entry-value{YOUR_PORTLET_DATA_PATH}env-entry-value env-entry Where YOUR_PORTLET_DATA_PATH refers to the path where you want to store portlet customizations. If you want to use a database preference store for your WSRP portlet producer, then you must set up the database preference store. For information, see the Setting Up a Preference Store section in the Oracle Fusion Middleware Developers Guide for Oracle WebCenter.

16.3.2 Web Clipping Portlet Producer

To specify the Web Clipping customization store, update the following entry in mds-config.xml: property name=metadata-path value={YOUR_PORTLET_DATA_PATH} For information about Web Clipping portlet configuration, see the Web Clipping Portlet Configuration Tips section in the Oracle Fusion Middleware Developers Guide for Oracle WebCenter. Note: If your application contains a content repository connection that uses credentials, during application upgrade if there is a problem in retrieving credentials from the credential store or in creating the external application, you must edit the upgraded content repository connection. In the Edit Content Repository Connection wizard, you must select External Application as the authentication method, and then create an external application with the required credentials.