In the discovered pane of the Obix Point Manager, expand the root “lobby” to see the tree organization, as shown below. Items
of practical interest for proxy points are under the “config” branch.
Figure 18. Top-level lobby structure in
R2 station
Expand the “config” branch of the lobby to find proxy point candidates. The config hierarchy reflects the
R2 station’s object hierarchy, including a row for each object property, and expandable rows for child objects. The highest-level
config node is the Station object. So when you first expand config, at the top are the properties found on the various tabs
of the property sheet for the Station (when using the
R2 JDE).
Figure 19. ObixPointManager with lobby expanded to show discovered proxy point candidates
NOTE: As needed, click on column headers in the Discovered pane to sort as ascending

or descending

, in ASCII character order. For example, if you have the Obix Name column sorted ascending, when you expand items containers
will be at top, and properties at bottom, as shown.
Figure ?. Use column header sorts and expand containers as needed to find
R2 objects and properties
R2 container objects appear in the discovered lobby as expandable gray rows (Figure 2-11), which you can add as Obix Point Folders
by double-clicking. See “About Discover “Include” options” on page 2-10.
Typical expandable target containers contain
R2 “shadow objects” or related objects in the
R2 station—often the same objects that are linked to
R2 Gx objects in GxPages for real-time values and commands.
NOTE: Although each discovered object is available as a “root” node, you should always expand discovered objects to specify a property
for any proxy point. For related details, see “Specify the property” on page 2-11.