Changes for page Configuring Apache for WebObjects

Last modified by Aaron Rosenzweig on 2020/09/03 22:17

From 19.1 to 20.1 From 21.1 to 22.1

From version 20.1

edited by David Avendasora
on 2010/12/03 11:05

Change comment: There is no comment for this version

To version 21.1

edited by smmccraw
on 2007/07/08 09:45

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Title

@@ -1,1 +1,1 @@
--Configuring Apache for WebObjects
++Programming__WebObjects-Web Applications-Deployment-Apache

Author

@@ -1,1 +1,1 @@
--XWiki.avendasora
++XWiki.smmccraw

Content

@@ -1,109 +1,103 @@
--== Overview ==
++== Overview  ==
--In a deployment scenario on Mac OS X, Linux, Solaris or even Windows, your applications will most likely use Apache to server static resources.  Additionally, if you develop with WODirectConnectEnabled=false (you **should**, see the [[Direct Connect>>Development-Direct Connect]] section for details), you will be running your application locally through Apache as well.  Apache is a very extensible web server that provides a huge number of capabilities, some of which we will detail here.
++In a deployment scenario on Mac OS X, Linux, or Solaris, your applications will most likely be deployed on Apache.  Additionally, if you develop with WODirectConnectEnabled=false (you **should**, see the [[Direct Connect>>Programming__WebObjects-Web Applications-Development-Direct Connect]] section for details), you will be running your application locally through Apache as well.  Apache is a very extensible web server that provides a huge number of capabilities, some of which we will detail here.
--== Split Install ==
++== Split Install  ==
--WebObjects applications are deployed in a "split install".  A split install means that your application code, components, and resources are deployed in one location to be served from your WebObjects application (on OS X, ##/Library/WebObjects/Applications/##{{{}{_}YourApp{_}{}}}##.woa##), while your ##WebServerResources## are installed in another location (on OS X, ##/Library/WebServer/Documents/WebObjects/##{{{}{_}YourApp{_}{}}}##.woa/Contents/WebServerResources##) to be served directly by Apache.  This provides the optimal performance scenario, as Apache is specifically tuned for serving static content, and it does not make sense to send requests for large binary files through WebObjects if it is not necessary.
++WebObjects applications are deployed in a "split install".  A split install means that your application code, components, and resources are deployed in one location to be served from your WebObjects application (on OS X, /Library/WebObjects/Applications/YourApp.woa), while your WebServerResources are installed in another location (on OS X, /Library/WebServer/Documents/WebObjects/YourApp.woa/Contents/WebServerResources) to be served directly by Apache.  This provides the optimal performance scenario, as Apache is specifically tuned for serving static content, and it does not make sense to send requests for large binary files through WebObjects if it is not necessary.
--== mod//expires// ==
++== mod//expires // ==
  To get the most performance out of Apache, you should make sure that you have mod//expires enabled.  mod//expires controls the caching headers that are applied to static resource requests.  Depending on your installation, Apache may default to mod//expires disabled, which would cause your end-users' browser to re-request every resource on your site on every page, even if it's a common header graphic.//
  An example mod//expires configuration might look like~://
--{{code value="xml"}}
++{{panel}}
--<IfModule mod_expires.c>
--  ExpiresActive On
--  ExpiresDefault A60
--  ExpiresByType image/bmp A3600
--  ExpiresByType image/gif A3600
--  ExpiresByType image/ief A3600
--  ExpiresByType image/jpeg A3600
--  ExpiresByType image/png A3600
--</IfModule>
++  <IfModule mod_expires.c>
++    ExpiresActive On
++    ExpiresDefault A60
++    ExpiresByType image/bmp A3600
++    ExpiresByType image/gif A3600
++    ExpiresByType image/ief A3600
++    ExpiresByType image/jpeg A3600
++    ExpiresByType image/png A3600
++  </IfModule>
--{{/code}}
++{{/panel}}
  You will also need the corresponding type-extension mappings:
--{{code value="xml"}}
++{{panel}}
--<IfModule mod_mime.c>
--  AddType image/bmp bmp
--  AddType image/gif gif
--  AddType image/ief ief
--  AddType image/jpeg jpeg
--  AddType image/jpeg jpg
--  AddType image/jpeg jpe
--  ...
--</IfModule>
++  <IfModule mod_mime.c>
++    AddType image/bmp bmp
++    AddType image/gif gif
++    AddType image/ief ief
++    AddType image/jpeg jpeg
++    AddType image/jpeg jpg
++    AddType image/jpeg jpe
++    ...
++  </IfModule>
--{{/code}}
++{{/panel}}
  This tells Apache that when a request is made for a type image/gif, the requesting browser will be told not to request the image again for an hour (A3600 = 3600 seconds).
--== mod//rewrite// ==
++== mod//rewrite // ==
--Anyone who has used WebObjects has likely noticed that WebObjects URLs are long ##[[http://yoursite.com/cgi-bin/WebObjects/AppName.woa/wa/something]]##.  It is a common request to make these URLs nicer for end-users who are used to just requesting ##[[http://yoursite.com]]##.  Fortunately Apache provides an amazingly extensive module called "mod//rewrite" that allows you to rewrite the URL requests of your site based on a series of regular expressions and rules.//
++Anyone who has used WebObjects has likely noticed that WebObjects URLs are long (http:~/~/yoursite.com/cgi-bin/WebObjects/AppName.woa/wa/something).  It is a common request to make these URLs nicer for end-users who are used to just requesting "http:~/~/yoursite.com".  Fortunately Apache provides an amazingly extensive module called "mod//rewrite" that allows you to rewrite the URL requests of your site based on a series of regular expressions and rules.//
--Aaron Rosenzweig has a very thorough article about [[using mod//rewrite with Apache//>>http://www.jewelryluv.com/fashion/pageWithName/ModRewrite/]].
++Aaron Rosenzweig has a very thorough article about [[using mod//rewrite with Apache//>>http://www.jewelryluv.com/fashion/pageWithName/ModRewrite]].
--=== mod//rewrite with mod//webobjects ===
++=== mod//rewite with mod//webobjects  ===
  I ran into a problem with mod//rewrite when using mod//WebObjects where mod//WebObjects had be loaded first or it just wouldn't work properly (it would work fine with cgi-bin adaptor).//
  So in http.conf, search for mod//rewrite and change it to~://
--{{noformat}}
++{{panel}}
--LoadModule WebObjects_module    /System/Library/WebObjects/Adaptors/Apache/mod_WebObjects.so
--LoadModule rewrite_module       libexec/httpd/mod_rewrite.so
++  LoadModule WebObjects_module    /System/Library/WebObjects/Adaptors/Apache/mod_WebObjects.so
++  LoadModule rewrite_module         libexec/httpd/mod_rewrite.so
--{{/noformat}}
++{{/panel}}
  , find again:
--{{noformat}}
++{{panel}}
--AddModule mod_WebObjects.c
--AddModule mod_rewrite.c
++  AddModule mod_WebObjects.c
++  AddModule mod_rewrite.c
--{{/noformat}}
++{{/panel}}
--There's still a load module in /System/Library/WebObjects/Adaptors/Apache/apache.conf, but you can just ignore it - it produces a warning about being loaded twice.
++There's still a load module in /System/Library/WebObjects/Adaptors/Apache/apache.conf, but you can just ignore it ~-~- it produces a warning about being loaded twice.
--=== Mike Schrag ===
++=== Mike Schrag  ===
  Here's an example mod//rewrite we use on one of our apps~://
--{{code value="xml"}}
++{{panel}}
--<IfModule mod_rewrite.c>
--  RewriteEngine On
--  RewriteRule ^/$ /page/HomePage [R]
--  RewriteCond %{QUERY_STRING} ^appNum=([-0-9]+)(.*)$
--  RewriteRule ^/page/(.*)$ /cgi-bin/WebObjects/AppName.woa/%1/wa/viewPage?pageName=$1%2 [L,PT]
--  RewriteRule ^/page/(.*)$ /cgi-bin/WebObjects/AppName.woa/wa/viewPage?pageName=$1 [L,PT,QSA]
--</IfModule>
++  <IfModule mod_rewrite.c>
++    RewriteEngine On
++    RewriteRule ^/$ /page/HomePage [R]
++    RewriteCond %{QUERY_STRING} ^appNum=([-0-9]+)(.*)$
++    RewriteRule ^/page/(.*)$ /cgi-bin/WebObjects/AppName.woa/%1/wa/viewPage?pageName=$1%2 [L,PT]
++    RewriteRule ^/page/(.*)$ /cgi-bin/WebObjects/AppName.woa/wa/viewPage?pageName=$1 [L,PT,QSA]
++  </IfModule>
--{{/code}}
++{{/panel}}
--The WOA produces URLs in the format ##[[http://site.com/page/HomePage?appNum=2]]##, which turns into ##[[http://site.com/cgi-bin/WebObjects/AppName.woa/2/viewPage?pageName=HomePage]]##.
++The WOA produces URLs in the format http:~/~/site.com/page/HomePage?appNum=2, which turns into http:~/~/site.com/cgi-bin/WebObjects/AppName.woa/2/viewPage?pageName=HomePage.
--{{id value="Apache22Adapter"}}{{/id}}
++== WebObjects Adaptor for Apache 2.2  ==
--=== Jeff Schmitz ===
++=== Travis Cripps  ===
--This one stumped me for a couple days, so thought I'd add it. &nbsp;Was trying to add mod//rewrite functionality as described above, and things went well on my dev machine by adding the rewrite rules just to the /etc/apache2/httpd.conf file. &nbsp;However, on the deployment machine I also had to add them to the /etc/apache2/sites/0000//any//.conf file. &nbsp;//
++A number of people have expressed interest in using the WebObjects adaptor with Apache 2.2.x.  I finally gotten a chance to sit down and work on it today.  I'm writing to let you know that it's available in the Project Wonder CVS repository.
--== WebObjects Adaptor for Apache 2.2 ==
--
--=== Travis Cripps ===
--
--A number of people have expressed interest in using the WebObjects adaptor with Apache 2.2.x.  I finally gotten a chance to sit down and work on it today.  I'm writing to let you know that it's available in the Project Wonder CVS repository. (also there are [[precompiled binaries>>http://webobjects.mdimension.com/wonder/mod_WebObjects/]] for various OS available)
--
  The necessary changes turned out to be mostly minor updates to change calls to outdated/deprecated functions.  The biggest (and non-trivial) change was for SSL support.  It's been re-written to use Apache's mod//ssl module.//
  I've tested with MacOS X 10.4.7, Apache 2.2.2, with and without ssl support.  It works in all of my tests.
@@ -112,32 +112,21 @@
  The new default configuration is:
--{{code value="xml"}}
++{{panel}}
--<Directory />
--   Options FollowSymLinks
--   AllowOverride None
--   Order deny,allow
--   Deny from all
--</Directory>
++  <Directory />
++     Options FollowSymLinks
++     AllowOverride None
++     Order deny,allow
++     Deny from all
++  </Directory>
--{{/code}}
++{{/panel}}
  Your options are to comment out the last 2 lines of that block, or to override them in a VirtualHost block.  Just setting the usual Location block didn't seem to work for me.
  And, of course, either change the name of the WebObjectsAlias setting from /cgi-bin/WebObjects to <foo>/WebObjects or comment out the ScriptAlias definition for the /cgi-bin/ directory.
--{{info title="Note"}}
--
--The default {{ScriptAlias}} directive in the 10.5 and 10.6 {{httpd.conf}} files is:
--\\
--{noformat}
--ScriptAliasMatch ^/cgi-bin/((?!(?i:webobjects)).*$) "/Library/WebServer/CGI-Executables/$1"
--{noformat}
--This prevents {{/cgi-bin/WebObjects}} from matching, so no change to {{WebObjectsAlias}} or {{ScriptAlias}} is necessary.
--
--{{/info}}
--
  Other than these tips, it's pretty much the standard compilation and installation, and configuration.
 . Alter the make.config file in the Adaptors directory of the Wonder repository to reflect your apache installation setup.
@@ -150,19 +150,21 @@
 . Test.
 . Curse again.  Change the httpd.conf file as necessary.
 . apachectl graceful.  Go to 8 as necessary.
--1. Finally  apachectl graceful
++1. Finally!  apachectl graceful
--Enjoy your shiny new WO adaptor. :-)
++Enjoy your shiny new WO adaptor. :)
  * Note: if you are getting the error
--{{noformat}}
++{{panel}}
--libtool: compile: unable to infer tagged configuration
--libtool: compile: specify a tag with `--tag'
--apxs:Error: Command failed with rc=65536
++  libtool: compile: unable to infer tagged configuration
++  libtool: compile: specify a tag with `--tag'
++  apxs:Error: Command failed with rc=65536
--{{/noformat}}
++{{/panel}}
  Add to the end of your make.config the following:
--##CC = gcc##
++CC = gcc
++
++Category:WebObjects

Changes for page Configuring Apache for WebObjects

Summary

Details

Applications

Navigation

My Recent Modifications

Need help?