About Platform Services
Under its Services container, every Niagara station has a PlatformServices container.
Figure 7. Example JACE 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