Skip Headers
Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for Microsoft Windows (64-Bit) on Intel Itanium
B25335-02
  Go To Documentation Library
Home
Go To Table Of Contents
Contents

Previous
Previous
Next
Next
 

8 Oracle Application Server Portal

This chapter describes issues and workarounds related to Oracle Application Server Portal. It includes the following topics:

8.1 OracleAS Portal 10g Release 2 (10.1.2) Issues and Workarounds

This section describes issues and workarounds related to OracleAS Portal 10g Release 2 (10.1.2). It includes the following topics:

8.1.1 General Issues and Workarounds

This section describes general issues and their workarounds in OracleAS Portal. It includes the following topics:

8.1.1.1 Error in portal.log File After Installing OracleAS Metadata Repository

After installing OracleAS Metadata Repository using OracleAS Metadata Repository Creation Assistant, the following error is recorded in the portal.log file:

Error while opening file:
/private1/iasinst/Repca_050712/portal/admin/plsql/lib/sitedb.jar

Exception java.io.FileNotFoundException:
/private1/iasinst/Repca_050712/portal/admin/plsql/lib/sitedb.jar

This error does not affect the installation process and can be ignored.

8.1.1.2 OracleAS Portal Login Fails After OracleAS Cold Failover Cluster (Middle Tier) Configuration

If you configure an OracleAS Cold Failover Cluster (Middle Tier) that resides on the same node as the infrastructure associated with the middle tier from which the portal is running, then you may see the following error when you log in to OracleAS Portal:

Internal error (WWC-00006)
Unexpected error encountered in wwsec_app_priv.process_signon
(User-Defined Exception) (WWC-41417)

The Oracle Internet Directory host name in the Portal Dependency Settings file, iasconfig.xml, may incorrectly specify the host name of the new middle tier. As a workaround, perform the following steps:

  1. Update the IASInstance element in the iasconfig.xml file so that the Host (of the IASInstance element associated with the Oracle Internet Directory component) is that of the Oracle Internet Directory host.

  2. Run the ptlconfig tool to update the Oracle Internet Directory settings, as shown in the following example:

    ptlconfig -dad <dad> -pw <portal schema password or Oracle Internet Directory password> -oid
    
    

For more information about updating the iasconfig.xml file and running ptlconfig, refer to Appendix A "Using the Portal Dependency Settings Tool and File" in Oracle Application Server Portal Configuration Guide.

8.1.2 Upgrade Issues and Workarounds

This section describes upgrade-related issues and their workarounds in OracleAS Portal. It includes the following topic:

8.1.2.1 Configuring OracleAS Portal After Upgrade

If OracleAS Portal is not configured in the source Oracle home before you upgrade, then it will remain unconfigured even after the upgrade. You can configure OracleAS Portal after upgrading the middle tier or after upgrading the OracleAS Metadata Repository, by performing the following steps:

  1. Modify the port entries in the ptlem script:

    %ORACLE_HOME%\assistants\opca\ptlem.bat

    You need to update the following port values:

    • http_port - Oracle HTTP Server port

      (Get this value from %ORACLE_HOME%\Apache\Apache\conf\httpd.conf)

    • wc_invalid - OracleAS Web Cache invalidation port

    • wc_admin - OracleAS Web Cache administration port

    • em_port - Application Server Control port

    Use Oracle Enterprise Manager 10g to obtain port values for wc_invalid, wc_admin, and em_port as follows:

    1. In your browser, enter the URL for the Application Server Control Console.

    2. Enter the ias_admin login credentials that you used for the destination Oracle home.

    3. In the Standalone Instances section, click the name of the destination middle-tier instance.

    4. Click the Ports tab.

      The Ports page displays the port values you require.

  2. Use Oracle Enterprise Manager 10g Application Server Control Console to configure OracleAS Portal.


    See Also:

    Section 7.2.2 "Using Application Server Control Console to Configure OracleAS Portal" in the Oracle Application Server Portal Configuration Guide.

  3. Run ptlconfig to configure the portal schema in the OracleAS Metadata Repository with the upgraded middle-tier instance as follows:

    DESTINATION_ORACLE_HOME\portal\conf\ptlconfig -dad <portal_dad>
    
    

Note:

