The overall configuration options for ActiveEfficiency are set during installation but changes must be made to configure, support and run each feature post-installation. The following diagram shows a schematic of the components involved in the ActiveEfficiency features.

ActiveEfficiency Feature Architecture

  • The Web API component defines the interface for ActiveEfficiency and provides a central location where information coming from the Scout and scripts can be stored and retrieved by each 1E Product. The Scout communicates with the Configuration Manager database to retrieve information on virtual applications and devices.
  • Feature components may retrieve information from the network and post XML files to a local directory for the Scout to consume, with the information being processed by the Scout along with the information retrieved from Configuration Manager and then passed back to the Web API component to store in the ActiveEfficiency database. An example of a Feature Component is the VirtualAppExporter used by the AppV feature.
  • An alternate method used by features is a script that uses the Web Services to add data into the ActiveEfficiency database, this can be matched to information retrieved by the Scout from the Configuration Manager database.
  • The ActiveEfficiency Agent may also be installed on computers in the network to retrieve information on software installations and software usage.
  • Each 1E product has its own method of communicating with ActiveEfficiency. AppClarity, for example, has an ActiveEfficiency Connector that must be synchronized regularly to retrieve information, whereas Nomad communicates directly with ActiveEfficiency each time it needs to retrieve or set single site download information.

The components access various data sources to gather their information. These data sources require various permissions to enable access, which are described in Data capture accounts.