Installation Instructions
Configuration Settings
Installation Instructions
Windows
Apache Installation
If you have already installed Apache you can disregard these instructions. If you haven’t installed Apache you can grab a build from the download page. http://sourceforge.net/projects/apachegui/files/1.11-Windows/
Apache 2.4
MSI Installer
1. Run the msi installer.
2. Apache should now be seen in your computers Program Files directory under
[PROGRAM_FILES]\Apache Software Foundation\Apache2.4
. This full path to Apache is known as the Server
Root.
3. You can now install and use ApacheGUI.
Zip File
1. Download the appropriate zip file for your system architecture.
2. Extract the Apache24 directory to the desired location of the Apache installation.
The full installation path that you use is known as the Server Root. For the purposes of these steps we will refer
to the Server Root path as [SERVER_ROOT]
.
3. Open a command prompt as an Administrator. Go to [SERVER_ROOT]/bin
and
run the command httpd -k install
.
4. You can now install and use ApacheGUI or start Apache manually using httpd -k
start
.
Apache 2.2
MSI Installer
1. Run the msi installer.
2. Apache should now be seen in your computers Program Files directory under
[PROGRAM_FILES]\Apache Software Foundation\Apache2.2
. This full path to Apache is known as the Server
Root.
3. You can now install and use ApacheGUI.
ApacheGUI Installation
1. Unzip the ApacheGUI archive to a directory of your choice. We will refer to this
directory as [APACHEGUI_HOME]
in the following installation steps.
2. You will need a jdk or jre in order to run Apache GUI. This means Java must be installed on your machine.
If you do not have Java installed then you can download Java from the Oracle download
pages.
http://www.oracle.com/technetwork/java/javase/downloads/index.html
Set your JAVA_HOME
and/or JRE_HOME
environment variable to the
pathname of the directory of your jdk or jre. You may add environment variables on Windows by selecting System
from the Control Panel, selecting Advanced system settings, and clicking Environment
Variables.
It is mandatory to set one of these environment variables, although you are free to set both.
JRE_HOME
The following is an example path for a correct JRE_HOME
C:\Program Files\Java\jdk1.7.0_05
(Incorrect)
C:\Program Files\Java\jre7
(Correct)
JAVA_HOME
JAVA_HOME
must be set to a jdk and not a jre! The following is an example
path for a correct JAVA_HOME
C:\Program Files\Java\jdk1.7.0_05
(Correct)
C:\Program Files\Java\jre7
(Incorrect)
3. To start the web tool go to [APACHEGUI_HOME]/bin
and run the batch file
run.bat
. Once the GUI has started it may be accessed through http://localhost:9999/ApacheGUI/.
4. To stop the web tool go to [APACHEGUI_HOME]/bin
and run the batch file
stop.bat
Linux Solaris and Mac OSX
ApacheGUI Installation
You will need a Java jdk in order to run Apache GUI. It is recommended that you install a jdk through your Operating System’s package manager.
1. Extract ApacheGUI.tar.gz to the desired location of install. For the purposes of these
steps we will refer to this directory as [APACHEGUI_HOME]
.
2. Open a terminal and switch to root permissions. You should be prompted for a password if you try to start ApacheGUI without root permissions.
3. Set your JAVA_HOME
environment variable to the pathname of the directory
of your jdk.
ApacheGUI will not start without a valid JAVA_HOME
. If you install Java from a package manager JAVA_HOME
should already be set up and you may skip this step.
4. To start the web tool go to [APACHEGUI_HOME]/bin
and run the
command:
#./run.sh
Once the GUI has been started it may be accessed through http://localhost:9999/ApacheGUI/.
5. To stop the web tool to [APACHEGUI_HOME]/bin
and run the command:
#./stop.sh
Package Settings
The following settings can be used to configure the GUI if you have installed Apache using your Operating System’s package manager. These settings are not applicable if you have installed Apache from source.
Mac OSX
Server Root – /usr
Primary Configuration File – /etc/apache2/httpd.conf
Configuration Directory – /etc/apache2
Log Directory – /var/log/apache2
Modules Directory – /usr/libexec/apache2
Binary File – /usr/sbin/apachectl
Debian, Ubuntu, Other Debian variants
Server Root – /etc/apache2
Primary Configuration File – /etc/apache2/apache2.conf
Configuration Directory – /etc/apache2
Log Directory – /var/log/apache2
Modules Directory – /usr/lib/apache2/modules
Binary File – /usr/sbin/apache2ctl
Fedora, CentOS, RHEL, other fedora variants
Server Root – /etc/httpd
Primary Configuration File – /etc/httpd/conf/httpd.conf
Configuration Directory – /etc/httpd
Log Directory – /var/log/httpd
Modules Directory – /etc/httpd/modules
Binary File – /usr/sbin/apachectl
OpenSUSE and SLES
Server Root – /etc/apache2
Primary Configuration File – /etc/apache2/httpd.conf
Configuration Directory – /etc/apache2
Log Directory – /var/log/apache2
Modules Directory – /usr/lib/apache2
(32 bit OS) or /usr/lib64/apache2
(64 bit
OS)
Binary File – /usr/sbin/apache2ctl
Configuration Settings
Endpoints
ApacheGUI is configured by default to run using http on port 9999.
The default endpoint and credentials are:
http://[HOST]:9999/ApacheGUI/ Username: admin Password: admin
You may change the username and password when configuring ApacheGUI after the first login.
Ports
ApacheGUI runs by default on port 9999.
To change or add a port open [APACHEGUI_HOME]/tomcat/conf/server.xml
and add
or modify a connector.
The following is the default connector that you will see in the server.xml file:
<Connector port="9999" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" URIEncoding="UTF-8" />
You may change port 9999 in the above connector or add a new connector to the file. You must restart ApacheGUI for any connector changes to take effect.
Please see the following for more information on tomcat connectors:
http://tomcat.apache.org/tomcat-7.0-doc/config/http.html
Logging
ApacheGUI currently only logs errors.
The error output is logged to the following file:
[APACHEGUI_HOME]/tomcat/logs/catalina.out
SSL
SSL has not been configured by default due to the fact that each server requires a different ssl certificate.
The ApacheGUI runs on tomcat 7, as such the following tutorial can be used to configure SSL:
http://tomcat.apache.org/tomcat-7.0-doc/ssl-howto.html
The following endpoint may be used once SSL has been configured:
https://[HOST]:[SSLPORT]/ApacheGUI/
SELINUX
The history functionality may be blocked on SELINUX enabled systems. To use the history functionality you must switch SELINUX to permissive mode.
To do this open /etc/selinux/config
and make sure SELINUX is in permissive mode
like below. You may need to reboot for changes to take effect.
# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
# enforcing - SELinux security policy is enforced.
# permissive - SELinux prints warnings instead of enforcing.
# disabled - No SELinux policy is loaded.
SELINUX=permissive
# SELINUXTYPE= can take one of these two values:
# targeted - Only targeted network daemons are protected.
# strict - Full SELinux protection.
SELINUXTYPE=targeted