The Kinetic Jump site navigation header requires JavaScript to be enabled and the latest version of the Macromedia Flash Player. If you are you using a browser with JavaScript disabled please enable it now. Otherwise, please update your version of the free Flash Player by downloading here.

Welcome Guest Search | Active Topics | Log In | Register

Client-server update scenario Options
aminkov
#1 Posted : Tuesday, August 26, 2008 7:49:37 AM
Rank: Newbie
Groups: Member

Joined: 8/26/2008
Posts: 4
Hello, we are currently evaluating the product.  It looks very powerful and flexible but they are still a few gray areas for us.
Could you please suggest on how we should approach the update process if our typical customer looks like this:

Laptops A, B and C are on a LAN and have a Windows application installed that needs to be updated periodically. Laptop A is the "master" laptop and also has an instance of MSSQL installed. Laptops B and C ("client" laptops) are pointing to the database on the master laptop. Usual update patches can include application EXE or DLL update or SQL database update or both. How do we configure it so that the updates are downloaded only once (preferrably) and only run SQL update scripts on the master but distribute EXE / DLL updates to the client laptops B and C?
Also, how do we make sure that the database and application are in sync? For instance - the update was run on the master laptop but not on client laptops and the database is now newer than the application on the client expects, which could cause problems.
Any suggestions on how to accomodate this scenario?
Thank you in advance!
brianh
#2 Posted : Tuesday, August 26, 2008 9:04:17 AM
Rank: Administration
Groups: Member, Administration

Joined: 5/24/2007
Posts: 362
Location: Minnesota

Hello,

 

You can architect an update scheme for your scenario with AppLife Update.  Here's how:

 

Update packages created by AppLife Update consist of a packaged directory of files (x.x.x.x.zip) and an xml file that describes the updates available(director.xml).  When an update is published, these two files are added to the defined publish location, which is just a folder available on your network/internet.  Then, when clients check for updates, they retrieve the director.xml file which describes all of the available updates.  This information does not directly relate to your question, but understanding this concept does.

 

A good way to approach your scenario is to build two updates.  One for your master laptop and a separate update for a normal laptop. Use two separate AppLife Update projects. The output of the normal update project will become part of the Master update package.

 

Enable the Master Laptop to check for and retrieve updates from your public facing update location (most likely the internet).  This Master update will update the local install of your application, the SQL Database, and a local update folder. The Master update will include an update package and director.xml that only updates the client folder.  The local update folder on the Master Laptop can be shared with the other laptops on the LAN via a local IIS install, or just a plain old UNC file share. 

 

The other (non-master) laptops will be configured to check for updates from the master laptop's local update folder.  A new update will be available for the non-master laptop immediatly following a Master update.  As for when the clients should check for updates, it will depend on your application.

 

A variation could also be considered by looking at the Sql Server and the local update folder as a single "server application".  You build an update for these pieces and a have a small executable or service that performs this update.  Then all of the client applications (even the Master laptop) are configured to check for updates from the "server application" local update folder.

 

Hopefully this will get you going.  Let me know if you have more questions.

Brian Haas
Kinetic Jump Software
aminkov
#3 Posted : Tuesday, August 26, 2008 10:36:07 AM
Rank: Newbie
Groups: Member

Joined: 8/26/2008
Posts: 4
Thank you for your prompt reply. Both ways make perfect thanks. Thanks again!
Users browsing this topic
Guest
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.