I agree with Wolf - to my knowledge the physical path setting does not do anything. Chris will correct me if I am wrong. In the early 4 beta's before they worked out the virtual mappings this parameter was used but I don't think it does anything anymore.

Wolf Koelling wrote:
Billy

We are using IIS and not Apache so I'm not sure whether it's down to that
but I can't see why you need to fill in that field in the first place. In
our setup all the csp gateway needs to know for an application is what cache
server to connect to. The web server needs a virtual directory /csp that
points to a physical directory which contains subdirectories for the
binaries and for the csp applications. It is in the properties of the
virtual directory where you link .csp and .cls extensions to the csp binary.
We have the csp binaries and java files on the web server, also all
application static files. In your live-shadow configuration all those files
need to be the same for both servers so there is no reason to keep them on
the cache servers themselves.

Wolf Koelling
Slaughter and May


"Billy Young" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]

Hallo all,

We have a customer who wants to implement the following hardware
configuration with Cach� 4.1.12 :

1. Live Server on IP Address xx.xx.xx.1
2. Shadow Server on IP Address xx.xx.xx.2

However, the servers are reached by the users using IP Address
xx.xx.xx.3, which maps to the live server xx.xx.xx.1 when that's up and
running, or xx.xx.xx.2 when they have to use the shadow server for some
reason.

We have a CSP application which is to run on these servers, and which is
accessed through a separate webserver using Apache.  At the moment, the
CSP Applications are accessed on the webserver via a mapped network
drive, so in the Web Gateway Management the Application Access has
something like "Web Server Physical Path = M:\myapp\" where M: is mapped
to cachesys\csp on the live server xx.xx.xx.1.

My problem is that it doesn't seem possible to map a network drive to IP
Address xx.xx.xx.3 on the webserver (Windows NT) as it's not a real
computer, so although we can set up Server Access for xx.xx.xx.3 in the
Gateway, the Application Access at the moment has to be either for
xx.xx.xx.1 or xx.xx.xx.2.

Is there an alternative syntax for the Web Server Physical Path entry in
the Gateway, so that we can link the application through xx.xx.xx.3 ?

Thank You
Billy






--
Bill McCormick
Web/Objects Support Manager
InterSystems Corporation
[EMAIL PROTECTED]




Reply via email to