-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
5943d04
commit 680e086
Showing
293 changed files
with
40,018 additions
and
0 deletions.
There are no files selected for viewing
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,4 @@ | ||
# Sphinx build info version 1 | ||
# This file hashes the configuration used when building these files. When it is not found, a full rebuild will be done. | ||
config: 877a467e62892ff1022262f37f485127 | ||
tags: 645f666f9bcd5a90fca523b33c5a78b7 |
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file added
BIN
+19.8 KB
docs/_build/html/.doctrees/creating_a_test_case_using_robot_framework.doctree
Binary file not shown.
Binary file added
BIN
+91.3 KB
docs/_build/html/.doctrees/creating_your_own_controller_application.doctree
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file added
BIN
+23.7 KB
docs/_build/html/.doctrees/responding_to_a_message_sent_to_an_agent.doctree
Binary file not shown.
Binary file added
BIN
+31.7 KB
docs/_build/html/.doctrees/retrieving_information_about_your_agent_network.doctree
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file added
BIN
+8.72 KB
docs/_build/html/.doctrees/using_supplemental_files_in_your_automation.doctree
Binary file not shown.
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
Activating Agents | ||
======================================================= | ||
|
||
Remember that depending on how your Agents' Behaviors are programmed, Agents may execute code in response to being activated. | ||
|
||
|
||
Agent entities can be activated in multiple ways. | ||
|
||
**Using the SAGE App** - You can activate your existing Agents using the SAGE App. This method is a fast way to activate a large number of agents simultaneously on a single Node. | ||
|
||
1) In the SAGE App, select the targeted Node name or single Agent name and click :mod:`Activate Agent`. | ||
|
||
**By a Controller Appliction** - You can activate agents using a Controller Application, such as Robot Framework. This method is a fast way to activate a large number of single Agents across multiple Nodes. | ||
|
||
1) Use the :mod:`Activate Agent` keyword to activate a targeted Agent name residing on the targeted Node. | ||
|
||
.. code-block:: bat | ||
Activate Agent nodeName1 newAgentName1 | ||
Activate Agent nodeName1 newAgentName2 | ||
Activate Agent nodeName2 newAgentName1 | ||
**Through the execution of a Behavior** - Agents have the ability to activate other agent entities. This is a dynamic way to build your agent network to be more robust. This unique SAGE capability is supported by activating agents within your SAGE Behavior code. This enables agents to activate other agents. | ||
|
||
1) In your Behavior file, use the :mod:`setAgentActive` method to activate a targeted Agent name residing on the targeted Node. | ||
2) Set the value to *true* to activate or *false* to deactivate. | ||
|
||
.. code-block:: bat | ||
setAgentActive(nodeName1, newAgentName2, true); | ||
setAgentActive(nodeName1, newAgentName2, false); | ||
33 changes: 33 additions & 0 deletions
33
docs/_build/html/_sources/adding_a_behavior_to_an_agent.rst.txt
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,33 @@ | ||
Adding a Behavior to an Agent | ||
============================================================ | ||
|
||
The Server will distribute behavior files to the target Nodes by way of a file transfer. From there, a targeted Agent will be given access to the Behavior. | ||
|
||
A Behavior contains some action expected to be fulfilled by an Agent residing on a Node instance. | ||
|
||
Behaviors can be sent to connected Agents in a number of ways. | ||
|
||
**Using the Behavior Manager in SAGE App** - You can populate your existing Agents with Behaviors using the SAGE App. This is the manual way to configure your agent network with the proper Behaviors prior to executing your automation. | ||
|
||
1) In the SAGE App, select the targeted Agent name and click :mod:`Add Behavior`. | ||
2) Select the Behavior name from the list of available Behaviors and click :mod:`Ok`. | ||
3) Enter the desired Behavior topic strings and click :mod:`Ok`. | ||
|
||
Assuming the Behavior file is in the proper sub-directory on the Server: | ||
|
||
**By a Controller Application** - You can add available behaviors to agents using a Controller Application, such as Robot Framework. This gives SAGE users the ability to control complex test scenarios, involving multiple nodes and agents, from a single controller entity. | ||
|
||
1) In your robot file, use the :mod:`Add Behavior` keyword to populate a targeted Node and Agent name with the specified behavior. | ||
|
||
.. code-block:: bat | ||
Add Behavior nodeName1 newAgentName1 ExampleBehavior ExampleBheavior.jar Topic1 Topic2 | ||
**Through the execution of a Behavior** - Agents have the ability configure other agent entities. This is a dynamic way to build your agent network to be more robust. This unique SAGE capability enables agents to send behaviors to other agents. | ||
|
||
1) In your Behavior file, use the :mod:`addBehavior` method to populate a targeted Node and Agent with the specified behavior. | ||
|
||
.. code-block:: bat | ||
addBehavior("nodeName1", "newAgentName1", "ExampleBehavior", "ExampleBheavior.jar", "Topic1", "Topic2"); |
Oops, something went wrong.