If you configure OracleAS Portal using Application Server Control, without updating the ports (in ptlem.sh or ptlem.bat), then the iasconfig.xml and targets.xml files will contain incorrect port entries; therefore, the portal will not be accessible. To reconfigure OracleAS Portal with correct port values and make it accessible, you must first enter correct port values in iasconfig.xml and targets.xml, and then configure OracleAS Portal.

Updating the targets.xml File

To update DESTINATION_ORACLE_HOME\sysman\emd/targets.xml:

  1. Modify the port entries in DESTINATION_ORACLE_HOME\assistants\opca\ptlem.bat as mentioned earlier.

  2. Back up DESTINATION_ORACLE_HOME\sysman\emd\targets.xml.

  3. Remove the target entry for the portal you are reconfiguring. You must remove the complete target entry for <Target TYPE = "oracle_portal">. For example,

    <Target TYPE="oracle_portal" 
      ....
    </Target>
    
    

    Before removing the target entry for this portal, ensure that this target contains the property <Property NAME="portal_DAD" VALUE="portal"/> and its OracleHome property maps to the destination middle tier.

  4. Save the file.

  5. Set the value of the ORACLE_HOME environment variable to DESTINATION_ORACLE_HOME.

  6. Run the script DESTINATION_ORACLE_HOME\assistant\opca\ptlem.bat.

  7. Check the log file, DESTINATION_ORACLE_HOME\assistant\opca\install.log, for errors.

Updating the iasconfig.xml File

To update DESTINATION_ORACLE_HOME\portal\conf\iasconfig.xml:

  1. Update the port values for the WebCacheComponent and EMComponent elements that the portal instance you are reconfiguring refers to. You can obtain the upgraded port values for all the following ports from Oracle Enterprise Manager 10g, as described earlier.

    • Update ListenPort, InvalidationPort, and AdminPort in WebCacheComponent with WebCache Listen Port, Web Cache Invalidation, and WebCache Admin Port respectively.

    • Update ConsoleHTTPPort in EMComponent with Application Server Control Port.

  2. Run ptlconfig to configure the portal schema in the OracleAS Metadata Repository with the upgraded middle-tier instance as follows:

    DESTINATION_ORACLE_HOME\portal\conf\ptlconfig -dad <portal_dad> [-pw <portal schema password>]
    
    

For more information on iasconfig.xml and ptlconfig, refer to Oracle Application Server Portal Configuration Guide.

8.1.2.2 OracleAS Portal Users Cannot Log on to Oracle Ultra Search

OracleAS Portal users cannot log on to manage Oracle Ultra Search if the OracleAS Metadata Repository is prepared by a 9.2.0.x database with OracleAS Metadata Repository Creation Assistant installed.

The workaround is to log on as a database user to manage Oracle Ultra Search, or invoke the following PL/SQL API to grant orcladmin super-user privileges.

Log on as WKSYS.

BEGIN
  WK_ADM.GRANT_SYSADMIN(
  <orcladmin dn>,
  1,
  null,
  <subscriber dn>
  )
EXCEPTION WHEN OTHERS THEN WK_ERR.RAISE;
END;

Here is an example:

BEGIN
WK_ADM.GRANT_SYSADMIN('orcladmin',1,null,'dc=oracle,dc=com');
EXCEPTION WHEN OTHERS THEN WK_ERR.RAISE;
END;
/ 


Note:

The wk_adm_code from 9.2 does not support the fully qualified name and, therefore, generates an ORA-6502 error if you use the following string:
cn=orcladmin,cn=users,dc=oracle,dc=com

To avoid this error, specify only orcladmin as the user ID rather than the complete string.


8.1.3 User Interface Issues and Workarounds

This section describes User Interface-related issues and their workarounds in OracleAS Portal. It includes the following topics:

8.1.3.1 Issue Adding Regions to Pages Displayed in the Generic Page Portlets

When you add a region to a page displayed in a generic page portlet, the new region is not displayed immediately as expected. As a workaround, manually invalidate the cache by clicking the Clear Cache link (Access tab) for the page containing the generic page portlet.

8.1.3.2 Portlets on Subpages Not Displayed

If a page displays a page portlet (Portlet A) with a subpage link to a page with tabs and portlets (Portlet B), the portlets under tabs in Portlet B are not displayed if you use the subpage link to navigate to Portlet B, from Portlet A. This is a known issue.

8.1.3.3 Cannot Set Privileges Using List View on Pages Inheriting Privileges from Parent or Template

