Apache server - tomcat - jk, virtual hosts, database/context.xml question?

Hello,
I have an web application that runs perfectly in Tomcat 5.5 when running tomcat stand-alone.
I also have Apache HTTP server integrated with Tomcat using the jk connector and running virtual hosts in a mod_jk.conf file, which is working for html files. When I run apache and tomcat at the same time, the jsp opens but the servlet cannot get a database connection.
To run virtual hosts and apache and tomcat, I added this host container to server.xml:
<Host name="www.mydomain.com" debug="0" appBase="d:/WebApps/mydomain"
unpackWARs="true" autoDeploy="true">
<Context path="" docBase="" debug="0"/>
</Host>
Does anybody see anything wrong with this? Is there some reason why the context.xml (which contains the database info) is not being read?
Any suggestions are greatly appreciated.
Thank you,
Logan

Hi,
In the docmentation of Tomcat 5.x is written that is not recommended to put <context> element in the server.xml file. Create a file in CATALINA_HOME/conf/Catalina/www.mydomain.com/ with an XML extension. For example context.xml. In files like this you should write all of your <context> elements.

Similar Messages

Apache: sharing assets between virtual hosts best practise

Hello,
We've got a few virtual hosts on our server that share certain assets. I'm looking for a the best way to accomplish this. If it were just me I would use Alias directives, but I would like it to be as transparent as possible for our web designer. Years ago we use to do this with WebStar by sharing one document root. But there's no excuse for that these days.
Here are some of the ideas I'm considering:
1. Put hard links to each shared directory in the document root of each virtual host and not bother with Alias directives.
2. Same as above but include corresponding aliases in the server's config.
3. Same as 1 and 2, but use symbolic links instead of hard links. Not sure about this option since the ftp client will know they are links. But maybe that doesn't matter(?).
Thanks for any thoughts.
Cole

orangekay wrote:
I don't understand what kind of "transparency" your designer requires. It shouldn't make any difference where the files live so long as they're accessible.
The designer will likely not understand that shared assets will not actually be stored in the document root, but in another directory all together. Then I say, "Well don't worry. Just pretend they're in your document root. The server will find them because of the Alias directives I've added to Apache's configuration."
I'm trying to avoid this conversation. I work with artists and programmers. Part of my job requires finding common ground between peoples' various technical skill sets.
I'll try symlinks and Aliases. After reading the ln man page again I see: "Hard links may not normally refer to directories and may not span file systems."
Cole

Apache mod_rewrite, htaccess and virtual host

Does not appear that the htaccess file is doing anything at all; I tested with a 301 redirect and even put some random nonsense in it in hopes to provoke a server error and nothing.
httpd.conf : http://pastebin.com/36qFCg5q
httpd-vhosts.conf
<VirtualHost *:80>
    DocumentRoot "/Users/jwindhall/Railo/tomcat/webapps/ROOT/dentist_app"
    ServerName xxx.com
    ServerAlias www.xxx.com
<Directory "/Users/jwindhall/Railo/tomcat/webapps/ROOT/dentist_app">
    Options All Includes Indexes
    Order allow,deny
    Allow from all
    AllowOverride All
</Directory>
ProxyRequests Off
<Proxy *>
Options All Includes Indexes
Order allow,deny
Allow from all
AllowOverride All
</Proxy>
ProxyPass / http://www.xxx.com:8080/
ProxyPassReverse / http://www.xxx.com:8080/
</VirtualHost>
jwindhall.conf:
<Directory "/Users/jwindhall/Railo/tomcat/webapps/ROOT/dentist_app">
Options Indexes MultiViews FollowSymlinks
AllowOverride All
Order allow,deny
Allow from all
</Directory>

The question etresoft was asking was around what goal or end or configuration you were trying to achieve here, and not who you might be. With some background on the problem and on the particular goal, we might be able to provide you with a more direct solution, or debug the error.
It looks like you're trying to run some Tomcat stuff. Something like this?
Though that articile doesn't indicate it, the provided set-up there looks to be specific to OS X client. Are you running OS X Server, or OS X client. And in either case, which version?   (The management user interfaces do vary here, both by client and server, and by version.)
The article also looks to be for 10.6 or earlier, or it presumes that you have Java installed. That's not the default, so that's something you'll need to establish.
Apache redirects do work on OS X and OS X Server. If you're just testing that, get rid of Java and Tomcat and the rest (from your configuration test) and test just the URL redirects.
Apache is also sensitive to file protections and ownerships, as it strives to avoid allowing an attacker at your whole system (by default), though those protections can be overridden.
As a first step toward troubleshooting your current configuration, invoke the Apache configuration test on your system and see if it tosses any errors, and also check the Apache server logs for relevant errors. The logs are usually in the /var/log/apache2 directory, though that can be changed. This'll make sure the core giblets are working. The next steps would usually then involve checking the protections on the web directories, and then testing Java and Tomcat individually.
OS X Server is a little more simple to set up and (mostly) avoids needing to access the configuration files, and the directories and related are IMO a little easier to deal with; you're using Server Admin.app or Server.app (depending on the OS X Server version) to manage all that, and not a text editor.
And you may already be aware of this; do not try to use a GUI editor to edit the configuration files. TextWrangler will work here, but most other GUI editors won't. Using a command-line editor is more common; nano or vim or emacs or such. FWIW.

Move just wikis to new Lion server (redirect one virtual host)

