BillB:
I’m new to Servoy and would like a bit of help understanding the deployment of the product to the end user.
Hello Bill Belanger, it’s nice to hear you’re working with Servoy.
I’m currently using Filemaker Server on a 2003 machine so that’s where my “head is”. When I develop a new solution, I just put it into the Filemaker server folder and it is served up to the clients.
Uploading a solution to the client’s server is just as simple with Servoy. You export the solution you’re releasing from your development environment, resulting in yoursolutionname.servoy file, use the browser-based Admin UI and upload/import it on the client’s server. And tables, fields, relationships, value lists, etc. that you’ve created using Servoy Developer will be automatically created on the client’s server, regardless of whether the back end they are using is the same as yours.
The part you left out
is what’s entailed in updating FMP solutions. With Servoy, generally speakig you only need repeat the process you used to upload the solution the first time. Changes to schema will be made automatically when the new version is imported. Click the button to activate the new version and it is instantly deployed. Click the button to roll back the version if need be, it is rolled back. Instances where manipulating the actual data would be very seldom, and there is no need to import data from one db to another if you’ve made schema changes. I think you’ll like that aspect of Servoy vs. FMP.
Here’s what I think I understand about Servoy. I might be way off in left field here, so please bear with me. The database is an SQL database and we are offered Sybase for free as part of the Servoy package.
Yes, and unless you’re already conversant with another SQL RDBMS and alredy have it installed and running on your local setup, it’s easiest to simply use the default ASA database for development (Adaptive Server Anywhere, from http://www.ianywhere.com, a subsidiary of Sybase). If your clients do not already have a database server running some other db that they prefer, the client license for ASA is included in the cost of the client license for Servoy, so long as only Servoy is used to connect to the database.
The database contains client tables as well as a table for us that is referred to as a repository and the repository holds our user interface.
The repository holds the entire Servoy solution: interface, value lists, unstored calcs, methods, UI and so on.
After I build that interface with developer, I need to somehow install Sybase along with all the tables and repository on the client’s server for them to use on their network.
On a server you install Servoy Developer, which also installs Servoy Server (app server) and ASA.
Then you launch the Servoy Developer application which will set up the repository connection for you, and you need to add db’s (just the db, not the tables/columns etc) and the named connections (same name is important only for the connection, not for the db) using Servoy Dev.
Next, you set things up so that Servoy Server and the database are running as a background service. (Instructions are in the server admin guide, look for the downloadable pdf’s on servoy’s main site.) Then you use a web browser (locally or remotely) to import a solution to the server. During the import Servoy will create the schema automatically.
I see that Servoy Application Server is running as a service on my server, so I’m guessing that is the interface for the clients to access their data and the solution (forms etc).
End-users will access the solution for the first time via a browser link. For Smart Client deployment, the app is downloaded to their webstart cache, or to their desktop, depending on what settings you have made. When you update the server, or add a new plug-in to the server, or update or roll back a solution, those changes will automatically be broadcast to users (even mid-session). For Web Client deployment, Servoy Server, with a simple click of your mouse, will also serve the application for use in a web browser. Web Client users have a real session on the server and data changes will be broadcast to them same as to Smart Client users.
So it’s actually Smart or Web Client that the clients use “to access their data and the solution”; Servoy Server, well, serves it. ![Smile :-)]()
Would I download a complete install package at my customer’s office and then insert some license keys?
You would download the install package, launch the Developer app to set up repository and specify your named connections, quit Developer, get the database and the Servoy server running as services, and then use a browser to the admin page in order to enter license key(s) for the clients. That’s an abbreviated explanation, to be sure, but I’ve done it successfully on a Linux server at a client’s on my first try – it’s pretty simple.
Thanks for any clarification.
you’re welcome. Marcel’s recommendation to read the docs is a good one, as you move forward in your process. But I hope this overview helps get you started,
kazar