If you use the List View to set access privileges for one or more pages, then privileges will not be set on pages inheriting privileges from a parent page or template. As a workaround, change the privileges for such pages individually, that is, using the Access tab for the subpage.

8.1.4 Export and Import Issues and Workarounds

This section describes export and import issues and their workarounds in OracleAS Portal. It includes the following topic:

8.1.4.1 Export and Import Does Not Support Reports Server Components

If you include Reports Server Components within a transport set, then they are deleted on export and import. In addition, do not configure the Oracle Reports item type in any page groups intended for export and import. If you do, then the following error is displayed when you try to configure item types in the imported page group (by clicking the Content Type and Classifications Edit link on the Configure tab for the page group):

Internal error (WWC-00006)
Unexpected error - User-Defined Exception (WWC-35000)
Unexpected error - ORA-01403: no data found (WWC-35000)

8.1.5 Portlet and Provider Issues and Workarounds

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

8.1.5.1 Using OmniPortlet Web Page Data Source After Cloning

If you clone a middle-tier instance, then you must perform the following steps before you can use OmniPortlet Web Page Data Source:

  1. Open the web.xml file.

    %ORACLE_HOME%\j2ee\OC4J_Portal\applications\portalTools\omniPortlet\WEB-INF\web.xml
    
    
  2. If the usePort context parameter is present, then set it to the Oracle HTTP Server port of the cloned target instance. This port number is specified in %ORACLE_HOME%\install\portlist.ini.

  3. Restart the OC4J_Portal instance.

    %ORACLE_HOME%\opmn\bin\opmnctl stopproc process-type=OC4J_Portal
    %ORACLE_HOME%\opmn\bin\opmnctl startproc process-type=OC4J_Portal 
    
    

8.1.5.2 Issue Adding or Deleting Portlets on Page Portlets

If you have the Customize Portlets (Full) privilege on two pages, Page A and Page B, then you cannot add or delete portlets on Page B when Page B is displayed as a page portlet on Page A. However, you can add or delete portlets when pages A and B are displayed as individual pages. This is a known issue.

8.1.6 PDK Issues and Workarounds

Oracle Application Server Portal Developer Kit (PDK) version 10.1.2 is included with the Portal and Wireless installation. Release notes for the PDK-Java and PDK-PL/SQL can be found at the following middle-tier ORACLE_HOME locations:

  • PDK-Java: ORACLE_HOME/portal/pdkjava/v2/pdkjava.v2.releasenotes.html

  • PDK-PL/SQL: ORACLE_HOME/portal/pdkjava/v2/pdkplsql.release.notes.html

Latest Version of OracleAS PDK

New versions of the OracleAS PDK are released periodically providing new features, new APIs, and additional documentation. To take advantage of all the latest features, download the latest PDK from the PDK downloads page on the Oracle Technology Network (OTN) at http://www.oracle.com/technology/products/ias/portal/pdk.html.

Release notes for the latest OracleAS PDK version are available on Oracle Application Server Portal on OTN and also in these PDK download locations:

  • pdk\plsql\pdkplsql.release.notes.html

  • pdk\jpdk\v2\pdkjava.v2.release.notes.html

This section includes the following PDK-related issues and workarounds in OracleAS Portal:


See Also:

Section 8.1.8.1.12, "Exposing Your Application as a Web Service" for issues related to adding a custom JPS provider.

8.1.6.1 Support for WSRP and JSR 168

OracleAS Portal supports the building of Java Specification Request (JSR) 168 portlets. OracleAS Portal does not yet support consumption of Web Services for Remote Portlets (WSRP)-enabled portlets. Currently, you can only test your JSR 168 portlets against the hosted OracleAS Portal Verification Service at http://portalstandards.oracle.com/ or the Developers Preview for OracleAS Portal available for download. Note that both the Developers Preview and the hosted OracleAS Portal Verification Service are provided for development purposes only and, should not be used for production systems.

8.1.7 Globalization Support Issues and Workarounds

This section describes issues and workarounds related to Globalization Support in OracleAS Portal. It includes the following topics:

8.1.7.1 Oracle Text Searching Limitation (Text Files and HTML Files)

In some non-ASCII character set environments, you are unable to search non-ASCII character content of plain text files and HTML files.

You can search plain text and HTML files if the document character set is the same as the database character set.

8.1.7.2 Text Entry Always Right to Left in BiDi Languages

