|
Hello-
We're launching our new production software to our editorial staff
on Tuesday and of course, I am the last person to find out exactly how the
programmers structured it, so I am stuck for a solution... The software
will be running on the same LVS-DR system that our website runs on, with
two RS's (apache 1.3.20, tomcat on linux-2.4.5). This has been working
beautifully when I don't screw it up, but now I have to configure this
system for the new software.
The software is session based, and my RS'es are both web and app
servers, so for my website, I don't want persistence (we serve a shedload
of images into our emails off this system and persistence would create
severe imbalance under these conditions, especially when our corporate
customers hit us from behind a masq'ed corp network) but for our software
we need persistence. I had originally setup the website and software as
namebased virtual hosts in apache, but that negates the ability to set one
as a persistent service on the director as both the website and the
software are on the same VIP address.
I think my choices are to either move my software to another IP
address to separately LB it and then start up separate apaches with
different bind addresses, or have everyone access the software on a
different port (81 for instance) and then LB on a port basis.
Is there a better, easier, obvious way of doing this without
jumping through major hoops? I doubt that I am the only one who would like
to have persistence enable for certain parts of my site (or certain
virtual domains served by the system)...
Thanks for the help,
Zack
|
