Where is all the data stored that is retrieved by the BigFix Client?

The HCL BigFix architecture is centralized. BigFix Clients on endpoints evaluate system properties and Fixlet relevance, then compile this data into reports. These reports are sent upstream, typically through Relays, to the root BigFix Server. The server's primary role is to process these incoming reports and write all the aggregated data into the backend database (e.g., Microsoft SQL Server or IBM Db2). This database acts as the central repository and single source of truth for the entire deployment, storing all endpoint information, content, and action history.

A. The BigFix server is the application component that processes data, but the database is the dedicated persistent storage layer.

C. The local endpoint is the source of its own data, not the central storage location for all data from the entire deployment.

D. Relay servers act as communication and content caching intermediaries; they do not permanently store all endpoint data.

1. HCL BigFix Platform 10.0 Documentation

"BigFix Architecture Overview". This section states

"The BigFix server coordinates the flow of information to and from the individual clients and stores the information in the BigFix database." This confirms the database is the central storage.

2. HCL BigFix Platform 10.0 Documentation

"Server components". This document details the database's role: "The database is the core of the BigFix system. It stores the collected information about the managed endpoints

the Fixlet content

and the actions."

3. HCL BigFix Platform 10.0 Documentation

"Information Flow". The diagrams and text in this section illustrate that client reports (retrieved data) flow from the client

through relays

to the server

which then populates the database.