On Dec 10, 2009, at 4:52 PM, Kieran Kelleher wrote:
I have fully embedded WO 5.3.3 apps running on Snow Leopard (Client)
and talking to both MySQL 4.1.XX and MySQL 5.0.XX. In both cases, I
am using Connector/J 5.0.<latest> and I *never* use Apple's server
binaries. Actually I don't use Apple OS X Server anymore for WAM
(WebObjects-Apache-MySQL) deployments, even on new server, I wipe
the HD and install SL client.
This is encouraging news. In my case, the system is doing other
services so I need the OS X Server. I've gotten very lazy with these
boxes as they run internal apps and the Apple binaries (even with the
oddball PPC performance creep issues) have been adequate.
It might be something as simple as authentication.....
open terminal on the machine that the WO app is running and try to
connect to MySQL using the exact same user/password as the app uses:
mysql -u <webobjectsappuser> -h localhost -p
Password:
Fail! You are brilliant. I never thought to test. I always admin
MySQL with the root account and just assume that the additional
accounts will work. I've always setup with GRANT ALL PRIVILEGES ON
FEEDBACK.* TO wouser@"%" IDENTIFIED BY 'thePass'; Heck, I even
checked my old box and that is how it is set up.
So a quick GRANT ALL PRIVILEGES ON FEEDBACK.* to wou...@localhost
IDENTIFIED by 'thePass'; did the trick!
You do know that MySQL uses *three* things to authenticate ....
user, password *and* originating-host-name.
Also, in MySQL, do this to get an idea of the combinations you have
set up
select User, Host, Password from mysql.user;
user@'192.%' is not the same as u...@localhost .... also % is a
wildcard for a portion of an IP address or hostname.
That was the trick. Kieran, thank you very much for solving for me
what I spent most of the day being an idiot with :) Thanks so much.
Ah, long live the WO apps. This give new hope to a six year old
customer app that gets used everyday. The sad thing is that I have
not touched the code in 5 years and have no clue how I built it. The
power of WO.
Thanks again.
Reid
HTH, Kieran
On Dec 10, 2009, at 4:35 PM, ACN wrote:
Hello List,
Been a long time. I am looking to migrate my small collection of
WO apps over to Snow Leopard servers (older hardware is off lease
and going away) and I'm stuck getting access to my databases.
Where I am coming from:
WO is hosted on a couple of G5 Xserves running 10.5.8
Apple provide MySQL is the database
I've been using the Connector/J JDBC plugin version 3.1.12 for
ages with good success
WO Apps have been running for years with no modification of note
Where I am going:
A new Xserve running 10.6.x
Planned on using Apple provided MySQL database
What have I done so far:
WO 5.4.3 is installed and wotaskd and womonitor are up and running.
Connector/J 5.1.10 JDBC plugin is installed in /Library/Java/
Extensions
MySQL is up and running
I simply copied my .woa packages from the old machine to this one
(I did not attempt to recompile)
Used WOMonitor to deploy
Both apps are working in that they display initial content (no
fetches for either app on main page)
One of the applications is working all the way in that it linked
to a MySQL server on another Xserve (running 10.4.x)
Hand edited the index.eomodeld files to update the plugin
information and server address for the app that is referencing the
local MySQL
What is not working:
The application that is not working is the one that references
MySQL on itself (meaning the 10.6 server). I am throwing an
exception when I try to write to the database server on the host
server: _obtainOpenChannel. Now, if I go over to my development
machine, running 10.4.11, I can open up EOModeler and browse the
content of the new server's MySQL database. This was initially
accomplished using the original 3.1.12 Connector J plugin but I
also tried the 5.1.10 version on 10.4.11 to some success (although
eomodeler will occasionally crash which I can accept). I realize I
am referencing the connection process from the development box but
at least I know the data is accessible based on the user, password,
and plugin configuration.
With WO support in Snow in its current state, am I trying to
accomplish something that can not be accomplished? Is MySQL + Snow
Leopard + Connector/J + traditional WO development something I
should not be pursuing? Obviously, I have the option of moving my
database to the 10.4 server mentioned above. Then my app would, in
theory, work again since I am not trying to access the local MySQL
server.
Anyone have success building a Snow Leopard server with Apple's
MySQL and a JDBC plugin that works with traditional .woa
deployments? I know, I have actually become a dinosaur. The truth
is that I developed the apps so well that I really never need to
touch them. I just need to keep them working.
As always, thanks in advance
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list ([email protected]
)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/kieran_lists%40mac.com
This email sent to [email protected]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to [email protected]
