|
Oracle9i Application Server Release Notes Addendum,
Release 2 (9.0.2.0.1) for Solaris Operating System (SPARC) Part No. B10023-09 |
|
|
|
Oracle9i Application Server Release Notes Addendum,
Release 2 (9.0.2.0.1) for Solaris Operating System (SPARC) Part No. B10023-09 |
|
|
|
This section describes documentation issues in the following documentation:
This section describes issues in the following documentation:
Oracle9i Application Server: Migrating from Oracle Application Server
Oracle9i Application Server Migrating from Release 1 (1.0.2.2.x) to Release 2 (9.0.2)
Following are the known issues in Oracle9i Application Server Administrator's Guide:
The "Starting Infrastructure" section of the "Starting and Stopping the Application Server" chapter of the Oracle9i Application Server Administrator's Guide needs additional steps to correctly start the metadata repository. Use the following instructions to start the metadata repository:
Start the metadata repository. You can start the metadata repository using your preferred database tool, such as Oracle Enterprise Manager or SQL*Plus. To start the metadata repository using SQL*Plus:
Start the metadata repository listener:
ORACLE_HOME/bin/lsnrctl start
Set the ORACLE_SID environment variable to the metadata repository system identifier, for example:
(Bourne or Korn shell) ORACLE_SID=iasdb; export ORACLE_SID (C shell) setenv ORACLE_SID iasdb
Start the metadata repository instance using SQL*Plus:
ORACLE_HOME/bin/sqlplus /nolog sql> connect sys/password_for_sys as sysdba sql> startup sql> quit
Start the Enterprise Manager Web site in the Oracle home of the primary installation using the following command:
ORACLE_HOME/bin/emctl start
Start Oracle Internet Directory using the following commands:
ORACLE_HOME/bin/oidmon start ORACLE_HOME/bin/oidctl server=oidldapd configset=0 instance=n start
Where n can be any number like 1,2 which is not already in use.
Start the infrastructure instance using the Instance Home Page on the Enterprise Manager Web site:
Navigate to the Instance Home Page for the infrastructure on the Enterprise Manager Web site.
In the General section on the Instance Home Page, click Start All.
If Oracle Management Server (OMS) is configured, start OMS:
ORACLE_HOME/bin/oemctl start oms
The "Managing the Infrastructure" chapter of the Oracle9i Application Server Administrator's Guide contains a section called "Schemas Accessed Directly by Administrators." The list item about the OEM_REPOSITORY schema should read as follows:
OEM_REPOSITORY - This schema is used by Oracle Management Server. If you change the password in the database, you must update the Oracle Management Server configuration by running the Enterprise Manager Configuration Assistant and choosing the option to "Use an Existing Repository". By selecting this option and entering the new password, the Oracle Management Server configuration is updated.
The "Introduction to Administration Tools" chapter of the Oracle9i Application Server Administrator's Guide includes instructions for configuring the Oracle Management Server. If you configure the Oracle Management Server as part of the installation procedure, the Oracle Management Server repository is set up automatically using default settings.
If you choose to configure the Oracle Management Server after the installation of Oracle9iAS, or if you add a second infrastructure, use the Enterprise Manager Configuration Assistant (emca).
When you configure the Oracle Management Server using emca, consider the following details in addition to the instructions provided in the "Introduction to Administration Tools" chapter:
When you run the Enterprise Manager Configuration Assistant, select the following options:
Configure Local Management Server
Use Existing Repository
Selecting these options will create the omsconfig.properties file, which is required by the Oracle Management Server. The Enterprise Manager Repository schema is already pre-configured with the infrastructure installation.
Next, provide the following default information for the repository:
Repository Username: OEM_REPOSITORY
Repository Password: oem_repository
Connection Information: <host:port:sid>
OEM_REPOSITORY is the default Enterprise Manager schema. When you installed Oracle9iAS infrastructure, the OEM_REPOSITORY database user was created and the necessary Enterprise Manager schema was loaded. Oracle recommends that you do not change this user. However, you can change the default password. The repository username and password are stored in the omsconfig.properties file. The configuration assistant will encrypt the repository password in this file.
After you run the configuration assistant, you can start the Management Server using the following command:
oemctrl start oms
To stop the Management Server, use the following command:
oemctrl stop oms <username>/<password>
The default user name for the Management Server is sysman. The default password is oem_temp. If you do not provide the username and password on the command line, the Management Server will prompt you for the username and password.
The oemctrl and oemapp commands are installed in the following directory:
<ORACLE_HOME>/bin
The "Changing Instance Password in Oracle Internet Directory" section in the "Managing Oracle Internet Directory" chapter of the Oracle9i Application Server Administrator's Guide states:
To change the password:
resetiASpasswd.sh OID_Admin_user OID_Admin_passwd ORACLE_HOME
where OID_Admin_user is orcladmin or a user in the IASAdmins group.
Here, the above line is incorrect. It should state:
OID_Admin_user is cn=orcladmin.
The "Installing and Configuring Oracle9iAS" section in the "Managing Oracle Internet Directory" chapter of the Oracle9i Application Server Administrator's Guide should contain the following information:
In addition to being in the iASAdmins group, you must also be the "owner" of the iASAdmins group.
You must also be in the OracleDBCreators group if you need to create a new infrastructure database.
To perform a Portal installation, you must also be in the OracleDASAdminGroup in the Root Oracle Context.
Table "Oracle9iAS Port Usage (Sorted by Component)" in the "Default Port Numbers and Port Ranges" chapter of the Oracle9i Application Server Administrator's Guide contains an incomplete list of port numbers for Oracle9iAS Web Cache. Table 8-1 contains the complete list of Oracle9iAS Web Cache port numbers.
Table 8-1 Oracle9iAS Port Usage (Sorted by Component)
Section "Component Instances: Oracle HTTP Server" in the "Clustering" chapter of the of the Oracle9i Application Server Administrator's Guide contains the following incorrect statement:
"Forward an incoming stateless request to any OC4J process in the cluster. The priority is to forward the incoming request first to an OC4J process in its own application server instance. If none are available, it forwards the request to any OC4J process in another application server instance in the cluster."
It should be:
"Forward an incoming stateless request to any OC4J process in the cluster. It gives equal weight to each of the available OC4J processes in the cluster, local or remote, when determining where to forward the request."
There are three syntax errors in the sample configurations provided in the "Sample Configurations for Oracle Process Manager" section of the "High Availability" chapter of the Oracle9i Application Server Administrator's Guide.
The attribute describing the number of processes in the custom tag should be "numProcs" (not "num_of_procs").
The local, remote, and request attributes are all required in the port tag.
The island id and number of processes are defined with the id and numProcs attributes in the island tag (not with the islandID attribute).
The following samples use the correct syntax:
This configuration starts one Oracle HTTP Server and one OC4J process with default values.
<notification-server>
<port local="6001"
remote="6002"
request="6003">
</port>
<log-file path="/private/my_directory/tmp/opmn_logs/ons.log"
level="5">
</log-file>
</notification-server>
<process-manager>
<ohs/>
<oc4j>
<config-file path=ORACLE_HOME/j2ee/home/config/server.xml />
</oc4j>
<log-file path="/private/my_directory/tmp/opmn_logs/ipm.log"
level="4">
</log-file>
</process-manager>
This configuration starts one Oracle HTTP Server process, two OC4J processes, and one generic process with several user-specified values.
<process-manager>
<ohs gid="a1" maxRetry="3">
<config-file path="/my_directory/conf/httpd.conf"/>
</ohs>
<oc4j instanceName="home" maxRetry="4" gid="o1">
<config-file path="/my_directory/conf/oc4j.xml"/>
<port ajp="3000-3001" rmi="3002-3003" jms="3004-3005"/>
<island id="myIslandA" numProcs="2"/>
</oc4j>
<custom gid="g1" numProcs = "1">
<start path="/my_directory/bin/exec1"/>
<environment>
<prop name="PATH" value="/my_directory/ias/lib"/>
<prop name="CLASSPATH" value="/my_directory/ias/bin"
</environment>
</general>
</process-manager>
This configuration starts one Oracle HTTP Server and two OC4J processes with some user-specified values.
<notification-server>
<port local="6001"
remote="6002"
request="6003">
</port>
<log-file path="/private/my_directory/tmp/opmn_logs/ons.log"
level="5">
</log-file>
</notification-server>
<process-manager>
<!-- Start one ohs process with a process group ID of a1, with a config file in a
non-default directory location -- >
<ohs gid="a1" maxRetry="3">
<config-file path="Apache/Apache/my_conf/httpd.conf"/>
</ohs>
<!-- Start two oc4j processes with a process group ID of o1, with a instanceName
of myClusterA (This should be the worker specified in the mod_oc4j config file),
and an island id of myIslandA. Since we are starting two processes we have to
specify the port range used when starting the processes. So OC4J process1 starts
with ajp port 8010, jms port 8020 and rmi port 8030. The second OC4J process uses
ajp port 8011, jms port 8021, and rmi port 8031. -->
<oc4j instanceName="myInstanceA" gid="o1">
<port ajp="8010-8012", jms="8020-8022" rmi="8030-8032"/>
<island id="myIslandA" numProcs="2"/>
</oc4j>
<!-- If the logs should be created in a specific directory provide that location
here --!>
<log-file path="/tmp/ipm.log" level="4"/>
</process-manager>
The "Starting and Stopping the Application Server" chapter of the Oracle9i Application Server Administrator's Guide should include Oracle9iAS Reports Services under "About Components that Cannot Be Started or Stopped".
By default, after installation, Oracle9iAS Reports Services is configured virtually identically to Forms. It is part of OC4J_BI_FORMS instance, and is brought "up" and "down" with that OC4J instance. In OEM, it displays an "up" status if it can successfully contact the Reports server, and a "down" status otherwise.
However, you can reconfigure the Reports server, using the report servlet configuration file, so that the Reports server will not be started automatically when OC4J is brought up. If you have done this, you will need to start and stop the Reports server manually. In this case, the instructions currently provided in the Oracle9i Application Server Administrator's Guide for starting and stopping the Reports server as a standalone process, either via OEM or the command line, are correct.
Scenario 1, step 3 of the "About Infrastructure Association" section of the "Concepts for Administrators" chapter of the Oracle9i Application Server Administrator's Guide incorrectly states the following:
Install J2EE and Web Cache on Host B. If you choose to use an infrastructure, it will automatically use the infrastructure on Host B.
It should instead say:
Install J2EE and Web Cache on Host B. If you choose to use an infrastructure, it will automatically use the infrastructure on Host A.
Step 6b in the "Using SSL for Your Production Environment" of the "Introduction to Administration Tools" chapter of the Oracle9i Application Server Administrator's Guide incorrectly states the following:
Enter the following emctl command:
emctl set ssl test
It should instead say:
Enter the following emctl command:
emctl set ssl on
The following note should be added to the "Relocating Metadata Repository Datafiles to a Different Directory" section of the "Managing the Infrastructure" chapter of the Oracle9i Application Server Administrator's Guide:
"Note that this procedure may only be used to move data files, that is, files in the data dictionary view DBA_DATA_FILES and the dynamic performance view V$DATAFILE. This procedure may not be used to move temporary files, that is, files in the DBA_TEMP_FILES and V$TEMPFILE views. This is because the database does not support renaming of temporary files."
In the "Starting and Stopping the Enterprise Manager Web Site on UNIX" section of the "Introduction to Administration Tools" chapter of the Oracle9i Application Server Administrator's Guide, an incorrect link to Table 3-4 is displayed. The correct link is to Table 3-2.
The following are known issues with Oracle9i Application Server Installation Guide:
The "Preventing Conflicts with Other Oracle Homes" section in the "Getting Started" chapter of the Oracle9i Application Server Installation Guide should not list setting LD_LIBRARY_PATH as a prerequisite for installation.
Footnote 2 for table 3-2 "Oracle9iAS Components" in the "Oracle9i Application Server" chapter of the Oracle9i Application Server Installation Guide incorrectly states the following:
Oracle9iAS Portal installs Oracle Ultra Search and Oracle9iAS Syndication Server.
It should instead say the following:
Oracle9iAS Portal installs Oracle Ultra Search, Oracle9iAS Syndication Server, and Oracle UDDI Enterprise Web Services Registry.
Chapter "Oracle9iAS Infrastructure" in the Oracle9i Application Server Installation Guide contains incorrect information for screen 4-4 "Existing Oracle9iAS Single Sign-On". Currently, it says:
"One of the following two screens may appear based on your configuration choices on the "Select Configuration Options Screen", (Figure 4-3):
Existing Oracle9iAS Single Sign-On: This screen appears if you have unchecked the configuration of Oracle9iAS Single Sign-On on the Component Configuration and Startup screen.
Existing Oracle Internet Directory: This screen appears if you have unchecked the configuration of Oracle Internet Directory on the Component Configuration and Startup screen.
Existing Oracle9iAS Single Sign-On
Enter the host name and port number for the existing instance of Oracle9iAS Single Sign-On that you wish to use with this installation of Oracle9iAS Infrastructure and click Next.
If you do not have Oracle9iAS Single Sign-On installed, return to the Component Configuration and Startup screen and select the default configuration option for Oracle9iAS Single Sign-On.
Existing Oracle Internet Directory
Enter the host name and port number for the existing instance of Oracle Internet Directory that you wish to use with this installation of Oracle9iAS Infrastructure and click Next. "
It should instead say:
"The Existing Oracle9iAS Single Sign-On screen will not appear during Oracle9iAS Infrastructure installation if you deselect Oracle9iAS Single Sign-On on the Component Configuration screen. The Existing Oracle9iAS Single Sign-On screen appears if you just select installation of the Oracle9iAS Metadata Repository on the Component Configuration screen.
To use Oracle9iAS Single Sign-On with Oracle Internet Directory, choose one of the following configurations:
Select Oracle9iAS Single Sign-On and Oracle Internet Directory on the Component Configuration screen for configuration on the same host.
Install Oracle Internet Directory and Oracle9iAS Single Sign-On on different hosts:
Select Oracle Internet Directory and deselect Oracle9iAS Single Sign-On on the Component Configuration screen for configuration on Host 1.
Select Oracle9iAS Single Sign-On and deselect Oracle Internet Directory on the Component Configuration screen for configuration on Host 2.
Point the Oracle9iAS Single Sign-On configuration on Host 2 to the Oracle Internet Directory configuration on Host 1 (Oracle Universal Installer will prompt you for the location of your existing Oracle Internet Directory.)"
The "Hardware Requirements" table in the "Getting Started" chapter of the Oracle9i Application Server Installation Guide incorrectly says that Business Intelligence and Forms requires 95 MB for /var/tmp space.
However, during Business Intelligence and Forms installation, the following error message is displayed:
"Insufficient space in /var/tmp. Requires 200MB. Fix problem and restart."
Accordingly, the value for /var/tmp space for Business Intelligence and Forms should be changed from 95 MB to 200 MB.
The description of the installation screen for step 3a in Section 3.2, Chapter 3 of the Oracle9i Application Server Installation Guide is incorrect. The description should be:
If you have an Oracle9iAS mid-tier instance on the install computer that is already associated with an Oracle9iAS Infrastructure, then the Infrastructure Summary screen appears. Review and note the information provided on the screen and click Next.
The following sections are invalid and should be removed from the Oracle9i Application Server Installation Guide:
3.3.2 Installing the Oracle9i Application Server Patches
4.2.2 Installing the Oracle9iAS Infrastructure Patches
The Recommended Processor description in Appendix B, Table B-1 is incorrect. Instead of recommending a Pentium I 266 the recommendation is for a Pentium U 266.
The Recommended Processor description in Appendix B, Table B-1 is incorrect. Instead of recommending a Pentium I 266 the recommendation is for a Pentium U 266.
In Appendix C, Section C.5.1, page C-36, there is an incorrect screen reference in Step 1. Instead of Available Products Screen it should read Install Type Screen.
The following are known issues in Oracle9i Application Server Security Guide:
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.
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."
Following are the known issues in Oracle9i Application Server: Migrating from Oracle Application Server:
Table 1-3, "Summary of ssl2ossl or osslconvert Tools Parameter", in the "Introduction to Oracle9i Application Server" chapter of the Oracle9i Application Server: Migrating from Oracle Application Server incorrectly states that the default path of the wallet is documented as ORACLE_HOME/Apache/Apache/conf/ssl.wlt/0. The correct path of the wallet is ORACLE_HOME/Apache/Apache/bin/wallet.
The "Applying the 9.0.2.1.0 database patch" section in the "Migrating Management Components" chapter of the Oracle9i Application Server: Migrating from Oracle Application Server contains incorrect database patch number.
Following is the correct information:
Applying the 9.0.1.3.0 database patch
Ensure that the database is brought up in ORACLE_HOME_2. To apply the 9.0.1.3.0 database patch set, please follow the instructions in the "Post Install Actions section" in ORACLE_HOME_2/rdbms/notes/patch_note.htm.
Following are the knows issues in Oracle9i Application Server Migrating from Oracle9iAS Release 1 (1.0.2.2.x) to Release 2 (9.0.2):
Step 3 of the "Installation on Separate Computers" section in Migrating from Oracle9iAS Release 1 (1.0.2.2.x) to Release 2 (9.0.2) should be changed to state the following:
Copy the entire directory structure
<OLD_ORACLE_HOME>/panama/server/classes
from machine mc1 to a temporary directory. Modify the file:
<temporary_dir>/panama/server/classes/oracle/panama/spatial/spatial.properties
to replace the <OLD_ORACLE_HOME> prefix for each property with the absolute path to the temporary directory.
For example, if the temporary directory was /tmp, you should modify the file:
/tmp/panama/server/classes/oracle/panama/spatial/spatial.properties
to change entries of the form
file.providers.config.xml.geocoding = /private/ias/10220PME/panama/server/classes/oracle/panama spatial/geocoder/Geocoders.xml
(where /private/ias/10220PME is the OLD_ORACLE_HOME) to the form
file.providers.config.xml.geocoding = /tmp/panama/server/classes/oracle/panama spatial/geocoder/Geocoders.xml
The "Post-Upgrade Manual Tasks and Database Migration Alternatives" section in the "Migrating Management Components" chapter of the Migrating from Oracle9iAS Release 1 (1.0.2.2.x) to Release 2 (9.0.2) should include the following section:
Post-Upgrade Step for iPlanet Synchronization
Integration Profiles for iPlanet synchronization, namely iPlanetImport and iPlanetExport, are created as part of the upgrade. For these profiles to be configured and used for synchronization, they need to be added to configset1.
If the profiles are available in Configset 1 as part of upgrade, it will be shown in ODM under Integration Server as part of Configuration Set1. If the profiles are not available, they can be added by using LDAPMODIFY as below:
ldapmodify -h <OID Host> -p <OID Port> -D <OID Super-user> -w <OID Super-user password> -f <ORACLE_HOME>/ldap/install/upgdip.ldif
Migrating Oracle9iAS SOAP
This section describes how to migrate SOAP applications from Oracle9iAS Release 1 (1.0.2.2.x) to Oracle9iAS Release 2 (9.0.2).
SOAP is implemented as a servlet. A servlet delegates service invocations to user supplied implementation classes. In Oracle9iAS Release 1 (1.0.2.2.x), JServ was the default servlet engine. In Oracle9iAS Release 2 (9.0.2), OC4J is the servlet engine. To migrate SOAP applications, you must copy and re-packaging the service implementation classes and descriptors, and also consider the configuration aspects of the JServ and OC4J containers.
|
See Also: Ò"Migrating Oracle9iAS SOAP" for more information on JServ and OC4J configuration. |
Oracle9iAS Release 2 (9.0.2) contains empty (that is, containing no services) SOAP application and web application archives ready to install. These files are named soap.ear and soap.war, and are located in ORACLE_HOME/soap/webapps/soap.ear.
The soap.war file is a copy of the WAR file contained in the soap.ear file.
The SOAP migration process involves inserting Oracle9iAS Release 1 (1.0.2.2.x) files into a copy of the empty SOAP application, and then deploying the application in OC4J. Files can be "inserted" in one of two ways:
Using jar -x to unpack the soap.ear and soap.war files into component directories, copying old files to the corresponding directories, then using jar -c to create new .ear and .war files.
Using jar -u to update the contents of the .war and .ear files without unpacking them.
Below are the steps in the migration process.
Copy ORACLE_HOME_2/soap/webapps/soap.ear and ORACLE_HOME_2/soap/webapps/soap.war to a convenient work directory (workdir, in this example).
Copy all user-written class files for the SOAP services to soap.war.
|
See Also: Ò"Migrating User-written Classes" section for an approach to handling user-written classes. |
Insert all jar files except soap.jar and samples.jar from ORACLE_HOME_1/soap/webapps/soap/WEB-INF/lib into workdir/soap.war.
If you are sure that the old configuration file, ORACLE_HOME_1/soap/webapps/soap/WEB-INF/config/soapConfig.xml was never changed, go to step 6.
Make a copy of the old configuration file, ORACLE_HOME_1/soap/webapps/soap/WEB-INF/config/soapConfig.xml renaming it to soap.xml.
Edit the file, examining the class attribute of the providerManager and serviceManager elements.
|
Note: The providerManager and serviceManager interfaces have changed from Release 1, so if you supplied the class, you must change and recompile your code, then insert it inworkdir/soap.war. The location in soap.war is directly in WEB-INF, not WEB-INF/config. The SOAP javadocs on the Oracle9iAS documentation CD detail the changes.
If you did not supply the class, delete the class attribute from the |
All of the code to be migrated is now in workdir/soap.jar.
Insert the new workdir/soap.jar into workdir/soap.ear.
Deploy the .ear file in OC4J.
Activate the installed SOAP services as described in the Oracle9iAS Web Services Developer's Guide.
Migrating User-written Classes
The directory structures in Oracle9iAS Release 1 (1.0.2.2.x) do not correspond directly to those in Oracle9iAS Release 2 (9.0.2). Specifically, soap.ear is a SOAP sample application that runs in a SOAP server instance. It no longer contains soap.jar (which is in the OC4J system classpath).
For this reason, to migrate, it might be easiest to create a new .ear file (using soap.ear as a guide) for the services you want to deploy.
To migrate user-written classes from Release 1 to Release 2, follow these steps:
Identify and locate the user-written class files by examining the JServ configuration files and/or ORACLE_HOME_1/soap/webapps/soap/WEB-INF/config/soap.properties files.
Create an .ear file with a WEB-INF/classes directory that contains the class files that implement the services you want to deploy.
Create a .war file that contains:
.jar or class files (under WEB-INF/lib or WEB-INF/classes) the application requires.
web.xml (under WEB-INF), the web application deployment descriptor. This file contains the SOAP servlet configuration and the servlet mapping set. You must specify oracle.soap.server.http.SOAPServlet as the servlet class, but the servlet name and mapping can be any names you choose. You must specify the initial parameter for the SOAP configuration file. To use the default location, copy the init-param from web.xml in the soap.ear file.
soap.xml (under WEB-INF), the SOAP servlet configuration file. You can start with the soap.xml file in soap.ear, and modify it as needed.
index.html, the index file specific to the application.
Include the application .war file in the .ear file, and an application.xml file under WEB-INF. The application.xml file is not specific to SOAP; it contains application deployment information. (For required file entries, see the application.xml file in soap.ear.)
Following are the known issues in Oracle9i Application Server Performance Guide:
Figure "Setting Java Heap Size for an OC4J Instance Using Oracle Enterprise Manager" in the "Optimizing J2EE Applications In OC4J" chapter of the Oracle9i Application Server Performance Guide is outdated. The OEM screen does not contain the configuration file path fields.
Following are the known issues in Oracle9i Application Server Release Notes:
The section discussing "Configuring Oracle9iAS Clickstream Intelligence After Installing Oracle9iAS Using Oracle Universal Installer" in the Oracle9i Application Server Release Notes should read:
If you choose not to configure Oracle9iAS Clickstream Intelligence via Oracle Universal Installer and decides to configure it at a later time, perform the following steps:
|
Note: Configuring Oracle9iAS Clickstream Intelligence at a later time is normally done through Oracle Enterprise Manager (OEM), but currently, configuring Oracle9iAS Clickstream Intelligence through OEM is unavailable. |
Verify that the environment variable ORACLE_HOME set to your Oracle9iAS installation directory before running the scripts provided below.
Run Oracle9iAS Clickstream Intelligence Configuration tool.
LD_LIBRARY_PATH=ORACLE_HOME/lib:ORACLE_HOME/network/lib: ORACLE_HOME/jdk/jre/lib/sparc export LD_LIBRARY_PATH touch ORACLE_HOME/j2ee/deploy.ini ORACLE_HOME/jdk/bin/java -cp ORACLE_HOME/click/lib/click.jar:ORACLE_HOME/jlib/repository.jar oracle.click.common.ConfigureBI ORACLE_HOME/j2ee/deploy.ini ORACLE_HOME
Deploy Oracle9iAS Clickstream Intelligence to OC4J.
ORACLE_HOME/jdk/bin/java -classpath
ORACLE_HOME/dcm/lib/dcm.jar:
ORACLE_HOME/jlib/emConfigInstall.jar:
ORACLE_HOME/lib/classes12.zip:
ORACLE_HOME/lib/dms.jar:
ORACLE_HOME/j2ee/home/oc4j.jar:
ORACLE_HOME/lib/xschema.jar:
ORACLE_HOME/lib/xmlparserv2.jar:
ORACLE_HOME/opmn/lib/ons.jar:
ORACLE_HOME/j2ee/home/jaas.jar:
ORACLE_HOME/j2ee/home/jazn.jar:
ORACLE_HOME/j2ee/home/jaznplugin.jar:
ORACLE_HOME/dcm/lib/oc4j_deploy_tools.jar
oracle.j2ee.tools.deploy.Oc4jDeploy
-oraclehome $ORACLE_HOME
-verbose
-inifile $ORACLE_HOME/j2ee/deploy.ini
Oracle9iAS Clickstream Intelligence uses Discoverer to display reports. The steps above will configure Discoverer automatically if you have not done so. already.
Restart the Oracle9iAS server and Discoverer server
ORACLE_HOME/dcm/bin/dcmctl stop ORACLE_HOME/dcm/bin/dcmctl start ORACLE_HOME/discoverer902/util/stopall.sh ORACLE_HOME/discoverer902/util/startall.sh
You will then be able to access Oracle9iAS Clickstream Intelligence at the following URL:
http://iashost:port/click
The section discussing "Error Displaying Clickstream Runtime Administrator" in the Oracle9i Application Server Release Notes should read:
An intermittent "Page Not Displayed" error may be experienced when using certain versions of Microsoft Internet Explorer to access Clickstream Runtime Administrator. This is due to issues between Oracle9iAS Web Cache and Internet Explorer when SSL is enabled.
This problem can be worked around using one of the following methods:
By using the Reload button of the browser to reload the page.
Disable SSL (recommended).
To do this, edit the file ORACLE_HOME/click/conf/click-apache.conf to comment out the following lines (by adding a "#" character at the beginning of each line):
<Location /click>
RewriteEngine on
RewriteCond %{HTTPS} !=on
RewriteRule ^(config/.*)$
https://%{SERVER_NAME}:%{APACHEPORTSSL}/click/1
[R]
</Location>
Restart Oracle9iAS using OEM or the following commands:
ORACLE_HOME/dcm/bin/dcmctl stop ORACLE_HOME/dcm/bin/dcmctl start
Disable Oracle9iAS Web Cache "KeepAlive" option. You can disable "KeepAlive" by setting KeepAlive to 0 on the Network Timeouts page (Cache-Specific Configuration > Network Timeouts) of the Oracle9iAS Web Cache Manager.
The section discussing "Oracle Enterprise Manager Does Not Support Multiple Locales" in the Oracle9i Application Server Release Notes should read:
Oracle Enterprise Manager does not support multiple locales. The following components use the browser's locale when displaying pages in OEM:
Oracle9iAS Discoverer
Oracle9iAS Forms Services
Oracle9iAS Portal
Oracle9iAS Single Sign-On
PL/SQL properties
Oracle9iAS Unified Messaging
All other management pages use the Java default locale when displaying pages.
The section discussing "Enabling Oracle9iAS Web Cache and mod_osso" in the Oracle9i Application Server Release Notes should read:
When the Oracle9iAS installer initially registers mod_osso with the Oracle9iAS Single Sign-On, it passes the registration URLs containing the port number of the Oracle HTTP Server, instead of the port number of Oracle9iAS Web Cache. Since the installer passes the incorrect port number, it bypasses Oracle9iAS Web Cache.
For mod_osso to work correctly, manually re-register mod_osso using URLs that have the Oracle9iAS Web Cache port.
|
See Also: ""Component Configuration Dependencies" chapter in the Oracle9i Application Server Administrator's Guide for detailed information on how changes in hostname and port affect Oracle9i Application Server, and, specifically, howmod_osso and Oracle9iAS Single Sign-On may be affected.
|
Another alternative workaround is to shutdown Oracle9iAS Web Cache instead of re-registering the SSO partner. Since the entry point is now Oracle HTTP Server instead of Oracle9iAS Web Cache, the error would not show up.
|
Note: You can use the above mentioned workaround before re-registering using the Oracle9iAS Web Cache port. Also, when you use this workaround, you have to enter with the Oracle HTTP Server port. For example, if Oracle HTTP Server is running on 7779 and Oracle9iAS Web Cache is running on 7778, then you need to enter the following URL:http://<host.domain>:7779.
|
On Microsoft Internet Explorer, refresh the page once the changes are made. Otherwise, you might encounter the following error:
Forbidden You don't have permission to access /osso_login_success on this server.
The section "Deploying UIX JSP and XML Applications Using Oracle Enterprise Manager" in the Oracle9i Application Server Release Notes should read:
Deploying BC4J JSP, UIX JSP and UIX XML Applications Using Oracle Enterprise Manager
BC4J JSP, UIX JSP, and UIX XML applications from JDeveloper deployed to Oracle9iAS through the Enterprise Manager deployment functionality runtime will result in a runtime rendering data access error. This happens only if data source information is added subsequently through Enterprise Manager and not pre-packaged already in the EAR file from JDeveloper.
If the EAR file generated from JDeveloper doesn't package the data source information or the "deploy to EAR files" option is chosen instead of "deploy to connection," and if that information is subsequently added through the Enterprise Manager through the edit data sources functionality, then the UIX/JSP and UIX/XML applications cannot run successfully due to runtime rendering error.
To avoid the error, do not add the data sources information after deployment through EM. Instead, package the EAR file with the data sources information from JDeveloper prior to deployment through EM. While creating the UIX/JSP or the UIX/XML application from JDeveloper, instead of just deploying to an EAR file, deploy to any existing connection, including dummy connections. That process will create an EAR file with the data sources information packaged.
If deploying to a dummy connection, although the process will result in deployment errors in JDeveloper, it will create an EAR file that includes the data source information that can be successfully deployed to Oracle9iAS.
The section "Multiple Infrastructure-based Deployment" in the Oracle9i Application Server Release Notes should read:
Oracle9iAS supports multiple infrastructure installations. The first (or primary) infrastructure installation must contain SSO, Oracle Internet Directory, a Metadata Repository, and, optionally, Oracle Management Server. Any subsequent (or secondary) infrastructure installations:
must point to the SSO in the primary installation.
must point to the Oracle Internet Directory in the primary installation.
must contain their own Metadata Repository.
may optionally contain Oracle Management Server.
The purpose of a secondary installation is to provide an additional Metadata Repository in case the load on the primary Metadata Repository is excessive.
You can install a secondary infrastructure by choosing a custom installation and selecting Metadata Repository and optionally Oracle Management Server. You will be prompted for SSO and Oracle Internet Directory information, at which time you should supply the information for the primary infrastructure.
The middle tier application server installations that are installed after a secondary infrastructure can use that secondary infrastructure. This means that you cannot change existing middle tier application server installations to use the secondary infrastructure.
If you want a middle tier installation to use the secondary infrastructure, specify the SSO and Oracle Internet Directory from the primary infrastructure at install time. When you are prompted to specify which infrastructure's Metadata Repository you would like to use, choose the Metadata Repository from the secondary installation.
The "Avoid Use of Symbolic Links" section should be removed from the Oracle9i Application Server Release Notes as it is not an issue any more. The issue in the release notes stated:
"When installing, avoid selecting an ORACLE_HOME directory that is a symbolic link to another directory. If you do this, the following errors may occur when running the configuration tools:
java.lang.SecurityException: access denied
oracle.ias.repository.schema.SchemaException: access denied
As a workaround, install into a directory that is not a symbolic link."
It has been fixed for the Solaris release.
The "Problems Logging In When Two Oracle HTTP Servers Are on the Same Host" section in the Oracle9i Application Server Release Notes should be updated with the information below:
Problems Logging in When Two Oracle HTTP Servers are on the Same Host and are Using Internet Explorer with SSL Configuration
When two Oracle9iAS Oracle HTTP Servers are running on a single machine, such as when an infrastructure install and a Portal and Wireless middle tier install are both installed on a single machine, login to the Portal is not possible when using a Microsoft Internet Explorer (MSIE) Browser. This has been verified with versions 5.5 and 6.0 of MSIE. The problem occurs when a browser redirect is issued from one port used by the Oracle9iAS Single Sign-On server to the port used by Oracle9iAS Web Cache, which is fronting Oracle9iAS Portal. When MSIE receives the redirect, it erroneously sets the Host: header with the first port rather than the destination port. This behavior is not exhibited by Netscape Navigator (versions 4.6, 4.7). When this error occurs with MSIE, one of the following messages may be shown after an attempt to log in:
Error: Unexpected error encountered in wwsec_app_priv.process_signon (ORA-06502: PL/SQL: numeric or value error: character string buffer too small) (WWC-41417)
or
Error: The decryption of the authentication information was unsuccessful. This may be caused by corruption of the data, an incorrect encryption key in this application's configuration, or an illegal access attempt. Please notify your administrator. (WWC-41454)
Although MSIE sets the Host: header incorrectly in either SSL or non-SSL mode, the problem only shows up in SSL mode because Oracle9iAS Web Cache is setup to map ports to a catch-all default HTTP port in non-SSL mode. The workaround is to use two separate machines, with the two install types.
This section describes issues in the following Oracle9iAS Containers for J2EE documentation:
Following are the known issues in Oracle9iAS Containers for J2EE Services Guide, Oracle9iAS Containers for J2EE Support for JavaServer Pages Reference, and Oracle9iAS Containers for J2EE JSP Tag Libraries and Utilities Reference:
The release 9.0.2 versions of the Oracle9iAS Containers for J2EE Services Guide, Oracle9iAS Containers for J2EE Support for JavaServer Pages Reference, and Oracle9iAS Containers for J2EE JSP Tag Libraries and Utilities Reference contain inaccuracies or incomplete information regarding file locations. The files involved are xmlparserv2.jar, xsu12.jar, and JSP tag library descriptor (TLD) files.
In Oracle9iAS, note the following:
The xmlparserv2.jar file is automatically installed on your system and into your classpath. It is located in the Oracle9iAS lib directory and is picked up from there automatically.
The xsu12.jar file may not have been installed in the OC4J_Demos instance. This file is under the rdbms/jlib directory. To access xsu12.jar for OC4J demos, please add the following to j2ee/OC4J_Demos/config/application.xml:
<library path="../../../rdbms/jlib/xsu12.jar" />
And, in accordance with the instructions found in the Oracle9i Application Server Administrator's Guide, the DCM Command-Line Utility updateConfig command must be run after making any hand edits to OC4J.xml files.
JSP TLD files are in the <OC4J_HOME>/jsp/lib/tlds directory. Copy them to your application WEB-INF directories as needed. (JSP TLD files are also available from the ojspdemos.ear file in the OC4J_Demos instance in Oracle9iAS.)
Following are the known issues in Oracle9iAS Containers for J2EE Services Guide:
The "Data Sources" chapter of the Oracle9iAS Containers for J2EE Services Guide refers to "Merant Drivers". This should be changed to "DataDirect Connect Drivers".
According to the "Deploying Stand-Alone Resource Adapter Archives" section of Chapter 12, you can deploy a stand-alone resource adapter (RAR) that is compliant with J2EE Connector Architecture using the -deployconnector switch in admin.jar. This switch is not in fact supported in the 9.0.2 implementation.
Chapter 14 describes the support that HTTPClient provides for the java.net.URL class. The following text appears:
If the java.net.URL framework is used, then set the java.protocol.handler.pkgs system property to select the HTTPSConnection package as a replacement for the JDK client as follows:
java.protocol.handler=HTTPClient
The preceding contains the following errors:
The package that replaces the JDK HTTP client should be HTTPClient, not HTTPSConnection.
The property setting example is incorrect. It should be:
java.protocol.handler.pkgs=HTTPClient
Following are the known issues in Oracle JDBC Release Notes:
Section 4, "Release Notes for Oracle JDBC," should read:
This section includes issues with JDBC that are not reflected in the Oracle9iAS documentation. The JDBC drivers shipped with this Oracle9iAS version have known problems. A JDBC patch addresses the problems. The patch is accompanied by a release note, which includes a list of known problems. Follow the instructions in the Oracle9i Application Server Installation Guide to install the necessary patches before you run Oracle9iAS.
Following are the known issues in Oracle JAZN Release Notes:
Section 7, "Release Notes for JAZN," should be called "Release Notes for JAAS". The first sentence should also refer to JAAS. The note should read:
|
Note: Some class and component names contain the word "JAZN," which is the internal code name for "JAAS provider." |
The default jazn.xml file is located in ORACLE_HOME/j2ee/home/config. The jazn.xml file found in ORACLE_HOME/j2ee/home/jazn/config is a private copy used by Oracle Universal Installer.
The above issue should be added in the OC4J Release Notes under "Release Notes for JAAS".
When the user repository (either XML-based file or OID, that is, LDAP-based Oracle Internet Directory), has multiple realms, the default realm should be specified in jazn.xml. For example, if you are using JAZN-XML, and your default realm is called jazn.com, your jazn.xml file would consist of the following:
<jazn provider="XML" default-realm="jazn.com" location="./jazn-data.xml" />
If you are using JAZN-LDAP, the location would be the URL for the OID server, as, for example:
<jazn provider="LDAP" default-realm="jazn.com"location="ldap://oid.us.oracle.com:389" />
Furthermore, the jazn tag in ORACLE_HOME/j2ee/home/config/application.xml must also specify the default realm if there is more than one.
|
Note: In the JAAS context, a realm refers to a user community. This is a namespace for users and roles. When there are multiple realms in the user repository, the default realm must be specified, so that JAAS knows the default namespace in which to look up users and roles. |
The above issue should be added in the OC4J Release Notes under "Release Notes for JAAS".
The Oracle9i Application Server mod_plsql User's Guide contains the following documentation errata:
In Section 2.6.8, "Direct BLOB Download", Step 2, the example:
procedure download_blob(varchar2 name) is
should be:
create or replace procedure download_blob(name in varchar2) is
In Section 2.6.8, "Direct BLOB Download", Step 2b, the example:
htp.p('Content-Length: ' || dbms_lob.get_length(myblob))
should be:
htp.p('Content-Length: ' || dbms_lob.getlength(myblob));
This section describes issues in the following Oracle HTTP Server documentation:
Following is the known issue in Oracle HTTP Server Administration Guide.
Step 6 in the "Configuring the IIS Listener for Single Sign-On" section of the "Using Oracle9iAS Proxy Plug-in" appendix of the Oracle HTTP Server Administration Guide incorrectly states the following:
Restart IIS (stop and then start the IIS Server), ensuring that the oproxy filter is marked with a green up-pointing arrow.
It should say:
Restart IIS (stop and then start the IIS Server), ensuring that the osso filter is marked with a green up-pointing arrow.
In the "Using Single Sign-On with the Plug-in" section of appendix A of the Oracle HTTP Server Administration Guide, the "OSSO Configuration File Examples" incorrectly presents the syntax for the LoginServerFile directive with double quotes around the value.
The correct syntax is:
LoginServerFile = /path/config/sso_conf
This section describes issues in the following Oracle9iAS InterConnect documentation:
Following are the known issues in Oracle9iAS InterConnect User's Guide.
Figure 1-2 in the Oracle9iAS InterConnect User's Guide. should include the term "First Name" under the "Common View".
In Chapter 2, "Using iStudio" under the "Deploy Navigation Tree" topic the second line is:
"Each object type in the Design Navigation tree is identified by an icon and name."
It should read:
"Each object type in the Deploy Navigation tree is identified by an icon and name."
This section describes issues in the following Oracle9iAS Discoverer documentation:
Following are the known issues in Oracle9iAS Discoverer Configuration Guide:
The Oracle9iAS Discoverer Configuration Guide describes how to use Oracle Enterprise Manager (OEM) to specify the communication protocol that the Discoverer Plus applet and the Discoverer servlet use to communicate. The protocol you specify in OEM is saved in the plus_config.xml file.
However, currently you cannot use OEM to specify the communication protocol. Instead, you must use a text editor (or an XML editor) to modify the plus_config.xml file directly, as follows:
Open plus_config.xml in a text editor.
The file is located in:
<ORACLE_HOME>/j2ee/OC4J_BI_Forms/applications/discoverer/web/plus_files/xsl
Locate the following line in the file:
<transport name = "protocol_option"/>
where "protocol_option" is one of the following:
"jrmp" (the default)
"http"
"https"
|
Note: Do not change the line<transport name = "codebase"/>
|
Change the value of "protocol_option" as required.
Save the changes you have made and close the file.
Use OEM to stop and restart the OC4J_BI_FORMS system component.
Notes:
The above protocol options are referred to in the Oracle9iAS Discoverer Configuration Guide as follows:
jrmp is the "Default" option
http is the "Tunneling" option
https is the "Secure Tunneling" option
The Oracle9iAS Discoverer Configuration Guide includes detailed descriptions of the different protocol options. For convenience, the following is a summary of the options:
If transport is set to "jrmp", Discoverer will first attempt to make a direct connection using RMI. A direct connection will only work within a firewall. If a direct connection cannot be established, Discoverer will automatically attempt to use HTTP or HTTPS.
If transport is set to "http", Discoverer will use the same protocol to communicate with the Discoverer servlet as was originally used to download the applet itself (i.e. either HTTP or HTTPS depending on the URL). This method supports access via firewalls.
If transport is set to "https", Discoverer will always use HTTPS tunneling. This method only supports secure access via firewalls.
This section describes issues in the following Oracle9iAS Single Sign-On documentation:
Following are the known issues in the Oracle9iAS Single Sign-On Administrator's Guide:
The "Enabling the Single Sign-On Server for SSL" section in "Concepts for Administrators" chapter of the Oracle9iAS Single Sign-On Administrator's Guide implies that administrators have the option of enabling the Single Sign-On Server for SSL during an Oracle9iAS infrastructure installation. In Oracle9iAS, Release 2, no such option exists. The server must be enabled for SSL after Oracle9iAS has been installed, using the procedures provided.
Following are the known issues in Oracle9iAS Single Sign-On Release Notes:
Section 1.3, "Configuring the Oracle HTTP Server for Legacy Applications", of the Oracle9iAS Single Sign-On Release Notes states that the mod_osso.conf file on the Oracle HTTP Server must contain the following directive:
Listen 5000
This parameter denotes the non-SSL port through which mod_osso accesses information about external applications. The parameter should appear in the httpd.conf file on the Single Sign-On server instead of in the mod_osso.conf file on the Oracle HTTP Server.
This section describes issues in the following Oracle9iAS Wireless documentation:
Following are the known issues in Oracle9iAS Wireless Developer's Guide:
The Calendar and Tasks Modules require configuration. In Oracle9iAS Wireless Developer's Guide, you are instructed to install the Lotus Domino Toolkit for Java/CORBA, add NCSO.jar to the classpath for Oracle9iAS Wireless 2.0. Installing the toolkit creates "DTJava" directory on the file system.
Note the following cautions:
Ensure you download "Lotus Domino Toolkit for Java/CORBA Release 5.0.8 Update" or "Lotus Domino Toolkit for Java/CORBA Release 5.0.5 Update Shipping". Do not use the version 2.x toolkit.
On the Domino server, the server tasks HTTP and DIIOP must be running. Ensure that the Domino server notes.ini file contains the following line:
ServerTasks=<other tasks>,http,diiop
The following parameter should be added to the table "Configuration Parameters for the Mobile Directory" in the Oracle9iAS Wireless Developer's Guide:
ORACLE_SERVICES_PIM_DIRECTORY_QUERY_BYNAME_RESULTLIST_SHORTLIST
Comma-delimited series of tokens, either "true" or "false", and is of the same length as the parameter ORACLE_SERVICES_PIM_DIRECTORY_QUERY_BYNAME_RESULTLIST.
This section describes issues in the following Oracle Ultra Search documentation:
Following are the knows issues in Oracle Ultra Search Release Notes:
The following changes should be made in the Oracle Ultra Search Release Notes:
The reference to "primary schedule", and "default web source" is wrong. "Primary schedule" and "default web source" have been removed from Oracle9iAS.
Change the term "Seed URLs" to "Starting address".
Section 4, "Understanding Web Data Sources" is invalid and should be removed from the release notes.
Section 2.2.2, "Setting the JOB_QUEUE_PROCESSES parameter" should be changed to the following:
Oracle Ultra Search schedule launching uses the DBMS_JOB package. Therefore, the Oracle Ultra Search DBA must make sure that there is least one SNP process running. In other words, the initialization parameter file for the Oracle Ultra Search database instance should contain a line that specifies the JOB_QUEUE_PROCESSES parameter to be at least 2.
Section 5.12, "Portal Users Should Embed Ultra Search Portlets That Are Hosted On The Same Host" in the Oracle Ultra Search Release Notes should be modified to state the following:
Portal Users Should Embed Ultra Search Portlets Hosted On Same OC4J InstancePortal users should embed Ultra Search portlets that are hosted on the same OC4J instance as the Oracle9iAS Portal server. For example, if the Oracle Portal OC4J instance is installed on host A / port 7777, then the Ultra Search provider must also be hosted as a Web application on host A / port 7777.
It is possible that the Ultra Search provider running on host A / port 777 could be registered with a second Oracle Portal instance running on a different host / port combination. In such cases, when the Ultra Search portlet is embedded within portal pages, the pop-up list-of-values will not work correctly. This is because of an security bug inherent in Javascript.
The following change should be made in the Oracle Ultra Search online documentation:
The "Create a Data Source Type" section in the "Sample Crawler Agent README" page of the Oracle Ultra Search online documentation contains an incorrect value for the sample agent jar file name. This causes you to get the following crawler error when you try to use the sample agent:
WKG-30116: Can not find agent class "SampleAgent" from the java class path
The correct value is "sampleAgent.jar", instead of "sampleagent".
