15 Oracle Application Server Portal

This chapter describes issues associated with OracleAS Portal. It includes the following topics:

• Section 15.1, "Portlet and Provider Issues and Workarounds"

• Section 15.2, "Documentation Errors"

15.1 Portlet and Provider Issues and Workarounds

This section describes issues and workarounds related to OmniPortlet, Web Clipping, Simple Parameter Form, Page portlet, and WSRP providers. This section includes the following topic:

• Section 15.1.1, "Error Configuring OC4J Standalone for OmniPortlet Deployment"

15.1.1 Error Configuring OC4J Standalone for OmniPortlet Deployment

As part of the procedure to deploy OmniPortlet in a multiple middle-tier environment, you are required to create a database preference store to store the OmniPortlet preference information.

If you installed OC4J release 10.1.3, and added a data-source entry in the data-sources.xml file, then you will get errors. This is because data sources are defined differently in OC4J release 10.1.3 due to a change in the format of the data-sources.xml file.

To configure OC4J release 10.1.3 for OmniPortlet deployment, perform the following steps:

1. Add a new entry in the data-sources.xml file as described in step 8 under Section 6.3.2, "Configuring OC4J Standalone" in Oracle Application Server Portal Developer's Guide.

2. Edit the provider.xml file located in the directory, ORACLE_HOME/j2ee/OC4J_Portal/applications/portalTools/omniPortlet/WEB-INF/providers/omniPortlet. Edit the preferenceStore tag as shown in bold:

   
   <provider class="oracle.webdb.reformlet.ReformletProvider"> 
   
      <vaultId>0</vaultId> 
   
      <session>true</session> 
   
      <preferenceStore class="oracle.portal.provider.v2.preference.DBPreferenceStore"> 
   
         <name>omniPortletprefStore</name> 
   
         <connection>jdbc/PooledConnection</connection> 
   
      </preferenceStore>
   
   
   
   

3. Restart OC4J.

15.2 Documentation Errors

This section describes known errors in OracleAS Portal documentation. It includes the following topic:

• Section 15.2.1, "Edit Defaults Mode"

15.2.1 Edit Defaults Mode

In Oracle Application Server Portal Developer's Guide, the last list item under Section 3.2.6, "Edit Defaults Mode" reads as follows:

Configure OmniPortlet to use the DBPreferenceStore, and follow the steps in Section "5.3.6 Step 6: Configure Portal Tools and Web Providers (Optional)" of Oracle Application Server Portal Configuration Guide.

These steps in Oracle Application Server Portal Configuration Guide are applicable only for OC4J versions prior to 10.1.3. This list item should read as follows:

Configure OmniPortlet to use the database preference store. Depending on the version of OC4J that you have installed, perform either of the following:

• If you have installed an OC4J release prior to 10.1.3, then perform the steps described in section "5.3.6 Step 6: Configure Portal Tools and Web Providers (Optional)" of Oracle Application Server Portal Configuration Guide.

• If you installed OC4J release 10.1.3, then perform the following steps:

  1. Add a new entry in the data-sources.xml file as described in step 8 under Section 6.3.2, "Configuring OC4J Standalone" in Oracle Application Server Portal Developer's Guide.

  2. Edit the provider.xml file located in the directory, ORACLE_HOME/j2ee/OC4J_Portal/applications/portalTools/omniPortlet/WEB-INF/providers/omniPortlet. Edit the preferenceStore tag as shown in bold:

     
     <provider class="oracle.webdb.reformlet.ReformletProvider"> 
     
        <vaultId>0</vaultId> 
     
        <session>true</session> 
     
        <preferenceStore class="oracle.portal.provider.v2.preference.DBPreferenceStore"> 
     
           <name>omniPortletprefStore</name> 
     
           <connection>jdbc/PooledConnection</connection> 
     
        </preferenceStore>
     
     
     
     

  3. Restart OC4J.