Yes. Charlie Arehart and Jeff Houser wrote an article in the Sept. 2003 ColdFusion Developer's Journal on how to do this. I'm assuming here that you're using IIS. Apache is somewhat different.
What you need to do is to install both MX and Blue Dragon. Then set up a virtual directory for BD and change some of the configuration for it. To quote from the article (see http://www.sys-con.com/story/?storyid=42069):
--
Let's take stock of what you've done to your machine thus far. ColdFusion 5, ColdFusion MX, and BlueDragon are installed. Only ColdFusion MX is set up to run using IIS. All CFML templates in all directories run though IIS will execute by way of CFMX. BlueDragon will run only in stand-alone mode using its built-in Web server. ColdFusion 5 won't work at all because its mappings were replaced by ColdFusion MX. We now want to accomplish our goal of having everything run off of our single instance of IIS, pointing to the inetpub/webroot.
The solution is to create virtual directories for each server that point to the webroot, but run the templates through the desired CFML server. The key is in those extension mappings that we referred to before. In fact, we can create different virtual directories that each use a different mapping for CFML templates. You can do this from the Internet Services Manager. Follow these instructions:
1. Right-click on the Default Web Site and select Virtual Directory from the New menu.
2. Name the first virtual directory something like CF5. When asked to enter the path containing the Web content, use the available Browse button to point to inetpub\wwwroot. Now the virtual directory is created.
3. Bring up that new virtual directory's properties by right-clicking it and selecting Properties. Click on the Configuration button on the virtual directory tab. It will probably have inherited mappings (for the .cfm and .cfml extensions) that point to the ColdFusion MX IIS DLL, because CFMX was configured to use IIS integration in that previous CFMX install step. We will want to override this mapping. Change the cfm and cfml mappings to point to C:\Cfusion\BIN\ISCF.DLL, the value you wrote down earlier in this article during the CF5 setup.
4. Now, templates executed with the new /CF5 URL will execute via CF5 instead. You can confirm that your new setup is working by using the URL http://localhost/CF5/ to run some CFML templates in the inetpub\wwwroot. If you followed the recommendation of renaming the CFDOCS directory that had been installed with CF5, the URL would now be http://localhost/cf5/cfdocs5/dochome.htm. The CF5 Administrator would be http://localhost/cf5/cfide5/administrator/index.cfm. Admittedly, not all the images will work correctly and some links may not work as expected, but at least it's better than having lost the CF 5 Admin and docs if we'd installed CFMX directly to the IIS webroot and had overwritten them entirely.
Now, what about CFMX? Though it's already set up to serve docs in the webroot, you may want to create another virtual directory, named CFMX, to parallel what you did for CF5. You can follow steps similar to those above to create a virtual directory named CFMX, using the CFMX version of the IIS DLL mappings we had taken note of earlier.
--
hth,
larry
--
Larry C. Lyons
Web Analyst
BEI Resources
American Type Culture Collection
email: llyons(at)atcc.org
tel: 703.365.2700.2678
--
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
