Importing oBIX histories
As with device objects in a few other drivers, each ObixClient device has a Histories extension that serves as the container for history import descriptors. The default view for each is a History Import Manager. You use this view to add history imports, which create histories in the local station with data imported from the oBIX server.
Prerequisites: You have added an ObixClient.
- Locate the row in the Client Manager view that represents the device for which import histories are available and double-click the Histories icon (
) under the Exts column.The Obix History Manager view opens. - Click the Discover button in the history manger.An oBIX history discovery job launches, after which an expandable Lobby node appears in the Discovered pane. After the discovery job runs, all log objects and archives appear in the Discoverd pane. This includes log objects with identical names. However, by default their swid/href, which give them varying locations, give them unique names.
- To sort the discovered logs by name, click the “Obix Name” column in the Discovered pane. This groups identically-named log objects together.
- Expand the root Lobby to see the tree organization.Items of practical interest for histories are typically under a Histories branch, and appear with a History icon (
).
- To add a history import descriptor, double-click a history.The Add window opens.
- Enter its
NameandHistory Id, as well as itsExecution Scheduleand (local) collection properties, and click OK.This adds the import descriptor to the database, where it is visible in the Database pane of the view, showingnullas last success. - To archive locally (create the local history), click to select one or more import descriptors, then click the Archive button.
- Continue to add history import descriptors as needed under the Histories extension of each client device.
- To edit one or more existing import descriptors, double-click the descriptor row in the table.The Edit window opens.
This window is similar to the New window used to create the descriptors. Common properties to edit are
Execution Times.NOTE: An additional device extension Alarms may also exist under an ObixClient.
Although you can create multiple import descriptors (with default values) for an identical Obix Name, only one can successfully
import using the same
History Id. Import descriptors with duplicate History Ids go into fault upon N import attempts. Therefore, by grouping you can select
and edit History Ids appropriately when you add them to the database.
For example, if you have a station named “RN_Hall”, with several logs each named “RmTemp”, you could edit the second property of the History Id for each descriptor to make each unique: “Zn1_RmTemp”, “Zn2_RmTemp”, and so on. This way, complete History Ids for each would be “RN_Hall/Zn1_RmTemp”, “RN_Hall/Zn2_RmTemp”, and so forth.