Horst
ArgusMessenger is restricted to running on the same machine as the
database for the following reasons:
1. ArgusMessenger supports Archiving and Restoring which require the
Interbase program gbak. The program cannot be called using SQL, and must
be run on the same machine as the Interbase database server.
2. ArgusMessenger is meant to set up and run services which run in the
background. These services run on the machine on which they were
configured. Since the PKI store which stores your private key is only
created on the hard drive of the server machine, the service needs to be
configured on the same machine.
We will put a new command line argument in ArgusMessenger which will
allow database login to a remote host. This feature will not be turned
on by default.
Regards
Horst Herb wrote:
Most specialists in our Division seem now ready to go with Argus and I thought
I should join them
I installed Argus yesterday and ran into a "problem", which the help desk
could not solve yet but they will ring me back - maybe the people on the
mailing list are even quicker?
I run a dedicated Firebird SQL server on a headless machine. It is set up for
self-replication, automated backups, and has a replacement clone. So this is
where the database is going to reside, end of discussion.
However, Argus GUI insists on having the database on "localhost", and I
haven't been able to find the configuration option where to change it yet,
nor was the help desk able to help me yet
Anybody any ideas where Argus hides this configuration detail?
Horst
--
Andrew N. Shrosbree B.Sc, B.Ec
Technical Director
ArgusConnect Pty Ltd
http://www.argusconnect.com.au
Suite 4, Greenhill Centre, Mt Helen
Victoria, Australia
Tel: +61 (0)3 5335 2214
Mob: +61 (0)415 645 291
Skype: andrewshroz
_______________________________________________
Gpcg_talk mailing list
[email protected]
http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
