Agents

Setup one or more Agent machines that will execute Test Sets when Run from VERA. On the Tosca side, each run executes a Test Event. A Test Event can be setup to run on certain machines, if required.

Note: each Agent communicates with a specific Tosca Server. If there is more than one Tosca Server in your environment, configure accordingly. There is no facility to share Agents across multiple Tosca Servers.


High Level Setup Activities

In general, the following activities are performed to set up a Remote Execution Environment in Tosca:

  1. Setup one or more Tosca Agent machines, per Tricentis instructions for installed version (ex: Set up Tosca Distributed Execution without AOS (tricentis.com))
  2. Update the Tosca ConfigurationParameters file on the server
  3. In the Tosca project, create a Configuration item for the ALM Project
  4. On any Agent to be included in the group, set its Project Name parameter to match the ALM Project name.
  5. Update the "DEX" (Distributed Execution) services "ConfigurationParameters.xml" file to modify any parameters needed to identify Agents. For example, include the ALM Project name in a list of values for the parameter called "Project Name". This then allows for a subset of Agents to be assigned to a specific project. In Tosca Commander, a Configuration can be used to configure a Test Event to target machines for a specific project. 
  6. To update the configuration properties from the Tosca Server configuration parameters, check out the Project root.  Select the Configuration folder, right click and select "Update configurations from Server" then select "Checkin All" and "Update All".

        


Setup one or more Tosca Agent machines

Follow Tosca instructions to setup remote "Agent" machines that will execute automated Tosca Execution Lists.
Note these machines require:

  1. Windows 7, 8 or10
  2. The correct version of Tosca Commander to be installed
  3. Software to be tested (e.g. SAP client; Remedy client)
  4. ToscaRemoteAgent.exe to be configured correctly and running
  5. A user session active on the machine
  6. That user (that owns the session) must connect to the license server at least once
  7. That user (that owns the session) must complete first-time use browser prompts, at least once
  8. A successful connection to the Tosca Distribution Server (green light in system tray icon)


Refer to the Tosca documentation for further information.

These are steps used at Tx3 to configure a Remote Tosca Agent machine for use with VERA/Tosca Integration:

  1. Install TOSCA Commander (Full Installation) on all agents
  2. Login to Windows on the Agent machine and Open TOSCA Commander
  3. Go to Settings -> Commander -> Distributed Execution -> Server and specify End Point Address (Distribution server address format:  http://<serverAddress>/DistributionServerService/ManagerService.svc (The end point address should not contain ''. If machine name contains '-', use the IP address. For example: server address - xx.xx.xx.xx:xxxx).  Confirm the "ToscaDistributionAgent.exe.config" file in %TRICENTIS_DEX_AGENT_HOME% directory specifies the "BasicHttpBinding" for HTTP as security mode="None" and for HTTPS as security mode="Transport".
  4. Go to TOSCA commander -> New and create a local agent workspace using a Common Repository. See Tosca documentation for how to setup a repository.
  5. Start your agent by double-clicking the ToscaDistributionAgent.exe file located at %TRICENTIS_HOME%\DistributedExecution\Agent
  6. Go to machine tray icon on right down corner and right click on TOSCA agent icon and click on Configure Agent. The ToscaDistributionAgent Configuration window opens:
  7. Go to the Connect to server tab and make sure that Distribution server name/IP address is reflected here. If not provide the distribution server name/address. Click Ok and exit agent and restart the ToscaDistributionAgent.exe file. If Agent can connect it will show as green icon
  8. Go to 'Configure machine' and setup the Memory as 16 GB, make sure that IP address is that of the agent machine:
  9. Set additional parameters, as necessary to target a specific Agent. For example, in the above screen, the parameter "ProjectName" was configured and its value set to "Comet" to identify this as a machine that can run Comet Test Events, if a Test Event has a Configuration with its ProjectName set to "Comet".
  10. Go to 'Setup workspace' and select the local agent workspace created in step-4 as well as provide username and password of user from which execution on agent will be performed. It is recommended to use the account described in the "Accounts" section above. For example, an Admin account named "VERAExecutor".
  11. Click Ok, Save and exit the agent and run the ToscaDistributionAgent.exe again. Make sure the System Tray icon remains green.


Test the Agent

  1. Go to the local machine from where you want to start the remote execution, Open Tosca Commander
  2. Go to Settings > Commander -> Distributed Execution -> Server and specify End Point Address (Distribution server address in format:  http://<serverAddress>/DistributionServerService/ManagerService.svc (The end point address should not contain ''. If machine name contains '-', use the IP address. For example: server address - 10.20.6.29:8080
  3. Go to Execution List tab and go to Configuration section. Right click and Refresh Agents

  1. Create a Test Event, drag & drop an execution list to use as a test
  2. Create a Configuration and specify the Agent's IP address in the IP address property
  3. Drag & drop the new Configuration into the Test Event
  4. To run the event, right-click the event and select "Execute Now"