I have a bunch of services on my Mac Pro with Snow Leopard Server, including file sharing, VPN, subversion, wikis, several websites, a few webapps, etc. I don't want to upgrade that server right now, but I'd like to try upgrading the wikis to Lion Server and Wiki Server 3.
How could I move the wiki's to Lion Server on another machine? They are all accessed through a seperate virtual host.
We only have one public IP right now (I maybe could get a second public IP but don't want to just for this.) Everything hits my router (dd-wrt device, so quite configurable) which sends port 80 (and most other ports) to my snow leopard server.
One idea would be to have the router redirect another port (8080 or something) to the new lion server, and then put a redirect page on the original wiki address (port 80) to redirect over to 8080, which would then go to the other server. But that's not really ideal because then the users of my wiki would see it on a new port and a lot of times ports other than 80 are blocked by firewalls (not my firewall, but firewalls closer to my users.)
So does anyone have an other ideas on how to redirect the traffic of one virtual host to another internal machine behind NAT?
Separate question: any experience migrating a wiki from Wiki Server 2 to Wiki Server 3? Did it work well?
John

The best way to do this is to take the contents of /Library/Collaboration and put it in a location accessible from your newly set up Lion install. In Server.app, enable Wiki, and run:
     sudo wikiadmin migrate -r /Path/To/Library/Collaboration
After that, start the wiki and you should be good to go. You should bind your Lion server to the same Directory as the Snow Leopard server, to ensure permissions and users carry across successfully.
    A.

Tomcat 5.5.7 and context.xml

I am having difficulty corrcetly setting up the context.xml file. Perhaps someone can shed some insight as to how to do this...
I have a .war file called myWar.war I place this in the webapps directory
I want to use a path of a/b to access it.
so, if my browser url is
http://localhost:8080/a/b/html/index.html it will actually access webapp/myWar/html/index.html
I keep reading things that confuse me as to how to do this. Do I need something called context.xml, ROOT.xml, or myWar.xml. Also do I place it in the conf/Catalina/localhost directory r in the myWar/Meta-Inf directory
thank you

I remember reading something about the path value not being recognized for 5.5.x . It seems to validate it in the documentation below. I don't know how to 'fix' it though...
"The context path of this web application, which is matched against the beginning of each request URI to select the appropriate web application for processing. All of the context paths within a particular Host must be unique. If you specify a context path of an empty string (""), you are defining the default web application for this Host, which will process all requests not assigned to other Contexts. The value of this field must not be set except when statically defining a Context in server.xml, as it will be infered from the filenames used for either the .xml context file or the docBase."

Context.xml question , Thanks

Hi, developers:
I would like to connect to another server using context.xml. I did like the following link: < a href="http://tomcat.apache.org/tomcat-5.5-doc/jndi-resources-howto.html"> link to instruction</a>
In the "JDBC Data Source" :4 Configure Tomcat's Resource Factory part said a Context.xml tshould be stored in the META-INF directory .
My problem is:
1) where is /META-INF so I can find the contect.xml. I using tomcat5.5 and find only at Tomcat5.5\conf\context.xml?
2) When I restart with my context.xml below, the tomcat can start but application can NOT.
Error msd: Http status 404 : The requested resource (/account App) is not available.
code of context.xml is:
<?xml version='1.0' encoding='utf-8'?>
<Context displayName="account" path="/accountApp" debug="0" reloadable="true" docBase="serverdb">
<Resource name="jdbc/dbinstance" auth="Container" type="javax.sql.DataSource"
factory="org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory"
driverClassName="oracle.jdbc.OracleDriver"
url="jdbc:oracle:thin:@//dburl:1522/"
username="accuser"
password="accpw"
maxActive="20"
maxIdle="10"
maxWait="120000"
removeAbandoned="true"
logAbandoned="true"
removeAbandonedTimeout="300"
testOnBorrow="true"
testOnReturn="true"
validationQuery="select 1 from dual" />
</Context>
is some one can give me a help to solve it. Thanks in advance

The "context" here is an artifact of the way that Tomcat works. It contains deployment information - the path to the application files, the JNDI mappings and various other bits and pieces.
The "context" of a web application is the path to which it is deployed within the application server. An application deployed to a context called "foo" would probably be accessed by the following URL:
http://localhost:8080/foo/And the application files would probably be stored somewhere like this:
C:\Program Files\Apache Software Foundation\Tomcat 5.5\webapps\fooTomcat keeps its context information EITHER in a file called server.xml or in a seperate file named after the application's context. So typically it will be in one of these files (for our "foo" application):
C:\Program Files\Apache Software Foundation\Tomcat 5.5\conf\server.xml
C:\Program Files\Apache Software Foundation\Tomcat 5.5\conf\Catalina\localhost\foo.xmlYou can create the entry in one of several ways:
1. Edit server.xml manually
2. Edit foo.xml manually
3. Use an application such as the admin webapp to deploy your application
4. Include a Context.xml file in the META-INF directory of the application
The last option allows you to specify the default values that you want the application to take up when you deploy it to Tomcat. This saves time during development, but may cause problems for your clients when they come to deploy the application themselves.
It is this last file that you seem to be talking about. You would normally create it as a directory and file within the source directory for your application, from which you build and deploy a WAR file. For example, you might build the following files and directories into foo.war:
C:\dev\foo\index.jsp
C:\dev\foo\WEB-INF\web.xml
C:\dev\foo\META-INF\MANIFEST.MF
C:\dev\foo\META-INF\Context.xml
This would be built to a WAR file called foo.war that represents a Zip of the contents of the C:\dev\foo directory. Deploying this will cause Tomcat to notice Context.xml and extract its contents into the conf/Catalina/localhost directory as foo.xml

Apache Server not resolving virtual hostnames from an iPad

I am hosting multiple websites from a single IP address and have come across the following problem. If I access it from my mac, the correct website is displayed, but if I use my iPad the web site is not found and my default website displays instead.
Checking the access log I can see a clear difference between what is passed from a mac and an ipad but don't know how to fix it, any suggestions greatly appreciated.
The Mac sends this
www.parksurgery-hursleyrd-ppg.org.uk 81.138.225.73 - - [03/Oct/2013:00:15:11 +0100] "GET / HTTP/1.1" 200 4857 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Firefox/24.0"
The iPad sends this
www.advtraining.co.uk 192.168.1.73 - - [03/Oct/2013:00:22:03 +0100] "GET / HTTP/1.1" 200 7847 "http://www.parksurgery-hursleyrd-ppg.org.uk/" "Mozilla/5.0 (iPad; CPU OS 7_0 like Mac OS X) AppleWebKit/537.51.1 (KHTML, like Gecko) Version/7.0 Mobile/11A465 Safari/9537.53"
the website I am trying to display is www.parksurgery-hursleyrd-ppg.org.uk
I just tried allocating different port numbers to the web site and that has the effect of the iPad displaying the correct website and the mac going to the default.
Any help much appreciated

