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.
-
Changes you make to PlatformServices and all child services are not stored in the station database. Instead, changes are stored in other files on that platform, such as its
platform.bogfile, or within the platform’s operating system.
Do not attempt to edit platform.bogdirectly; always use PlatformServices’ views!
In summary, when you make changes under a station’s PlatformServices, those changes are independent of the running station. If you install another station, platform services are dynamically recreated again when the new station starts, based upon the last settings.
In addition, understand that some changes in platform services views may require the host to be rebooted to become effective. Examples include TCP/IP changes, or some NTP-related changes in a QNX-based JACE. A “Reboot Now?” popup dialog appears upon saving such a change.