Service Virtualization

VSEName
Specifies the name of the VSE.

By default the vseName is called VSE.  If you have more than one VSE attached to the same Registry and the names are not unique, you can see where they each reside easily from the DevTest Registry Monitor on the Workstation.

But from the Portal Monitor even thought there are two VSEs, it is only showing one since they have the same name:

You would have to view Server Health to see that is more than one VSE.

This example is showing how to change each VSE to have a unique name.

One of the VSEs is on Windows and connecting to a Linux Registry.  I will be updating the VirtualServiceEnvironmentService.vmoptions on my Windows machine where my VSE is with the below values:

My other VSE is running on the same Linux machine as my Registry.   I will be updating the VirtualServiceEnvironmentService.vmoptions on my Linux machine where my VSE is with the below values:

At this point both of the VSEs will need to be restarted to pick up the new names.

Now from my Workstation the DevTest Registry Monitor shows the new unique vseName:

Now from the Portal Monitor we can see both VSEs running since they now have unique names:

 KB: TEC1913713

youtube video:  

https://www.youtube.com/watch?v=OY8EGYbQBiw