I am getting ready to install my solution onto a network server. I will be using OS windows server 2003, Backend SQL 2000, and Sybase for repository Data (which will be switched to SQL 2000 enventually).
I have only accessed my solution via my local machine Via Developer and Client, (played around with server admin a while back).
I have a few questions regarding managing solutions:
If I have an active solution running and I want to access it via Developer, what types of changes can I make, and when will the client see the changes.
If I want to make more significant changes (create a new version), then make is active, when will the clients see the changes, if they are connected when the version changes, what do they see?
Regarding flushing the clients cache, when is this necessary? Can I flush all the clients cache from server Admin? Would I need to flush the server cache?
If I want to access the solution via developer, do I need to remote into the server and run developer, or is there a way to run it from my local machine?
I suppose I will want to be able to make some changes (layouts, etc…) to the active solution, and other times I will want to add logic, fields etc.
I am trying to get an idea of the best practices for managing my solution now that I will be setting it up on a server. I have see allot of issues on the forum regarding client connections, server conections etc.. I just want to make sure I will avoid problems that others have run into>
Don’t work with developer on an active running Servoy Server. There are a lot of topics here, handling this issue.
Just make the changes in your developer, export it and upload it to the server. No hassle, no flush, no nothing. Users have to close en open the client again, to see the changes.
I’m sure you’ll get some more technical responses but following is my experience after hosting several clients solutions over ast 6-8 months.
If I have an active solution running and I want to access it via Developer, what types of changes can I make, and when will the client see the changes.
I do not make any solution changes on Server Developer but use a seperate setup on my laptop to develop & test then Export to File and Update Solution onto Server. Do occasionaly access hidden developer forms on Server Developer to manipulate data.
If I want to make more significant changes (create a new version), then make is active, when will the clients see the changes, if they are connected when the version changes, what do they see?
Clients only see changes on re-start - this is good because it enables you to test latest version on the Server before telling Clients its available. If Clients are online I use the built in Server Message system to point them to an email detailing the changes.
Regarding flushing the clients cache, when is this necessary? Can I flush all the clients cache from server Admin? Would I need to flush the server cache?
Have never used this - and there is a warning that it will slow clients.
If I want to access the solution via developer, do I need to remote into the server and run developer, or is there a way to run it from my local machine?
Believe you can do it both ways - although I just use GotoMyPC so that can acess Server Developer from anywhere.
I suppose I will want to be able to make some changes (layouts, etc…) to the active solution, and other times I will want to add logic, fields etc.
I do all this from Developer on my laptop - only push out to Server after testing etc.
This was my first attempt to setup a Server and host solutions but Servoy has been completely stable all this year without any downtime other than for planned work.
I have been searching on the Forum for some answers/similar posts to the issues raised here but without success. I was wondering if someone could help answer my questions below or point me in the right direction to similar posts in the past. In particular I have questions regarding the posts by HJK and Graham.
HJK - Don’t work with developer on an active running Servoy Server. There are a lot of topics here, handling this issue.
Just make the changes in your developer, export it and upload it to the server. No hassle, no flush, no nothing. Users have to close en open the client again, to see the changes.
Is this just a problem when Servoy Server and Developer are running on the same box?
I’m inheriting a legacy system here and others access the data in other ways so I can’t totally change the backend database. The reason I have some problems with importing is that I find is that there are enough hassles doing a solution import that I would rather do changes (particularly small changes) directly in Developer. Import issues are things like Servoy objecting to column names, having to reestablish row identity columns when they are not defined by the database, etc.
Can you tell me why you shouldn’t work with developer on an active running Servoy Server? What about when you point Developer on one machine to use the same Servoy repository as Servoy Server?
In my case I have my main database as well as the Servoy repository on a SQL Server box in one location. I then have Servoy Server running on a separate box. Finally I run developer on a third computer with the solution pointing to the SQL Server repository. So I make changes to the solution remotely using developer and then flush the changes via the browser to the clients. So far I haven’t had any problems but these posts have me worried. Can you tell me more what the issues are?
Graham - Have never used this (flushing server cache) - and there is a warning that it will slow clients.
We don’t have a lot of clients and generally speaking I can always do it at off hours anyway when clients are logged out. The flushing seems to go smoothly but again I don’t know if I have just been lucky! Any advice or suggestions would be gratefully received.