Oracle Portal, Forms, Reports, and Discoverer Post-Upgrade Tasks 4-3
3.
Modify the existing jdbcportletPrefs data source so it references your existing preference store. You can use the Oracle WebLogic Server Administration
Console to perform this task.
For more information, see Create JDBC data sources in the Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help. Specifically,
you must modify the database connection details on the Connection Properties page for the data source in the Administration Console.
4.1.1.4 Oracle Portal Post-Upgrade Tasks If You Are Not Using a Database-Based Preference Store
If you are not using a databased-based preference store, you can use the Oracle WebLogic Server Administration Console to remove the jdbcportletPrefs data
source.
For more information, see Delete JDBC data sources in the Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help.
4.1.1.5 Oracle Portal Post-Upgrade Tasks If You Are Using One or More File-Based Store
If you are using one or more file-based preference stores for WSPR or PDK-Java applications, then use the Preference Store Migration and Upgrade Utility to migrate
each of your existing Oracle Portal 10g preference stores to the an Oracle Portal 11g file-based preference store.
For more information, see Using the PDK-Java Preference Store Migration and Upgrade Utility in the Oracle Fusion Middleware Administrators Guide for Oracle Portal.
4.1.1.6 Creating a New Database Preference Store for PDK-Java or WSRP Applications
A preference store is a mechanism for storing information like user preference data, portletprovider settings, or even portlet data, while using Oracle Portal.
The information stored in the preference store is persistent in the sense that, even if you log out and log back in later, you can still access previously saved preferences. The
preference store maintains the user preference information and invokes the user preferences whenever the user logs in again.
PDK-Java provides the PrefStorePersonalizationManager, which uses a PreferenceStore implementation to persist personalized data. Currently, PDK-Java has
two PreferenceStore implementations: DBPreferenceStore and FilePreferenceStore. The DBPreferenceStore persists data using a JDBC
compatible relational database and FilePreferenceStore persists data using the file system.
For more details of these implementations, refer to the Javadoc on the Oracle Technology Network OTN, by clicking Java Doc API on the Portlet Development
page available at:
http:www.oracle.comtechnologyproductsiasportalportlet_development_ 10g1014.html
Example 4–1 shows some sample SQL code that demonstrates how you can create a
preference store table in an Oracle database. For more information about using preference stores, refer to the following resources:
4-4 Oracle Fusion Middleware Upgrade Guide for Oracle Portal, Forms, Reports, and Discoverer
■
Enhancing Java Portlets in the Oracle Fusion Middleware Developers Guide for Oracle Portal
■
Setting Up a Preference Store in the Oracle Fusion Middleware Developers Guide for Oracle WebCenter
Example 4–1 Sample SQL Code for Creating a New Oracle Portal Preference Store
CREATE TABLE JPDK_PREFERENCE_STORE2 PATH_TYPE VARCHAR2 60 NOT NULL,
REFERENCE_PATH VARCHAR2 250 NOT NULL, SEARCH_PATH VARCHAR2 250 NOT NULL,
DATA_CLASS VARCHAR2 250, LONG_VALUE LONG RAW,
CONSTRAINT JPS2_PK PRIMARY KEY REFERENCE_PATH, PATH_TYPE ;
CREATE INDEX JPDK_PATH_TYPES2 ON JPDK_PREFERENCE_STORE2PATH_TYPE;
CREATE INDEX JPDK_SEARCH_PREFS2 ON JPDK_PREFERENCE_STORE2SEARCH_PATH;
4.1.2 Upgrading the PDK-Java Sample Application and Its Customizations from Oracle Portal 10g to 11g
