...

Linux Installation – Desktop and Server Agent

Estimated reading: 8 minutes

This document aims to show the installation procedure of Automatos Desktop / Server Agent for the Linux Operating System.

To start the installation, copy the binary to the /tmp directory of the machine that will be installed.
To do this, identify which Linux distribution is.

We currently have 2 types of “ADA” (Desktop Agent) and “ASA” (Server Agent) Agents:

  • For Debian-based Distributions (dpkg / .deb). Debian, Ubuntu, etc;
  • For Red Hat (RPM) based Distributions. Red Hat, Suse, Fedora, etc.

Download Agent

https://lad1-smartcenter.almaden.app/auth/signin/ if your account is from the LAD1 environment.
https://lad2-smartcenter.almaden.app/auth/signin/ if your account is from the LAD2 environment.
NOTE: To download the agent, you need access to SmartCenter / CIQ ITAM, and your account must have the necessary permissions to download the agent.

AdaWin1 Linux Installation - Desktop and Server Agent
Agent Download

Note: Software distribution is only available for Microsoft Windows.

DPKG x32 – Installation

Desktop Agent (ADA) and Server Agent (ASA) for common linux distributions: Debian, Ubuntu, Mint…

1 – Update Repository (Optional)

apt update

2 – Install library libc6 for x32

apt-get -y install libc6

3 – Elevate installation package permission (Check the name of the package that was downloaded.)

chmod 775 axa-##.##.##-en.i386.lin.deb

4 – Install Desktop Agent or Server Agent (Check the name of the package that was downloaded.)

dpkg -i axa-x.x.x-en.i386.lin.deb

DPKG x32 – Data sending configuration

The data forwarding configuration can be done for SmartCenter Cloud or Central Relays
Execute only one of the following configuration commands, either SmartCenter Cloud or Central Relays.

NOTE: Replace the fields below with your environment.
<your@account.com>: The primary SmartCenter access account.
<Department>: The department to which the equipment should be organized in SmartCenter.
<ENV>: The database where the account is created in SmartCenter, which can be lad1 or lad2.
<RELAY1> and <RELAY2> : Replace the fields with the IP or Hostname of the Central Relays.

Data sending SmartCenter Cloud

SmartCenter Cloud – Desktop Agent (ADA)

/opt/automatos/ada/bin/asetup -s -a -s -i<your@account.com> -b<Department> -ca127.0.0.1:1999 -crssl:<ENV>-receiver.almaden.app:443

SmartCenter Cloud – Server Agent (ASA):

/opt/automatos/asa/bin/asetup -s -a -s -i<your@account.com> -b<Department> -ca127.0.0.1:1999 -crssl:<ENV>-receiver.almaden.app:443

EXAMPLE:
CloudCom Linux Installation - Desktop and Server Agent
NOTE: The expected outcome after executing the configuration SmartCenter Cloud command.
Test

Data sending Central Relays

Central Relays – Desktop Agent (ADA)

/opt/automatos/ada/bin/asetup -s -a -s -i<your@account.com> -b<Department> -ca<RELAY1>:1999 -oaar<RELAY2>:1999

Central Relays – Server Agent (ASA)

/opt/automatos/asa/bin/asetup -s -a -s -i<your@account.com> -b<Department> -ca<RELAY1>:1999 -oaar<RELAY2>:1999

NOTE: The expected outcome after executing the configuration to Central Relays command.
Relay Linux Installation - Desktop and Server Agent

End of configuration DPKG x32


DPKG x64 – Installation

1 – Update Repository (Optional)

apt update

2 – Install library libc6 for x64

apt-get -y install libc6-i386

3 – Elevate installation package permission (Check the name of the package that was downloaded.)

chmod 775 axa-##.##.##-en.i386.lin.deb

4 – Install Desktop Agent or Server Agent (Check the name of the package that was downloaded.)

dpkg -i axa-x.x.x-en.i386.lin.deb

DPKG x64 – Data sending configuration

The data forwarding configuration can be done for SmartCenter Cloud or Central Relays
Execute only one of the following configuration commands, either SmartCenter Cloud or Central Relays.

NOTE: Replace the fields below with your environment.
<your@account.com>: The primary SmartCenter access account.
<Department>: The department to which the equipment should be organized in SmartCenter.
<ENV>: The database where the account is created in SmartCenter, which can be lad1 or lad2.
<RELAY1> and <RELAY2> : Replace the fields with the IP or Hostname of the Central Relays.

Data sending SmartCenter Cloud

SmartCenter Cloud – Desktop Agent (ADA)

/opt/automatos/ada/bin/asetup -s -a -s -i<your@account.com> -b<Department> -ca127.0.0.1:1999 -crssl:<ENV>-receiver.almaden.app:443

SmartCenter Cloud – Server Agent (ASA):

/opt/automatos/asa/bin/asetup -s -a -s -i<your@account.com> -b<Department> -ca127.0.0.1:1999 -crssl:<ENV>-receiver.almaden.app:443

EXAMPLE:
CloudCom Linux Installation - Desktop and Server Agent
NOTE: The expected outcome after executing the configuration SmartCenter Cloud command.
Test

Data sending Central Relays

Central Relays – Desktop Agent (ADA)

/opt/automatos/ada/bin/asetup -s -a -s -i<your@account.com> -b<Department> -ca<RELAY1>:1999 -oaar<RELAY2>:1999

Central Relays – Server Agent (ASA)

/opt/automatos/asa/bin/asetup -s -a -s -i<your@account.com> -b<Department> -ca<RELAY1>:1999 -oaar<RELAY2>:1999

NOTE: The expected outcome after executing the configuration to Central Relays command.
Relay Linux Installation - Desktop and Server Agent

