You can use arivis Hub DMS in a setup with one or multiple workers. In this setup the image analysis should be disabled on the central server to avoid excessive resource consumption (which might degrade system performance). This can be done on the Configure page in the arivis Hub Server Setup of the central server by deactivating Enable Sub Image Analysis. If needed, the central server can be used as an additional worker, but this requires an arivis Hub DMS Analysis Workers license for the central server (in addition to one license for each worker).

To install and configure a worker, run ah-setup.exe worker (i.e. with command line argument "worker") on a worker PC. This opens the arivis Hub Worker Setup, with which you install a subset of only those arivis Hub DMS components that are needed to run image analysis. For general information on installation and configuration of arivis Hub DMS, see Installing the Components of arivis Hub DMS and Configuring the Software with the Configure Tab.

When you use external workers, the Data Path setting of the central server must be identical to the Data Path setting of every worker. This usually means that the central server must be configured with a UNC path (e.g. \\my-server\my-share), even when the data is stored on a local disk directly attached to the central server. The reason is that the central server generates some configuration files with absolute paths which are then interpreted by the worker. The worker must be able to access the data files using the path names generated by the central server. Creating the network share and granting required access rights must be done manually by your IT support.

The arivis Hub Workflow Worker service needs to have read and write access to the Data Path directory that is also used by the central server to get access to the image data and to store image analysis results. By default, the service runs in the SYSTEM account (the local system account). The local system account might not have the required access rights on the network share by default. You/your IT support needs to setup a working network connection, as the details are highly dependent on your IT environment. If an Active Directory domain is used, sharing with "Domain Computers" is one possible solution. Otherwise, the arivis Hub Workflow Worker service might need to be reconfigured to run under a user or service account which has access to the network share. A recommended option are gMSAs ("Group Managed Service Accounts").

The worker PC requires a TCP connection to the temporal service running on the central server. The default port number is 8085. The Windows firewall is already opened for the Temporal.exe process on the central server during installation. If there are additional firewalls or network protection software, TCP connectivity from the workers to the central server needs to be ensured.