<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Getting started on exense: oryon</title>
    <link>https://oryon.exense.ch/knowledgebase/2.10/getting-started/</link>
    <description>Recent content in Getting started on exense: oryon</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Sat, 01 Jan 2000 00:00:00 +0000</lastBuildDate><atom:link href="https://oryon.exense.ch/knowledgebase/2.10/getting-started/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Overview</title>
      <link>https://oryon.exense.ch/knowledgebase/2.10/getting-started/documentation/</link>
      <pubDate>Sat, 01 Jan 2000 00:00:00 +0000</pubDate>
      
      <guid>https://oryon.exense.ch/knowledgebase/2.10/getting-started/documentation/</guid>
      <description>What is Oryon? Oryon is an automation tool for Java UI applications (typically fat clients) which allows users to easily record and replay interaction scenarios. During recording, scripts are generated which serve as a blueprint for subsequent (automated, simulated) interactions.
Advanced users can leverage the groovy language to adapt the resulting scripts as needed, tailoring them exactly to their needs.
Used in combination with step, Oryon can be employed in massively concurrent simulations, potentially involving thousands of simulated clients, and can benefit from the wide range of features provided by step itself (centralized results, collaborative web app, natural language bindings, etc).</description>
    </item>
    
    <item>
      <title>Oryon Agent</title>
      <link>https://oryon.exense.ch/knowledgebase/2.10/getting-started/agent/</link>
      <pubDate>Sat, 01 Jan 2000 00:00:00 +0000</pubDate>
      
      <guid>https://oryon.exense.ch/knowledgebase/2.10/getting-started/agent/</guid>
      <description>The Oryon agent is the component which allows to interact with a Java GUI application, i.e. to retrieve its UI state and to control it.
The agent currently includes modules supporting the following Java UI technologies:
Swing: generic module for applications using the Java Swing framework. SyriusSwing: custom module, specifically for the Swing version of Adcubum Syrius. SyriusFX: custom module, specifically for the JavaFX version of Adcubum Syrius. Installation and configuration The first and most important step to control Java GUI applications using Oryon is to configure the target application in a way which will run the Oryon agent alongside it (or rather, technically: inside it, as part of the same Java process).</description>
    </item>
    
    <item>
      <title>Oryon IDE</title>
      <link>https://oryon.exense.ch/knowledgebase/2.10/getting-started/ide/</link>
      <pubDate>Sat, 01 Jan 2000 00:00:00 +0000</pubDate>
      
      <guid>https://oryon.exense.ch/knowledgebase/2.10/getting-started/ide/</guid>
      <description>The Oryon IDE is a full blown groovy editor with additional functionality tailored specifically for Oryon such as:
an object tree representing the current state of the Java application currently connected to (on the left side) a central code editor view, with a tabbed interface allowing to edit multiple scripts at once a console displaying the output script executions at the bottom step-compatible input and output controls at the top and bottom Once a target application is running with the Oryon agent, you can start the IDE using the script startOryonIDE.</description>
    </item>
    
    <item>
      <title>Integration with step</title>
      <link>https://oryon.exense.ch/knowledgebase/2.10/getting-started/step/</link>
      <pubDate>Sat, 01 Jan 2000 00:00:00 +0000</pubDate>
      
      <guid>https://oryon.exense.ch/knowledgebase/2.10/getting-started/step/</guid>
      <description>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 =&amp;gt; used by the plugin to access the oryon libraries plugins.oryon.errorhandler=../data/scripts/oryon_errorhandler.groovy =&amp;gt; can be used to define a script that is executed in case of TECHNICAL_ERRORs during the keyword execution &amp;hellip; and to the AgentConf.js:
{ &amp;#34;gridHost&amp;#34;: &amp;#34;&amp;#34;, &amp;#34;registrationPeriod&amp;#34;: 1000, &amp;#34;gridReadTimeout&amp;#34;: 20000, &amp;#34;workingDir&amp;#34;: &amp;#34;src/test/work&amp;#34;, &amp;#34;tokenGroups&amp;#34;: [ { &amp;#34;capacity&amp;#34;: 10, &amp;#34;tokenConf&amp;#34;: { &amp;#34;attributes&amp;#34;: { &amp;#34;key&amp;#34;: &amp;#34;val&amp;#34; }, &amp;#34;properties&amp;#34;: { &amp;#34;plugins.</description>
    </item>
    
  </channel>
</rss>
