Index | Prev | Next

Accessing hierarchies scoped against the SystemDb

You can access hierarchies scoped against the SystemDb, which allows the Supervisor station to navigate hierarchies with data based on entities from the remote JACE stations. The purpose of the System Database is to allow you to run queries against your entire Niagara system (the Supervisor and those Niagara stations connected to it), which allows your searches and hierarchies to span the entire system.
Prerequisites:
  • You have an open connection to a Supervisor station (via Workbench or browser).
  • The SystemDb is installed and configured on the Supervisor.
  • In order for any tagged entities to resolve correctly in virtual hierarchies, you must have installed the same tag dictionaries on the Supervisor station as are installed in the subordinate stations.
  • Entities in the subordinate stations are already tagged as needed.
  • You have the hierarchy palette open.
  • You have successfully indexed subordinate stations in your NiagaraNetwork, and Niagara virtuals must be enabled and set up properly for user permissions.

Although not a prerequisite, you may want to copy existing hierarchy definitions configured on the subordinate stations and paste those into to the HierarchyService on the Supervisor station. Also, you need to modify those definitions to point the hierarchy scope to the System Database. Otherwise, you need to create a properly scoped hierarchy definition as described here.

Perform the following steps:
  1. In the Nav Tree of the Supervisor station, expand the Services node.
  2. In the hierarchy palette, drag the Hierarchy component to the station’s HierarchyService and in the Name window, enter the desired name. Alternatively, there is a preconfigured SystemDbHierarchy component in the hierarchy palette that already has the SystemDb ("sys:") scope configured.
  3. Open a Property Sheet view of the HierarchyService, expand Hierarchy > Scope > Station and in the ScopeOrd field replace the default value by entering: “sys:“.
    Image
    You have changed the Hierarchy scope to run against the SystemDb.
  4. Continue to add level definitions as needed (based on objects and tags as used in the subordinate stations and how you wish to navigate those stations). For more details, see procedure “Setting up a Hierarchy Definition”.
  5. Right-click in the Nav Tree and select Refresh Tree Node.
  6. Expand the station’s Hierarchy space and navigate throughout the entities (including points and schedules) located on the subordinate stations as organized by the hierarchies.

Results vary based on how your hierarchy is defined, but here is an example of how one such hierarchy might look.

Image
 NOTE: If you add a new JACE to the NiagaraNetwork (one that has Niagara virtuals set up properly for user permissions) and the station has been indexed, the new subordinate station will automatically show up in the Supervisor’s Hierarchy space, provided the entities on the subordinate station are properly tagged. 

For more details on SystemDb, see the Niagara System Database and System Indexing Guide.

Related Links

  • Common hierarchy tasks (Parent Topic)

    • Related References

  • Hierarchy scopes

    • Index | Prev | Next