Skip to content

Collecting Data Stored in an External Application

Terminology

  • Connector- The collection of features, components and capabilities that comprise File Access Manager support for an endpoint.
  • Collector - The “Agent” component or service in a Data Classification and or Permission Collection architecture.
  • Engine - The core service counterpart of this architecture.

  • Identity Collector - A logical component used to fetch identities from an identity store and holds the configuration, settings for that identity store, and the relations between these identities.

    Note

    The identity collector has no “physical” manifest. The actual work is done by the Collector Synchronizer.

The list below describes the high level installation process required to collect and analyze data from an external application. Most of these should already be set up in your File Access Manager installation. See the server Installation guide for further details.

Install a Data Classification central engine - One or more central engines, installed using the server installer

Install a Permission Collection central engine - One or more central engines, installed using the server installer

Create an Application in File Access Manager - From the Business Website. The application is linked to central engines listed above.

Add an Activity Monitor - To collect activities for this application - run the Collector Installation Manager and add an application under Activity Monitoring.

Install Permission Collectors and / or Data Classification Collector (optional)

Optionally, you can install collectors that will run on a separate server and take some of the work from the central PC and DC engines (Where supported). When installing a collector, you attach it to an engine. If no collectors are installed, the central services act as both the engine and the collector.

To install a collector, you must have the RabbitMQ service installed for communication between the central engines and the collectors. RabbitMQ is installed

Note

Some cloud connectors ignore collectors connected to the central engine. (Box, Dropbox, OneDrive, SharePointOnline, Exchange Online, GoogleDrive) . In these applications the task will be done entirely by the engine, and not relegated to its collectors.

Note

For further details, see section Application > Central Service > Collector Relations in the File Access Manager Administrator Guide.