The direction of all text areas and fields is right to left (RTL). However, you may want some text areas to work left to right (LTR). Internet Explorer users can change this by pressing the left hand side Ctrl and Shift keys.

8.1.7.3 Non-ASCII Character Limitations in OracleAS Portal

This section discusses non-ASCII character limitations when working with OracleAS Portal:

  • Non-ASCII XML data is not displayed correctly in the XML Portlet. To display non-ASCII XML data, use OmniPortlet, which has this functionality.

  • If you use non-ASCII characters in Web Provider Display Names, then they are not displayed correctly. Similarly non-ASCII characters used in Provider Group Display Names cannot be displayed.

  • In Web Folders, if you change the name of a portal page to use non-ASCII characters, then an error message displays.

  • In some non-ASCII character set environments, you cannot use the Browse Users or Browse Groups list of values to select a user or group name. As a workaround, you can enter the user or group name manually.

  • When you copy and paste an item URL containing non-ASCII characters from one browser Location or Address field into another, you may not be able to access the item if your login credentials have not been authenticated through OracleAS Single Sign-On.

    As a workaround, log in to the portal before you access the item and copy the item URL.

8.1.7.4 Non-ASCII Character Limitations in Oracle Instant Portal

To use Oracle Instant Portal in an environment that supports non-ASCII character sets, you must use the UTF8 or AL32UTF8 database character set.

8.1.7.5 Shared Type Objects Cannot Be Exposed in Non-English Page Group

Shared type objects (page types and item types) always have English as the default language. If you create a page group in a language other than English, then a shared type cannot be made available to the page group unless a translation exists for the shared type in the default language of the page group.

To create the translation, follow these steps:

  1. Enable the language for the Shared Objects page group.

    For details, see Oracle Application Server Portal User's Guide - Section 4.6.1 Creating a Translation.

  2. Switch to the language in the Set Language portlet.

  3. Edit the page type or item type while the session language is set to the non-English language.

    This automatically creates a translation of the type in that language.

You can now make the shared type available to the non-English page group.

8.1.7.6 Translations Lost When Item Versioning Is Enabled

If versioning is enabled and the page group has two or more translations (for example, the default language is English and translations are enabled for German and French), then adding a translation as a new version does not display the other translation. For example, if you add or edit a French translation as a new version, then the German translation is no longer visible to the page viewers. As a workaround, when multiple translations are required, disable item versioning, or use the "overwrite" mode when adding or updating translations.

8.1.8 Documentation Errata

This section describes known errors and omissions in OracleAS Portal documentation:

8.1.8.1 Documentation Errors

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

8.1.8.1.1 Editing Item/Portlet Properties

The online help states that clicking the Edit icon enables you to edit the properties of the item or portlet. While this is true for items, clicking this icon next to a portlet takes you to the Edit Defaults page. To edit the portlet instance attributes (such as display name), click the Actions icon, then click the Edit Portlet Instance link.

8.1.8.1.2 Editing Pending Items

Online help for Pending Items: Preview (cawkpend.htm) incorrectly states that the submitter can continue to edit a pending item if it has not yet been approved by the first approver in the approval process.

8.1.8.1.3 Referencing the Current Version of Images

Image attributes can reference an uploaded source image. The documentation currently states:

To reuse an image that has been uploaded to OracleAS Portal, enter its internal name (not file name) without a path in this field, for example, enter 1645.GIF.

If you are versioning the referenced image item, and you use the internal file name in the reference (for example, 1645.gif), then the reference does not use a new, current version of the image if one is created. The image reference continues to show the original version. For example:

  1. In an image attribute, reference an image item by its internal file name, for example, 1645.gif.

  2. Update the image item and create a new version. The new version is given a new internal file name (for example, 1705.gif).

  3. The image attribute still refers to 1645.gif, it has not been updated to refer to the new version of the image.

Therefore, only use the internal file name if you are not using versioning, or if you want the reference to always point to the original version, even if it is no longer the current version.

If you are using versioning and you always want to show the current version, then use the durable link to the image item instead of the internal file name. The durable link always picks up the latest version of the image. So, instead of entering 1645.gif, enter:

/pls/<DAD>/url/item/<GUID>

This is the relative URL format of a durable link. For example:

/pls/portal/url/ITEM/A47D41ECA23648A9E030007F0100118A

Relative URLs should always be used in case the host or domain name changes, or the content is exported to another site. For more information on durable URLs, refer to section "Understanding Page and Item URLs" in Oracle Application Server Portal User's Guide.

