Setup Ouvvi Dependency Agent
Ouvvi Agents can be installed on multiple machines, these agents can then be defined as a dependency agent so only Ouvvi steps with the same dependency name will run on this agent.
You may wish to configure a dependency agent when you need steps to run on a specific machine.
- .NET Framework v4.6.2
- Windows Server 2012 or Higher
- 2 GB RAM
- 1 CPU Core
- 50 GB Disk Space
- Data Synchronisation Studio
- Ouvvi Server with firewall open to Ouvvi Site URL.
Important your Ouvvi Server Web Application must be accessible from the network. If you open the Ouvvi Server Web Application to the network consider the use of TLS/SSL for the site.
Install Ouvvi Agent
Follow the steps below to manually install and configure the Ouvvi Agent on this machine.
Create a folder on this machine to hold your Agent Service and copy the Service folder from
C:\Program Files\Simego\Data Synchronisation Studio 3.0\Ouvvi\Service to this folder.
Copy or edit the
Simego.Console.Service.exe.config file to match the configuration in your Ouvvi Tenant.
OuvviServiceUrl must match your Ouvvi Tenant configuration.
In Ouvvi go to
Services->System Services->Add Service Agent to register this machine in Ouvvi to run the Ouvvi Service Agent.
Provide the name of the Server as the Agent Name, Service Type is Agent Service and the Dependency Name should be the name you want to use for this dependency.
The Agent will run a processing thread for each registered agent in services so create Service Agents as required.
Use the windows
sc.exe utility to Install the Ouvvi Service into Windows Service Control Manager
sc.exe create OuvviAgent binpath="C:\Ouvvi\Service\Simego.Console.Service.exe" type=own start=delayed-auto DisplayName="Ouvvi Processing Service (OuvviAgent)"
Edit the Ouvvi Agent Windows Service and set the Windows Account to run this Service.
This Windows Account must also be registered in Ouvvi User Profiles with Admin+Agent permission.
To configure a step in Ouvvi to run on this agent only set the
Execute On parameter to the Dependency name you defined for the service.