.... It says that in the Technical Article "Deploying ElevateDB
Applications" on the Elevate site.

Hi

I can't see how EDBMgr can be used to administer the server - there menu
entries and buttons for all sorts of stuff, but I can't see how to do that.

I'm sorting through deployment issues at present (and getting a little
confused) and I presume that there will be times that the server may
need to get shutdown e.g. new version of the server itself.  In our
scenario, the server computer is likely to be locked in a broom cupboard
somewhere and all access for the application will c/s.

If I can see how EDBMgr does it then perhaps I can write something to do
the same.

Cheers

Jeff

On 2/23/2015 8:48 PM, Jeff Cook wrote:
> I can't see how EDBMgr can be used to administer the server - there menu
> entries and buttons for all sorts of stuff, but I can't see how to do that.

I believe administer in this case refers to DB administration -
adding/changing databases, tables, users, triggers etc.

> I'm sorting through deployment issues at present (and getting a little
> confused) and I presume that there will be times that the server may
> need to get shutdown e.g. new version of the server itself.  In our

AFAIK this cannot be done thru EDBManager - i.e. if you could stop the
server then how would you restart a service again?

Couple of options here - remote into the server itself (i.e. RDP) or if
edb server is configured as windows service then those can easily be
managed remotely using windows tools (i.e. Service plugin for remote
computer for example).

Raul

Thanks for your response Raul.

I have just realised that that I posted in the wrong newsgroup.  I'll
repost in EDB NOT DBISAM!

The Subject line above appears in a Technical article on the elevate
website.

We have 40+ clients running our software and it would not be practical
to manually go into each client machine and replace the server.  Also
the client machine could be disconnected from the internet, in a
different timezone etc. and if we had a sales boom, then there might be
100 machines to log into.  I'm searching for a way to do this
automatically e.g. client machine checks our website for new version,
downloads it, shuts down the server, copies in the new and restarts.

Cheers

Jeff

On 25/02/2015 2:20 a.m., Raul wrote:
> On 2/23/2015 8:48 PM, Jeff Cook wrote:
>> I can't see how EDBMgr can be used to administer the server - there menu
>> entries and buttons for all sorts of stuff, but I can't see how to do
>> that.
>
> I believe administer in this case refers to DB administration -
> adding/changing databases, tables, users, triggers etc.
>
>> I'm sorting through deployment issues at present (and getting a little
>> confused) and I presume that there will be times that the server may
>> need to get shutdown e.g. new version of the server itself.  In our
>
> AFAIK this cannot be done thru EDBManager - i.e. if you could stop the
> server then how would you restart a service again?
>
> Couple of options here - remote into the server itself (i.e. RDP) or if
> edb server is configured as windows service then those can easily be
> managed remotely using windows tools (i.e. Service plugin for remote
> computer for example).
>
> Raul

On 2/24/2015 5:50 PM, Jeff Cook wrote:
> The Subject line above appears in a Technical article on the elevate
> website.

I read it - it's ambiguous in what it refers to as administration. You
can do everything in EDBManager that you needed dbisam server admin tool
before in DBISAM so in that sense the statement is true.

> We have 40+ clients running our software and it would not be practical
> to manually go into each client machine and replace the server.  Also
> the client machine could be disconnected from the internet, in a
> different timezone etc. and if we had a sales boom, then there might be
> 100 machines to log into.  I'm searching for a way to do this
> automatically e.g. client machine checks our website for new version,
> downloads it, shuts down the server, copies in the new and restarts.

The only way i can think of doing this automatically is to write a
little helper utility app or service that you install alongside
edbserver. All the utility app has to do is to is check for updated
file, download it, stop edbserver, replace exe and restart edbserver.

All very straightforward operations and quite easy to write. We have
dome something like this for our app auto-update and it works well.

Make the update check to be site specific (using url params or url
itself) and you can centrally control what and how you update client sites.


Raul