Release 1.0.2.2 for Windows NT
Part Number A90220-07
 Library |
| Oracle9i Application Server Release Notes Addendum Release 1.0.2.2 for Windows NT Part Number A90220-07 |
|
Release 1.0.2.2 for Windows NT
September 2001
Part No. A90220-07
This addendum notes information that is missing from the Oracle9i Application Server Release 1.0.2.2 Release Notes. It is intended to be used in conjunction with the Release Notes.
Oracle will periodically update these notes as new information becomes available. The latest version can be found at
http://otn.oracle.com/products/ias
The Rights and Restrictions included in the Release Notes also apply to the information in this Addendum.
Before using Oracle9i Application Server, read through each item in this section to gain an understanding of the restrictions and limitations in this release that may require additional steps.
For a the most current OJSP and a related information, get OJSP version 1.1.3.1 or higher from
http://otn.oracle.com/tech/java/servlets/
There are port conflicts between mod_oprocmgr and the Oracle9i File System. The jserv.properties file by default has JServ listening only on port 8007. As part of setting up the Group Mount (ApJServGroupMount), Oracle9i File System uses the jserv.properties file. This, however, causes a conflict with mod_oprocmgr, which is also using 8007. The solution is to use a different properties file for the ifs group, and use a different port number.
Please note that the automated Oracle9i File System servlet configuration does not cater to the revised configuration mechanism in the High Availability feature. These steps are detailed out in the Oracle9i File System release notes, and the following steps are in addition to the release notes.
The Oracle9i File System release notes contain information on the steps that you must perform to be able to configure the Oracle9i File System Servlet with the Oracle HTTP Server for Oracle9iAS Release 1 (v1.0.2.2).
You must perform the following steps in addition to the steps mentioned in the Oracle9i File System release notes.
%ORACLE_HOME%\Apache\Apache\bin apachectl stop
%ORACLE_HOME%\Apache\Apache\bin apachectl start
Here is a list of new features and changes in OAI 4.1 from OAI 4.0:
Throughput Measurement - Ability to monitor the throughput of Adapters through the EM Console.
Message Tracking - Ability to track any messages that flow through OAI. To use this feature, you must select at least one "Tracking Field" in iStudio. Then, you will be able to track messages by specifying values for any of these tracking fields in the EM Console.
Remote Management - EM Console provides features for remotely managing Adapters and Repository. Features include start/stop, view log files, edit ini file, etc.
Metadata Updates to running adapters - When you make changes to the metadata through iStudio, you now have an option to push this new metadata to any running adapter. (Use the "File -> Push Metadata" menu option in iStudio).
Notification on failure/shutdown - EM Console provides Email/Pager alerts, to notify you that Adapters or Repository have stopped.
Message Resubmission - The EM Console now lets you view, modify, and resubmit all "errored out" messages in the database.
Workflow Support - OAI works with Oracle Workflow for business process collaborations.
Enhanced AQ Support - The AQ Adapter has been enhanced to handle more than just XML payload. For XML, the payload can be in either a BLOB or CLOB. For non-XML, the payload can be any ADT; this ADT can be directly imported in iStudio.
SAP Adapter - SAP Adapter is available on the Solaris platform as well.
SAP ABAP Support - SAP Adapter supports ABAP function modules in addition to BAPIs and IDOCs.
Enhanced Array Mapping Support - iStudio provides graphical mapping of array attributes.
Password encryption - All passwords stored in configuration files can now be encrypted. Please refer to the Configuration Security section of the Installation Guide.
OID no longer necessary - All necessary configuration is stored directly in the HUB database. When creating a project in iStudio, you must provide the hub database connection information along with the repository information.
OMB no longer necessary - OAI uses Oracle JMS interface to Oracle AQ, so OMB is no longer needed.
Single .ini file - All OAI configuration parameters are all in one file, adapter.ini (as opposed to adapter.ini, Agent.ini, and service.ini).
Improved logging - To preserve log files from a previous run, log files are created in a different directory every time the adapter is started. The timestamp is used as the name of the directory to keep it unique across various runs. All logging is done to only one file "oailog.txt" (as opposed to AgentLog.txt, <Adapter>Log.txt, service.log). As before, when the size of this file exceeds 1MB, a new file "oailog-1.txt" is created (followed by "oailog-2.txt", .... and so on).
Persistence Files - To avoid cluttering up the adapter directory with files, all the persistence files (containing persisted messages, cached metadata, and other information to ensure Guaranteed & Exactly Once delivery) are stored in the .../persistence/... directory.
Database Adapter more performant - The database adapter performance has been enhanced. The database hosting the OAI Schema has support for Oracle Objects in order for the performance gain to be realized.
Cascading Deletion of integration objects in iStudio - When an object is deleted, all objects referred to by that object are also deleted (provided they are not referenced by other objects). For example, if a Customer object contains an Address object, and the Customer object is deleted, the Address object will also be deleted. But if a Purchase Order object contains the Address object, then Address will not be deleted. Also, the Address object cannot be deleted directly, since it is referenced by another object.
Importing data types - iStudio supports importing attributes of other iStudio data types.
The Oracle9iAS Portal online help does not get installed during the Oracle9iAS install process. Follow these steps to install the help:
From the <ORACLE_HOME>/assistants/opca directory:
runimp.csh ../../bin/imp <portal_schema>/<portal_password> <database_hostname> <database_port> <database_sid> PORTAL_HELP <portal_schema> ../../portal30/doc/site/hlp30ca.dmp hlp30ca.dmp.log
@utlsbmrg.sql reuse database_user 0
To install Oracle Workflow Release 2.6, you must include the connect string for your database in your tnsnames.ora file ($ORACLE_HOME/network/admin/tnsnames.ora). The Workflow installation process requires this information in order to connect to the database.
The Oracle9iAS Email 5.2 for Windows NT Installation Guide contains sections with configuration information of jserv.properties and zone.properties (pages 3-16 and 3-17).
These sections currently instruct the user to add lines to these files that contain variables like $ORACLE_HOME and $ESCLIENT_HOME. This is incorrect; instead, the full path to directory locations should be used.
FastCGI programs are restarted continuously even if there are errors in the program or configuration. When you start the HTTP Server, ensure that all the FastCGI scripts can be started correctly (by looking at the messages in the log file).
When you install Portal, the configuration assistant may report that the shared pool size or java pool size is insufficient. This is because the assistant expects the pool size value to be in bytes. To fix this problem, change the shared pool size in init.ora to the integer value in bytes (not M, K or G notation). For example, if
SHARED_POOL_SIZE=100M
change it to:
SHARED_POOL_SIZE=100000000
and restart the database.
If mod_ose.conf is included in%ORACLE_HOME%\Apache\Apache\conf\oracle_apache.conf, the command "apache -k restart" does not work properly.
This prevents the HTTP Server from a graceful restart. The server will stop some time after the command is issued. The error log file will contain messages like these:
[Thu May 17 11:18:25 2001] [crit] (10038)(FormatMessage failed with code 317): Parent: WSADuplicateSocket failed for socket 292. [Thu May 17 11:18:25 2001] [error] (2)No such file or directory: master_ main:create child process failed. Exiting.
The Oracle9iAS Release 1 (v.1.0.2.2) installation changes the jserv.conf file so that any URLs (links, bookmarks, etc.) that include references to Discoverer4i\Viewer will no longer work. To fix this problem, change Discoverer4i\Viewer to discoverer4i\viewer (lower case) in the jserv.conf file.
Sites should be configured to restrict access to the locations to valid users of mod_oprocmgr. Valid users of mod_oprocmgr include external processes (JServ processes), administrators sending requests to /oprocmgr-status, and administators using DMS to monitor HTTP Server external processes.
The httpd.conf file should be modified as shown in the following example (additions are shown in bold text):
<IfModule mod_oprocmgr.c> ProcNode iashost.company.com 7777 <IfDefine SSL> ProcNode iashost.company.com 80 </IfDefine> <Location /oprocmgr-service> SetHandler oprocmgr-service order deny,allow deny from all allow from iashost.company.com </Location> <Location /oprocmgr-status> SetHandler oprocmgr-status order deny,allow deny from all allow from iashost.company.com </Location> </IfModule>
Another way that the system administrator may want to modify httpd.conf is to permit access by all nodes within the same domain using something similar to "allow from .company.com". Where possible, this strategy is preferable because it permits administration from multiple locations without having to explicitly list each administrative host. Hostname-based access control should be sufficient for most environments. The performance issue with performing DNS lookups during hostname-based access control is not critical in this case, because access to mod_oprocmgr occurs infrequently.
If you use the Services management window on Windows 2000 to start, stop, and restart the Oracle HTTP Server multiple times after any servlet invocation has occurred, the server stops and a Dr. Watson window appears. There is no workaround; simply close the Dr. Watson window. This problem has only been observed during shutdown and should not affect proper functioning of the installation.
Running Oracle9iAS Forms using the ListenerServlet causes an ORA-12222 error. The solution is to install Oracle9iAS Forms 6.0.8.14 (patch set 5, available on MetaLink) after installing Oracle9iAS Release 1 (v1.0.2.2).
If you install Oracle9iAS onto the same machine where Oracle9iAS Discoverer has been previously installed, the following error occurs:
The procedure entry point ??OVBJRuntime@@QAE!PAD!Z could not be located in the dynamic link library vbjruntime.dll" during the installation of Oracle9i Application Server.
Click OK to continue. This error is not fatal, and is generated by the OAD utility program within Oracle9iAS Discoverer. After the installation is complete, you can complete the preferences registration for Discoverer by running the registerall.bat file located in the%806_HOME%\discwb4\util directory.
The JDBC Thin Driver provided as part of Oracle9iAS Release 1 (v1.0.2.2), cannot be used to connect and run against an Oracle9i database.
You must download and install a patch in order to connect to a 9i database. The patch and associated information is at:
http://metalink.oracle.com/metalink/plsql/ml2_documents.showNOT?p_id=146267.1
The download contains instructions to install the patch. If you install jdbc 8171, or rdbms 8171, or rdbms 8171B, after installing the JDBC patch, you will need to re-install the JDBC Thin patch in order to connect to an Oracle9i database.
After the Oracle9iAS installation is complete, Discoverer objects must be registered with the Object Activation Daemon (OAD). To register the objects:
%806_HOME%\discwb4\util.
The Oracle9iAS Installation Guide contains terminology errors on the following page numbers:
3-17, 4-19, 5-23
On these pages, "Upgrading Installation Detected" should read, "Migration Installation Detected". All occurrences of "upgrading" should be changed to "migrating".
Release Note 1.4.2.1.7 contained examples with syntax errors. Below are the correct examples:
ApJServGroup group1 2 1
P:\ORACLE\10210PWE\Apache\Jserv\etc\jserv.properties
ApJServGroup group1 1 1
P:\ORACLE\10210PWE\Apache\Jserv\etc\jserv.properties
ApJServGroup group2 1 1
P:\ORACLE\10210PWE\Apache\Jserv\etc\jservSoap.properties
Oracle9iAS Portal Configuration Assistant stops at 90% during the Oracle9iAS 1.0.2.2 installation. In Oracle9iAS Release 1 (v1.0.2.2), Diagnostics was an added feature of the Oracle9iAS Portal Configuration Assistant. Diagnostics portion checks the validity of the JServ and Oracle HTTP Server URLs for the installed Portal repository. If the JServ and Oracle HTTP server are not properly configured or not running during the Portal installation, the diagnostics stop during this validation. The Portal installation is complete, so you can safely cancel the Portal Configuration Assistant and resume the installation. However, because the Diagnostics detected a misconfiguration in JServ and/or the HTTP Server, you must resolve this before accessing the installed Oracle9iAS Portal.
The Oracle9iAS Email Installation Guide that was released with the Oracle9iAS Release 1 (v1.0.2.2) Windows NT/2000 documentation was for SUN SPARC Solaris. The updated Oracle9iAS Email Installation Guide is available with the Oracle9iAS Release 1 (v1.0.2.2) Windows NT/2000 documentation at
http://otn.oracle.com/docs/products/ias/content.html.
The following warning message in the ssl_engine_log file is wrong and should be ignored:
[warn] You are using mod_ssl under win32. This in *NOT* officially supported. Use at your own risk!
If you use JDK version 1.1.8 instead of the JDK (version 1.2) shipped with Oracle9iAS, JServ processes will fail to start. Messages similar to the following are found in the error_log:
ORACLE_HOME/Apache/jdk/bin/java[15]: dirname: not found ORACLE_HOME/Apache/jdk/bin/java[15]: dirname: not found ORACLE_HOME/Apache/jdk/bin/java[16]: basename: not found ORACLE_HOME/Apache/jdk/bin/java[16]: basename: not found ORACLE_HOME/Apache/jdk/bin/java[65]: test: argument expected ORACLE_HOME/Apache/jdk/bin/java[65]: test: argument expected was not found in ORACLE_HOME/Apache/jdk/bin/../bin/sparc/native_threads/ was not found in ORACLE_HOME/Apache/jdk/bin/../bin/sparc/native_threads/
To resolve this error, add the following line to the jserv.properties and jservSoap.properties files:
wrapper.env=PATH=/usr/bin
After adding this line, perform a graceful restart of the server. The JServ processes will start.
Oracle9iAS v.1.0.2.2 is certified to run against a 9i Database Server v9.0.1.0.0 Solaris release with the following known limitations:
In order to run Oracle9iAS Portal with a version 8.1.7 database, you must be using these versions:
There is a known issue with the Oracle9iAS Portal on 8.1.7 Standard Edition (SE). The Installer gives an error when installing Oracle9iAS Portal into 8.1.7 SE. The workaround is to execute the Oracle Portal Configuration Assistant (OPCA) from the command line and specify the "verbose" mode. In this mode, the errors are ignored and the installation runs to completion.
To run OPCA from the command line for Oracle9iAS Portal version 3.0.9:
At approximately line 27 there is a long command line ending in:
> install.log
...change_on_install USERS TEMP USERS USERS TRUE FALSE FALSE TRUE > install.log
changes to:
...change_on_install USERS TEMP USERS USERS TRUE TRUE FALSE TRUE > install.log
The Oracle Plug-in for Microsoft IIS is only installed with Oracle9iAS Enterprise and Standard Editions. The Oracle9i Application Server Installation Guide incorrectly states that it is installed with the Minimal Edition.
Section 1.5.7.1.4, Oracle9iAS Discoverer Patch is obsolete and should be disregarded.
Section 1.4.1.2.2, "Support for Third Party Components in Oracle9i Application Server"in the subsection entitled "Apache Modules" is amended as follows:
The text:
"In addition, Oracle will only provide technical support for problems that can be reproduced with an Apache configuration consisting only of supported Oracle Apache Modules."
is replaced with:
"Apache modules modify Apache event processing; therefore, Oracle may require that a problem be reproduced with an Apache configuration consisting only of supported modules in order provide support. Oracle will only provide bug fix support for those problems which can be reproduced in a configuration consisting only of supported modules."
Oracle9i Application Server v. 1.0.2.2 includes Oracle Internet Directory 2.1.1. A more recent version of Oracle Internet Directory, 3.0.1, is available with Oracle9i Database. If you wish to use this latest version, order the Oracle9i CD Pack for your platform and install Oracle Internet Directory from that media kit. For information about Oracle Internet Directory and any available patchsets, please see
http://otn.oracle.com/products/oid/content.html.
Release notes that are no longer valid are listed below:
1.5.1.8 Deploying Enterprise JavaBeans to Oracle9iAS is obsolete and should be deleted.
1.5.3.1.12 Executing the owaload.sql script is obsolete and should be deleted.
1.5.1.18 Apache Configuration Error Upon Installation is obsolete and should be deleted.
1.5.1.3 De-Installation/Cleanup Procedure is incorrect and should read:
instead of:
1.5.6.2.1 Configuration Assumes Incorrect Listener Port is incorrect and should read:
instead of:
Oracle is a registered trademark of Oracle Corporation. Other names may be trademarks of their respective owners.
Copyright © 2001, Oracle Corporation.
All Rights Reserved.
|
|
 Copyright © 2001 Oracle Corporation. All Rights Reserved. |
|