That would be very strange if it's true because they have an entry in the
config file for both the LOCAL and the REMOTE directories.
I'd be very appreciative on anything you dig up. :)
-----Original Message-----
From: Mike Moulton [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 28, 2001 1:40 PM
To: Fusebox
Subject: Re: Distributed Coldfusion!
I am not so sure it is a bug...
I remember reading somewhere a while back that the directory structure for
the web server root had to be the same when using your particular setup. I
am trying to locate the docs where I read it and will post if I find it.
Mike
----- Original Message -----
From: "Stacy Young" <[EMAIL PROTECTED]>
To: "Fusebox" <[EMAIL PROTECTED]>
Sent: Monday, May 28, 2001 1:52 PM
Subject: HELP: Distributed Coldfusion!
> Hi All!
>
> I'm desperate here. Been trying to dig up an answer everywhere concerning
a
> strange bug (maybe) with our CF server setup in a distributed manner.
> (Distributed meaning CF server resides on a separate machine than the web
> server)
>
> CF Server: 4.5.1 SP2 on NT
> Web Server: Apache on NT
>
> If you're familiar with the requirements for setting this up you know
> there's a config file on the web server telling the CF Module for Apache
> what the local web root is and the remote (CF server) document root is on
> the CF machine. Well our setup works as is. If the Apache server gets a
call
> for a CFM template it calls out to the CF server on the other machine. BUT
> it only works if the directory structure on the CF server is identical to
> the Apache web server (for document root)!
>
> Example A: This works
> Apache document root: d:\wwwroot
> CF server document root: d:\wwwroot
>
> Example B: This does NOT work
> Apache document root: d:\wwwroot
> CF server document root: d:\documentroot
>
> On each example the changes to the INI config file for Apache were made
> accordingly and all services restarted.
>
> Anyone?
>
> --------------------------------------------------------------------------
--
> ----------
>
> Here's my INI file on the web server:
>
> ; Use this to turn on/off the remoting capability.
> ;
> ; Valid values: Yes, No.
> ;
> REMOTING = "YES"
>
>
> ; Use this to specify the IP address of the remote computer running
> ; the CF Application Server.
> ;
> ; Valid values: a valid IP address, eg: 139.56.205.102.
> ;
> IP = "172.16.61.20"
>
>
> ; Use this to specify the port on that computer on which the remote
> ; CF Network Listener Module is listening.
> ;
> ; Valid values: a valid port number (integer).
> ;
> PORT = "6969"
>
> ; Use this to specify the document root of the local web server
> ; Filenames with this path prefix will be translated in to paths
> ; on the remote system using REMOTEPATH
> ;
> ; Valid values: a pathname. eg: /usr/local/apache/htdocs
> ;
> LOCALPATH = "e:\Development_Sites\CF_FirePay_Reports [DEV1]"
>
> ; Use this to specify the document root of the remote ColdFusion server
> ; This path prefix will be substituted for LOCALPATH in filenames
> ; before they are passed on to the ColdFusion Net Listener
> ;
> ; Valid values: a pathname. eg: c:\Inetpub\WWWRoot
> ;
> REMOTEPATH = "e:\Development_Sites\CF_FirePay_Reports [DEV1]"
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
