Fox service
The NiagaraNetwork's Fox Service holds configuration properties for the local station's Fox settings. Some of these settings can affect traffic between the local station and other stations. Often in a multi-station job, in each station you create a user account specifically for station-to-station communications, with an assigned profile type of “super user.” This is the account that you reference when you edit a NiagaraStation's Client Connection properties, entering its username and password.
The Fox Service also has a Server Connections container slot with a default ServerConnectionsSummary view. Client connections to the station's Fox server are dynamically modeled as “SessionN” child components. The summary view allows you to see all current connections, and if necessary, perform a right-click Force Disconnect action on one or more connected users.
Fox Service properties are shown in Figure 4-5 and completely described in the User Guide.
Figure 4-5 Fox service
The Fox service parameters that are more likely to significantly affect network traffic are mentioned below:
Max server connections
This property limits the number of server connections that are allowed on the local station. When the maximum number of connections is reached, any successive attempts to logon to the station will fail. The default setting is 100 sessions. Adjust this parameter, as needed, to fit your requirements.
Trace settings
The four Trace components allow you to return all message activity (verbose) on those parameters you set to True. This includes all transactional messages, which may result in too many messages to be useful. Increasing station output by assigning trace levels consumes extra station resources and exacts a performance penalty.
Note: Be careful using Trace! After troubleshooting, remember to return log levels to default values.