Skip Headers

Oracle9i Application Server Release Notes
Release 2 (9.0.2.0.1) for Sun SPARC Solaris

Part Number B10022-01
Go To Documentation Library
Home
Go To Table Of Contents
Contents

Go to previous page

5
Documentation Errata

This section describes documentation issues in the following documentation:

5.1 Oracle9i Application Server Installation Guide

The following are known issues with the Oracle9i Application Server Installation Guide:

5.1.1 InterConnect Software

To clarify the information in Oracle9i Application Server Installation Guide, Appendix C, the Oracle9iAS Interconnect software is in the Oracle9iAS Integration CD-ROM in the CD Pack.

5.2 Oracle9i Application Server Administrator's Guide

Following are the known issues in the Oracle9i Application Server Administrator's Guide:

5.2.1 Association Middle-Tier Installations with an Infrastructure

Chapter 2 of the Oracle9i Application Server Administrator's Guide states that once an infrastructure is installed on a host, all subsequent middle-tier installations on that host will automatically use the infrastructure. For Release 2 (9.0.2), if you install an infrastructure on a host, subsequent middle-tier installations will not automatically associate with that infrastructure. However, once a middle-tier installation has been associated with an infrastructure, all subsequent middle-tier installations on the same host will automatically associate with that infrastructure.

For the initial installation of the J2EE and Web Cache install type on a host, you can choose whether to associate an infrastructure with the install. If you do want to associate the install with an infrastructure, you can supply the information for whichever infrastructure you want.

For initial installations of all other install types on a host, the installation must be associated with an infrastructure of your choosing. You will be prompted to supply information about the infrastructure you want to use.

5.3 Oracle9i Application Server Concepts

Following is the known issue in the Oracle9i Application Server Concepts:

5.3.1 Characterization of New iPlanet Connector

The Oracle9i Application Server Concepts positioned Oracle Internet Directory incorrectly and mischaracterized the new iPlanet connector.

The sentence from the Oracle9i Application Server Concepts:

"With Oracle9iAS, Oracle Internet Directory includes an agent for out-of-the-box synchronization with Oracle Human Resources and an agent for synchronizing information with selected third party LDAP servers"

should read:

"With Oracle9iAS, Oracle Internet Directory includes connectors for out-of-the-box synchronization with Oracle Human Resources and iPlanet Directory Server 4.2 and 5.0."

5.4 Oracle9i Application Server Security Guide

Following are the known issues in the Oracle9i Application Server Security Guide:

5.4.1 SSLPassPhraseDialog Not Valid in Virtual Host Context

The Oracle9i Application Server Security Guide lists the "virtual host" as a context for SSLPassPhraseDialog directive. The valid context for SSLPassPhraseDialog directive is "server" only.

5.4.2 Remove PLsqlEnableConnectionPooling from Configured dads.conf File

The "Configuring Oracle9iAS Single Sign-On"chapter of the Oracle9i Application Server Security Guide contains information about a configured dads.conf file. The term PlsqlEnableConnectionPooling should be deleted from the file.

5.4.3 Updated Information Regarding Oracle9iAS Portal Default User Accounts

The "Oracle9iAS Portal Default User Accounts" bullet in the "Relationship between Oracle9iAS Portal and Oracle Internet Directory" section of the "Configuring Oracle9iAS Portal Security" chapter of the Oracle9i Application Server Security Guide states the following:

(cn=PUBLIC, cn=PORTAL, cn=PORTAL_ADMIN) are created in the subscriber's user base (cn=Users,o=MyCompany,dc=com).

It should be changed to:

(cn=PUBLIC, cn=PORTAL, cn=PORTAL_ADMIN) are created in the subscriber's user base (cn=Users,dc=MyCompany,dc=com).

5.4.4 Updated Information for Default User Password Policy

The "Default User Password Policy in Oracle9iAS" table in the "Oracle9i Application Server Security Architecture and Features" chapter of the Oracle9i Application Server Security Guide should state this additional information:

"After ten failed attempts to log in with an incorrect password, user accounts are locked out for a period of 24 hours."

5.5 Oracle9i Application Server Globalization Support Guide

Following are the known issues or errors in the Oracle9i Application Server Globalization Support Guide.

5.5.1 Multilingual Support for Oracle9iAS Single Sign-On

