Platform services (station) and administration

A few platform configuration items in the JACE are not directly accessible in the Workbench platform connection to that controller—that is, via the Commissioning Wizard or any of the platform views. Instead, you must have a station installed and running on the controller (any station).

Then using Workbench, you open a (Fox) connection to that station, and configure these platform-related items by accessing services under the station’s PlatformServices container. Under its Services container, every station has a PlatformServices container.

NOTE: In Niagara 4.8 and later, there is added support for the IEEE 802.1X wired authentication standard for JACE-8000 and Edge platforms. For more details, see the Niagara IEEE 802.1X Configuration Guide.

Figure 9. Example controller station’s PlatformServices

PlatformServices is different from all other components in a station in the following ways:

It acts as the station interface to specifics about the host platform (whether JACE or a PC).
It is built dynamically at station runtime—you do not see PlatformServices in an offline station.
Any changes you make to PlatformServices or its child services are not stored in the station database.
Instead, changes are stored in other files on the host platform, such as its platform.bog file.

NOTE: Do not attempt to edit platform.bog directly; always use PlatformServices’ views.

Included services are a TcpIpService and LicenseService, providing station (Fox) access to dialogs used in platform views, for instance the TCP/IP Configuration. These services support installations where all configuration must be possible using only a browser connection (and not Workbench connected to the JACE’s platform daemon).

Platform services (station) and administration

Figure 9. Example controller station’s PlatformServices

Related Links