To access a device’s Sedona app via a Sedona device’s Sox Gateway, do one of the following:
In the property sheet of the Sedona device, simply click the Sox Gateway slot.
or, expand a Sedona device in the Nav tree, and double-click the Sox Gateway node.
Either method produces the Sedona property sheet view for the app in the device (Figure 27), as the entrance to its “Sox gateway space”.
Once this Sox gateway session is active, you can navigate the app by expanding it in the Nav tree, just as in a regular direct (or tunneled) Sox connection to the device (Figure 28).
That concludes the “usage portion” of the Sox Gateway, with a few added technical notes as follows:
The Sox Gateway uses the same credentials from the Credentials property in the parent Sedona device to authenticate the connection. If those credentials are invalid, the gateway connection fails.
The Sox Gateway keeps the underlying Sox connection open until all the following are met:
There are no views/subscribers to any Sedona component in the Sox gateway space.
There are no expanded nodes in the Nav tree for Sedona components in the Sox gateway space.
Once both conditions above are met, after a brief period, the Sox connection automatically closes.
Sox connections are considered “expensive” on both the client side (JACE) and server side (Sedona device). Therefore, the
recommended practice is for you to fully navigate away from the Sox gateway space when done.
Copyright © 2000-2014 Tridium Inc. All rights reserved.