|
Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for Microsoft Windows (64-Bit) on Intel Itanium B15849-03 |
|
 Previous |
 Next |
|
Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for Microsoft Windows (64-Bit) on Intel Itanium B15849-03 |
|
|
Previous |
Next |
This chapter describes issues associated with Oracle HTTP Server. It includes the following topics:
This section describes general issues and workarounds. It includes the following topic:
To use the Oracle Application Server Containers for J2EE (OC4J) plug-in with the OC4J standalone product without Oracle Process Management and Notification Server (OPMN), only static routing to specific hosts and ports is allowed within the OC4J plug-in. OC4J must be configured to use Apache JServ Protocol (AJP). Using static routing with hosts and ports means that only Oc4jMount directives such as the following are supported:
Oc4JMount /j2ee/* ajp13://localhost:6001,localhost:6002
To enable AJP in the OC4J configuration, a line such as the following must be present in the default-web-site.xml file in the OC4J configuration:
<web-site port="3000" protocol="ajp13" display-name="OracleAS Java Web Site">
In this example, the web-site port value specifies the port at which the OC4J process will listen for incoming AJP requests.
This section describes configuration issues and their workarounds. It contains the following topic:
By default, Oracle HTTP Server sends redirects to the OracleAS Web Cache listening port. If OracleAS Web Cache is not running or is disabled, then redirects from Oracle HTTP Server and any OC4J application behind Oracle HTTP Server will not work. If you are not planning to run OracleAS Web Cache, then edit the httpd.conf and ssl.conf files, changing the Port directive so that it matches the Listen directive instead of the OracleAS Web Cache listening port.
