worked):

Basics: 29 remote sites connected with a 512 kb line
1 "hub" site with the DB and Remedy server

Goal: Avoid downloading the Java client over the 512 kb line

Proposed course of action: Put a copy of the Java client files on each of
the remote sites file servers. The remote sites could then run the client
from the LAN, but connect via the 512 kb line to input/query/modify tickets.
Full Remedy functionality is necessary, so ARWeb is not an option. Also,
they don't want to have to deal with the "roll out" of setting up a full
Remedy client on each machine (lots of remote users, would like a central
file storage for ease of upgrade/implementation.

I am thinking that there has to be a way to connect the "remote" Java client
copy to the main Remedy server without setting up Remedy web servers in each
remote location (and not having to DL the 7 MB Java client at each
connection)

Has anyone successfully implemented this? What was involved?

Thanks in advance,
Brett S.
CNC Professional Services

---------------------------------------------------------------------------
To unsubscribe from this list, send mail to listserv@listserv.buffalo.edu
with a body of "signoff arslist". The subject line is ignored.