Trace:
Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
visionx:faq_tech [2022/01/10 10:03] admin |
visionx:faq_tech [2023/11/07 17:49] admin |
||
---|---|---|---|
Line 7: | Line 7: | ||
==== Which database & which platform are you using? ==== | ==== Which database & which platform are you using? ==== | ||
- | VisionX supports all major database vendors: Oracle, Postgres, MySql/MariaDB, MS Sql, DB2, Hana. We're using Java and support all Java application servers like: Tomcat, Wildfly, Glassfish, etc. You can deploy the created application with VisionX or manually, to the cloud, on premise, or as client/server desktop application. | + | VisionX supports all major database vendors: Oracle, Postgres, MySql/MariaDB, MS Sql, DB2, EDB and Hana. We're using Java and support all Java application servers like: Tomcat, Wildfly, Glassfish, etc. You can deploy the created application with VisionX or manually, to the cloud, on premise, or as client/server desktop application. |
==== Is VisionX on premise or a cloud service? ==== | ==== Is VisionX on premise or a cloud service? ==== | ||
Line 110: | Line 110: | ||
==== Column with same name created when making a subtable ==== | ==== Column with same name created when making a subtable ==== | ||
- | //When I click “Make Subtable” after adding a field on the “Edit table” screen, a mandatory column is added that has the same name as the subtable. This is always confusing to me, as I have almost never had a situation where I would have wanted to create a column that has the same name as the table. I am always unsure if best practice here would be to replace the table name with the intended first column name, or if the column with the table name has to be kept in place for another reason (especially since it is mandatory). Can it just be replaced? | + | //**When I click “Make Subtable” after adding a field on the “Edit table” screen, a mandatory column is added that has the same name as the subtable. This is always confusing to me, as I have almost never had a situation where I would have wanted to create a column that has the same name as the table. I am always unsure if best practice here would be to replace the table name with the intended first column name, or if the column with the table name has to be kept in place for another reason (especially since it is mandatory). Can it just be replaced? |
\\ \\ | \\ \\ | ||
- | Also, when I click the “Make Subtable” button in the “New Screen” wizard, the ID column is not shown. But when I edit an existing table, add a new field and click “Make Subtable” the ID column is shown. Is that intentional? // | + | Also, when I click the “Make Subtable” button in the “New Screen” wizard, the ID column is not shown. But when I edit an existing table, add a new field and click “Make Subtable” the ID column is shown. Is that intentional?** // |
\\ \\ | \\ \\ | ||
This is nearby best practice, the only downside is, that we do not know the plural or singular of the given word, to have it perfect. | This is nearby best practice, the only downside is, that we do not know the plural or singular of the given word, to have it perfect. | ||
Line 143: | Line 143: | ||
A table should have a name that describes the data it stores. | A table should have a name that describes the data it stores. | ||
Normally this table should have a identifier/name column whose name describes which kind of data you get (so this should be the singular of table name), and whose value represents the whole row, to be able to use it as a combobox. | Normally this table should have a identifier/name column whose name describes which kind of data you get (so this should be the singular of table name), and whose value represents the whole row, to be able to use it as a combobox. | ||
+ | |||
+ | ==== Change E-Plug standard ports ==== | ||
+ | |||
+ | The standard ports for E-Plug communication are 1725 (E-Plug port in Eclipse for VisionX to E-Plug) and 1726 (Port in VisionX for E-Plug to VisionX). If you have problems e.g. ports are already in use, simply change the ports with following system parameters: | ||
+ | |||
+ | ''EPlugPort (default: 1725)'', ''VisionXPort (default: 1726)'' | ||
+ | |||
+ | Simply add the system parameters to the [[#additional_jvm_start_parameters|start configuration of VisionX]]. | ||
+ | |||
+ | ==== VCS folders ==== | ||
+ | |||
+ | Which folders should be added to VSC like git or svn? | ||
+ | |||
+ | All folders and files in your application directory, but not: | ||
+ | |||
+ | <code> | ||
+ | config_new.xml (if available) | ||
+ | build/classes | ||
+ | src.client.backup | ||
+ | src.server.backup | ||
+ | work/classes | ||
+ | </code> | ||
+ | |||
+ | ==== My WebContent/ui will be overwritten automatically ==== | ||
+ | |||
+ | The directory contains the react UI and if you update VisionX, the latest version will be put into your application. Yes, your ''WebContent/ui'' folder will be updated automatically. If you don't want that, simply create a file with name ''.custom'' in your '''WebContent/ui'' folder. But be careful because if you have such file, VisionX won't update to the latest version. So it's in your hands and if you have an incompatible version, you have to update on your own or remove the ''.custom'' file. | ||
+ | |||
+ | |||
+ | ==== How to update react UI to latest version? ==== | ||
+ | |||
+ | The latest version can be found [[https://github.com/sibvisions/reactUI/releases|here]]. Download the zip, unzip the content into your VisionX installation: ''<VisionX>/rad/apps/visionx/resources/application/WebContent/ui'' directory. VisionX will update all your applications automatically after next VisionX restart or next application reload. | ||
+ | |||
+ | It's also possible to update only single applications. To do this, copy the content into your application' ''WebContent/ui'' folder. But be careful because VisionX will automatically update to its own version if you don't create a ''.custom'' file. | ||
+ | |||
+ | If you use a react UI from the github repo, we don't guarantee compatibility with VisionX because the UI depends on the server implementation. Problems with custom or manually updated react UI versions are not included in standard product support. | ||
+ | |||
+ | ==== Update export doesn't contain custom folders ===== | ||
+ | |||
+ | The update export doesn't contain custom files or folders. We automatically include following files and folders of WebContent directory: | ||
+ | |||
+ | <code bash> | ||
+ | *.css | ||
+ | *.json | ||
+ | *.jpg | ||
+ | *.png | ||
+ | *.gif | ||
+ | images/** | ||
+ | scripts/** | ||
+ | content/** | ||
+ | data/** | ||
+ | js/** | ||
+ | css/** | ||
+ | </code> | ||
+ | |||
+ | If you want support for your custom folders, you have to change the following file: | ||
+ | |||
+ | ''<VisionX>/rad/apps/visionx/resources/ant/export.xml'' | ||
+ | |||
+ | and search for: | ||
+ | |||
+ | ''<target name="update"'' | ||
+ | |||
+ | There are different include definitions like: | ||
+ | |||
+ | ''<include name="WebContent/css/**"/>'' | ||
+ | |||
+ | Simply add your own includes and the update export will contain your custom files and directories as well. |