8.1.8.1.4 Working in List View

List View functionality is documented in the online help topic Page Edit Mode: List View (pobpglst.htm). Some information in this topic is incorrect:

Button: Actions List - Options Enable ILS and Disable ILS are not available.

Button: Find - The search is not case-sensitive.

Subitems - The online help states that the List View does not display sub-items. This is correct, however, sub-items will be listed in search results if they meet the search criteria.

Also, note that in List View, pages based on templates do not show any tabs or items belonging to the template. You must click the Edit Template link to see tabs and items on a template. Therefore, when editing the page in List View, you cannot add items to tabs that are inherited from the template. Likewise, if items are added to these tabs when editing the page using another edit view (for example, Graphical View), you do not see these items in List View.

If you are using Netscape 4.8, then you may notice that version information is incorrectly displayed under the Description column. This is not a problem in Internet Explorer.

8.1.8.1.5 Unpublished Items Section Documented Incorrectly

Online help for the Edit Page Group Items tab (sbrsmit.htm) incorrectly refers to the Expired and Deleted Items section and the Display Expired and Deleted Items and Retain Expired and Deleted Items check boxes. These should be, respectively, the Unpublished Items section and the Display Unpublished Items In Edit Mode and Retain Deleted Items check boxes. Refer to the text on the page itself for details on how to use these check boxes.

8.1.8.1.6 Item Level Security and Page Caching

The online help incorrectly states that when item-level security (ILS) is enabled, page caching is automatically disabled. Page caching is not disabled when ILS is enabled.

8.1.8.1.7 User Profile Help Incorrect

Online help for the Edit Portal User Profile tabs, Preferences (secumed1.htm) and Privileges (secgmed3.htm), incorrectly states that there are Reset to Defaults buttons on these pages. This option is not available.

8.1.8.1.8 Defining a Display Style for Results from a Custom Search

Online help for Edit Defaults: Custom Search - Results Display page (sbrrsres.htm) incorrectly states that style and attribute settings apply only to items returned in search results. The Style and Attribute settings (section Which style and attributes should be used to render the search results?) apply to both items and pages.

8.1.8.1.9 Applying Background Color or Image to Page Portlets

If you want page portlets (including navigation pages) to display a background color or background image, then follow these steps:

  1. Ensure that the navigation page uses its own style when published as a portlet, that is, do not select Use Style Of Page On Which Portlet Is Placed in the page properties.

  2. In the style for the container page (the page containing the portlet), set Portlet Body Color to null (no value). This step is missing from the documentation.

8.1.8.1.10 Registering JSR Portlets

The Oracle Application Server Portal Configuration Guide provides instructions on how to register a JSR 168 portlet in a local instance of OracleAS Portal, in section "Registering and Viewing Your Portlet". These instructions do not apply to the current production release of the product, but can be used for the Developer's Preview release until the production WSRP-enabled OracleAS Portal is released. Please note that the Developer's Preview is provided for development purposes only, and should not be used for production systems.

8.1.8.1.11 Corporate Page Groups No Longer Installed

In some sections of the documentation, you may find reference to the Corporate Pages page group. This page group is no longer installed with OracleAS Portal and you may disregard any mention of it in the documentation. However, if you are upgrading an existing OracleAS Portal instance which contained the Corporate Pages page group, then it will not be removed by the upgrade.

8.1.8.1.12 Exposing Your Application as a Web Service

Section "Exposing Your Application as a Web Service" in the Oracle Application Server Portal Developer's Guide has an inaccurate step and a missing step. The section should read as follows:

