obixDriver-ObixHistoryDeviceExt

This component discovers, adds, and manages history imports for the ObixClient and R2ObixClient. It manages the import of historical data from the oBIX server into the Niagara 4 history space. Use its default Obix History Manager view to add oBIX history importdescriptors.
Figure 6.   History device extension properties
Image

To access these properties expand ObixNetwork > ObixClient, right-click Histories and click Views > AX Property Sheet.

Property Value Description
Retry Trigger container
Defines how frequently to attempt a failed operation again. This continues until successful execution occurs.

Appears in the Nav tree but not in any manager view and is unique in that it requires no linking of its output for operation.

Getting Started with Niagara documents Retry Trigger properties.

Trigger Mode drop-down list
Determines when a TimeTrigger fires.

Daily fires the trigger at a specific time on selected days of the week, and includes a randomized interval so that the trigger does not fire at exactly the same time every day. Randomized firing is useful when handling large volumes of data.

Interval fires a trigger each time the specified interval elapses. You would use it to fire the trigger several times per day (for example, every 5 minutes).

Manual requires a human to fire a trigger.

When this trigger fires for a station database, a system indexer (LocalSystemIndexer or GlobalNiagaraNetworkIndexer) executes its index operation.
 CAUTION: Indexing a database is a memory- and CPU-intensive operation that affects the availability of your SystemDb and remote stations. Do not configure a re-index to occur too often so your SystemDb and remote stations can maintain availability throughout the day. If your SystemDb is indexed frequently, query performance degrades. 
Last Trigger read-only
Reports when (by displaying a timestamp) the last trigger fired.
Next Trigger read-only
Reports when the trigger is scheduled to fire again.