Platform tunneling works independently from Fox tunneling. Typically, if a job uses tunneling, both Fox tunneling and HTTP tunneling are already enabled.
However, note that one FoxService property on the Supervisor (proxy tunnel server) affects platform tunneling. That property is shown highlighted in Figure C.3.
On the Supervisor, expand its
Config,
Drivers, nodes to reveal its
NiagaraNetwork, then right-click to select ->. Expand the
Fox Service container, and scroll near the bottom of its contained
properties.
Tunneling Enabled
Can be either true or false, it affects Fox tunneling only (not platform tunneling). If Fox tunneling is already enabled, this should already be true.
Only Tunnel Known Stations
May be either true or false. This property was first introduced in AX-3.4.
Depending on its setting, this affects the ability to open a tunneled platform connection, including how you enter the target (JACE) host in the Open Platform dialog:
If false, you can tunnel a platform connection to any AX-3.5 or later JACE that is reachable from the Supervisor station, using the
target IP address (or hostname) of that JACE.
If true, you can tunnel a platform connection only to a JACE that is currently represented in the Supervisor’s NiagaraNetwork. Here, you use its station name as the target destination—not the JACE’s IP address or hostname.
Note this property was originally for Fox tunneling, and works in the same manner. However, it is a bit more “intuitive” in Fox tunneling, where you equate Fox connections and stations.
Copyright © 2000-2014 Tridium Inc. All rights reserved.