Skip Headers

Oracle9iAS Portal Release Notes
Release 2 (9.0.2)

Part Number A96191-02
Go To Documentation Library
Home
Go To Table Of Contents
Contents

Go to previous page

14
Documentation Errata

This section describes known errors or omissions in the Oracle9iAS Portal documentation.

14.1 Help for Schema Name Property is Incomplete

Help for the Create Schema dialog, specifies the following for the Schema Name property:

In addition, it should be noted that the Schema Name may not contain special characters, such as *, %, etc.

14.2 Help for Sequence Value Property is Incorrect

The Help for the Create Sequence dialogs, specifies the following for the Cache Value property:

Cache Value must be less than Maximum Value and Minimum Value.

This text should read:

Cache Value must be between the Maximum Value and the Minimum Value.

14.3 Help for Timeout Message Property is Incomplete

Help for the Create Provider and Edit Provider dialogs, specifies the following for the Timeout Message property:

Enter the text of the message to display when Oracle9iAS Portal cannot establish contact with this portlet provider within the number of seconds specified in the Timeout field. The message will be displayed within the body of the portlet.

In addition, it should be noted that the Timeout Message may not contain either mobile (mobileMXL) or desktop (HTML) markup.

14.4 Help for DAV URL Format Is Incorrect

The Help topic 'Accessing Oracle9iAS Portal from WebDAV clients' describes WebDAV and how to set up a DAV client.

The DAV URL format specified in this topic is incorrect, i.e:

http://<hostname>:<port>/<dad>/

Please use the following format instead:

http://<hostname>:<port>/dav_portal/<dad>/

14.5 Customize Link Removed from Custom Search Portlet

Help for the Custom Search portlet states that you can customize this portlet via a Customize link. This link is no longer available and all references to the link are to be removed from the next Help release.

To change the properties of the Custom Search portlet, switch to Edit mode and click Edit Defaults in the portlet.

14.6 Default Privileges for the AUTHENTICATED_USER Group

By default, Authenticated User Groups have the following privileges, relating to Portal pages:

These privileges allow users to create a navigation page or a style in any page group.

Note: All users are added to the Authenticated Users group by default.

This information is missing from the Help.

14.7 Searching Multiple Page Groups

When you perform a search in All Page Groups the Bulk Action link is not displayed, even if the portlet is customized to display this link. Bulk Action links are only displayed when searching a single page group.

This information is missing from the Help.

14.8 Understanding the Import/Export Log

During both the import and export process a log file is generated that contains details of any errors that may have occurred.

It is important to note that the lowest level at which errors are reported, is the Page level. This means that in Check mode, the log details issues relating to pages but it does not include issues relating to items or portlets on the pages.

This information is missing from the Help.

14.9 Disabling Web Cache

If you do not want any Portal pages and portlets to be cached, you can disable the use of Web Cache by clearing the checkbox Administer->Global Settings->Web Cache Settings->Enable Web Cache for caching portal content.

It is important to note that the File Cache must also be cleared whenever Web Cache is disabled. To do this, remove the directories "session" and "plsql" under the directory "$IAS_HOME/Apache/modplsql/cache".

This ensures that existing items in the cache that contain the Web Cache specific cache headers are not sent to Web Cache if there is a cache HIT in the File Cache.

Note: If the File Cache is not cleared, items may still get cached in Web Cache even though it is disabled in Portal.

This information is missing from the Help.

14.10 Broken Links to DAS Online Help

A few Portal Help topics include links to the DAS (Delegated Administration Service) Help. If you find that these links are broken, it is probably because they are pointing to the wrong machine or port for your Oracle Internet Directory (OID) server. You can do one of the following:

14.11 Hosting Developer's Guide

A hosting developer's guide is available on OTN, see http://portalstudio.oracle.com.

14.12 Using Oracle9iAS Single Sign-On with Oracle9iAS Syndication Server

Appendix E in the Oracle Syndication Server User's and Administrator's Guide omitted the following information regarding how to use Oracle9iAS Single Sign-On with Oracle9iAS Syndication Server.

In the following instructions, ORACLE_HOME is the home directory for the Portal & Wireless mid-tier installation type (which includes Oracle9iAS Syndication Server). Perform the following tasks to make Oracle9iAS Single Sign-On protect the Oracle9iAS Syndication Server URL.

  1. Use Single Sign-On to protect the /syndserver/OSS URL.

    In the ORACLE_HOME/Apache/Apache/conf/mod_osso.conf configuration file, insert the following lines between the <IfModule> and </IfModule> tags. Adding these lines protects the /syndserver/OSS directory from unauthenticated access.

    <Location /syndserver/OSS>
       require valid-user
       AuthType Basic
    </Location>
    
    
  2. Configure the push URL, which is used internally to push content.

    Configure the push URL in the file ORACLE_HOME/j2ee/OC4J_Portal/applications/syndserver/syndserver/WEB-INF/web.xml by adding the following lines between the <web-app> and </web-app> tags.

    <servlet-mapping>
       <servlet-name>OSS</servlet-name>
       <url-pattern>/OSSPUSH</url-pattern>
    </servlet-mapping>
    
    
  3. Protect the push URL to allow only receiving the HTTP GET request from the local scheduler sub-system.

    In the ORACLE_HOME/Apache/Apache/conf/mod_oc4j.conf configuration file, add the following lines between the <IfModule> and </IfModule> tags.

    <Location /syndserver/OSSPUSH>
       <Limit GET>
          Order deny,allow
          Deny from all
          Allow from localhost local-machine-name
       </Limit>
       <Limit POST>
          Deny from all
       </Limit>
    </Location>
    
    
  4. Restart Oracle HTTP Server to apply the changes.

    You can use Oracle Enterprise Manager, the Distributed Configuration Management command-line tool (dcmctl), or opmnctl to restart Oracle HTTP Server.

  5. Configure the PUSH_HANDLER_URL parameter using the Oracle9iAS Syndication Server Administration page.

    In Oracle Enterprise Manager, go to the Syndication Server Administration Page. Choose the Global Properties tab, and change the value of the PUSH_HANDLER_URL parameter to the following URL:

    http://<your-local-machine-name>:<your-port-number>/syndserver/OSSPUSH
    

Go to previous page
Oracle
Copyright © 2002 Oracle Corporation.

All Rights Reserved.
Go To Documentation Library
Home
Go To Table Of Contents
Contents