Overview

The following components are involved in getting site and subnet information to Nomad for use in the Single-Site Download and Single-Site Peer Backup Assistant (PBA) features.

  • The Web API is used by the Single-Site Download script to store information in the ActiveEfficiency database and enables information to be stored and retrieved by Nomad.
  • The Single-Site Download script uses the Web API to add data from AD into the ActiveEfficiency database.


On this page:

Running the Single-Site Download Feature

The Single-Site Download feature uses a script to retrieve site and subnet information from AD and store it in the ActiveEfficiency database. 

Nomad queries the ActiveEfficiency Web API for site and subnet information and also uses it to store information on which Nomad machines on the site are holding a particular download.

Scheduling Components

We recommend that the Single-Site Download script is either configured to run on a schedule using Windows Task Scheduler or becomes part of the process for changing network infrastructure.

The following table shows the recommended schedules that should be used for the components:

ComponentSchedule
Single-Site Download ScriptOnce a month - though this can be varied according to how often the information being retrieved is likely to change.

Single-Site Download Scripts

A Single-Site Download Script should retrieve site and subnet information from the network and then use the ActiveEfficiency Web Service via the ActiveEfficiency Web API to post information back to ActiveEfficiency.

There are two example scripts:

  1. Retrieves information about all the sites and subnets from Active Directory, as described in Example Active Directory Single-Site Script.
  2. Shows how to add information about selected sites and subnets in ActiveEfficiency, as described in Custom single-site script example.