Differences

This shows you the differences between two versions of the page.

--- visionx:faq_tech [2022/08/08 09:33]
admin [Change E-Plug standard ports]
+++ visionx:faq_tech [2024/03/25 18:50] (current)
admin
@@ Line 7: / Line 7: @@
 ==== 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? ====
@@ Line 148: / Line 148: @@
 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)
+''EPlugPort (default: 1725)'', ''VisionXPort (default: 1726)''
-Simply add the system parameters to the [[#additional_jvm_start_parameters|start configuration of VisionX]]
+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.
+==== Different Windows file encodings ====
+Sometimes, you have the same Windows OS but different file encodings, e.g. cp1252 vs. UTF-8. This is not a VisionX problem, it's an OS setting. Some Windows installations have a new UTF-8 feature. You can see this option by going to Settings and then: All Settings -> Time & Language -> Language -> Administrative Language Settings
+Will look like:
+{{:visionx:utf8_windows.png?nolink&400|}}
+Simply unset UTF-8 or set cp1252 instead of UTF-8 as described [[:visionx:faq_tech/#additional_jvm_start_parameters|here]].
+==== Application directory ===
+If you want to know the directory in which an application is stored, simply press Shift + Alt (Shift + Option, MacOS) to show new icons besides the application. [[https://blog.sibvisions.com/2021/05/06/visionx-5-6-new-hidden-feature-for-developers/|Here]] are some details.