Introduction

Learn how the BigFix Explorer feature extends the power of BigFix.

BigFix Explorer is a new BigFix Platform component, part of the BigFix Platform offering, based on the datastore engine technology implementing it as a stand-alone service.

BigFix Explorer has two main components: datastore engine and the REST APIs.

The datastore engine acts like an in-memory cache that contains the data stored in the BigFix Root Server database. Together with the datastore engine BigFix Explorer offers a REST API interface designed to query the collected data using session relevance. BigFix Explorer must register to a BigFix Root Server and offers near real time data of the BigFix environment any time a BigFix Operator and/or a BigFix Application needs it.

BigFix Explorer can be connected to one BigFix Root Server only.

Multiple instances of BigFix Explorer will be able to connect to the same BigFix Root Server instance. Having more instances helps in failover cases, and when users directly query the BigFix Explorer instead of the BigFix Root Server, different instances might be placed closer to different users instead of having all users query the BigFix Root Server.

In the following figure, you can see the logical architecture of the new component.

The BigFix Client installed is a pre-requisite to install the BigFix Explorer on a machine. A BigFix Explorer instance will connect to the same BigFix Root Server to which the Client is registered.

  • BigFix Explorer is available starting from BigFix Platform Version 11.0.2 as a new Platform component.
  • For a list of BigFix Explorer requirements, see Requirements and assumptions.
  • BigFix Explorer can be installed using a Fixlet targeting a computer where the BigFix Client is available. For more details on installing BigFix Explorer, see Deploying BigFix Explorer.
  • BigFix Explorer exposes REST API interface to evaluate Session Relevance. For more details on using BigFix Explorer APIs, see Using BigFix Explorer.
  • BigFix Explorer can be customized using specific configuration options. For more details on configuring BigFix Explorer, see Administering BigFix Explorer.
  • BigFix Explorer is equipped also with uninstallation tools. For more details, see Uninstalling BigFix Explorer.
  • The authentication to BigFix Explorer is performed using BigFix Operators credentials that are valid for the BigFix Root Server. Both BigFix Master and Non-Master Operators are allowed. For more details about authentication, see BigFix Explorer APIs. The can use REST API privilege is required for BigFix Non-Master Operators to authenticate to the BigFix Explorer.