Re: Migrating WO app to 10.8.2 on new server from 10.5, using Wonder
Re: Migrating WO app to 10.8.2 on new server from 10.5, using Wonder
- Subject: Re: Migrating WO app to 10.8.2 on new server from 10.5, using Wonder
- From: Baiss Eric Magnusson <email@hidden>
- Date: Mon, 18 Mar 2013 14:37:18 -0700
On Mar 18, 2013, at 12:47 PM, Pascal Robert <email@hidden> wrote:
>> On Mar 18, 2013, at 11:51 AM, Chuck Hill <email@hidden> wrote:
>>
>>> It sounds like it is trying to use the CGI adaptor. Does your httpd.conf file include this line?
>>> Include /System/Library/WebObjects/Adaptors/Apache2.2/apache.conf
>>
>> No, these lines:
>>
>> Include /Library/WebObjects/Adaptors/wo_rewrite.conf
>> Include /Library/WebObjects/Adaptors/wo_expires.conf
>> Include /Library/WebObjects/Adaptors/wo_apache.conf
>
> Do a grep in /Library/WebObjects/Adaptors and /etc/apache2 and search for "cgi-bin".
I've listed below the actual stuff in wo_rewrite.conf and wo_apache.conf:
## File for Rewrite
<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>
*********************************************************
# WebObjects 5.4: Enable the WebObjects module.
LoadModule WebObjects_module /Library/WebObjects/Adaptors/mod_WebObjects.so
# You can change the 'cgi-bin' part of WebObjectsAlias to whatever you
# prefer (such as Apps), but the 'WebObjects' part is required.
WebObjectsAlias /cgi-bin/WebObjects
# Here are the 3 possible configuration modes.
# The apache module uses one of them to get information
# about your deployed applications.
# 1085 is the reserved port on which wotaskd processes listen to by default.
# Host List Configuration
# wotaskd is started automatically on supported platforms,
# so this is the default mode.
# The apache module gets its configuration from the wotaskds
# listed on the configuration line
# For multiple hosts:
# WebObjectsConfig http://<name-of-a-host>:<port-on-a-host>,http://<name-of-another-host>:<port-on-a-host> <interval>
# For localhost:
WebObjectsConfig http://localhost:1085 10
# Multicast Configuration
# The apache module gets its configuration from all wotaskds
# that respond to the multicast call on the subnet
# WebObjectsConfig webobjects://239.128.14.2:1085 10
# File Configuration
# The apache module gets its configuration from one file
# WebObjectsConfig file://<path-to-a-xml-config-file> 10
# To enable public access to the WOAdaptorInfo page, uncomment the following line
# WebObjectsAdminUsername public
# To enable the WOAdaptorInfo page with restricted access,
# uncomment the next two lines and set the user and password
# To access the WOAdaptorInfo page with restricted access,
# use a URL like: http://webserver/cgi-bin/WebObjects/WOAdaptorInfo?user+password.
# WebObjectsAdminUsername user
# WebObjectsAdminPassword password
# To change the logging options, read the following comments:
# The option name is "WebObjectsLog" and the first value indicates the path of the log file.
# The second value indicates the log level. There are five, in decreasing informational order:
# "Debug", "Info", "Warn", "Error", "User"
#
# Note: To enable logging, touch '/tmp/logWebObjects' as the administrator user (usually root).
#
# The following line is the default:
# WebObjectsLog /Library/WebObjects/Logs/WebObjects.log Debug
>
>>> Note: deployment hierarchy was generated from the click on Ken's WonderBar.
>
> This is exactly why we need one standard way for development, or else trying to help people can be a problem since the setup might be different. For OS X, we have at least 3 different deployment setups.
---
Baiss Eric Magnusson
cascadewebdesign.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden