The OHS is the abbreviation for the Oracle HTTP Server. This is the core component for the client facing interface of Oracle Applications. Much of how Oracle Applications behaves is controlled from the OHS.
The OHS is built upon the Apache Server project. The Oracle Application server in Oracle Applications 11i (220.127.116.11) is based on Apache 1.3.
Oracle Application Server 10g Release2 is based on Apache 2.Though we do not have 10g release 2 application server by default in 11i, we can choose to implement the 10g applications server with 11i.
You can find out the current version of OHS by the command httpd -version
$ httpd -version
Server version: Oracle HTTP Server Powered by Apache/1.3.19 (Unix)
Server built: Apr 5 2004 16:17:45 (iAS 18.104.22.168.2 rollup 4)
There are some core files which control the behavior of the Oracle HTTP Server. Again most of these files are autoconfig managed , so changes to them should be via the Oracle Applications Manager and autoconfig must be run to propagate these changes to the respective config files.
This is manin config file for the Apache based OHS. It contains all vital configuration information for the OHS like the port on which the server is running, the portocol used etc.A detailed list of derivates supported by the httpd.conf file can be found in the apache documentation. Again as mentioned before this file is also autoconfig managed.
The httpds.conf file is similar to the httpd.conf. The httpds.conf filers comes into use when apache runs in the Secure Sockets Layer implementation(SSL).Another way make sure if httpds.conf is being used in your environment or not is to open up the apachectl file in the Apache/bin directory and check if the httpds executable is being used along with the httpd executale. something similar to below
The access.conf file is natively used to specify the acess control files for the HTTP server. But in Oracle Implementation of Apache server this file is essentially kept empty and instead the AccessConfig directive in httpd.conf is used.
The URL firewall or the url_fw.conf file implementation is used to provide an additional layer of security on the external tier.This file comes into play once you define a node as external.
After this is enabled only the urls specified in the url_fw.conf files will be accessible through the external tier in a DMZ architecture.Once enabled the httpd.conf file will have a link to include this file.
This file contains the security configuration for the OHS.It has information regarding security auditing and also location of the security audit log file location.
This a file that stores the configuration information for various supported modules in Oracle applications like imeeting , OEM etc.It will contain entries to include these configuration files.
These module specific configuration file like the imeeting.conf will also reside in the Apache/conf directory on the application server.
Next» Oracle Administration Using adadmin