Tech Tips: Creating and Configuring Multiple Simulators on the Same Linux Machine

Document created by MarcyNunns Employee on Oct 17, 2016Last modified by MarcyNunns Employee on Jul 5, 2017
Version 3Show Document
  • View in full screen mode

This example is on Linux.

 

Copy SimulatorService to SimulatorService2
Copy SimulatorService to SimulatorService3
Copy SimulatorService to SimulatorService4

 

You will then create new vmoptions files for SimulatorService2, SimulatorService3 and SimulatorService4 and put the properties below in the file.

 

See these examples:

 

SimulatorService2.vmoptions file

 

-Dlisa.simulatorName=Sim2 (Or a name you would like, be unique)
-Dlisa.net.1.port=20142 (Whatever port you need to use for this new Simulator, needs to be unique)
-DLISA_LOG=sim2.log (correspond this to the simulatorName)


SimulatorService3.vmoptions file

 

-Dlisa.simulatorName=Sim3 (Or a name you would like, be unique)
-Dlisa.net.1.port=20143 (Whatever port you need to use for this new Simulator, needs to be unique)
-DLISA_LOG=sim3.log (correspond this to the simulatorName)


SimulatorService4.vmoptions file

 

-Dlisa.simulatorName=Sim4 (Or a name you would like, be unique)
-Dlisa.net.1.port=20144 (Whatever port you need to use for this new Simulator, needs to be unique)
-DLISA_LOG=sim4.log (correspond this to the simulatorName)


Stop and start the DevTest Components to pick up the new Simulators.


Note:  If putting Simulators on different machines and going to the same Registry, use the same type of method as above for the Simulator Name.  Even though on different machines, if going to the same Registry, the names need to be unique. You would not have to specify different ports or log files if only one Simulator on a machine.

3 people found this helpful

Attachments

    Outcomes