Page History

...

Assuming you have your VSC config file in ./vsc.cfg you can start the proxy manager using the command below. You can then use its GUI to activate the proxies individually or collectively. You do have to start the ones your script needs telemetry from before you launch the script engine.

lat-hobbit5:

^D                       (Exit your Python session and get back to the shell.)
xterm -title Proxies -n Proxies -e ${ONLINE_ROOT}/LICOS/tools/proxy/ProxyManager.py \
    --vscip   lat-elf1 \
    --config  vsc.cfg &

...

In the \[logging\] section you will normally run with logging disabled (lognbl = 0). If you set it to one then the logging files will be written to the logs directory.
*_IMPORTANT:_* _At present it seems that only one instance of the script engine at a time can run on the host machine with logging enabled, so do it only when you must, e.g., test script V&V._

One last pair of config filefiles: scriptOpts.cfg , which and your application config file. The scriptOpts file consists of sections that look like this:

[YOUR-SCRIPT'S-MAIN-CLASS-NAME]
intLimitChk=0
intLimitChkOnlyOnFail=0
askOnTestFail=0
askOnPhaseFail=0
pauseAfterPhase=0

Changing these settings goes beyond the scope of this page because they refer to the internal organization of your test application and its config file, both of which are topics you need to ask an Expert about (no, not Anne Expert of Brontosaurus Theory infamy).

At last you can launch the ScriptEngine:
lat-hobbit5:

python ${ONLINE_ROOT}/LICOS/start/startScriptEngine.py \
    --config      scriptEngine.cfg \
    --vscConfig   vsc.cfg \
    --scriptOpts  scriptOpts.cfg \
    --server      lat-elf1