Slow to the game on this but been busy working! If you want to get in on the 64bit / Leopard beta check out Kristen’s blog.
Apple has released the first general OS update for Leopard. Full information on their site and available via Software Update.
Having got ColdFusion 8 running in multi-server mode on Leopard I decided to try and deploy CF7 to it as well. Started out going well, following the same process I’ve always used. I created a new server, removed the default-ear, started the proxy service and stopped the web service then dropped in the cf7 ear file. Setup all the apache2 config and restarted that OK. For reference I’ve got a jrun.conf with the module in then a cf702.conf included by default with the jrun.conf in httpd.conf then a cf8.conf I include in vhosts as needed. The server started OK but when I tried browsing the cf7.local vhost I created I was shown the message:
Interesting as it’s the same box, both configured on 127.0.0.1. A reload didn’t cure it, so off to google. I found a couple of posts relating to flash remoting. The first one was over on <a href=”http://www.talkingtree.com/blog/index.cfm/2004/9/15/flashgateway”>Steven Erat’s</a> blog from way back in 2004 related to something with flash remoting. I found a few other posts saying I’d need to remove the flash remoting ear file, which, I didn’t have showing in the JMC.
I decided to take a look in the JRun4 directory to see what flash related files there were:
macmini:JRun4 ianwinter$ find . -name "*flash*"
Some of these obviously can stay but as I don’t use flash remoting I decided to remove the flashgateway.jar and flashremoting-update.jar files. I backed up the servers directory as well first and have at this point stopped the servers.
macmini:JRun4 ianwinter$ sudo rm
Restart all the JRun servers and browse back to cf7.local and voila it works. Bit of a faf and no good if you want flash remoting but it works. I don’t know if you remove just one of the flash remoting jar’s, like just from the cf7 server if it’d work, or, perhaps you can change mappings somewhere, solves my problem so I’m happy.
Taken via macrumours Apple have begun seeding OSX 10.5.1 to developers for testing. Seems like there’s a quite a few issues been looked into for the release.
Looks like Adobe could be announcing support for ColdFusion on Leopard and 64bit (other than Solaris) soon (hopefully). [via forta.com]
So, just got ColdFusion 8 working on my Mac Mini running an upgraded version of Leopard (from Tiger). Below are the steps I took. As I said before it’s basically Geoff’s guide with a couple more reboots!
1. Install Apple XCode Tools from Leopard DVD<br>
3. Install ColdFusion 8<br>
Multi-server, developer edition
ColdFusion 8 Document and Start ColdFusion on system init both checked
Installed to /Applications/JRun4
– Configuration Directory: /etc/apache2
– Server Binary: /usr/sbin/httpd
– Server Control Script: /usr/sbin/apachectl
CFIDE installed to default documents folder which is /Library/Webserver/Documents
4. Complete wizard ignoring web server startup and connector failure messages
6. Compile the new connector
unzip -d src wsconfig.jar
apxs -c -Wc,-arch -Wc,x86_64 -Wl,-arch -Wl,x86_64 -n jrun22 mod_jrun22.c jrun_maptable_impl.c jrun_property.c jrun_session.c platform.c jrun_mutex.c jrun_proxy.c jrun_utils.c
apxs -i -n jrun22 -S LIBEXECDIR=/Applications/JRun4/lib/src/connectors/src/ mod_jrun22.la
7. Check the connector with wsconfig
sudo java -jar wsconfig.jar
8. Delete the current connector and put your fresh shiny new one in
cp /Applications/JRun4/lib/src/connectors/src/mod_jrun22.so /Application/JRun4/lib/wsconfig/1/mod_jrun22.so
10. Start CF<br>
sudo /Applications/JRun4/bin/jrun -start cfusion
11. Kick apache
sudo apachectl restart
12. Browse to localhost/CFIDE/administrator/index.cfm (unless you’ve already added index.cfm as a default doc)<br>
13. Go to bed feeling happy.
Having read many articles and endured much swearing this morning I finally got CF8 running with apache 2.2.6 on Leopard with my Macbook.
For information it’s a Intel Core 2 Macbook which had a completely clean, erase and install version of Leopard on.
I’ve writing a guide to the steps I took for reference but I was following this guide by Geoff Bowers (thanks!) and also reading comments on Mark Drew’s post. Going to try on my Mac Mini tonight which is an upgraded version of Leopard from Tiger.
If you’re trying access Leopard via RealVNC on a Windows box make sure in before you try and connect you go into Options > Misc and check the “Only use protocol version 3.3” box otherwise you won’t actually be able to connect.
Finished installing, well upgrading my new Mac Mini from Tiger to Leopard. Took about an hour an was painless.
One issue with the last.fm player not working but after a quick scoot over to the forums Robert’s your Mother’s brother and there’s a fixed version.
I have to say inital impressions, awesome! It looks great. I could very much be becoming a full MAC convert.
All hail the shiny white hardware gods!