Hi,

In LRE 2023 R1 / 24.1, below options are currently un-available for VTS (Virtual Table Service) configuration. It would be helpful to have them considered as part of upcoming patches.

1. VTS paths should be able to be navigate correctly if configured using LRE Server's IIS URL Rewrite. At the moment, VTS is accessible using path "localhost:{VTS_Port}", "hostname/IP:{VTS_Path}", however if needed it should be able to configured using "LRE_Path/vts". Common path like /vts seems to be missing currently, as various requests redirects differently using /data, /engine.io, /css etc. This makes it challenging to implement vts using URL rewrite.

As per inputs received from MF support, "The URL rewrite may change the request or body structure of the VTS and cause it to not work properly. We suggest finding a dedicated server for VTS. Also, please note that VTS may consume many computer resources when you have huge amounts of data, so it may impact your LRE server."
However, if usage is limited then we should be able to set-up on same server, instead of having dedicated server just for the same.

2. For authentication, LDAP based authentication is not supported. This should be considered.

3. For VTS connection function lrvtc_connect_ex used for authentication type as Basic, NTLM, there is no option/argument to specify Keep Alive option like lrvtc_connect function used with VTS authentication as None. This should be considered even for lrvtc_connect_ex.