Nope, we have it running on two 10.5 Mac OS X servers. You just might
need to use different file locations to get it right. And see the not
from Ron Alt, about the issue with multiple processors, which is an
entirely different issue.
On Jun 17, 2009, at 7:28 AM, Marc Herman wrote:
Ouch! I need it for Server Mac OS X 10.5
Am i out of luck?
mvg
Marc Herman
Artefact
Gerard Vander Lindenstraat 8
3000 Leuven
marc.her...@artefact.be
T 016 28 48 40
F 016 28 48 49
Op 17-jun-09, om 12:27 heeft Dale Graham het volgende geschreven:
Here's the info I posted to the list quite some time ago...
Please note that we also have WitangoServer running on XServes
(Intel/Leopard) so that can be done, as well. However, I think some
of the addresses are different on Mac OS X server ...
Note that this is a solution for CLIENT Leopard, not for SERVER
Leopard.
WitangoServer for Intel Macs requires Apache 2.2+, but Leopard uses
Apache 2.2.6+ and that version does not support the Witango module,
which is designed for earlier versions of 2.2. Furthermore, I
couldn't get earlier 2.2 versions of Apache to run on Leopard.
(Stole some ideas from http://www.fatcatsoftware.com/blog/2007/running-fogbugz-on-leopard
and then modified as needed for Witango)
The problem was that I was getting a "module" error, and an
indication that it needed to be re-worked - apparently for 64-
bit. ... this method strips 64-bit-ness from Apache 2.2.6
************************
1] Workaround for 64 bit
cd /usr/sbin
sudo cp httpd httpd-fat <=== (creates httpd backup)
sudo lipo httpd -thin i386 -output httpd
Quote from website above:
"After making a backup of the httpd executable for safety purposes,
the lipo commands sucks out all of the architectures included in
the universal binary except the 32-bit Intel one (specified by
“i386″). Apache can’t run as 64-bit if it doesn’t have a 64-
bit binary!"
Note from DEG: I presume this would also (??) work for PPC
machines, but a different code (possibly PPC or ppc) would need to
be substituted for the i386 in the "lipo" command above.
2] Install
Create witango user
Install WitangoServer. Get usual install error (caused by Apache in
wrong location ... see below)
3] Workaround for non-standard location of Apache in Leopard (/etc/
apache2)
In Terminal -->
sudo cp /Applications/WitangoServer/5.5/install/Plug-Ins/
mod_witango55_apache22.so /usr/libexec/apache2/
mod_witango55_apache22.so
(copies module to the right place for Apache2 to see it)
note, no line break should be in the line above, even if there
appears to be one after going through email
Create backup of /etc/apache2/httpd.conf
cd /etc/apache2
sudo cp httpd.conf httpd-back.conf
cp httpd.conf /Users/<your user name>/httpd.conf <=== I prefer
editing outside of the /etc directory. This is the copy I can fool
with
Edit httpd.conf, adding THIS edited information instead of the
provided mod_witango55_apache22.so.httpd (to account for new
location for modules)
I just added this as the last part of the httpd.conf file
# LOAD WITANGO MODULE
# This loads the Witango 5.5 client for Apache 2.2 to enable
# communication with the Witango Application Server
LoadModule WitangoModule libexec/apache2/mod_witango55_apache22.so
WitangoModule mod_witango55_apache22.so
AddType application/witango-application-file taf tml thtml tcf wws
If you wish, change httpd.conf for location of web pages. In my
case I just deleted the Library/WebServer directory and aliased in
my working one, which is on an entirely different partition.
sudo cp /Users/<your user name>/httpd.conf /etc/apache2/
httpd.conf <=== Returns the edited copy to /etc/apache2
BTW, copy over old WitangoServer/5.5/configuration files from Tiger
config for WitangoServer, for quickest switchover.
4] Workaround for starting up WitangoServer due to incomplete
installer script ---
Witango startup unlikely to work, so I didn't bother with that (I
am on a development server, so I am not concerned with automatic
startups)...
In Terminal --->
cd /Applications/WitangoServer/5.5
./witangod -uo
My server admin developed an automatic script to get Witango
running on restart of our servers. Contact me if you need that as
well.
5] If you get an error message for clients.ini
Change permissions (and path to permissions) so that these are wide
open (because I wasn't sure who the "owner" was for the http
process - system? wheel? root?) This is NOT the best solution, but
it was good for checking that there was ANY situation in which I
could start up. The more experienced among you can tackle that.
Start up Apache webserver using Preferences --> Sharing ---> Web
sharing. If you had already started it, shut it down, restart.
Start up WitangoServer as indicated above. (Note that if this
start up of the Web sharing process "hangs", it means that you've
done something wrong with the httpd.conf file - check the console
application to find out where the problem was.)
This looks complicated, but it took far longer for me to tweak
around and test at each point get it running. If you follow this
(AND if I didn't leave some critical bit out), it should take you
less than 5 minutes to get the Witango Server running.
and, lastly, be sure to put your JDBC drivers here, if you're
running JDBC.
Library/Java/Extensions
PS, the J2EE version runs just fine without any issue. But I like
to test with the WitangoServer first before compiling/deploying
there.
On Jun 17, 2009, at 2:06 AM, Marc Herman wrote:
off topic:
Studio is working fine with me on 10.5
I haven't managed to install the server on 10.5 though, indeed,
due to these "non-standard" locations.
Can someone point me in the right direction to do that?
mvg
Marc Herman
Artefact
Gerard Vander Lindenstraat 8
3000 Leuven
marc.her...@artefact.be
T 016 28 48 40
F 016 28 48 49
Op 17-jun-09, om 06:04 heeft Robert Garcia het volgende geschreven:
I am not just referring to the server, but more importantly, the
studio.
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
rgar...@bighead.net - rgar...@eventpix.com
http://bighead.net/ - http://eventpix.com/
On Jun 16, 2009, at 5:28 PM, Dale Graham wrote:
Actually, the only problem we have ever had with 10.5 was
installation, and that related to non-standard locations for
items relating to the (native) Apache server and (worse) the
fact that Apache graduated to 64 bit and therefore could not
recognize the Witango module, which is not 64 bit. Once the
locations are corrected and the Apache server is downgraded to
32 bit, it works like a charm.
(Of course if you have other processes that need the 64 bit
Apache, then you're right, there's a serious problem.)
On Jun 16, 2009, at 7:27 PM, Robert Garcia wrote:
Witango was never compatible with 10.5 completely, so 10.6 will
be a tall order.
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
rgar...@bighead.net - rgar...@eventpix.com
http://bighead.net/ - http://eventpix.com/
On Jun 16, 2009, at 6:48 AM, Paul Wilson wrote:
Hello,
As we are planning ahead for our upgrade to Snow Leopard, has
anyone heard of (or know of) compatibility issues between
Witango Server and Mac OS 10.6?
Thank you,
Paul
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/
maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
