Starting in Sedona TXS-1.2 (with AX-3.7 and later), usage of Sox tunneling is typically bypassed in favor of “Sox Gateway” and “Sedona Tools” access to networked Sedona devices. Workbench is not the Sox client in this case—instead, the hosting JACE/station acts as Sox client, using “Sedona environment files” on that host platform. This provides the same benefits as Sox tunneling, as well as other advantages.
For related details, see the Sedona Framework TXS 1.2 Networks Guide sections “Sox Gateway” and “Sedona device ‘tools’ views”, as well as the “Sedona environment management” appendix that explains the necessary platform configuration to support such access.
Regardless if Sedona TXS 1.2 or TXS 1.1, Sox tunneling is not required if you have direct access to a Sox device’s network. In that case you can make a direct (Workbench client) Sox connection to the device.
Copyright © 2000-2014 Tridium Inc. All rights reserved.