The Agent (the JAMS Incident Connector) also runs on Linux, for integrations whose servers are often Linux machines: GoAnywhere MFT and Skybot Scheduler. It's the same Agent as the Windows installer, with the same guided setup: you paste a pairing token and it asks the right questions for that integration.
Windows only: the JAMS Scheduler integration and Windows service monitoring need the Windows Agent. Setup on Linux tells you so if you paste one of their tokens.
What you'll need
- An x86_64 Linux server with systemd. The Agent is built and tested for RHEL 8 and 9 and compatible distributions.
- sudo access on that server.
- Outbound HTTPS from the server to JAMS Incident Management, and to the product it watches (for example GoAnywhere on port 8000 or 8001). No inbound ports are needed.
- A pairing token from the integration's page in JAMS Incident Management (for example Integrations → GoAnywhere MFT → Add server).
Step 1: Download
On the integration's page, next to the Windows installer, click Download for Linux (.tar.gz). You'll get a file named like jams-connector-linux-x64-0.9.17.tar.gz. Copy it to the Linux server.
The Linux steps button beside it shows the same commands as below, with your version's file name filled in.
Step 2: Check the download (recommended)
Every Linux release comes with a SHA-256 checksum and a GPG signature. On the integration's page, open Linux steps and download the SHA-256 checksum and GPG signature files into the same folder as the .tar.gz.
Checksum (confirms the file arrived intact):
sha256sum -c jams-connector-linux-x64-0.9.17.tar.gz.sha256
It should print OK.
Signature (confirms the file really came from JAMS Software). Do this once to get our signing key:
curl -fsSLO https://jamssoftware.blob.core.windows.net/incidentmanagement/jams-connector-signing-key.asc
gpg --import jams-connector-signing-key.asc
gpg --fingerprint incidentmanagementsupport@jamssoftware.com
Check that the fingerprint shown is exactly:
2B75 5B2D 1837 2CE6 DDB8 92FB 556D 6394 8740 4AA0
Then verify each download:
gpg --verify jams-connector-linux-x64-0.9.17.tar.gz.asc jams-connector-linux-x64-0.9.17.tar.gz
Look for Good signature from "JAMS Software LLC (Incident Connector Linux signing)". A warning that the key "is not certified with a trusted signature" is normal; it only means you haven't personally marked our key as trusted. If it says BAD signature, don't install the file, and contact support.
The signing key is itself certified by the JAMS Software Repository key. If you already have that key and have marked it as trusted, gpg shows this one as valid too, without the warning.
Step 3: Install
tar -xzf jams-connector-linux-x64-0.9.17.tar.gz
cd jams-connector-linux-x64-0.9.17
sudo bash install.sh
Use sudo bash install.sh exactly as shown. Running ./install.sh fails with "Permission denied", because the file isn't marked executable in the download.
The installer:
- puts the Agent in
/opt/jams-connector - creates a system user,
jamsconnector, that the Agent runs as (it never runs as root) - installs and starts the
jams-connectorsystemd service, set to start on boot
At the end it asks Configure the connector now? Answer Y, paste the pairing token, and answer the questions for your integration. Setup tests the connection before saving and restarts the Agent.
To configure it later, or to change its settings, run:
sudo /opt/jams-connector/JamsConnector setup
Back in JAMS Incident Management, the integration's page shows the Agent as connected within a minute.
Managing the Agent
| To | Run |
|---|---|
| See whether it's running | systemctl status jams-connector |
| Restart it | sudo systemctl restart jams-connector |
| Read its log | journalctl -u jams-connector -n 100 |
| Follow the log live | journalctl -u jams-connector -f |
Upgrading
Download the new version and repeat Steps 2 and 3. The installer stops the Agent, replaces it and starts it again. Your settings, including the pairing, are kept; there's no need to run setup again.
Removing the Agent
sudo systemctl disable --now jams-connector
sudo rm /etc/systemd/system/jams-connector.service
sudo systemctl daemon-reload
sudo rm -rf /opt/jams-connector
sudo userdel jamsconnector
Then remove the server (or Agent) from the integration's page in JAMS Incident Management, so its pairing token stops working.