We
wanted to install Oracle HTTP Server instance in the DMZ to front-end the web
Logic Server hosted in the application layer and hence did the standalone
installation.
Launch
the installation program by entering the following command: ./fmw_12.1.3.0.0_ohs_linux64.bin
This
screen introduces you to the product installer.
Enter
the path to an existing Oracle Fusion Middleware Infrastructure Oracle home.
Select
Standalone HTTP Server (Managed independently of WebLogic server) if you are
installing Oracle HTTP Server in a Standalone domain.
If
you want to save these options to a response file, click Save Response File and
provide the location and name of the response file
Configuring Oracle HTTP Server in a Standalone Domain
To
begin domain configuration, go to ORACLE_HOME/oracle_common/common/bin
./config.sh
Select Oracle HTTP Server (Standalone) -
12.1.3.0 [ohs].
Select Oracle Hotspot JDK.
Specify the system component name
Specify the OHS Server details
Select Per Domain as the Node
Manager type and specify the Node Manager credentials.
Review the details of each item on the screen and verify
that the information is correct.
Starting the Node Manager & Oracle HTTP Server
Navigate to the DOMAIN_HOME/bin and execute
$ nohup sh startNodeManager.sh &
To start the web server run script $
./startComponent.sh
ohs1 in the same location
To test the server enter the url as http://hostname:port
Starting Oracle HTTP Server Instances on a Privileged Port (UNIX Only)
On a UNIX system, TCP ports in a reserved range (typically less than 1024) can only be bound by processes with root privilege. Oracle HTTP Server always runs as a non-root user; that is, the user who installed Oracle Fusion Middleware. On UNIX, special configuration is required to allow Oracle HTTP Server to bind to privileged ports.
To enable Oracle HTTP Server to listen on a port in the reserved range (for example, the default port 80 or port 443) as a process without root privilege, use the following steps.
No comments:
Post a Comment