Zoomed Image
USA
800 691 9120
UK
01225 704844

Collection Server Architecture

xAssets Configuration Guide
Deployment and Administration

Collection Server Architecture

The Collection Server is a Windows service that sits between the xAssets application server and remote networks, collecting hardware and software discovery data from machines that cannot communicate directly with the application server. This page explains what the Collection Server does, when you need one, and how to plan your deployment.

What the Collection Server Does

The Collection Server performs three main functions:

  1. Distributes discovery agents -- it hosts a shared folder (the PCAnalyser folder) containing the discovery executables and scripts that remote machines download and run.
  2. Collects discovery results -- discovered data files (PCA, PCZ, PCV, PCS files) are written back to the Collection Server's netdiscover folder by the discovery agents running on remote machines.
  3. Forwards data to the application server -- the Collection Server periodically uploads the collected discovery files to the xAssets application server for processing via batch jobs.

The Collection Server does not process or interpret the discovery data itself. It acts purely as a relay and staging point for file-based data exchange between remote networks and the central application server.

When You Need a Collection Server

You need at least one Collection Server when:

  • Remote offices or branch networks cannot reach the xAssets application server directly (for example, they are behind a firewall or on a separate VLAN with no route to the application server).
  • Discovery agents need a local distribution point -- deploying discovery agents from a server on the same LAN is faster and more reliable than downloading them across a WAN link.
  • Barcode scanners require file-based data exchange -- intelligent barcode scanners (such as TracerPlus devices) write files to a Collection Server share for import into xAssets.

You do not need a Collection Server if all machines to be discovered can reach the application server directly over the network, and you are not using intelligent barcode scanners.

When You Need Multiple Collection Servers

Deploy a separate Collection Server for each network segment that is isolated from the others:

  • Geographically separate offices with their own LAN and no direct connectivity to the application server.
  • Air-gapped or high-security networks where data must be staged before transfer.
  • Networks behind NAT or restrictive firewalls where inbound connections to the application server are blocked.

Each Collection Server operates independently, collecting data from its local network and forwarding it to the central application server.

Network Requirements

Between the Collection Server and the Application Server

Requirement Detail
Protocol HTTPS (recommended) or HTTP
Port 443 (HTTPS) or 80 (HTTP), or the custom port configured on the application server
Direction Outbound from Collection Server to application server
Bandwidth Low -- discovery files are typically small (a few KB per machine per scan)
Connectivity The Collection Server initiates all connections to the application server. No inbound connections to the Collection Server are required from the application server.

Between Discovered Machines and the Collection Server

Requirement Detail
Protocol Windows file sharing (SMB)
Port 445 (SMB)
Direction Discovered machines read from and write to the Collection Server's PCAnalyser share
Permissions Discovered machines need read access to the PCAnalyser share to download discovery agents, and write access to the netdiscover subfolder to deposit results

Firewall Rules Summary

Source Destination Port Protocol Purpose
Collection Server Application Server 443 or 80 HTTPS/HTTP Upload discovery data
Discovered machines Collection Server 445 SMB Access PCAnalyser share

The PCAnalyser Folder Structure

The Collection Server installation creates a shared folder structure used by all discovery operations:

Folder Purpose
pcanalyser Root of the shared folder, contains discovery executables
pcanalyser\netdiscover Holding folder where all discovery engines and agents write their results back to the Collection Server

The netdiscover folder accumulates PCA, PCZ, PCV, and PCS files over time as machines are scanned. The data loader on the application server processes and archives these files during batch job execution.

Tip: Monitor disk space on the Collection Server, especially the netdiscover folder. In large environments with frequent scans, this folder can grow significantly between processing cycles.

Installation

The Collection Server is installed as a separate component from the main xAssets application. It runs as a Windows service and includes a system tray icon for monitoring status.

For detailed installation steps, see How to Set Up a Collection Server.

Warning: The Collection Server requires Windows. It cannot be installed on Linux or macOS. See System Requirements for supported Windows versions.

Monitoring the Collection Server

After installation, the Collection Server appears as a system tray icon. Right-clicking this icon provides options to:

  • View the current status (connected, disconnected, transferring)
  • Check the last successful upload time
  • View error logs if uploads are failing

If the Collection Server cannot reach the application server, discovery files continue to accumulate locally and are uploaded when connectivity is restored.