I’m developing a solution with Servoy Offline, which involves deploying a disabled version of Servoy developer to the users, so they can run server and client on the same box, without always having an internet connection.
Is there a way to prevent the deployed software from autoupdating when a new release of Servoy is available? I like to make sure my solution is stable on the new release of Servoy before recommending an update of customer installations.
Thanks
Hi Antonio,
Only Developer will check for new updates. Server and the clients will not.
Also why deploying a Servoy Server, database server and client to each user ?
Why not use the Servoy Runtime?
I’ve tried using Servoy runtime, but it is really only good for static solutions. If you need to issue updates, especially if this involves modifying the structure of the database/tables, then Runtime is not the way to go. Instead, Servoy has “Servoy Offline” which is Servoy Developer without the access to the Repository etc. It runs a server and client on the same machine, which my customers need as they are often not connected to the internet, and the data is never served anyway, it has to be stored locally, for security reasons. The side-effect is that it looks like a developer for the purposes of Servoy updates.
I’d value your thoughts on the best approach.
There are some other considerations with Runtime.
You can only connect to the one database - in my case I have 2 DBs one for user data and another for a catalogue. This way I can distribute update of the catalogue data without disturbing the userdata.
Here’s a summary from Jan Aleman
Can’t you just uncheck the box asking for updates? Or is that just beta updates? If memory serves I thought it was any update but perhaps it is beta updates… For sure though it doesn’t ‘auto-update’. I’ve never had it do that. You have to request it at the prompt.
You are right - my sloppy terminology. What I’d really like is that my offline clients don’t see the ‘Update’ dialog automatically. They should have to go request it.
The check box is for betas.
Hi Antonio,
Sounds to me you need to put in a feature request for this.
Done - Case 60698
antonio:
Here’s a summary from Jan Aleman
- Runtime
Plus:
- Solution and passwords are stored in single solution file
- To do new version all you need to distribute is that single file
- All tables in one database
Downsides:- only single user capable
- You have to roll your own SQL to perform table changes, you can use the raw sql plugin for this but always make sure to restart after any table changes
- Servoy Offline (Disabled Developer)
Plus:
-multi user capable up to 3 users (make sure to license)
-can connect to multiple database including remote databases
-double click app to start using out of the box
Downsides
-upgrade procedure
Wasn’t Servoy Offline Edition the one to be use in conjunction with Mobilink? Servoy site Offline Section (http://www.servoy.com/generic.jsp?mt=39 … omy_id=430) doesn’t mention this other option (if it’s a different option). Is there any documentation available on it?
Servoy Offline is a disabled Servoy developer, and optionally you can use Sybase Mobilink to synchronise data between any number of offline clients and a consolidated database on a server. It’s quite nice. Clients can run without any connection to the internet or a LAN. In my main solution, the clients’ user data is confidential to them and never leaves their machine - ie it never synchronises with my central server. However, I provide 3-monthly updates to reference tables as part of my solution. The tables differ for each state. I push all tables up to a server. Using Mobilink, clients download only the schedules they need for their state, then continue to work off line.
If required, Mobilink can also synchronise client data to the server.