Prev: XML
Next: OLE Drag & Drop - does it work with VO?
From: Nick Friend on 17 Feb 2010 13:33
I'm interested to see how others are managing this type of scenario
(or suggestions generally).

The particular case is this.... we have a construction management
software (DBF/CDX) which is typically installed in the clients main
office, and then with smaller installations in each building site.
We're currently doing the development work to implement Advantage
Database Server in our app to be able to use replication. The idea is
that each site will be constantly updating the central office database
and vice versa. We've run tests and it all works perfectly so far.

The problem I want to crack is this. I don't want to force clients to
establish static IPs for each site, I want our system to be as
transparent and simple for them to implement as possible. But for
replication to work our software needs to establish the current IP
address of each site every time the systems come up. We'll also need
to occasionally transmit additional data, such as when a new work
directory and database are created in the central office for a new
site for example.

So far, my thought is to use a single common email account that the
different locations can all send coded messages to... so on start up
the program at each site looks up it's current IP address, sends an
email with date and time stamp, and then queries the same account for
messages from the other sites to extract their IP addresses.

Has anyone dealt with this type of situation before, or hopefully got
a better suggestion of how to deal with this?

TIA

Nick
From: James Martin on 17 Feb 2010 14:42
Could you not set up a VPN between the locations? I have experience
with
OpenVPN, and with it you can have the same IP address every time you
connect. It is secure and uses compression for speed.

James

On Feb 17, 1:33 pm, Nick Friend <nicktek...(a)googlemail.com> wrote:
> I'm interested to see how others are managing this type of scenario
> (or suggestions generally).
>
> The particular case is this.... we have a construction management
> software (DBF/CDX) which is typically installed in the clients main
> office, and then with smaller installations in each building site.
> We're currently doing the development work to implement Advantage
> Database Server in our app to be able to use replication. The idea is
> that each site will be constantly updating the central office database
> and vice versa. We've run tests and it all works perfectly so far.
>
> The problem I want to crack is this. I don't want to force clients to
> establish static IPs for each site, I want our system to be as
> transparent and simple for them to implement as possible. But for
> replication to work our software needs to establish the current IP
> address of each site every time the systems come up. We'll also need
> to occasionally transmit additional data, such as when a new work
> directory and database are created in the central office for a new
> site for example.
>
> So far, my thought is to use a single common email account that the
> different locations can all send coded messages to... so on start up
> the program at each site looks up it's current IP address, sends an
> email with date and time stamp, and then queries the same account for
> messages from the other sites to extract their IP addresses.
>
> Has anyone dealt with this type of situation before, or hopefully got
> a better suggestion of how to deal with this?
>
> TIA
>
> Nick

From: John Martens on 17 Feb 2010 14:49
Why not use FTP to share the data ?

Op 17-2-2010 19:33, Nick Friend schreef:
> I'm interested to see how others are managing this type of scenario
> (or suggestions generally).
>
> The particular case is this.... we have a construction management
> software (DBF/CDX) which is typically installed in the clients main
> office, and then with smaller installations in each building site.
> We're currently doing the development work to implement Advantage
> Database Server in our app to be able to use replication. The idea is
> that each site will be constantly updating the central office database
> and vice versa. We've run tests and it all works perfectly so far.
>
> The problem I want to crack is this. I don't want to force clients to
> establish static IPs for each site, I want our system to be as
> transparent and simple for them to implement as possible. But for
> replication to work our software needs to establish the current IP
> address of each site every time the systems come up. We'll also need
> to occasionally transmit additional data, such as when a new work
> directory and database are created in the central office for a new
> site for example.
>
> So far, my thought is to use a single common email account that the
> different locations can all send coded messages to... so on start up
> the program at each site looks up it's current IP address, sends an
> email with date and time stamp, and then queries the same account for
> messages from the other sites to extract their IP addresses.
>
> Has anyone dealt with this type of situation before, or hopefully got
> a better suggestion of how to deal with this?
>
> TIA
>
> Nick
From: Nick Friend on 17 Feb 2010 15:06
Just to clarify, this is a commercial solution that could be
implemented in dozens or even hundreds of sites, so we want to do
something that doesn't require any major input either from us or the
client to make it work... ie. what I want is something that will run
out of the box effectively. Hence the idea of using an email account
for this, anyone can make an email account...

Nick
From: John Martens on 17 Feb 2010 15:23
Nick,

If you use an FTP account you could centralize for all your accounts
without having them to do anything. It can just be a fixed part of your
app to deal with the parameters.

John


Op 17-2-2010 21:06, Nick Friend schreef:
> Just to clarify, this is a commercial solution that could be
> implemented in dozens or even hundreds of sites, so we want to do
> something that doesn't require any major input either from us or the
> client to make it work... ie. what I want is something that will run
> out of the box effectively. Hence the idea of using an email account
> for this, anyone can make an email account...
>
> Nick
 |  Next  |  Last
Pages: 1 2 3 4
Prev: XML
Next: OLE Drag & Drop - does it work with VO?