End of configuration DPKG x64


RPM x32 – Installation

1 – Refresh Repository (Optional)

zypper refresh

2 – Install library glibc for x32

zypper install glibc -y

3 – Elevate installation package permission (Check the name of the package that was downloaded.)

chmod 775 axa-x.x.x-en.i386.lin.rpm

4 – Install Desktop Agent or Server Agent (Check the name of the package that was downloaded.)

rpm -Uhv axa-x.x.x-en.i386.lin.rpm

RPM x32 – Data sending configuration

The data forwarding configuration can be done for SmartCenter Cloud or Central Relays
Execute only one of the following configuration commands, either SmartCenter Cloud or Central Relays.

NOTE: Replace the fields below with your environment.
<your@account.com>: The primary SmartCenter access account.
<Department>: The department to which the equipment should be organized in SmartCenter.
<ENV>: The database where the account is created in SmartCenter, which can be lad1 or lad2.
<RELAY1> and <RELAY2> : Replace the fields with the IP or Hostname of the Central Relays.

Data sending SmartCenter Cloud

SmartCenter Cloud – Desktop Agent (ADA)

/opt/automatos/ada/bin/asetup -s -a -s -i<your@account.com> -b<Department> -ca127.0.0.1:1999 -crssl:<ENV>-receiver.almaden.app:443

SmartCenter Cloud – Server Agent (ASA):

/opt/automatos/asa/bin/asetup -s -a -s -i<your@account.com> -b<Department> -ca127.0.0.1:1999 -crssl:<ENV>-receiver.almaden.app:443

EXAMPLE:
CloudCom Linux Installation - Desktop and Server Agent
NOTE: The expected outcome after executing the configuration SmartCenter Cloud command.
Test

Data sending Central Relays

Central Relays – Desktop Agent (ADA)

/opt/automatos/ada/bin/asetup -s -a -s -i<your@account.com> -b<Department> -ca<RELAY1>:1999 -oaar<RELAY2>:1999

Central Relays – Server Agent (ASA)

/opt/automatos/asa/bin/asetup -s -a -s -i<your@account.com> -b<Department> -ca<RELAY1>:1999 -oaar<RELAY2>:1999

NOTE: The expected outcome after executing the configuration to Central Relays command.
Relay Linux Installation - Desktop and Server Agent

End of configuration RPM x32


RPM x64 – Installation

1 – Refresh Repository (Optional)

zypper refresh

2 – Install library glibc x32

zypper install glibc-32bit -y

3 – Elevate installation package permission (Check the name of the package that was downloaded.)

chmod 775 axa-x.x.x-en.i386.lin.rpm

4 – Install Desktop Agent or Server Agent (Check the name of the package that was downloaded.)

rpm -Uhv axa-x.x.x-en.i386.lin.rpm

RPM x64 – Data sending configuration

The data forwarding configuration can be done for SmartCenter Cloud or Central Relays
Execute only one of the following configuration commands, either SmartCenter Cloud or Central Relays.

NOTE: Replace the fields below with your environment.
<your@account.com>: The primary SmartCenter access account.
<Department>: The department to which the equipment should be organized in SmartCenter.
<ENV>: The database where the account is created in SmartCenter, which can be lad1 or lad2.
<RELAY1> and <RELAY2> : Replace the fields with the IP or Hostname of the Central Relays.

Data sending SmartCenter Cloud

SmartCenter Cloud – Desktop Agent (ADA)

/opt/automatos/ada/bin/asetup -s -a -s -i<your@account.com> -b<Department> -ca127.0.0.1:1999 -crssl:<ENV>-receiver.almaden.app:443

SmartCenter Cloud – Server Agent (ASA):

/opt/automatos/asa/bin/asetup -s -a -s -i<your@account.com> -b<Department> -ca127.0.0.1:1999 -crssl:<ENV>-receiver.almaden.app:443

EXAMPLE:
CloudCom Linux Installation - Desktop and Server Agent
NOTE: The expected outcome after executing the configuration SmartCenter Cloud command.
Test

Data sending Central Relays

Central Relays – Desktop Agent (ADA)

/opt/automatos/ada/bin/asetup -s -a -s -i<your@account.com> -b<Department> -ca<RELAY1>:1999 -oaar<RELAY2>:1999

Central Relays – Server Agent (ASA)

/opt/automatos/asa/bin/asetup -s -a -s -i<your@account.com> -b<Department> -ca<RELAY1>:1999 -oaar<RELAY2>:1999

NOTE: The expected outcome after executing the configuration to Central Relays command.
Relay Linux Installation - Desktop and Server Agent

End of configuration RPM x64


Status of agents

The following commands are used to check the configurations applied to the Desktop Agent and Server Agent.

Status – Desktop Agent

Desktop Agent “aengine” and “arelay” status

/opt/automatos/ada/bin/aengine -status
/opt/automatos/ada/bin/arelay -status

Status – Server Agent

Server Agent “aengine” and “arelay” status

/opt/automatos/asa/bin/aengine -status
/opt/automatos/asa/bin/relay -status

Check “aengine” and “arelay” status
aenginestatus Linux Installation - Desktop and Server Agentarelaystatus Linux Installation - Desktop and Server Agent


Services

Interacting with the Desktop Agent and Server Agent services.

# Start Services
systemctl start aengine
systemctl start arelay

# Stop Services
systemctl stop aengine
systemctl stop arelay

# Restart Services
systemctl restart aengine
systemctl restart arelay

# Status Services
systemctl status aengine
systemctl status arelay

Share this Doc

Linux Installation – Desktop and Server Agent

Or copy link

Table of Contents
Scroll to Top