User manual
Table Of Contents
- Web Technologies Administration
- Contents
- Web Technologies Overview
- Managing Web Technologies
- Managing Websites
- Using Server Admin to Manage Websites
- Changing the Access Port for a Website
- Improving Performance of Static Websites (PerformanceCache)
- Enabling Access and Error Logs for a Website
- Setting Up Directory Listing for a Website
- Connecting to Your Website
- Enabling WebDAV on Websites
- Enabling a Common Gateway Interface (CGI) Script
- Enabling Server Side Includes (SSI)
- Viewing Website Settings
- Setting Server Responses to MIME Types and ContentHandlers
- Enabling SSL
- Enabling PHP
- User Content on Websites
- WebMail
- Secure Sockets Layer (SSL)
- Working With Open-Source Applications
- Installing and Viewing WebModules
- Solving Problems
- Where to Find More Information
- Glossary
- Index
56 Chapter 6 Working With Open-Source Applications
If you want to experiment with Apache 2, note the following:
• It is installed in a separate location in the file system: /opt/apache2.
• It is not connected to Server Admin.
• It serves webpages from /opt/apache2/htdocs.
• Its configuration is in /opt/apache2/conf/httpd.conf. Apple modified this file by
configuring it to run the httpd processes as user and group www. If you enable
WebDAV with Apache 2, note that although your WebDAV clients using version 10.1
of Mac OS X or Mac OS X Server will be able to mount Apache2 WebDAV volumes,
they will not have write access; they will have read-only access. WebDAV clients using
version 10.2 will not have this problem.
• It is controlled by its own version of the apachectl script, so to start it, type “sudo /
opt/apache2/bin/apachectl start.”
• Although it's possible to run both versions of Apache, you should be cautious when
doing so. Make sure the two versions do not attempt to listen on the same port. Both
are configured to listen on port 80, so either edit /opt/apache2/conf/httpd.conf to
change the Listen directive or use the web section of Server Admin to change the
port of all your virtual hosts to something other than 80. Also note that if the web
performance cache is enabled, it may be the process that's actually listening on
port 80.
JBoss
JBoss is an open-source application server designed for J2EE applications; it runs on
Java 1.4.1. JBoss is a widely used, full-featured Java application server. It provides a full
Java 2Platform, Enterprise Edition (J2EE) technology stack with features such as:
• An Enterprise Java Bean (EJB) container
• Java Management Extensions (JMX)
• Java Connector Architecture (JCA)
By default, JBoss uses Tomcat as its web container, but you can use other web
containers, such as Jetty, if you wish.
You can use the Application Server section of Server Admin and the command-line
tools in the Terminal application to manage JBoss. Server Admin integrates with the
watchdog process to ensure continuous availability of JBoss once JBoss has been
started. You can use Server Admin to start one of the available JBoss configurations,
stop JBoss, and view the log files.
Two web-based tools for working with JBoss are also included with Mac OS X Server,
one for management and configuration of the JBoss server and one for deployment of
existing applications. Both tools are located in /Library/JBoss/Application.
LL2350.book Page 56 Friday, August 22, 2003 2:32 PM