A web browser sends the text that was entered in the address bar as part of the HTTP or HTTPS connection, irrespective of the IP address.
What your log is showing looks to be a refer from www.parksurgery-hursleyrd-ppg.org.uk to www.advtraining.co.uk, too.
If you're running OS X Server as implied by the choice of forum, make certain that your DHCP server for your private network is vending only the address of your own OS X Server DNS server, and that there are no references to any off-LAN DNS servers.
Also verify the contents and configuration of the local DNS server.
Also look at the refers and any rewrite or redirection rules within the Apache setup for the web sites. This for the rewrite and refer settings.
If you reference Google DNS at 8.8.8.8 and 8.8.4.4 as mentioned earlier, you will get the public IP translations, but — depending on whether your gateway device can "reflect" those references back into your local network via whatever you're using for NAT — you may or may not reach the intended host. You will generally not receive a 192.168.1.0/24 IP address as a translation from a public DNS server.
All that written, if you're running OS X Server, then you need DNS locally, and it's then common to configure the LAN to reference that server for all DNS.

Server admin overwriting virtual host conf file

For some reason the website crashed this morning. The error log pointed to the virtual_host conf file. It crashes each time the we attempt to create an alias and then save changes.
The only way to fix it is to go back and edit the conf file and then web service starts on its own.
When I look at the file, it says: This file is auto generated by the Server Admin Web backend plugin whenever server settings are saved.
Is there a way to configure this so the file does not change?
Thanks!

The best way to do this is to take the contents of /Library/Collaboration and put it in a location accessible from your newly set up Lion install. In Server.app, enable Wiki, and run:
sudo wikiadmin migrate -r /Path/To/Library/Collaboration
After that, start the wiki and you should be good to go. You should bind your Lion server to the same Directory as the Snow Leopard server, to ensure permissions and users carry across successfully.
A.

Apache, name based virtual hosts and multiple servers.

Hi,
Ive been playing with Apache and name-based virtual hosts for a while now, but, ive been doing it with one single server... now i have the need to forward a name-based request to another server inside the intranet (wich doesnt have a public IP, but a private)...
Something like this:
internet -----> Webserver (name based vhosts) ----> intranet-webserver
Where "webserver" has several domains resolved via name based virtual hosting, and one of those needs to be redirected (or forwarded) to another server on the LAN.
Any ideas on how to do this? i tryed searching the web, but i dont know under which keywords, so i always end on single server virtual hosting help sites.
thanks in advance!

you need to define a virtual server for it..but inside that definition.. define a proxy.
Then the middle webserver, will actually handle the request to the intranet server, on behalf of the internet client..and then pass the traffic to the internet client.
this looks like a reasonable example..
http://www.linuxfocus.org/English/March … le147.html
namely, the section "Mapping Virtual Servers"

Apache, virtual hosts & cgi-bin

