Both Marcel’s and Robert’s responses are helpful. This is an interim followup, won’t have access to the server again until Monday.
IT2BE:
Morley:
And we DID move ALL database files from Servoy Database directory and ALL the files from the Sybase_db directory. We also checked to make sure permissions are properly set.
This I don’t understand, moving db files is ok since they are cross platform but moving xp sybase (config) files and executables doesn’t make sense to me or do I misenterpret what you are doing here?
That’s exactly what we did, we didn’t consider the cross platform issues. We were overly focused on the absence of platform issues with Java and failed to consider the Sybase backend separately.
I’m not personally skilled in server issues and am therefore working with an IT consultant who is not himself overly familiar with Sybase issues. These are the resources we have available at hand.
IT2BE:
Morley:
But our tables are not in place (didn’t have this problem last fall). Opening our solution shows the opening screen but reports relationship failures throughout the opening script.
Is your db just not running? Or not available in Servoy? Or are the relations screwed up?
In case of the first or second what do your sybase.config and servoy.config files look like?
Yes, Sybase is up and running and a database called “seven_office” is running (because we manually created in Servoy Prefs/DB Servers). Going into Dataprovider definitions we can see two icons there only (don’t recall their names as I write) and zero tables.
ROCLASI:
Morley:
In attempting to get our solution and database into place we DID add the database in Servoy Prefs/DB Servers and we DID add it to the Sybase.config file. And we DID move ALL database files from Servoy Database directory and ALL the files from the Sybase_db directory. We also checked to make sure permissions are properly set
Why did you copy the sybase_db directory over?
Servoy installer already puts that on the server for you.
You only have to copy your database directory over.
This directory holds all Sybase databases.
Because the WinXP sybase_db directory contains a database and a text file by the name of “seven_office” and the sybase_db directory installed on the Xserve does not.
Way back at the beginning (last June) we were told we needed to create a separate database for our solution, which we did with Sybase Central.
I remain unclear how to rectify the Sybase issue – how to migrate the data structure and the data itself from the WinXP installation to the Xserve installation. This issue has not been resolved.
IT2BE:
Morley:
While I’m at it, a secondary question. We’re not clear how to quit Servoy Developer and leave Servoy Server running.
First of all running the server and developer at the same time is not advised. Any changes in the solution made by developer can only be seen by the server/client after a solution flush or a reset of the system (maybe that’s where your issues come from).
Second, if you do so, you can just close down developer and your server keeps on running. They are different applications. The only thing you have to think of is that develper doesn’t close your db’s.
Something else we missed entirely. Neither of us caught on to the concept of launching Servoy as a “Service” from Servoy’s docs. (Yes, I’m sure it’s there but not sufficiently prominent for either of us to catch it.)
I’ve noted Robert’s reposting of Marcel’s solution to running Servoy as a service on an Xserve. Will put his fix into place on Monday.
Sounds as if a tutorial on this subject would be a useful amplication of the Server documentation.