How to configure a custom JVM path in the .ini file (semarchy-xdi-designer-windows.ini, for example under Windows OS) to specify the JVM to be used to start the Designer?
Best Answer
C
Cécile FRANCHINI
said
about 1 year ago
xDI documentation is now detailing the different ways to choose the JVM xDI Designer is using - please refer to Choosing your Java instance
We suggest that you make first a backup of the file, as it is very sensible and easily "breakable" (because of extra spaces or line breaks). If you do not have any backup, but you need to recover a functional version of this file, you can still find the original file in the zip archive of the designer.
The JVM path can be specified in the .ini configuration file (which is located in the Designer's directory), using the following argument (for example) :
-vm
C:\Program Files\Java\jdk-11.0.16.1\bin
Important:
It must be added at the beginning of the file, otherwise it will not work
The line break after -vm is also necessary, without any space character
C
Cécile FRANCHINI
said
about 1 year ago
Answer
xDI documentation is now detailing the different ways to choose the JVM xDI Designer is using - please refer to Choosing your Java instance
Xavier Meunier
How to configure a custom JVM path in the .ini file (semarchy-xdi-designer-windows.ini, for example under Windows OS) to specify the JVM to be used to start the Designer?
xDI documentation is now detailing the different ways to choose the JVM xDI Designer is using - please refer to Choosing your Java instance
- Oldest First
- Popular
- Newest First
Sorted by Oldest FirstXavier Meunier
We suggest that you make first a backup of the file, as it is very sensible and easily "breakable" (because of extra spaces or line breaks).
If you do not have any backup, but you need to recover a functional version of this file, you can still find the original file in the zip archive of the designer.
The JVM path can be specified in the .ini configuration file (which is located in the Designer's directory), using the following argument (for example) :
Important:
Cécile FRANCHINI
xDI documentation is now detailing the different ways to choose the JVM xDI Designer is using - please refer to Choosing your Java instance
-
File external resolver with encrypted value
-
Timeout on Mapping/Webservice call
-
UNIQUE TEMP TABLE NAMES
-
Previous step name from a sub-process of execute delivery
-
Dropping multiple tables at once in XDI
-
Freeze Designer and corrupted workspace
-
FileWait/Move/Copy: FileInclude with space
-
Loop excel files
-
Change SVN user in the Designer
See all 64 topics