[OPEN-ILS-GENERAL] Seperate Servers for OPAC and ILS?

[Wolf Halton]

We have done multi-server set-ups both the 2 front-ends (running different
versions of Evergreen) pointing to the same database, and also breaking the
front-end opac on one server with the web server, one server for reporter
and a couple other services and a third running the database.  Evergreen is
modular enough to handle it.  Simple but not always easy.  The
troubleshooting issues are more complicated when you are running on more
than one front-end as in the latter example.

-Wolf Halton (LYRASIS)

On Mon, Nov 28, 2011 at 5:27 PM, Ben Shum <bshum at biblio.org> wrote:

>  We've done this before where we have two different hostnames pointing at
> two different Evergreen servers, but both servers end up pointing at the
> same database backend.
>
> In a scenario like that, Server A could be "opac-only" where you tell
> users to use for opac stuff, and then Server B could be "staff-client-only"
> where you tell staff to use that server's address/hostname for that.  I'm
> not sure about locking down server A to prevent staff from logging into it
> though, since the staff client acts like a browser (runs on the same ports
> 80 and 443), you couldn't deny incoming requests from a client trying to
> talk to your public server side.  I suppose you could "trick" it with a
> fake server redirect that led nowhere or wasn't the same stamp as your
> actual staff client server; that way nobody would easily attach themselves
> with a staff client to the opac-only Server A.
>
> What are you trying to accomplish by having these services separated?
> Load concerns or worried about performance hits between sharing of
> OPAC/staff client functions?
>
> -- Ben
>
>
> On 11/28/2011 05:09 PM, Stephen Wills wrote:
>
> Hi Tom,
>
>  Evergreen lends itself well to being scaled to multi servers using "the
> Brick" technique.
>
>  I am not the expert in this deployment but we currently have a server
> that runs the OPAC and answers the staff client.  This server talks to a
> separate database server that handle the actual catalog, and database
> functions.
>
>  Many installations go even farther.   The needs of your library or
> consortium will dictate how much provisioning you will need to do.
>
>  In short, Evergreen is designed "out of the box" to be deploy on
> multiple servers.
>
>  Steve Wills
>
>  On Nov 28, 2011, at 4:50 PM, Thomas Misilo wrote:
>
>   Hello,****
> ** **
> I was wondering if it is possible to have separate servers for the OPAC
> and ILS with the default software? Or would I need to use another OPAC such
> as VuFind to accomplish this?****
> ** **
> Thank you,****
> ** **
> Tom****
>
>
>
> --
> Benjamin Shum
> Open Source Software Coordinator
> Bibliomation, Inc.
> 32 Crest Road
> Middlebury, CT 06762203-577-4070, ext. 113
>
>


-- 
This Apt Has Super Cow Powers - http://sourcefreedom.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://libmail.georgialibraries.org/pipermail/open-ils-general/attachments/20111129/b485ce86/attachment.htm>