Index | Prev | Next

Set enabled runtime profiles

Enabled runtime profiles specify what types of N4 software module .jar files to be installed. Enabling these profiles affects the total file space consumed by the installed module .jar files. The wizard preselects this step and sets it to be read-only for any new unit.
  1. Click all module profile types to be installed in this controller:
    Image

    For N4.0, the selection of UX automatically includes WB, and vice-versa. This is likely to change in a future Niagara 4 release.

    • RUNTIME — Always pre-selected and read-only. All Niagara 4 platforms require the base module .jars.
    • UX — Select to support Web client browser access, using HTML5, Javascript, and CSS technologies only (the client does not need to run Java and download WbApplet from the controller).
    • WB — Select (in addition to UX) if the controller must also support browser Web Workbench access from Java-enabled clients, using the WbApplet. If UX (or UX and WB) are not selected, the controller does not support client Web browser access from its WebService—only client access from Workbench via Fox.
    • SE — Not available for QNX-based controllers. For QNX-based platforms (which run the Java 8 compact 3 VM), you may select UX (-ux) and WB (-wb) module . jars, but not SE (-se) module .jars.
    • DOC — Downloads the documentation into the remote controller. Although selectable, this option is not recommended for file space reasons on a controller.

     
    NOTE: Following commissioning, you can also change the enabled runtime profiles, working from the Platform Administration view. For details, see the NiagaraAX Platform Guide.
     
  2. Click the Next button for the next step.

Related Links

  • Controller commissioning (Parent Topic)

    • Index | Prev | Next