Ouvvi Agents

The below tutorial will cover what Agents are and how to create them.

Service Agents run the tasks within Ouvvi. They can run across multiple machines and networks providing that they can reach and authenticate with this web application (Ouvvi). You can setup the Agents to run your projects, steps and triggers in the location where you need them.

Each configured Agent is an individual thread in the Agent Service, so the more Agents that are configured means the more work that is executed in parallel.

Dependencies allow you to control your Ouvvi steps so that they only execute on a specific group of Agents. E.g. Running a step that has access to on premise resources behind the corporate firewall.

Add an Agent

To add a Service Agent to Ouvvi go to Services > System Services and then click Add Service Agent.

Agents run on the machines you specify here you will need to install the Ouvvi service on each machine that you specify agents to run.

Now enter the machine name to run your Agent using . will default to the local machine, a service type (either agent service or agent maintenance service), and the dependency name. Press Save once you are done to create the Service Agent.

• Agent Service runs the tasks within Ouvvi for example, these will run the steps and triggers.

• There should only be one Agent Maintenance Service in each Ouvvi System as these preform the clean up tasks, such as trimming the logs and resetting locked queue items. By default this will run every 5 minutes.

Add an Agent User

To add an agent user you will need to either create or edit an existing user. To add a new user please see our Users Page which covers how to add a new user with agent/admin permissions.

To edit an existing user to have agent and admin permissions go to Settings > User Profiles and click on the user you wish to edit.

This will bring up the edit user page. Check the admin and agent checkboxes and press Save. Your user is now an agent.

You will need to add admin permissions alongside the agent as they are synonymous. The agent allows API calls and the admin enables read and write status.