Platform Services
This section explains the platform access available in a running station—in other words, the station’s perspective on its
host platform. Unlike the various platform views, a platform connection is not needed to access platform services. Instead,
you need only a standard station (Fox) connection.
Under Config, Services, every running station has a PlatformServices container, which any station user, with admin-level permissions to this component, can access.
Figure 88. Example JACE station’s PlatformServices
Platform services in a running station provide two main types of functionality:
- A subset of platform views available in a platform connection. Platform services does not provide the full set of functions available in a platform connection. For example, you cannot install or upgrade software, or transfer stations and files. However, a number of platform configuration views are available under a station’s PlatformServices.
- Certain platform configuration settings accessible only through PlatformServices—that is, not available in a client platform
connection.NOTE: When you are working to design station security, be careful about assigning user permissions to PlatformServices and its child service components. In general, you should regard this portion of the station as most critical, as it allows access to items such as host licenses and TCP/IP settings. Furthermore, right-click actions on the PlatformServices include “Restart Station”. For related details, see the Niagara Station Security Guide.
PlatformServices and all child components are unique from all other station components.