After you click Discover in the Obix History Manager to see the lobby, your subsequent initial expansion of the “histories” node in the Discovered pane may take a long time to process, often
several minutes, depending on the number of log objects in the source
R2 station, and particularly how many archives are in a source
R2 Web Supervisor station. During this period, the
Workbench cursor changes to an “hourglass,” and other operations must wait. However, after this initial expansion, the discovered history
tree remains cached in memory—at least until you leave the Obix History Manager view. NOTE: In a few cases involving large numbers of logs or archives, after expanding the histories node, the
Workbench connection to the station was found to timeout and drop. Contact Systems Engineering for assistance in this scenario.
Note that all log objects and archives appear in the Discover pane after a discover—including log objects with identical names.
However, note by default that they are unique by swid/href because of varying locations. It is recommended that you sort (click)
the “Obix Name” column in the Discover pane to ASCII-sort discovered logs by name. This will group any identically-named log
objects together.Although the Obix History Import manager allows you to create multiple import descriptors (with default values) for an identical
Obix Name, note that only one can successfully import using the same History Id. Import descriptors with a duplicate History
Id will go into fault upon import attempt. Therefore, by grouping you can select and edit History Ids appropriately when you
add them to the database.
For example, if you had a station named “RN_Hall”, with several logs each named “RmTemp”, you could edit the second field
of the History Id for each descriptor to make each unique, for example “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.