I was just looking at the Linux system requirements for ColdFusion MX 7. For supported linux operating systems, it lists:
- Red Hat Enterprise Linux AS & ES 2.1 or 3.0
- SuSE Linux Enterprise Server 8.x
- TurboLinux 8 Server (Japanese only)
In 6.1 the Supported Linux Operating Systems included:
- Red Hat Linux 7.2, 7.3, 8.0, 9, AS & ES 2.1, AS & ES 3.0
- SuSE Linux 7.2, 7.3, or 8.x
- TurboLinux 8 Server (Japanese Only)
- Linux for zSeries: SuSE Linux Enterprise Server 8 Service Pack 2 running in 31-bit mode
What I'm wondering is - where is SuSE Linux Enterprise Server 9? It has been out since Aug 2004. If I were going to setup a SuSE/CFMX install, I would probably want to go with SuSE 9 - the reason for that, is so I don't have to upgrade my OS, the next time MM drops support for older linux distros (like they did from 6.1 to 7.0). I don't have a problem with MM dropping old distros, I just want to see support for current version, I don't even see where you can get SuSE 8 on their site.
There are also no free linux distros supported eg Debian, or Fedora might be good choices.
I do understand that Macromedia will not support an OS just because a few vocal people think its a good idea. They like to have some numbers, so I started a poll on my site (lower left). And you can also post a comment with the distro you would like to see supported.
I also asked Tim Buntel about doing a survey for linux like they did for Mac OSX, and he said - he would post something on his blog about it, if it is something they think they need community input for.
Update - As of ColdFusion MX 7.0.1 updater 1 SuSE 9 is now supported, Red Hat Linux AS 3.0, 4.0 are supported, and support for Redhat 2.1 was removed.
I've been running CF on Suse Linux Enterprise Server 8 for 2 years. It runs like a champ. It doesn't install on Suse 9. Rather then being a platform, like Windows, Linux is merely the kernel that ties everything together. Upon installation, it is up to the admin to choose which packages he/she wants to install, depending on the function of the server. Each Linux distro offers a different set of packages, depending upon the target audience. This flexibililty is nice, b/c you can only install what you want to install. It would be safe to say that RedHat and SuSE target the enterprise.
When installing CF, some packages, along with your distro, are required to be installed. SUSE 9 offers an updated set of packages than what is included on SUSE 8, so it really is a compatibility issue. If I recall corretly, the initial issue with SuSE 9 is that the installation uses deprecated syntax for an command that has been updated in Suse 9. I couldn't change it to the correct syntax b/c that part of the .bin installation file was encrypted.
MACR doesn't say you are liminted to only RedHat, SUSE, and TurboLinux. They just say that those are the only suppoted platforms. You are not limited to the packages that are included on a particular Linux distro. If you can find the right combination of required packages, the you should be able to install CF with no issues.
For example, the SUSE installation I'm using for CF is under 400MB. Remember, I am only running what I need.
Well, I've written all my notes down, I will try and summarize quickly here then later point to some better HTTP based documentation.
1. Get coldfusion-70-lin.bin ($$$)
2. Distributed ( meaning server on one box and cf on another box ): If different subnet between web and JRun, then grant permission to the web server(s). ( JNDI ) <cf_root>/runtime/lib/security.properties add web server IP like this 'jrun.trusted.hosts=192.168.1.10', then restart JRun
3) Install Java 1.4 ( jre )
check with 'java -version'
3b) You should be able to open the CFadmin panel on the JRun box if you installed with the internal web server; otherwise, continue...
4) Copy cf_root/runtime/lib/wsconfig.jar to your web server filesystem
5) Run the wsconfig.jar on the web server:
java -jar /tmp/wsconfig.jar
- server coldfusion
- ws Apache
- bin /usr/sbin/httpd2-prefork
- script /usr/sbin/apache2ctl
- dir /etc/apache2
- map .cfm,.cfc,.cfml,.jsp
- host 192.168.1.100 # this is the jrun server ip
6) Copy the CFIDE/ directory to the web root on the web server, this must match exactly with the root of jrun
7) Confirm cfadmin runs on the web server
8) Adjust the Mapping root to the web server root, again, this must exist exactly on both the web server and the jrun server.
9) Disable the internal jrun web server on the jrun server: cf_root/runtime/servers/default/SERVER-INF/jrun.xml
WEBSERVER attribute:deactivated to 'true'
, restart jrun
10) You are live.
My notes are very jumbled, but this was a first attempt to pulling them together, please forgive typos. Also, let me know if something doesn't wash, I might have translated my chicken-linux scratch incorrectly. :D
Let me know how it goes, Jimmy.