Installing a Non Secure Apache Web Server

Language:

This section provides procedures for installing a non secure Apache web server.

This procedure installs a non secure version of the Apache web server.

The Apache binaries are included in the web/server/apache-22 package.

Place the binaries on the local file system on each of your cluster nodes or on a cluster file system.

Run the pkg info command to determine if the Apache data service package, ha-cluster/data-service/apache, has been installed.
If the package has not been installed, install it as follows.
- Run the following command.
```
# pkg install ha-cluster/data-service/apache
```

This procedure installs a non secure version of the Apache web server.

Place the web server binaries on the local file system on each of your cluster nodes or on a cluster file system.

On a cluster member, become an administrator that provides solaris.cluster.admin authorization.

Install the Apache software using the installation procedures found in the Apache installation documentation.
Install the Apache software using the Apache installation documentation you received with your Apache software or see the installation instructions at http://www.apache.org.

Update the httpd.conf configuration file.
- Set the ServerName directive. (In Version 2.2 of Apache, the ServerName directive specifies the hostname and the port.)
- Set the BindAddress directive (optional). (The BindAddress directive only exists in versions prior to Apache 2.2. For Apache 22, see the following bullet for the Listen directive.)
- Set the Listen directive. The Listen directive must use the address of the logical host or shared address. (The Listen directive only exists in Apache 2.2 and beyond. For Apache versions prior to Apache 2.2, see the previous bullet for the BindAddress directive.)
- Set the ServerType, ServerRoot, DocumentRoot, ScriptAlias, and LockFile directives.
  Note - The ServerType directive does not exist in Apache 2.2.
- Set the Port directive to the same number as the Port_list standard resource property. See Step 4 for more information.
- Add the following lines of code to the httpd.conf configuration file if you choose to configure the Apache software as a proxy server.
```
# Proxy Server Directives.
<IfModule mod_proxy.c>
  ProxyRequests On
  <Directory proxy:*>
    Order deny,allow
    Deny from all
    Allow from IP_ADDRESS
  </Directory>
  ProxyVia On
</IfModule>
# End of Proxy Server Directives.
```
  Note - If you configure the Apache software as a proxy server, the CacheRoot setting must point to a location on the cluster file system.

Verify that the port number or numbers in the httpd.conf file match those of the Port_list standard resource property.
You can edit the httpd.conf configuration file to change its port number or numbers to match the standard Oracle Solaris Cluster resource property default (port 80). Alternatively, while you configure Oracle Solaris Cluster HA for Apache, you can set the Port_list standard property to match the setting in the httpd.conf file.

Update the paths in the Apache start/stop script file (Bin_dir/apachectl).
You must change the paths from the Apache defaults to match your Apache directory structure. For example, change the line in the BIN_dir/apachectl script beginning with HTTPD=/usr/local/apache/bin/httpd to the following.
```
HTTPD='/usr/local/apache/bin/httpd -f /global/foo/apache/conf/httpd.conf'
```

Perform the following tasks to verify your configuration changes.
1. Run apachectl configtest to check the Apache httpd.conf file for correct syntax.
2. Ensure that any logical hostnames or shared addresses that Apache uses are configured and online.
3. Issue apachectl start to manually start your Apache server.
  If Apache does not start up correctly, correct the problem.
4. After Apache has started, stop it before moving to the next procedure.