# Launch a VSE Server as a Windows Service with a different local.properties (using .vmoptions)

Document ID : KB000048429
Show Technical Document Details

Question: How do you launch a VSE Server as a Windows Service with a different local.properties?

1. Create a new text file in LISA_HOME/bin called VirtualServiceEnvironmentService.vmoptions.
2. Edit the file, and add this line:
-DLISA_LOCAL_PROPERTIES=C:\path\to\vse.local.properties(tweak the path accordingly)
3. Restart the VSE service. It should now be using the local.properties that you specified.

You can do the same thing with any LISA executable in the bin directory. Just make an exename.vmoptions file and put the JVM options you want in the file (one option per line). The vmoptions files are used to pass additional parameters to a Java process in order to modify the default settings used for the JVM. These files can be used to customize the memory allocation settings for each of the LISA processes used in the server. Thesefiles must be located on the same folder as the actual executable scripts and must have the same name, with the exception of the extension ( .vmoptions).

These files are located at LISA_HOME\bin folder.

The contents can be like:
-Xms256m
-Xmx1024m
-Xss512k

Okay, this works for Internet based licenses, but I have file based licenses. How can this work for that?

We use the same vmoptions file. In the above example, it is used to point to a different license via a local.properties file. This works for an Internet based license, but not a file based license because by DEFAULT the lisalic.xml file is in LISA_HOME. There is a property, lisa.license, that can be changed to allow for multiple file based licenses in LISA_HOME. The lisa.license property contains the fully qualified path to the license file and defaults to the lisalic.xml in the LISA_HOME folder.

How can we use this to our advantage?