The following information was omitted from the Oracle9i Application Server Globalization Support Guide.

The Single Sign-On login page does not display language selection buttons if other languages were not installed. As a result, no product can run in non-English mode.

Oracle9iAS Single Sign-On supports 29 languages. English is the only language installed by default. You need to install other languages in order to support these languages during Single Sign-On login. To install additional languages, execute the following command:

ORACLE_HOME/jdk/bin/java -jar ORACLE_HOME/sso/lib/ossoca.jar langinst
lang make_lang_avail ORACLE_HOME

lang specifies the code for the language to be installed.

make_lang_avail specifies whether or not to make the language available. Enter 1 to make the language available, 0 otherwise.

See Also:

Oracle9iAS Single Sign-On Administrator's Guide

5.5.2 Updated Instructions for Deploying World-of-Books Demo

The section on "How to Deploy the World-of-Books Demo" in the "Multilingual Demo for Oracle9iAS" chapter of the Oracle9i Application Server Globalization Support Guide should be changed to remove the references on manual steps to deploy an OC4J applications.

The content should be replaced with the following:

How to Deploy the World-of-Books Demo on Oracle9iAS J2EE:

  1. Add data sources through Oracle Enterprise Manager. The data source attributes can found in the following file:

    ORACLE_HOME/j2ee/home/demo/globalization/j2ee_config/data-sources.xml
    
    • Replace <HOSTNAME> with the database server's hostname.

    • Replace <PORT> with the database server's port number.

    • Replace <ORACLE_SID> with the database server's oracle SID.

    After the data sources are added through Oracle Enterprise Manager, your J2EE_HOME/config/data-sources.xml should contain entries that correspond to those in globalization/j2ee_config/data-sources.xml.

  2. Deploy the application J2EE_HOME/demo/globalization/lib/g11n.ear through Oracle Enterprise Manager, or the dcmctl command utility as demonstrated below:

    dcmctl deployApplication -file J2EE_HOME/demo/globalization/lib/g11.ear
    -application g11n -component home
    
    

    where home is the default OC4J instance onto which the demo is deployed.

  3. You can verify this by visiting the pages listed below on a Web browser. In order to view a particular language, your operating system should have that language installed.

    Main site: http://<host>:<port>/g11n/imap.html
    WOB site: http://<host>:<port>/g11n/wob/jsp/welcome.jsp
    Supplier A: http://<host>:<port>/g11n/suppA/html/frame.html
    Supplier B: http://<host>:<port>/g11n/suppB/html/frame.html
    
    

5.6 Oracle9i Application Server: Migrating from Oracle Application Server

Following are the known issues in Oracle9i Application Server: Migrating from Oracle Application Server.:

5.6.1 Updated ossoconvert or ssl2ossl Migration Tool Information

The Oracle9i Application Server: Migrating from Oracle Application Server guide lists the following parameters for the ssl2ossl or osslconvert tool:

Table 5-1 Summary of ssl2ossl or osslconvert Tool Parameters
Parameter Description Requirement

chain

Oracle Application Server certificate chain file

optional

capath

Oracle Application Server certificate authority file

optional

cafile

Oracle Application Server certificate authority file

optional

To make sure a valid wallet generates, you must specify the trustpoints, that is, you need to specify the signers of the server certificates. This is the most common reason result for an invalid wallet.

There are two ways to specify the signers:

If you want to import other CA certificates, like SSLCACertificateFile in the httpd.conf, then use -cafile and -capath to do so.

5.7 Oracle Syndication Server User's and Administrator's Guide

Following are the known issues in the Oracle Syndication Server User's and Administrator's Guide:

5.7.1 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
    
    

5.8 Oracle9i Application Developer's Guide - XML

Updated versions of Chapters 5 and 6 of Oracle9i Application Developer's Guide - XML are available from OTN at

http://otn.oracle.com/tech/xml/doc.html

5.9 Online Help

The following are issues with online help for various components:

5.9.1 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:

5.9.2 Online Help May Not Display Correct Language

Translated versions of online help are installed into the Oracle home directory but are not always called correctly when using Oracle9iAS Discoverer Plus, Oracle9iAS Portal, or Oracle Ultra Search.

In order to view help information in the correct language, go to ORACLE_HOME/component/doc to find the translated help files.


Go to previous page
Oracle
Copyright © 2002 Oracle Corporation.

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