Each instance of VSE should have some specific port ranges identified. User should get an error message if they are using a port outside the pre-defined range.
Maybe this question should be transferred to an idea.
It would be a very usefull option concerning ports management
As Davy says - this is an "idea" - otherwise a product enhancement request. If you raise this as an "idea" then it will reach the DevTest product management team, who will be able to assess whether this functionality should be included in the DevTest product.
I see the below properties in lisa.properties which can define the dynamic range of ports.lisa.vseasy.http.min.dynamic.port=8000lisa.vseasy.http.max.dynamic.port=65535
These properties control the dynamic assignment of ports when using auto configuration with the HTTP protocol in VSEasy. The rules for these properties are as follows:- If max <= min, then both get reverted to the defaults (65535 and 8000 respectively)- If max > 65535, max is set to 65535- If min < 1024, min is set to 1024
If you want to configure specific range for different VSE's then you can use local.properties and configure the above properties.
Thank you for your answer although the 2 properties are a definition for the overall port range (min and max) to be used by the VSE's.
If I would have 3 VSE's (VSE_X, VSE_Y and VSE_Z), it is not yet clear to me how to exactly define these properties per specific VSE.
If that would be possible, it would already be a huge step forward.
You can override default settings by adding the properties and their new settings to the vmoptions file for the respective VSE binaries (Example port range 11001 - 11099):
Depending on which binary you will start it is either VirtualServiceEnvironment.vmoptions or VirtualServiceEnvironmentService.vmoptions.
Aaah makes sense rather then local.properties as suggested before :-)
Thank you Ulrich!
Tested the below properties in 9.0 and 9.5.1 and both worked as expected but not in10.0 and10.1.
Support has patches for 10.1 and 10.1 in DE287721.
If you are using 3 VSE's on 3 different machines then you can define the properties in local.properties.
If you are using only one machine then, I would recommend what Ulrich was saying. You can still define in local.properties and refer the local.propeties path in VSE vmoptions file.
Retrieving data ...