Horst,

Most people prefer their software to be neatly packaged, easy to install and easy to support.

In order to make this possible, ArgusConnect has adopted a deployment architecture and procedure that minimises complexity. Having engaged with you in this tail-chasing exercise, can I simply reassure you that we will happily add a command-line directive to allow you to do all these things, and though it may be technically feasible to do what you ask, it is not something we would want any of our users to do if we hope to avoid being buried with support calls.

Regards, Andrew


Horst Herb wrote:
On Monday 21 August 2006 10:55, you wrote:
  
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.
    

gbak does not need to be run on the same machine as the Interbase server.
I quote form "man gbak":
---------------------------------------------------
 gbak is the tool for managing Firebird database backup and restore.

       In  backup mode source is an existing database path (may include server
       name) and target is backup file name.
---------------------------------------------------

No, you don't use SQL calls to activate it, but you can run gbak on any 
machine which has teh Interbase client libraries installed, and point it to 
the server.

IN any case, this has nothing at all to do with where I choose to run the 
Argus user interface and where I choose to run the 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.
    

All the more it makes sense to run it on a headless machine (as I am doing it) 
and allow the GUI tools to be run on another machine

If you just tell me how to set up and configure Argus without your GUI tools I 
am happy too.

What I got so far:
- Firebird (Interbase) running
- Argus.gdb installed and accessible with isql
- Java installed and working
- HeSA location keys installed (and imported into my local OpenSSL keystore)

so what's the next step if I cannot run your GUI tools (e.g. ArgusMessenger)?

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

Reply via email to