Open topic with navigation
The Director enables the integrator to create, configure, launch and monitor simulators.
A simulator file contains the description of simulation applications distributed over a network of computers.
The following properties are configurable in a simulator:
The Director has the following interface:
The Director can discover computers present on the selected network. This can be useful to verify whether the service is running on the expected machines.
To launch a simulator, select its name in the list and press Launch Simulator.
The director can also stop the running applications using the Force Stop button: a soft close will be sent to the running applications and a hard kill will be applied if they are not responding after that.
The launch function can also be called in the command line interface so that deployed turn key simulators used by operators will not have to go through the Director user interface to start their simulation.
When using the launch command line, the data store is automatically deduced relatively to the simulator file.
|Launching a simulator from the command line or a shortcut|
VortexDirector.exe --launch mydatastorepath\Simulators\mysimulatorfile.simulator
The Director window can be minimized and will continue to monitor the simulator.
In order to properly quit the Director, select File>Quit' must be used.
If the simulator is still running, you will be asked whether all applications must be force stopped.
Once the simulator has started, the usual simulation windows and user interface will appear either on the local or remote machines.
Monitoring of the remote applications can be performed using the Applications tab.
The screenshot below shows the monitoring panel opened using the Director tray icon after locally launching Vortex Studio Player.
It reports the following information that might help when troubleshooting the simulator:
When one simulation application stops unexpectedly, the Director reports it with a warning icon.
Users can locally open the log of the remote application on their workstation to investigate the cause of the issue.
All simulator files created and modified by the Director are stored under the data store path.
The default path is
User Document\CM Labs\Simulator on the machine starting the Director.
Each simulator has its own file. They can be manipulated with the file explorer and will be detected and monitored by the Director.
The data store path can be globally modified in the Director interface under Tools>Settings.