Before you deploy your WAR file to the Oracle Application Server, you must perform the following steps:

  1. Update your web.xml file. These entries are required to expose your application as a Web Service as soon as it is deployed.

    <web-app>
     <description>Empty web.xml file for Web Application</description>
      <session-config>
       <session-timeout>35</session-timeout>
      </session-config>
     <mime-mapping>
      <extension>html</extension>
      <mime-type>text/html</mime-type>
     </mime-mapping>
     <mime-mapping>
      <extension>txt</extension>
      <mime-type>text/plain</mime-type>
     </mime-mapping>
     <filter>
      <filter-name>portletfilter</filter-name>
      <filter-class>oracle.webdb.wsrp.server.ContextFilter</filter-class>
     </filter>
     <filter-mapping>
      <filter-name>portletfilter</filter-name>
      <servlet-name>portletjaxrpc</servlet-name>
     </filter-mapping>
     <filter-mapping>
      <filter-name>portletfilter</filter-name>
      <servlet-name>portletresource</servlet-name>
     </filter-mapping>
     <servlet>
      <servlet-name>portletdeploy</servlet-name>
    <servlet-class>oracle.webdb.wsrp.server.deploy.PortletDeployServlet</servlet-class>
      <load-on-startup>1</load-on-startup>
     </servlet>
     <servlet>
      <servlet-name>portletjaxrpc</servlet-name>
      <servlet-class>com.sun.xml.rpc.server.http.JAXRPCServlet</servlet-class>
      <init-param>
         <param-name>configuration.file</param-name>
         <param-value>/WEB-INF/WSRPService_Config.properties</param-value>
      </init-param>
     </servlet>
     <servlet>
      <servlet-name>portletresource</servlet-name>
      <servlet-class>oracle.webdb.wsrp.server.ResourceServlet</servlet-class>
     </servlet>
     <servlet-mapping>
      <servlet-name>portletjaxrpc</servlet-name>
      <url-pattern>/portlets*</url-pattern>
     </servlet-mapping>
     <servlet-mapping>
      <servlet-name>portletresource</servlet-name>
      <url-pattern>/portletresource*</url-pattern>
     </servlet-mapping>
    </web-app>
    
    
  2. When adding a custom JPS producer to the Oracle Application Server OC4J instance, you also must add the following library paths in your application.xml file:

    <library path="%ORACLE_HOME%\portal\jlib\commons-logging.jar"\>
    <library path="%ORACLE_HOME%\portal\jlib\dom4j.jar"\>
    <library path="%ORACLE_HOME%\portal\jlib\jaxrpc-api.jar"\> 
    <library path="%ORACLE_HOME%\portal\jlib\jaxrpc-ri-patched.jar"\>
    <library path="%ORACLE_HOME%\portal\jlib\namespace.jar"\>
    <library path="%ORACLE_HOME%\portal\jlib\relaxngDatatype.jar"\>
    <library path="%ORACLE_HOME%\portal\jlib\ptlshare.jar"\>
    <library path="%ORACLE_HOME%\portal\jlib\saaj-api.jar"\>
    <library path="%ORACLE_HOME%\portal\jlib\saaj-ri.jar"\>
    <library path="%ORACLE_HOME%\portal\jlib\wsrp-common.jar"\>
    <library path="%ORACLE_HOME%\portal\jlib\wsrp-container.jar"\>
    <library path="%ORACLE_HOME%\portal\jlib\oracle-portlet-tags.jar"\>
    <library path="%ORACLE_HOME%\lib\xml.jar"\>
    <library path="%ORACLE_HOME%\lib\xmlmesg.jar"\>
    <library path="%ORACLE_HOME%\lib\xmlparserv2.jar"\>
    <library path="%ORACLE_HOME%\portal\jlib\xsdlib.jar"\>
    
    
8.1.8.1.13 Changes Required in the Steps to Configure Security in OracleAS Portal

The chapter titled, "Securing OracleAS Portal" in the Oracle Application Server Portal Configuration Guide has the following known errors:

  • Step 1 in subsection "Configuring SSL to OracleAS Single Sign-On Using SSLConfigTool" under Section 6.3.2.1.2, "SSL to OracleAS Single Sign-On", currently states the following:

    Enter n when prompted by the script to configure your site to accept browser requests using the SSL protocol.

    This task must not be performed in step 1, as you will not be prompted for any input when you use the -config_w_default option. This task must be performed in step 3 in the same procedure where you run SSLConfigTool in the middle-tier Oracle home.

  • Step 2 in subsection "Configuring SSL to OracleAS Web Cache Using SSLConfigTool" under Section 6.3.2.1.3, "SSL to OracleAS Web Cache", currently states the command to run SSLConfigTool as shown:

    SSLConfigTool.bat -config_w_default -opwd <orcladmin_pwd>
    
    

    However, the command must be used as follows:

    SSLConfigTool.bat -config_w_prompt -ptl_inv_pwd <ptl_inv_pwd> -opwd <orcladmin_pwd>
    
    
  • Step 2 in subsection "Configuring SSL Throughout OracleAS Portal Using SSLConfigTool" under Section 6.3.2.1.4, "SSL Throughout OracleAS Portal" currently states the following:

    Enter the following values when prompted by the script:

    • y, when prompted to configure your site to accept browser requests using the SSL protocol.

    • y, when asked if your Oracle HTTP Server accepts requests in SSL protocol.

    This task must not be performed in step 2, as you will not be prompted for any input when you use the -config_w_default option. This task must be performed in step 3 where you run SSLConfigTool in the middle-tier Oracle home.

  • The following step is missing in subsection "Configuring SSL to OracleAS Web Cache Using SSLConfigTool" under Section 6.3.2.1.3, "SSL to OracleAS Web Cache":

    Enable SSL on the OracleAS Infrastructure that has Identity Management installed and then run SSLConfigTool in the infrastructure Oracle home, as shown in the following example, for Windows:

    SSLConfigTool.bat -config_w_default -opwd <orcladmin_pwd>
    
    

    Where:

    • config_w_default is used to run the tool in silent mode using the values specified in the portlist.ini and ias.properties files.

    • opwd is the Oracle administrator password. If no password is specified, then you will be prompted to enter the password.

    Perform this step after step 1.