Hello all,
I have an AL server running apache, qmail, vpopmail (&mysql), bincimap, squirrelmail.
I've setup apache to have 2 virtual hosts :
www.mydomain.com (with docroot /home/httpd/html/www.mydomain.com) as http & mail.mydomain.com (with docroot /home/httpd/html/mail.mydomain.com) as https.
Everything is working fine so far, except when I ask for http://mail.mydomain.com (not https) it shows the contents of www.mydomain.com. Minor annoyance, but I'd like to fix it some time. Any suggestions ?
My main problem is that I want to install qmailadmin in mail.mydomain.com, so I can access it via ssl, so I installed it as /home/httpd/cgi-bin/qmailadmin & made a symlink to /home/httpd/html/mail.mydomain.com/cgi-bin.
When I try to access it (https://mail.mydomain.com/cgi-bin/qmailadmin), I get "500 Internal server error" & in error_log:
[error] [client MY_IP] Premature end of script headers: qmailadmin
and in ssl_request_log :
[14/Jan/2004:17:00:45 +0200] MY_IP TLSv1 RC4-MD5 "GET /cgi-bin/qmailadmin HTTP/1.1" 674
I've never setup cgi-bin in virtual hosts before & it's driving me nuts, any suggestions ?
btw, qmailadmin works fine on my home server without any virtual hosts in apache...

This isn't perfect, but it's probably pretty close to what you're looking for. You may need to play around with some <Directory/> tags for your cgi-bin directory, or (as the example illustrates below), just put your cgi scripts in the document root for mail.mydomain.com.
<Directory "/home/httpd/html/www.mydomain.com">
AllowOverride All
Order allow,deny
Allow from all
</Directory>
<Directory "/home/httpd/html/mail.mydomain.com">
AllowOverride All
Options ExecCGI
Order allow,deny
Allow from all
</Directory>
NameVirtualHost 192.168.1.114:80
NameVirtualHost 192.168.1.114:443
<VirtualHost www.mydomain.com:80>
SSLDisable
Servername www.mydomain.com
ServerAdmin [email protected]
DocumentRoot /home/httpd/html/www.mydomain.com
DirectoryIndex index.html index.htm index.cgi
ErrorLog logs/www.mydomain.com_error.log
CustomLog logs/www.mydomain.com_access.log combined
</Virtualhost>
# redirect 80 to 443
<VirtualHost mail.mydomain.com:80>
SSLDisable
Servername mail.mydomain.com
Redirect / https://mail.mydomain.com
</Virtualhost>
<VirtualHost mail.mydomain.com:443>
SSLEnable
SSLCertificateFile /home/httpd/conf/mail.mydomain.com.pem
ServerName mail.mydomain.com
ServerAdmin [email protected]
DocumentRoot /home/httpd/html/mail.mydomain.com
ErrorLog logs/mail.mydomain.com_error.log
CustomLog logs/mail.mydomain.com_access.log combined
</Virtualhost>
hth,
farphel

One Server, Two Virtual Hosts, Two Applications, Two Mix,...

In the same server I have two virtual hosts (site1.com, site2.com). For each virtual host I have a PUBLIC page (40, 50).
The following accesses work perfectly:
(1) http://www.site1.com/portal/page?_pageid=40,1&_dad=portal&_schema=PORTAL
(2) http://www.site2.com/portal/page?_pageid=50,1&_dad=portal&_schema=PORTAL
... But the following ones also
(1) http://www.site1.com/portal/page?_pageid=50,1&_dad=portal&_schema=PORTAL
(2) http://www.site2.com/portal/page?_pageid=40,1&_dad=portal&_schema=PORTAL
Imagine that site1 is 'Coca Cola' and site2 'Pepsi' (page 40 is 'Coca Cola' and 50 'Pepsi'!)
How to avoid it?
I think about two ways of solving it:
1. To hide the url and to avoid the manipulation of the number of page. (Died the dog ended the anger)
2. To do that the page 40 works only with the virtual host site1 and the page 50 with the virtual host site2.
The question is:
How to do someone of these options?
Thanks for the help

Hi Sachin,
you're right with two different VM you can manage that, but this is similar to have two different server. My goal is to use only a server (phisical or virtual)... I think with 8.8 version we can do it, but I glad if someone has some experience of this scenario..
Regards,
Giovanni

Using SSL with Apache Virtual Hosts

I am configuring Apache to use 3 virtual Host(Named base virtual Host).
I would like to run SSL on two of the 3 virtual host.
Do I need to gen a certificate for each virtual host or can I just use 1?

William,
I thought I'd give my 2 cents on this...
Is there any particular reason as to why you are using named based virtual hosts?
Apache recommends using IP based virtual hosts over name based virtual hosts.
Go to http://httpd.apache.org/docs/dns-caveats.html and read the discussion on IP based virtual hosts and name based virtual hosts. The document describes the drawbacks to using the name-based approach.
Hope this helps!
-Manjeet

A second virtual host is deaf

Apache 2 and Tomcat 4.0 work together here on an NT as long as httpd.conf sees the Tomcat contexts denoted as a virtual host with the same name as the host : "host1".
So, I am trying now to use a second virtual host "host2" on my machine "host1".
I can still reach the contexts on host1 with http://host1/things
but should this also work? : http://host2/otherthings
must I give my system 2 (two) ip addresses in order to have a second virtual host? Seems strange.

yes and the link you posted before does actually mention this fairly important issue
Of course, you can't just make up names and place them in ServerName or ServerAlias. You must first have your DNS server properly configured to map those names to an IP address associated with your server.i suspect that is you want to test on win network if you don't want to mess about with dns you might be able to do some bejiggery in the LMHOSTS file that would have the same effect.
if you want to just test virtual hosts in general. one thing that also might work is using machine name(s) as well as the ip's
for example if the machine is called host1 and has an address of 192.168.100.10 then i think you could set up three sites.
the "real" (default) site.
192.168.100.10
127.0.0.1
virtual host 1
host1
virtual host 2
localhost
i think these would work although the last one would only work from the server itself. see virtual hosting uses the host header passed in HTTP so as long as you can have different ones that end up going to the same place you can invent some virtual hosts for testing.

Apache and Tomcat

hi
i have installed apache 2.0 and i am trying to map tomcat into it by using the JK2 module. i have configured the httpd.conf file and workers file.
but it gives me the following error
Service Temporarily Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
Apache/2.0.49 (Win32) mod_jk2/2.0.4 Server at localhost Port 80
my httpd.conf file is as follows
# Based upon the NCSA server configuration files originally by Rob McCool.
# This is the main Apache server configuration file. It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs-2.0/> for detailed information about
# the directives.
# Do NOT simply read the instructions in here without understanding
# what they do. They're here only as hints or reminders. If you are unsure
# consult the online docs. You have been warned.
# The configuration directives are grouped into three basic sections:
# 1. Directives that control the operation of the Apache server process as a
# whole (the 'global environment').
# 2. Directives that define the parameters of the 'main' or 'default' server,
# which responds to requests that aren't handled by a virtual host.
# These directives also provide default values for the settings
# of all virtual hosts.
# 3. Settings for virtual hosts, which allow Web requests to be sent to
# different IP addresses or hostnames and have them handled by the
# same Apache server process.
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path. If the filenames do not begin
# with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
# with ServerRoot set to "C:/Program Files/Apache Group/Apache2" will be interpreted by the
# server as "C:/Program Files/Apache Group/Apache2/logs/foo.log".
# NOTE: Where filenames are specified, you must use forward slashes
# instead of backslashes (e.g., "c:/apache" instead of "c:\apache").
# If a drive letter is omitted, the drive on which Apache.exe is located
# will be used by default. It is recommended that you always supply
# an explicit drive letter in absolute paths, however, to avoid
# confusion.
### Section 1: Global Environment
# The directives in this section affect the overall operation of Apache,
# such as the number of concurrent requests it can handle or where it
# can find its configuration files.
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
# NOTE! If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the LockFile documentation (available
# at <URL:http://httpd.apache.org/docs-2.0/mod/mpm_common.html#lockfile>);
# you will save yourself a lot of trouble.
# Do NOT add a slash at the end of the directory path.
ServerRoot "C:/Program Files/Apache Group/Apache2"
# ScoreBoardFile: File used to store internal server process information.
# If unspecified (the default), the scoreboard will be stored in an
# anonymous shared memory segment, and will be unavailable to third-party
# applications.
# If specified, ensure that no two invocations of Apache share the same
# scoreboard file. The scoreboard file MUST BE STORED ON A LOCAL DISK.
#ScoreBoardFile logs/apache_runtime_status
# PidFile: The file in which the server should record its process
# identification number when it starts.
PidFile logs/httpd.pid
# Timeout: The number of seconds before receives and sends time out.
Timeout 300
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
KeepAlive On
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
MaxKeepAliveRequests 100
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
KeepAliveTimeout 15
## Server-Pool Size Regulation (MPM specific)
# WinNT MPM
# ThreadsPerChild: constant number of worker threads in the server process
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule mpm_winnt.c>
ThreadsPerChild 250
MaxRequestsPerChild 0
</IfModule>
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses (0.0.0.0)
#Listen 12.34.56.78:80
Listen 80
# Dynamic Shared Object (DSO) Support
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available before they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
# Example:
# LoadModule foo_module modules/mod_foo.so
LoadModule access_module modules/mod_access.so
LoadModule actions_module modules/mod_actions.so
LoadModule alias_module modules/mod_alias.so
LoadModule asis_module modules/mod_asis.so
LoadModule auth_module modules/mod_auth.so
#LoadModule auth_anon_module modules/mod_auth_anon.so
#LoadModule auth_dbm_module modules/mod_auth_dbm.so
#LoadModule auth_digest_module modules/mod_auth_digest.so
LoadModule autoindex_module modules/mod_autoindex.so
#LoadModule cern_meta_module modules/mod_cern_meta.so
LoadModule cgi_module modules/mod_cgi.so
#LoadModule dav_module modules/mod_dav.so
#LoadModule dav_fs_module modules/mod_dav_fs.so
LoadModule dir_module modules/mod_dir.so
LoadModule env_module modules/mod_env.so
#LoadModule expires_module modules/mod_expires.so
#LoadModule file_cache_module modules/mod_file_cache.so
#LoadModule headers_module modules/mod_headers.so
LoadModule imap_module modules/mod_imap.so
LoadModule include_module modules/mod_include.so
#LoadModule info_module modules/mod_info.so
LoadModule isapi_module modules/mod_isapi.so
LoadModule jk2_module modules/mod_jk2.so
LoadModule log_config_module modules/mod_log_config.so
LoadModule mime_module modules/mod_mime.so
#LoadModule mime_magic_module modules/mod_mime_magic.so
#LoadModule proxy_module modules/mod_proxy.so
#LoadModule proxy_connect_module modules/mod_proxy_connect.so
#LoadModule proxy_http_module modules/mod_proxy_http.so
#LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
LoadModule negotiation_module modules/mod_negotiation.so
#LoadModule rewrite_module modules/mod_rewrite.so
LoadModule setenvif_module modules/mod_setenvif.so
#LoadModule speling_module modules/mod_speling.so
#LoadModule status_module modules/mod_status.so
#LoadModule unique_id_module modules/mod_unique_id.so
LoadModule userdir_module modules/mod_userdir.so
#LoadModule usertrack_module modules/mod_usertrack.so
#LoadModule vhost_alias_module modules/mod_vhost_alias.so
#LoadModule ssl_module modules/mod_ssl.so
# ExtendedStatus controls whether Apache will generate "full" status
# information (ExtendedStatus On) or just basic information (ExtendedStatus
# Off) when the "server-status" handler is called. The default is Off.
#ExtendedStatus On
### Section 2: 'Main' server configuration
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition. These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
# ServerAdmin: Your address, where problems with the server should be
# e-mailed. This address appears on some server-generated pages, such
# as error documents. e.g. [email protected]
ServerAdmin [email protected]
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
# If this is not set to valid DNS name for your host, server-generated
# redirections will not work. See also the UseCanonicalName directive.
# If your host doesn't have a registered DNS name, enter its IP address here.
# You will have to access it by its address anyway, and this will make
# redirections work in a sensible way.
ServerName cipl-soft2.unit1.cepha.net:80
# UseCanonicalName: Determines how Apache constructs self-referencing
# URLs and the SERVER_NAME and SERVER_PORT variables.
# When set "Off", Apache will use the Hostname and Port supplied
# by the client. When set "On", Apache will use the value of the
# ServerName directive.
UseCanonicalName Off
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
DocumentRoot "C:/Program Files/Apache Group/Apache2/htdocs"
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
# First, we configure the "default" to be a very restrictive set of
# features.
<Directory />
Options FollowSymLinks
AllowOverride None
</Directory>
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
# This should be changed to whatever you set DocumentRoot to.
<Directory "C:/Program Files/Apache Group/Apache2/htdocs">
# Possible values for the Options directive are "None", "All",
# or any combination of:
# Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
# Note that "MultiViews" must be named explicitly --- "Options All"
# doesn't give it to you.
# The Options directive is both complicated and important. Please see
# http://httpd.apache.org/docs-2.0/mod/core.html#options
# for more information.
Options Indexes FollowSymLinks
# AllowOverride controls what directives may be placed in .htaccess files.
# It can be "All", "None", or any combination of the keywords:
# Options FileInfo AuthConfig Limit
AllowOverride None
# Controls who can get stuff from this server.
Order allow,deny
Allow from all
</Directory>
# UserDir: The name of the directory that is appended onto a user's home
# directory if a ~user request is received. Be especially careful to use
# proper, forward slashes here. On Windows NT, "Personal/My Website"
# is a more appropriate choice.
UserDir "My Documents/My Website"
# Control access to UserDir directories. The following is an example
# for a site where these directories are restricted to read-only.
# You must correct the path for the root to match your system's configured
# user directory location, e.g. "C:/WinNT/profiles/*/My Documents/My Website"
# or whichever, as appropriate.
#<Directory "C:/Documents and Settings/*/My Documents/My Website">
# AllowOverride FileInfo AuthConfig Limit
# Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec
# <Limit GET POST OPTIONS PROPFIND>
# Order allow,deny
# Allow from all
# </Limit>
# <LimitExcept GET POST OPTIONS PROPFIND>
# Order deny,allow
# Deny from all
# </LimitExcept>
#</Directory>
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
# The index.html.var file (a type-map) is used to deliver content-
# negotiated documents. The MultiViews Option can be used for the
# same purpose, but it is much slower.
DirectoryIndex index.html index.html.var
# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives. See also the AllowOverride
# directive.
AccessFileName .htaccess
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
<Files ~ "^\.ht">
Order allow,deny
Deny from all
</Files>
# TypesConfig describes where the mime.types file (or equivalent) is
# to be found.
TypesConfig conf/mime.types
# DefaultType is the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value. If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
DefaultType text/plain
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type. The MIMEMagicFile
# directive tells the module where the hint definitions are located.
<IfModule mod_mime_magic.c>
MIMEMagicFile conf/magic
</IfModule>
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
HostnameLookups Off
# EnableMMAP: Control whether memory-mapping is used to deliver
# files (assuming that the underlying OS supports it).
# The default is on; turn this off if you serve from NFS-mounted
# filesystems. On some systems, turning it off (regardless of
# filesystem) can improve performance; for details, please see
# http://httpd.apache.org/docs-2.0/mod/core.html#enablemmap
#EnableMMAP off
# EnableSendfile: Control whether the sendfile kernel support is
# used to deliver files (assuming that the OS supports it).
# The default is on; turn this off if you serve from NFS-mounted
# filesystems. Please see
# http://httpd.apache.org/docs-2.0/mod/core.html#enablesendfile
#EnableSendfile off
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here. If you do define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
ErrorLog logs/error.log
# LogLevel: Control the number of messages logged to the error.log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel warn
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %b" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent
# You need to enable mod_logio.c to use %I and %O
#LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
# The location and format of the access logfile (Common Logfile Format).
# If you do not define any access logfiles within a <VirtualHost>
# container, they will be logged here. Contrariwise, if you do
# define per-<VirtualHost> access logfiles, transactions will be
# logged therein and not in this file.
CustomLog logs/access.log common
# If you would like to have agent and referer logfiles, uncomment the
# following directives.
#CustomLog logs/referer.log referer
#CustomLog logs/agent.log agent
# If you prefer a single logfile with access, agent, and referer information
# (Combined Logfile Format) you can use the following directive.
#CustomLog logs/access.log combined
# ServerTokens
# This directive configures what you return as the Server HTTP response
# Header. The default is 'Full' which sends information about the OS-Type
# and compiled in modules.
# Set to one of: Full | OS | Minor | Minimal | Major | Prod
# where Full conveys the most information, and Prod the least.
ServerTokens Full
# Optionally add a line containing the server version and virtual host
# name to server-generated pages (internal error documents, FTP directory
# listings, mod_status and mod_info output etc., but not CGI generated
# documents or custom error documents).
# Set to "EMail" to also include a mailto: link to the ServerAdmin.
# Set to one of: On | Off | EMail
ServerSignature On
# Aliases: Add here as many aliases as you need (with no limit). The format is
# Alias fakename realname
# Note that if you include a trailing / on fakename then the server will
# require it to be present in the URL. So "/icons" isn't aliased in this
# example, only "/icons/". If the fakename is slash-terminated, then the
# realname must also be slash terminated, and if the fakename omits the
# trailing slash, the realname must also omit it.
# We include the /icons/ alias for FancyIndexed directory listings. If you
# do not use FancyIndexing, you may comment this out.
Alias /icons/ "C:/Program Files/Apache Group/Apache2/icons/"
<Directory "C:/Program Files/Apache Group/Apache2/icons">
Options Indexes MultiViews
AllowOverride None
Order allow,deny
Allow from all
</Directory>
# This should be changed to the ServerRoot/manual/. The alias provides
# the manual, even if you choose to move your DocumentRoot. You may comment
# this out if you do not care for the documentation.
AliasMatch ^/manual(?:/(?:de|en|fr|ja|ko|ru))?(/.*)?$ "C:/Program Files/Apache Group/Apache2/manual$1"
<Directory "C:/Program Files/Apache Group/Apache2/manual">
Options Indexes
AllowOverride None
Order allow,deny
Allow from all
<Files *.html>
SetHandler type-map
</Files>
SetEnvIf Request_URI ^/manual/de/ prefer-language=de
SetEnvIf Request_URI ^/manual/en/ prefer-language=en
SetEnvIf Request_URI ^/manual/fr/ prefer-language=fr
SetEnvIf Request_URI ^/manual/ja/ prefer-language=ja
SetEnvIf Request_URI ^/manual/ko/ prefer-language=ko
SetEnvIf Request_URI ^/manual/ru/ prefer-language=ru
RedirectMatch 301 ^/manual(?:/(de|en|fr|ja|ko|ru)){2,}(/.*)?$ /manual/$1$2
</Directory>
# ScriptAlias: This controls which directories contain server scripts.
# ScriptAliases are essentially the same as Aliases, except that
# documents in the realname directory are treated as applications and
# run by the server when requested rather than as documents sent to the client.
# The same rules about trailing "/" apply to ScriptAlias directives as to
# Alias.
ScriptAlias /cgi-bin/ "C:/Program Files/Apache Group/Apache2/cgi-bin/"
# "C:/Program Files/Apache Group/Apache2/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
<Directory "C:/Program Files/Apache Group/Apache2/cgi-bin">
AllowOverride None
Options None
Order allow,deny
Allow from all
</Directory>
# Redirect allows you to tell clients about documents which used to exist in
# your server's namespace, but do not anymore. This allows you to tell the
# clients where to look for the relocated document.
# Example:
# Redirect permanent /foo http://www.example.com/bar
# Directives controlling the display of server-generated directory listings.
# IndexOptions: Controls the appearance of server-generated directory
# listings.
IndexOptions FancyIndexing VersionSort
# AddIcon* directives tell the server which icon to show for different
# files or filename extensions. These are only displayed for
# FancyIndexed directories.
AddIconByEncoding (CMP,/icons/compressed.gif) x-compress x-gzip
AddIconByType (TXT,/icons/text.gif) text/*
AddIconByType (IMG,/icons/image2.gif) image/*
AddIconByType (SND,/icons/sound2.gif) audio/*
AddIconByType (VID,/icons/movie.gif) video/*
AddIcon /icons/binary.gif .bin .exe
AddIcon /icons/binhex.gif .hqx
AddIcon /icons/tar.gif .tar
AddIcon /icons/world2.gif .wrl .wrl.gz .vrml .vrm .iv
AddIcon /icons/compressed.gif .Z .z .tgz .gz .zip
AddIcon /icons/a.gif .ps .ai .eps
AddIcon /icons/layout.gif .html .shtml .htm .pdf
AddIcon /icons/text.gif .txt
AddIcon /icons/c.gif .c
AddIcon /icons/p.gif .pl .py
AddIcon /icons/f.gif .for
AddIcon /icons/dvi.gif .dvi
AddIcon /icons/uuencoded.gif .uu
AddIcon /icons/script.gif .conf .sh .shar .csh .ksh .tcl
AddIcon /icons/tex.gif .tex
AddIcon /icons/bomb.gif core
AddIcon /icons/back.gif ..
AddIcon /icons/hand.right.gif README
AddIcon /icons/folder.gif ^^DIRECTORY^^
AddIcon /icons/blank.gif ^^BLANKICON^^
# DefaultIcon is which icon to show for files which do not have an icon
# explicitly set.
DefaultIcon /icons/unknown.gif
# AddDescription allows you to place a short description after a file in
# server-generated indexes. These are only displayed for FancyIndexed
# directories.
# Format: AddDescription "description" filename
#AddDescription "GZIP compressed document" .gz
#AddDescription "tar archive" .tar
#AddDescription "GZIP compressed tar archive" .tgz
# ReadmeName is the name of the README file the server will look for by
# default, and append to directory listings.
# HeaderName is the name of a file which should be prepended to
# directory indexes.
ReadmeName README.html
HeaderName HEADER.html
# IndexIgnore is a set of filenames which directory indexing should ignore
# and not include in the listing. Shell-style wildcarding is permitted.
IndexIgnore .??* *~ *# HEADER* README* RCS CVS *,v *,t
# DefaultLanguage and AddLanguage allows you to specify the language of
# a document. You can then use content negotiation to give a browser a
# file in a language the user can understand.
# Specify a default language. This means that all data
# going out without a specific language tag (see below) will
# be marked with this one. You probably do NOT want to set
# this unless you are sure it is correct for all cases.
# * It is generally better to not mark a page as
# * being a certain language than marking it with the wrong
# * language!
# DefaultLanguage nl
# Note 1: The suffix does not have to be the same as the language
# keyword --- those with documents in Polish (whose net-standard
# language code is pl) may wish to use "AddLanguage pl .po" to
# avoid the ambiguity with the common suffix for perl scripts.
# Note 2: The example entries below illustrate that in some cases
# the two character 'Language' abbreviation is not identical to
# the two character 'Country' code for its country,
# E.g. 'Danmark/dk' versus 'Danish/da'.
# Note 3: In the case of 'ltz' we violate the RFC by using a three char
# specifier. There is 'work in progress' to fix this and get
# the reference data for rfc1766 cleaned up.
# Catalan (ca) - Croatian (hr) - Czech (cs) - Danish (da) - Dutch (nl)
# English (en) - Esperanto (eo) - Estonian (et) - French (fr) - German (de)
# Greek-Modern (el) - Hebrew (he) - Italian (it) - Japanese (ja)
# Korean (ko) - Luxembourgeois* (ltz) - Norwegian Nynorsk (nn)
# Norwegian (no) - Polish (pl) - Portugese (pt)
# Brazilian Portuguese (pt-BR) - Russian (ru) - Swedish (sv)
# Simplified Chinese (zh-CN) - Spanish (es) - Traditional Chinese (zh-TW)
AddLanguage ca .ca
AddLanguage cs .cz .cs
AddLanguage da .dk
AddLanguage de .de
AddLanguage el .el
AddLanguage en .en
AddLanguage eo .eo
AddLanguage es .es
AddLanguage et .et
AddLanguage fr .fr
AddLanguage he .he
AddLanguage hr .hr
AddLanguage it .it
AddLanguage ja .ja
AddLanguage ko .ko
AddLanguage ltz .ltz
AddLanguage nl .nl
AddLanguage nn .nn
AddLanguage no .no
AddLanguage pl .po
AddLanguage pt .pt
AddLanguage pt-BR .pt-br
AddLanguage ru .ru
AddLanguage sv .sv
AddLanguage zh-CN .zh-cn
AddLanguage zh-TW .zh-tw
# LanguagePriority allows you to give precedence to some languages
# in case of a tie during content negotiation.
# Just list the languages in decreasing order of preference. We have
# more or less alphabetized them here. You probably want to change this.
LanguagePriority en ca cs da de el eo es et fr he hr it ja ko ltz nl nn no pl pt pt-BR ru sv zh-CN zh-TW
# ForceLanguagePriority allows you to serve a result page rather than
# MULTIPLE CHOICES (Prefer) [in case of a tie] or NOT ACCEPTABLE (Fallback)
# [in case no accepted languages matched the available variants]
ForceLanguagePriority Prefer Fallback
# Specify a default charset for all pages sent out. This is
# always a good idea and opens the door for future internationalisation
# of your web site, should you ever want it. Specifying it as
# a default does little harm; as the standard dictates that a page
# is in iso-8859-1 (latin1) unless specified otherwise i.e. you
# are merely stating the obvious. There are also some security
# reasons in browsers, related to javascript and URL parsing
# which encourage you to always set a default char set.
AddDefaultCharset ISO-8859-1
# Commonly used filename extensions to character sets. You probably
# want to avoid clashes with the language extensions, unless you
# are good at carefully testing your setup after each change.
# See http://www.iana.org/assignments/character-sets for the
# official list of charset names and their respective RFCs.
AddCharset ISO-8859-1 .iso8859-1 .latin1
AddCharset ISO-8859-2 .iso8859-2 .latin2 .cen
AddCharset ISO-8859-3 .iso8859-3 .latin3
AddCharset ISO-8859-4 .iso8859-4 .latin4
AddCharset ISO-8859-5 .iso8859-5 .latin5 .cyr .iso-ru
AddCharset ISO-8859-6 .iso8859-6 .latin6 .arb
AddCharset ISO-8859-7 .iso8859-7 .latin7 .grk
AddCharset ISO-8859-8 .iso8859-8 .latin8 .heb
AddCharset ISO-8859-9 .iso8859-9 .latin9 .trk
AddCharset ISO-2022-JP .iso2022-jp .jis
AddCharset ISO-2022-KR .iso2022-kr .kis
AddCharset ISO-2022-CN .iso2022-cn .cis
AddCharset Big5 .Big5 .big5
# For russian, more than one charset is used (depends on client, mostly):
AddCharset WINDOWS-1251 .cp-1251 .win-1251
AddCharset CP866 .cp866
AddCharset KOI8-r .koi8-r .koi8-ru
AddCharset KOI8-ru .koi8-uk .ua
AddCharset ISO-10646-UCS-2 .ucs2
AddCharset ISO-10646-UCS-4 .ucs4
AddCharset UTF-8 .utf8
# The set below does not map to a specific (iso) standard
# but works on a fairly wide range of browsers. Note that
# capitalization actually matters (it should not, but it
# does for some browsers).
# See http://www.iana.org/assignments/character-sets
# for a list of sorts. But browsers support few.
AddCharset GB2312 .gb2312 .gb
AddCharset utf-7 .utf7
AddCharset utf-8 .utf8
AddCharset big5 .big5 .b5
AddCharset EUC-TW .euc-tw
AddCharset EUC-JP .euc-jp
AddCharset EUC-KR .euc-kr
AddCharset shift_jis .sjis
# AddType allows you to add to or override the MIME configuration
# file mime.types for specific file types.
#AddType application/x-tar .tgz
# AddEncoding allows you to have certain browsers (Mosaic/X 2.1+) uncompress
# information on the fly. Note: Not all browsers support this.
# Despite the name similarity, the following Add* directives have nothing
# to do with the FancyIndexing customization directives above.
#AddEncoding x-compress .Z
#AddEncoding x-gzip .gz .tgz
# If the AddEncoding directives above are commented-out, then you
# probably should define those extensions to indicate media types:
AddType application/x-compress .Z
AddType application/x-gzip .gz .tgz
# AddHandler allows you to map certain file extensions to "handlers":
# actions unrelated to filetype. These can be either built into the server
# or added with the Action directive (see below)
# To use CGI scripts outside of ScriptAliased directories:
# (You will also need to add "ExecCGI" to the "Options" directive.)
#AddHandler cgi-script .cgi
# For files that include their own HTTP headers:
#AddHandler send-as-is asis
# For server-parsed imagemap files:
#AddHandler imap-file map
# For type maps (negotiated resources):
# (This is enabled by default to allow the Apache "It Worked" page
# to be distributed in multiple languages.)
AddHandler type-map var
# Filters allow you to process content before it is sent to the client.
# To parse .shtml files for server-side includes (SSI):
# (You will also need to add "Includes" to the "Options" directive.)
#AddType text/html .shtml
#AddOutputFilter INCLUDES .shtml
# Action lets you define media types that will execute a script whenever
# a matching file is called. This eliminates the need for repeated URL
# pathnames for oft-used CGI file processors.
# Format: Action media/type /cgi-script/location
# Format: Action handler-name /cgi-script/location
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html
# Putting this all together, we can internationalize error responses.
# We use Alias to redirect any /error/HTTP_<error>.html.var response to
# our collection of by-error message multi-language collections. We use
# includes to substitute the appropriate text.
# You can modify the messages' appearance without changing any of the
# default HTTP_<error>.html.var files by adding the line:
# Alias /error/include/ "/your/include/path/"
# which allows you to create your own set of files by starting with the
# @exp_errordir@/include/ files an

I'm more of a 1.3 chick myself, but the words are the same just in a different language.
1. Is Tomcat running?
2. Have you configured the ajp13 connector on 8009 in Tomcat? (Should it be ajp13 for Apache 2.0? - I really must upgrade)

Which J2EE servers and shared virtual hosting

We currently host our clients websites on an IIS server., using sharded virtual hosting
I am looking to transfer these clients to a new dedicated server option made available by our hosting supplier. I would like to transfer those sites to a J2EE server that would then run on the new dedicated server.
My question is, which server to use? I have most expereince with the Sun App Server 8.1 - would the platform edition suffice for this task? i.e. for hosting multiple domains on a single hardware server?
Is it possible to setup virtual domains for use on the Sun platform edition server? I couldnt find any doc for this kind of thing anywhere.
Ive trawled google and yahoo and cant seem to find the answers I'm loking for.
Many thanks.
C.

Can I ask what kind of applications you're using
Tomcat for? The sites I have are all shopping cart
based, product catalogue etc - nothing too extreme.
If it were you would you just use servlets for the DB
accesses?I also have shopping cart and catalog applications. I'm using Hibernate for my database access. The servlets call into Hibernate to read and write to the DB.
I had read somewhere that using Entity EJBs resulted
in many more DB hits that were really neccessary, so
maybe I should just stick to JSPs and servlets.I feel that EJBs have a place but that for smaller sites it can be a bit of overkill. If you're running an amazon.com and you have a cluster of 20 machines upfront with some mongo database in the back then EJBs would be essential. But if you have an installation like I do with a single server talking to a single database and managed by a single person then I feel that the added complexity is more than it is worth.
For the begginer, J2EE can be a bit of a minefield!Yeah - there is alot to it. And, as we're talking about, the API's are just the first step.

Apache server - tomcat - jk, virtual hosts, database/context.xml question?

Similar Messages

Maybe you are looking for