Choose a name and a location for the export file. The name used for the export file automatically becomes the so-called "context" for the Servoy Application Server when installed on a application server, see About "context" for more info.
You can use the options described below, then click Next.
Include active solution and modules
Export the active solution and its modules. If unchecked, only the Servoy application server is exported.
Allow data model changes
If checked, it allows database structure in case the database structure on the server is different than the one in the export.
e.g. table/columns changes or missing sequences
It is also possible to specify the server names for which data model changes are allowed.
|Skip database view updates||If checked, it skips database view updates.|
Export based on DBI files only
Exports the database meta data information for the main solution and the modules (if needed) using only table definitions.
Export all tables from referenced servers
If checked, it will export all the tables for any server used in the solution.
If it is unchecked, only tables that are actually used in the solution will be exported.
|Allow SQL keywords|
It allows exporting tables which contain SQL keywords in table and column names.
e.g. table having a column named “title”
|Update sequences||If checked the sequences will be updated for the servers involved in the export, |
otherwise they will not be touched.
|Override sequence types|
The sequence types will be overridden for the exported servers.
Override default types
If checked, the default values will be overridden for the exported servers.
|Export metadata tables||Export all the metadata files in the workspace which are referenced by the solution.|
|Check metadata tables||Check whether the workspace metadata files are in sync with the database tables.|
If it fails, then it throws an exception with the suggestion to update the meta data for the tables first, and the export does not continue.
If it is left unchecked, the export will be done based on the existing workspace meta data files, without checking if they are in sync with the database tables or not.
If checked and no metadata file is found in the workspace, the export will not continue, but throw an exception suggesting to update the meta data for the tables first.
|Export solution sample data||If checked, data (from the current connection) for every table exported will be included. |
All rows or a limited number of rows can be chosen to be exported.
Export i18n data
Exports the i18n keys used in the solution
|Overwrite repository group security settings with import version||If checked, it overwrites the security settings for the groups which are exported and already present in the repository on the server.|
Exports the Servoy users specified in user and group security
Automatically upgrade repository if needed
In case the repository version on the server is lower than the one of the developer used to export the solution, it automatically upgrades the repository.
|Create Tomcat META-INF/context.xml||Tomcat specific option. Enable this option so that the options below can be enabled.|
|Set antiResourceLocking to true||Set this option to true if running Tomcat on Windows and if having problems undeploying the war file. This option allows Tomcat to workaround the file locking feature of the OS and execute the undeploy. This option will impact the startup time of the war.|
|Set clearReferencesStatic to true||Set this option to true if a war undeploy or stop operation causes a memory leak. This option sets static fields to null, thus allowing them to be garbage collected.|
|Set clearReferencesStopThreads to true||Use with care. Set this option to true only as a last resort. Please read https://tomcat.apache.org/tomcat-8.0-doc/config/context.html for more information.|
|Set clearReferencesStopTimerThreads to true||Set this option to true if after an undeploy or stop operation there are still Timer threads running.|
|Minimize JS and CSS||when set servoy will try to minimize the js of css files (when there are not already minimized so ending on .min.js) This is a much simpler minification then what a real minimizer does, so for component/service developers, if you have big support libs in your component or services packages use the minified version of that support lib. You can have reference the full version in the manifest and have the minified just besides it. Then in developer it will be easier to debug but at runtime the minified version will be taken.|
SocketFactory.tunnelConnectionModeon 'Network Settings' page in Servoy Admin is set to 'http&socket'. See About the servoy.properties file for more info.
.warfile will appear in the specified location.