NiagaraAX’s client/server architecture

The typical internet client/server relationship with a third-party verifying the server becomes a little more complicated when considering the relationships between the various programs (processes) within the NiagaraAX Framework.

NiagaraAX’s SSL implementation is platform based. All SSL Toolset functions can be configured using only a platform connection and without any station running.

Three NiagaraAX programs (processes) require communication protection:

For more information about how the NiagaraAX programs provide NiagaraAX functionality, see Types of NiagaraAX Programs in the Networking and IT Guide.

Figure 18. NiagaraAX client/server relationships


NiagaraAX client/server relationships

Figure 18 illustrates the possible client/server relationships within the NiagaraAX Framework:

  1. Workbench station (client) connected to JACE station (server) using secure Fox Service.

  2. Workbench (client) logged in to a JACE platform (server) using Niagarad (platform connection).

  3. JACE station (client) connected to a Supervisor station (server) using secure Fox Service.

  4. Supervisor station (client) connected to a JACE station (server) using secure Fox Service.

  5. Web browser (client) connected to the station (server) using Https.

  6. Station (client) connected to the remote Supervisor (server) (Http).

  7. JACE station (client) logged in to another JACE station (server) using secure Fox Service.

  8. Supervisor station (client) connected to a station (server) using Https.

NoteEach JACE in figure Figure 18 has all the same connections to Workbench and the Supervisor as the other JACE. For simplicity the illustration uses each to demonstrate the nearest connections (nearest in the drawing).