• Overview
  • What's new?
  • User Guide
  • exense: oryon
  • Getting started
  • Integration with step
This article references one of our previous releases, click here to go to our latest version instead.

Integration with step

To make the Oryon plugin usable from within step, add the following to the file step.properties on the step controller:

plugins.oryon.home=/path/to/oryon-x.y.z => used by the plugin to access the oryon libraries
plugins.oryon.errorhandler=../data/scripts/oryon_errorhandler.groovy => can be used to define a script that is executed in case of TECHNICAL_ERRORs during the keyword execution

… and to the AgentConf.js:

{ "gridHost": "", "registrationPeriod": 1000, "gridReadTimeout": 20000, "workingDir": "src/test/work", "tokenGroups": [ { "capacity": 10, "tokenConf": { "attributes": { "key": "val" }, "properties": { "plugins.oryon.home": "/path/to/oryon/oryon-x.y.z", "application.startcmd": "java.exe {oryon-agent} -jar myapp.jar" => the start command of the target application. IMPORTANT: do not forget the placeholder {oryon-agent} } } } ], "properties": { } }

Finally, you’ll have to create a Keyword to start an Oryon session, which requires that you have correctly set the application.startcmd and plugins.oryon.home properties inside the AgentConf.js file.

  • Overview
    • Overview
    • Oryon Agent
    • Oryon IDE
    • Integration with step
  • What's new?
    • Release Notes
  • User Guide
    • IDE Settings
    • Parameter input
    • Logging
    • Syrius Single Sign On
    • API documentation
    • Syrius Node Pruning
Step Logo
    • Overview
    • What's new?
    • User Guide
    • Overview
    • What's new?
    • User Guide