| Java Settings|
Note: if you are using Java 1.2.x you should be able to run NetLoony without making any changes to your system, via vision.sh (UNIX) or vision.bat (Win32). Go to Starting First Time section to find out more.
If you are using Java 1.1.x or have found the application simply won't start, it is likely you have to configure the Java environment for your system. This really is not as difficult as it all sounds, but may alter very slightly depending on your platform and Java version. The instructions below suit most Java environments.
Make copies of your start-up scripts before you begin editing.
Obtaining JFC/Swing 1.1x
If you DO NOT have Java 1.2.x then you must obtain the JFC/Swing 1.1.x components, which are freely available from:
Q What are the JFC/Swing components? A They are a collection of JavaBeans, developed by Sun, which are now a standard part of Java 1.2.x.
These beans extend and enhance the AWT interface, providing; tables, different Look and Feel GUI's, tabs, graphic buttons, pop-up menus, tool-tips, RTF and HTML viewers/editors and much more. The file that contains all these JavaBeans is called swingall.jar
Setting JFC/Swing 1.1x
This is done via the Java CLASSPATH variable which is defined and set at system boot time, although some operating systems allow you to define environment variables dynamically, environment variables are best set in system start-up scripts such as profile, .login or autoexec.bat. Each operating system has its own method and command to set environment variables.
The CLASSPATH variable might already exist, as it is required to run the Java JDK 1.1.x environment, although some ports don't always require this. If you are unsure, consult the Java documentation for your platform.If you are unsure about setting system variables for your operating system, consult the operating system manuals or your System Administrator.
Configuring Java to use the JFC/Swing components is very easy. You simply make an addition to the CLASSPATH variable with the location of the JFC/Swing swingall.jar file (include the file name in the path). For example:
Operating System Commands Linux
Note: You might have to include the location of the NetLoony installation directory into CLASSPATH as well. Linux might require it, but Windows95 is likely not to. It really depends on the type of platform, and port & version of Java.
Once this has been done, save the file you have been editing and reboot (if a reboot is required for your operating system to enable the CLASSPATH variable).
If you have any problems with Java, try the Troubleshooting Java Problems section.
| Preparing httpd.conf|
The next procedure is to prepare the httpd.conf to be used by NetLoony.
Make a copy of the current srm.conf, access.conf and httpd.conf files and save them in a secure area/directory before you begin editing.
Merging the configuration files and enforcing the formatting rules must be done or NetLoony will not be able to see or configure all of your existing commands!
Q Why do I have to prepare the httpd.conf? And why can't the program do it? A Apache 1.3.4 and above now recommend all commands to be located into the httpd.conf file only. This prevents anomalies and repeating commands creeping into the Apache configuration.
Only you are able to merge these files together, prepare commands and formatting because NetLoony recognises commented commands and might view comments which begin with a command as a commented command (see the Command Control section for more information). For example:
#You will find the command
#ScriptAliasMatch is okay to use.
NetLoony will see the above as a valid ScriptAliasMatch command which has been disabled.
Merging .conf Files
- Copy the contents of srm.conf then Paste to the end of httpd.conf
- Copy the contents of access.conf then Paste to the end of the now modified httpd.conf
- Enter or modify the following directives near the beginning of httpd.conf:
ResourceConfig /dev/null (UNIX)
AccessConfig /dev/null (UNIX)
ResourceConfig nul (Win32)
AccessConfig nul (Win32)
- Save httpd.conf
- Rename or Move srm.conf and access.conf
Comment & Formatting Rules
Commented commands should not have a space in between the hash (#) and the command.
# AllowOverride FileInfo AuthConfig Limit
# Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec
# <Limit GET POST OPTIONS PROPFIND>
# Order allow,deny
# Allow from all
# <Limit PUT DELETE PATCH PROPPATCH MKCOL COPY MOVE LOCK UNLOCK>
# Order deny,allow
# Deny from all
#AllowOverride FileInfo AuthConfig Limit
#Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec
#<Limit GET POST OPTIONS PROPFIND>
#Allow from all
#<Limit PUT DELETE PATCH PROPPATCH MKCOL COPY MOVE LOCK UNLOCK>
#Deny from all
Comments should have a space in between the hash (#) and the comment.
#LogLevel: Control the number of messages logged to the error_log.
#Possible values include: debug, info, notice, warn, error, crit,
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
| Starting First Time|
The installation procedure should have generated two scripts; vision.sh (for UNIX) and vision.bat (Win32). These files could be placed in an executable path such as /usr/bin (UNIX) or C:\Windows (Win32) so NetLoony can be run from anywhere on the system. This makes access to the program far more convenient, although correct security measures should be in place so only the webmaster can run these.
Depending on the version of Java and port behaviour, you could run NetLoony from the command prompt within the NetLoony 'root' directory using;
If you have any problems starting NetLoony, try the Troubleshooting Starting Problems section or go back to the Java Settings section.
Finally you should see the following:
Entering Required Information
You will notice that the Server and Resource top tabs are disabled. This is because NetLoony needs to know where certain files are. These are entered in the Settings display which should in front of you now:
Core Apache Files and Directories
- 'conf' Directory is required so the application can find the httpd.conf file.
- 'manual' Directory is required so the application can find the HTML documentation.
- 'httpd or Apache' Executable is the Apache server application.
- Support Apps Directory is the location of Apache applications such as ab, apachectl, apxs etc. At present, these applications are only available with the UNIX versions of Apache.
Third-party module References
These are optional third party module references, which can be either plain ASCII text or HTML. The list of third-party modules will soon increase.
- apache_ssl is the location of Apache SSL module reference documentation which can be copied from http://www.apache-ssl.org
- mod_ssl is the location of mod_SSL module reference documentation which can be copied from http://www.modssl.org/
After these details have been entered, then NetLoony (NetLoony has to be stopped and restarted to recognise the new settings).