|Minimum RAM||500 MB|
|Supported Operating System Types||64 bit|
|Supported Windows Server Versions||2008 R2 SP1 & later|
|Support Linux Variants||View Here|
Currently the Loome Integrate Online Agent does not support proxies and so proxies must be disabled during the installation process.
The Agent installer is a single Powershell Script that will download the necessary run times, the newest version of the agent and it will also pre-configure your agent to connect to this tenant.
The install script will automatically be installed as a Local System account. To change the account settings, you will need to modify the service.
Once you’ve downloaded the script, make sure to run the script with administrator privileges.
Windows users will need to ensure they have Powershell 4 at a minimum installed.
Linux users will need to install Powershell Core for their platform.
First, open up Services on your computer.
Find the agent you just installed with the same name listed in Services. It will be loome-agent followed by your unique agent code.
Once you’ve found your agent, open up the log on window.
Change the account here.
Once you save, the agent will now use this account.
Loome Integrate Agents are installed in a standard directory, based on a unique ID. All agent installs can be found in
%ProgramData%\LoomeAgent on Windows and
/.loomeagent/ on Linux. There is no need to take note of this directory when updating the agent, as the install script will automatically detect if an agent is installed for the related tenant.
Whilst we highly recommend you run the agent as a service, you are able to run it as a console application you startup when necessary. Agents can be run as a console application using the
Run.ps1 powershell script located in their install directory.
If the agent is running as a service, you will need to provide an account with “Logon as a Service” functionality.
When providing the username and password credentials for the service, ensure that you include the domain as part of the username. Eg: “Company\User” or “DeviceName\LocalUser”
Agent services can be viewed in the Windows Services manager under the name
loome-agent-[unique identifier for the agent] (eg:
The installer will create a new group called
loomeusers on install, this group is used for managing file permissions in the
/.loomeagent directory and so it is a requirement that the group is created.
From the homepage, click on the Tenant name in the top right corner. From the resulting dropdown menu, select Agents.
On the Agents page, select Setup Agent.
Follow the prompts in the installation wizard.
Loome Integrate also supports running the agent using Docker. The official Loome Integrate Agent image is available from the Docker Hub at loomesoftware/agent. Docker Agents are configured entirely through environment variables/secrets so there is no need to mount additional volumes for configuration files. Using the Docker installation screen, you can generate shell commands that will pre-configure the Docker based agent to automatically run and connect to your tenancy.
Once installed, this Docker agent will include PowerShell 7.
To update agents being hosted in Docker, just run the same installation script again.
Whilst Loome Integrate only generates commands for certain installation options, the agent is compatible with any Docker based platform.
The Docker Run tab provides a generated command for installing the agent using
docker run. This command by default will run the
agent as a detached background service which will automatically restart with the host PC’s restart.
Whilst the Docker Run command provides all environment variables inline with the
-e switch, these environment variables can be
used to host the agent using other means such as an
envlist or orchestration engines like Docker Swarm and Kubernetes.
The Azure Container Instances (ACI) tab provides a generated command for create an ACI resource for the agent.
The command provided needs to be ran in an instance of the Azure Cloud Shell or a connected Azure CLI, a valid resource group name is also required for billing purposes.
SQL Server may require a firewall exception for the container. To get a containers public IP address, execute the following command in the Azure Container instance: