Ask a Question related to Coldfusion Server Administration, Design and Development.
-
TFMX #1
Distributed ColdFusion
Is it absolutely necessary to have the ColdFusion files on both the Web Server
and the App Server? The Web Server is running IIS and the App Server is
running ColdFusion MX 7.1 Enterprise. ColdFusion 5.0 did not require the
ColdFusion files to be on both machines. Maybe there is some kind of registry
hack or something.
TFMX Guest
-
Coldfusion distributed IIS conection
Hello, I need some help to understand what goes into the ISAPI conection from a IIS server and a ColdFusion one. The IIS machine: Windows 2003 and... -
ColdFusion MX 7 - Distributed Mode and Context Root
Hey all, I'm currently using ColdFusion MX 7 (multi-server) on JRun in a distributed mode (i.e. I have 1 to N separate physical apache servers... -
Distributed Deployment
Hi, I am working on a ASP.NET Web Application that uses some business logic dlls (all written in .NET). If I deploy the business logic dlls to... -
Distributed Transaction Error
Hi there We have a asp page in which we are making some update calls connecting to SQL Server 2000. it's been done by... -
Coordinated Distributed Transactions
> In the CLI guid it says i cannot use SQLEndTran(), but what should i use? Huh? I think you've mistyped "cannot" for "must". According to the... -
LinuxInductee #2
Re: Distributed ColdFusion
Actually no. The Web server holds your static content and the web
connector, which points back to to your J2EE app server containing
your CFMX application, which holds your .cfm,cfc files.
In my distributed situation I was using Apache 2; however, I doubt
there would be any differences based on the HTTP server.
This distributed infrastructure approach is designed to split the code
into two places and macromedia recommends the split. Because some
people were putting all content back to the J2EE layer for simplicity
in deployment, performance was dragging. This, as you well know, puts
extra burden on the CFMX application to host static content when that
is what the HTTP layer is supposed to be optimally designed for. That
and the needless extra communication involved with hosting static
content from the app server layer both will drain resources and
performance dramatically depending on usage.
So are you having a problem? Are you sure your web connector is
configured properly?
LinuxInductee Guest



Reply With Quote

