Summary
In the "Configuring JVM options for SSL/TLS" topic it is suggested to edit the MTK launch script (runMTK.sh or runMTK.bat) to add custom Java runtime options. This seems risky (the script will be overwritten when MTK is upgraded) and unnecessary (you can add or override runtime options by setting JRE environment variables such as JAVA_TOOL_OPTIONS or JDK_JAVA_OPTIONS). Perhaps it's worth mentioning in the documentation as a better option. Related: https://enterprisedb.atlassian.net/browse/MTK-1519
Where did you see the problem?
https://github.com/EnterpriseDB/docs/blob/30274fd45f27884054a818cbd82bbab66017217a/product_docs/docs/migration_toolkit/55/configuring_ssl.mdx
Expected behavior
No response
Screenshots
No response
Browser / Platform
No response
Additional notes
No response
Summary
In the "Configuring JVM options for SSL/TLS" topic it is suggested to edit the MTK launch script (
runMTK.shorrunMTK.bat) to add custom Java runtime options. This seems risky (the script will be overwritten when MTK is upgraded) and unnecessary (you can add or override runtime options by setting JRE environment variables such asJAVA_TOOL_OPTIONSorJDK_JAVA_OPTIONS). Perhaps it's worth mentioning in the documentation as a better option. Related: https://enterprisedb.atlassian.net/browse/MTK-1519Where did you see the problem?
https://github.com/EnterpriseDB/docs/blob/30274fd45f27884054a818cbd82bbab66017217a/product_docs/docs/migration_toolkit/55/configuring_ssl.mdx
Expected behavior
No response
Screenshots
No response
Browser / Platform
No response
Additional notes
No response