Post-installation modifications may be required, particularly the database connection properties for installations that used the Standard PostgreSQL Server or an existing database.
Also, instructions are provided below for increasing the amount of memory allocated to Servoy, which can enhance overall performance.
Users can access the servoy.properties file found in the ../application_server/ folder (found in the root installation folder) to modify database connection settings.
Servoy also provides additional database connection configuration via the Resources Project while working on a solution. For details see Working with Database Servers.
The Servoy Repository, a set of tables in the database underlying the nameserver connection 'repository_server' is required to run Servoy. The repository is installed if you choose the bundled PostgreSQL option, but it will need to be manually installed if you choose the full-featured PostgreSQL installation or if you choose to connect to an existing database.
This is achieved via the command line process that can also used to upgrade the repository:
Macintosh/Linux/Unix:
./servoy_server.sh -upgradeRepository
Windows
servoy_server.bat -upgradeRepository
Executing the above command starts the Servoy Application Server and will create or upgrade the table structure required for the Servoy Repository to the version that the Servoy Application Server requires.
The Servoy Repository, a set of tables in the database underlying the nameserver connection repository_server, is required to run Servoy. The repository is installed if you choose the bundled PostgreSQL option, but it will need to be manually installed if you choose the full-featured PostgreSQL installation or if you choose to connect to an existing database.
This is achieved via the command line process that can also used to upgrade the repository:
Windows
servoy_server.bat -upgradeRepository
Macintosh/Linux/Unix:
./servoy_server.sh -upgradeRepository
Executing the above command starts the Servoy Application Server and will create or upgrade the table structure required for the Servoy Repository to the version that the Servoy Application Server requires.
The startup configuration file can be modified to increase the memory allocated to Servoy, which can improve overall performance.
Servoy Developer uses a browser component in several locations, like the Developer Start Page and the updated Form Editor for Servoy Mobile in Servoy 7.4.
By default the browser component used is the default browser of the operating system, so Internet Explorer on Windows or Safari on OSX.
In case of issues with the default browser (especially with the Form Editor), it is possible to install a FireFox based browser component called XulRunner into Servoy Developer, which will then be used instead of the default browser.
The XulRunner browser is available as plugin and can be installed using the following steps:
After the plugin is installed and before Servoy Developer is restarted the servoy.ini file in the {servoyInstall}/developer directory needs to be updated. Add the following line to the end of this file:
-Dorg.eclipse.swt.browser.DefaultType=mozilla
After restart of Servoy Developer the XulRunner browser component will be used as browser component inside Servoy Developer
If running Servoy Developer on OSX and there is a need to run Java 7 (for example for JavaFX integration ), some extra steps are required, as due to a bug in Eclipse (on which Servoy Developer is based), the process of running Servoy Developer on Java 7 is not as straight forward.
To setup Servoy Developer on OSX to work with Java 7 (assuming Java 7 is already installed) the following steps need to be performed:
In this same directory (.../developer/servoy.app/Contents/MacOS/) create a script called servoy.sh, which contains the following text:
#\!/bin/sh \# export JAVA_HOME=/Library/Java/JavaVirtualMachines/1.7.0.jdk/Contents/Home LAUNCHER_JAR=../../../plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar LAUNCHER_LIB=../../../plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.1.101.v20120109-1504 java \ \-showversion \ \-XX:MaxPermSize=256m \ \-Xms40m \ \-Xmx512m \ \-Xdock:icon=../Resources/servoy.icns \ \-XX:+UseParallelGC \ \-XstartOnFirstThread \ \-Dorg.eclipse.swt.internal.carbon.smallFonts \ \-Dnativeswing.interface.inprocess.useExternalSWTDisplay=true \ \-Dnativeswing.dependencies.checkVersions=false \ \-Dsun.awt.disableMixing=true \ \-Dosgi.requiredJavaVersion=1.6 \ \-jar $LAUNCHER_JAR \ \--launcher.library $LAUNCHER_LIB
note: make sure the script can be executed (maybe execute a 'chmod a+x servoy.sh', without the quotes)
To doublecheck that Servoy Developer actually runs with 1.7, see Servoy Developer > About Servoy Developer > Installation Details > Configuration java.runtime.version for instance)
NOTE: the four steps above correspond to advice from https://www.servoy.com/forum/viewtopic.php?f=5&t=19253#p103941