Re: Is Apache/Tomcat an alternative for us?

2001-03-28 Thread Robert de Geus



As far as I am aware, apxs is a utilty created when 
compiling apache when apache is configured for loadable modules. This program 
contains all information about the apache installation (header files, libraries, 
installation directory) and can be used to compile loadable apache modules. 
Running this program on jakarta-tomcat-3.2.1-src/src/native/apache/jserv with 
the commandline as specified in the tomcat installation manual gives the 
mod_serv.so which should be copied in the libexec directory of the apache 
installation. Include tomcat.conf in httpd.conf, and restart apache.  No perl 
needed to install tomcat and apache and mod_jserv. Apxs just saves you the 
problem to create the module inside the apache makefile structure etc. This is 
what I used to compile apache:
 
To create apache for loadable modules:
CFLAGS="-D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64"export CFLAGS
 
./configure --enable-rule=SHARED_CORE 
\   --enable-module=so  
 
make
make install
 
The compile the jserv module using apsx in the 
apache/bin directory.
 
you can start servlet using http://localhost/examples instead of http://localhost:8080/
 
Kind regards,
Robert de Geus
 

  - Original Message - 
  From: 
  Eyvind Almquist 
  To: [EMAIL PROTECTED] 
  Sent: Wednesday, March 28, 2001 3:29 
  PM
  Subject: Is Apache/Tomcat an alternative 
  for us?
  
  The mission was to set up a Java-application with 
  servlets.The persons to perform this task was two IT-consultants who both 
  hadprevious experience from setting up webservers and web-based 
  applications.Apache webserver 1.3.11 was already installed and had been 
  used for some time to serve static content.Since Apache webserver do not 
  have support for servlets we needed to install Tomcat also.This is how the 
  work proceeded:
   
  Tomcat 3.2.1 was installed on the 
  Unix-machine.According to the Tomcat website this was "the latest release 
  quality Tomcat build". Apache webserver was stopped. Then we tried to 
  start Tomcat. However it refused to start until wechanged the 
  configuration-script to another port than 8007.Then we changed the Apache 
  configuration file to include the Tomcat configuration file.
   
  To connect Apache and Tomcat we needed to 
  get  a webserver-adapter called Jserv. The User guide for Tomcat says 
  that we need to compile the source-files for Jserv to get a working version 
  for our OS (Solaris 5).After an extensive detective workwe found the 
  needed source-file in the source version of Tomcat. The detective worktook 
  a very long time, since these files where not in the place indicated by 
  the  User guide for Tomcat. So we downloaded the source for Tomcat 
  3.2.1.We located the source-files for Jserv.Then we moved to that 
  directory and ran the commands for compiling. However these commandsdidn't 
  succed, since they called a Perl-script and we didn't have Perl on our 
  machine.Since Perl was not included in the Apache server or our version of 
  Solaris,we needed to install the Perl parser.
   
  We found Perl  5.005_03 for Solaris on  
  Netscape's site and installed it. However the Perl parser didn't accept 
  the included script from Tomcat for compiling called "apxs"due to several 
  errors in it.So we now have three alternatives.
   
  Alternative 1
   
  Skip Apache web-server and use another one that 
  can handle Java-servlets better.If we used a Java-based web-server with 
  built-in support for servlets we wouldn't need a webserver-adapterlike 
  Jserv and no seperate servlet-engine like Tomcat.
   
  Alternative 2
   
  Download another version of Tomcat and hope that 
  the Perl-script apxs and everything else in itis correct this time. 
  
   
  Alternative 3
   
  Download another version of the Perl-parser and 
  hope that it accepts the Perl-script apxs.
   
  Does anyone has any opionons on what alternative 
  we should go for or some other alternative? We also need the webserver to 
  handle SSL, which means that
  we later would have to download and install a 
  module for that, since our Apache web-server don't support that.
   
  
  Eyvind AlmquistTietoenator 
  Consulting


Is Apache/Tomcat an alternative for us?

2001-03-28 Thread Eyvind Almquist



The mission was to set up a Java-application with 
servlets.The persons to perform this task was two IT-consultants who both 
hadprevious experience from setting up webservers and web-based 
applications.Apache webserver 1.3.11 was already installed and had been used 
for some time to serve static content.Since Apache webserver do not have 
support for servlets we needed to install Tomcat also.This is how the work 
proceeded:
 
Tomcat 3.2.1 was installed on the 
Unix-machine.According to the Tomcat website this was "the latest release 
quality Tomcat build". Apache webserver was stopped. Then we tried to start 
Tomcat. However it refused to start until wechanged the configuration-script 
to another port than 8007.Then we changed the Apache configuration file to 
include the Tomcat configuration file.
 
To connect Apache and Tomcat we needed to get  
a webserver-adapter called Jserv. The User guide for Tomcat says that we need to 
compile the source-files for Jserv to get a working version for our OS (Solaris 
5).After an extensive detective workwe found the needed source-file in 
the source version of Tomcat. The detective worktook a very long time, since 
these files where not in the place indicated by the  User guide for 
Tomcat. So we downloaded the source for Tomcat 3.2.1.We located the 
source-files for Jserv.Then we moved to that directory and ran the commands 
for compiling. However these commandsdidn't succed, since they called a 
Perl-script and we didn't have Perl on our machine.Since Perl was not 
included in the Apache server or our version of Solaris,we needed to install 
the Perl parser.
 
We found Perl  5.005_03 for Solaris on  
Netscape's site and installed it. However the Perl parser didn't accept the 
included script from Tomcat for compiling called "apxs"due to several errors 
in it.So we now have three alternatives.
 
Alternative 1
 
Skip Apache web-server and use another one that can 
handle Java-servlets better.If we used a Java-based web-server with built-in 
support for servlets we wouldn't need a webserver-adapterlike Jserv and no 
seperate servlet-engine like Tomcat.
 
Alternative 2
 
Download another version of Tomcat and hope that 
the Perl-script apxs and everything else in itis correct this time. 

 
Alternative 3
 
Download another version of the Perl-parser and 
hope that it accepts the Perl-script apxs.
 
Does anyone has any opionons on what alternative we 
should go for or some other alternative? We also need the webserver to handle 
SSL, which means that
we later would have to download and install a 
module for that, since our Apache web-server don't support that.
 

Eyvind AlmquistTietoenator 
Consulting