8.1.8.1.14 Portal Upgrade Error and Warning Messages Should Be Prefixed with WWU-

The Portal upgrade error and warning messages described in Chapter 6, "UPG-00001 to UPG-26001" of the Oracle Application Server Portal Error Messages Guide 10g Release 2 (10.1.2) are incorrectly prefixed with UPG-. These error and warning messages should be prefixed with WWU-.

8.1.8.2 Additional Documentation

This section describes known omissions and additions to the OracleAS Portal documentation. It includes the following topics:

8.1.8.2.1 Inaccurate Data in Log Registry Records

Online help describing Log Registry records (wvlogadm.htm) lists the set of actions that are logged. Since the introduction of OracleAS Web Cache, some of the actions logged in OracleAS Portal Activity Log tables have become inaccurate. Specifically, these actions are View, Execute, Show, and Perform. However, since all other actions logged are still accurate, the Activity Log tables and views still remain in the OracleAS Metadata Repository.

8.1.8.2.2 Expired Items Remain Visible in WebDAV Clients

Expired items continue to be visible in WebDAV clients until they are permanently removed from the database during a system purge.

8.1.8.2.3 Enhanced Rich Text Editor

The Rich Text Editor (WYSIWIG editor) that is used in OracleAS Portal to apply formatting to text items is described in a Technical Note OracleAS Portal 9.0.4.1 – Enhanced Rich Text Editor on OTN at http://www.oracle.com/technology/products/ias/portal/content_management.html.

8.1.8.2.4 Using Oracle Drive with OracleAS Portal

OracleAS Portal leverages the features of Oracle Drive to manage and publish portal content directly from the Windows desktop.

Oracle Drive is a powerful WebDAV client. It maps the Oracle Portal Repository as a drive and enables you to perform desktop authoring and publishing, as well as portal-specific metadata attribution, from the Windows desktop. For further information, refer to the technical note, How to Install and Configure the Oracle Drive on OTN at http://www.oracle.com/technology/products/ias/portal/content_management_10gr2.html.

8.1.8.2.5 Unable to Delete Tabs on Templates

You cannot delete a tab on a template (even with Manage Template privileges), if other users have placed content on the tab, in pages that are based on this template.

8.1.8.2.6 Error Removing Subscriber from Virtual Private Portal

The following error can display when you use the rmsub.csh script to remove a subscriber from a Virtual Private Portal (VPP):

ERROR: Interface Version Specified does not match Profile Interface Version - 1.1 
Could not delete Provisioning Profile. 

This error does not impact the use of VPP.

8.1.8.2.7 Unable to Monitor WSRP Providers in This Release

Oracle Enterprise Manager 10g Help describes how to monitor Web providers, database providers, and WSRP producers registered with OracleAS Portal. Support for WSRP providers will be provided in a future release. It is not possible to monitor WSRP providers in 10g Release 2 (10.1.2).

8.1.8.2.8 Location of the ptlwsrp_data.sql Script

Section "Using the ptlwsrp_data.sql Script to Create the WSRP Portlet Preference Store" in Appendix C of the Oracle Application Server Portal Configuration Guide mentions the use of the script ptlwsrp_data.sql. It does not mention that this script first needs to be downloaded from Portal Center:

http://portalcenter.oracle.com