Setting the enabled runtime profiles

Enabled runtime profiles specify what types of N4 software module JAR are to be installed, as shown in the following image. This affects the total file space consumed by the installed module JAR files.
Image

All Niagara 4 platforms require the base “RUNTIME” (-rt) module JARs, so it is pre-selected/read-only.

For QNX-based JACE platforms (which run the “Java 8 compact 3” VM), you can also select “UX” (-ux) and “WB” (-wb) module JARs, but not “SE” (-se) module JARs. Note that following commissioning, you can also change the enabled runtime profiles, working from the Platform Administration view. For details, see “ the Niagara Platform Guide.

At the Enabled Runtime Profiles step:


Perform the following steps:
  1. Click all module profile types to be installed in this JACE controller, which include one or more of these:
     
    NOTE: For N4.1, the selection of UX automatically includes WB, and vice-versa. This is likely to change in a future Niagara 4 release.
    • RUNTIME — Always selected. Note if UX (or UX and WB) are not selected, the JACE will not support client Web browser access from its WebService—only client access from Workbench via Fox.
    • UX — Select to support Web client browser access, using HTML5, Javascript, and CSS technologies only (client does not need to run Java and download WbApplet from JACE).
    • WB — Select (in addition to UX) if the JACE must also support browser “Web Workbench” access from Java-enabled clients, using the WbApplet.
    • SE — Not available for QNX-based JACE controllers.
    • DOC — Selectable, but not recommended for file space reasons on the JACE controller.

     
  2. Click the Next button for the next step.