Install Apache HTTPD from ZIP
4.2 Installation (as zip from JBoss EWS) NOTE – If you already have an instance of Apache HTTPD installed and just want to configure it, please skip this section. JBoss EWS comes with a version of Apache HTTPD web server. To install it, execute the following steps. If you haven’t done so already, download JBoss EWS from the customer support portal - https://access.redhat.com/jbossnetwork/restricted/listSoftware.html?product=webserver&downloadType=distributions&productChanged=yes&version=5.0.2%20GA Unzip this download. For the sake of consistency we will refer to the location where you unzipped this file to as $EWS_HOME. Copy recursively the httpd directory to the location on your filesystem where you want Apache HTTPD installed at. In this example we install to /var/local/httpd: Illustration 9: Copying ews httpd download to a new directory The version of Apache that ships with EWS comes ready with SSL. Because of this dependency, you will need to make sure that distcache and pcre are installed on your system (*nix) rpm -q distcache pcre If you get a version number back, then you are fine. If either is not installed, then you will need to install them, for example yum install distcache Once installation is complete, run the following again to make sure you see both installed: Illustration 10: Verifying distcache and pcre are installed If you see the above (or similar / higher version numbers) then continue on. Go to the $EWS_HOME/httpd directory (in these examples it is /var/local/httpd) Execute the postinstall script: (note you will need to have root access for this) Illustration 11: Running postinstall script If you do not see any errors, then the script has executed successfully. This script creates an SSL certificate to use when you first start up apache. NOTE – you will need to apply an enterprise level SSL certificate for proper use. The script also sets up some environment variables to be used as well as updates the configuration file with installation location information. The configuration file will be covered in upcoming sections: Illustration 12: Inside the postinstall script, looking at what values are being set At this point in time, we should verify that we can start up Apache HTTPD and that it starts without error. Illustration 13: Start up Apache HTTPD Go to the logs directory and make sure the following log files are present: Illustration 14: Verify logs are being written to Finally verify that you can access the web server through a browser by hitting http://localhost. NOTE – you will get a 403 error because of the default HTTPD configuration shipped with EWS. Illustration 15: First time accessing HTTPD through a browser If you have confirmed that your Apache HTTPD instance is up, stop the server now so we can finish configuring it. Do this by executing the following command: Illustration 16: Stop Apache HTTPD