The .NET version of the step agent is only available with the Enterprise Edition of step. It can be downloaded from our FTP server by enterprise customers at step Enterprise (credentials are provided upon requests).
As of step 3.17, we provide four distributions of the .NET agents, supporting multiple frameworks and operating systems:
The net5.0 agent is available for Windows, Linux and OSX and is provided as self-contained zip files for each of these runtimes (“step-enterprise-agent-net5-runtime-step_version.zip”).
The net4.x agent (step-enterprise-agent-net4-….zip), available only on windows and using the latest stable version of the net4.X framework for compatibility support.
To install an agent, extract the chosen archive in an empty folder and configure it as described in below sections.
For windows agents, you may need to execute the following command line as Administrator to allow the agent to listen on the configured agent port.
Per default the agent port is set to 8098 for the .NET agent (see below for more details concerning the configuration of the agent port).
For the net5.0 agent on macOS and Linux, it is necessary to add your hostname in the system file /etc/hosts.
Example: ‘127.0.0.1 hostname’.
You may validate the configuration using the command
Below the description of the agent structure folder :
├── bin : contains startup scripts
├── conf : contains configuration files
└── log : default location for the log files
├── ext : default location for external software binaries and libraries (java only)
├── lib : contains dependencies libraries (java only)
The configuration files of the agent can be found under agent/conf. This folder contains following data:
Since step 3.16 both JSON and YAML formats are supported for the configuration of the agent. The default configuration format is YAML. If you want to use the legacy JSON format (AgentConf.json) for the configuration you have to modify the start script located under agent/bin (see below) accordingly.
All the agent parameters are documented in the YAML file directly. The following paragraphs explain these parameters in more detail.
At startup the agent registers itself into the controller’s grid using the grid endpoint exposed by the controller. The grid endpoint to be used is defined by the parameter gridHost.
Change this parameter according to the hostname of your controller and its grid port. Per default the contoller is configured to use the port 8081. Please refer to the configuration of the controller for more details concerning the configuration of the grid.
For example :
Configure the agent to connect to the port 8081 of the grid host called controller
The agent exposes a REST service to the Controller, which is consumed by the controller to execute Keywords. The endpoint of this service is called agent endpoint. The agent endpoint is configured automatically at agent startup and is communicated to the controller at registration. If required, the endpoint can be tweaked as follow:
Per default the agent lets the system find a free port automatically at startup to listen on.
If required you can set the agent port explicitly using the parameter agentPort. The agent service would then run on that specific port.
For example :
# Configure the agent to listen on port 8080agentPort:8080
Per default the hostname of the agent endpoint is determined automatically at agent startup. If required you can set the agent hostname explicitly using the parameter agentHost.
For example :
# Configure the agent to be called by the controller using the hostname agent-host.mynetwork.netagentHost:agent-host.mynetwork.net
Per default the URL of the endpoint which is communicated to the controller is built as follow: http://<agentHost>:<agentPort>. If required (if your agent is behind a proxy for instance), you can set the URL of the agent endpoint explicitly using the parameter agentUrl:
As described here in more detail, Keywords are executed on so-called agent tokens. On agent can emit multiple groups of agent tokens. The token groups are configured using the parameter tokenGroups. Each token group has its own number of tokens (capacity) and attributes. The following paragraphs explain the configuration of token groups.
The number of agent tokens emitted by a token group is defined by the parameter capacity. This parameter defines how many tokens have to be made available to the controller for Keyword execution and thus defines the maximal number of parallel keyword executions to be allowed on the agent for a specific group. Set this value according to the resources of your agent:
For example :
# Defines 1 token group with 200 tokenstokenGroups:- capacity:200tokenConf:attributes:properties:
As described here, specific agent tokens can be selected for execution using so-called agent attributes. The agent attributes are defined as key-value pairs in the parameter tokenConf.attributes.
For example, we could define a pool of “Windows” agents by setting an “OS” attribute like below :
open a new command prompt as Administrator and navigate to the nssm executable location
execute the following command :
nssm gui will open, you can now specify the “startAgent.bat” location and the service name, then click on “Install service” :
You should then be prompted that the service installation has been successful :
you can double-check into Windows service list that the service has been properly installed and then you can start it :
Depending on your platform, they are various ways to check if the Agent is running :
open the Task Manager and look for the Agent processes
execute below command and check that a PID is returned :
ps -efl | grep Agent
open the Activity Monitor and look for the Agent processes
The Agent log file will be created on first startup under the log folder. (You can change the log file location by editing the bin/logback.xml file). A successful startup should display the following entry into the log file:
2017-09-26 13:22:40,639 INFO [main] o.e.j.s.Server [Server.java:379] Started @1326ms