Unimus
Page tree
Skip to end of metadata
Go to start of metadata

Disabling jobs by type

Due to security requirements, it might in some cases be desired to disable some specific Unimus features.

Unimus supports disabling specific job types on a per-core basis. As an example, you might want to disable Config Push in a specific Zone, or system-wide. If you only use the embedded Core inside the Unimus server (when all device communication is done directly from the server), you only need to configure this on the server itself. If you utilize remote Cores, you need to configure each Core separately per your requirements. More info in the Architecture overview.

You can disable any jobs by type by setting:

-Dunimus.core.discovery-disabled=true
-Dunimus.core.backup-disabled=true
-Dunimus.core.push-disabled=true
-Dunimus.core.scan-disabled=true
-Dunimus.core.device-cli-disabled=true

Disabling Core connection listener

Normally, the Unimus server listens to incoming Core connections on TCP 5509 (by default). If you are NOT using remote Cores, you can disable the Core connection listener completely (so Unimus would not even bind / listen on this port).

-Dunimus.server.core.listener-disabled=true

How to configure these settings

On Linux, edit the contents of /etc/default/unimus (or /etc/default/unimus-core for Unimus Core).
Please make sure all the configuration in this file is in a single line.

On Windows, add the lines to Unimus.l4j.ini in "C:\Program Files\Unimus\" (or "C:\Program Files\Unimus-Core\" for Unimus Core).
Please make sure every configuration item in this file is on a separate line.

Restart the Unimus (or Unimus Core) service to apply the new configuration.

  • No labels