Alphabetically, application types listed here include box, crypto, eas, email, fips140-2, genericAppliance, ieee8021x, ldapv3, mobile, provisioning, sedonaProvisioning, sox, station, tenantBilling, web, and workbench. However, applications station, web, and workbench have special importance, and are summarized first.
Enables a station to be run, and is typically present in any JACE platform, as well as a Supervisor.
<feature name="station" expiration="2014-03-31" resource.limit="none" guestEnabled="true" parts="AX-DEMO"/>
The station feature may not be present in a license for an engineering workstation (PC), unless specifically ordered with it.
resource.limit="none" - If the resource.limit flag is specified (in kRUs), then the station displays a warning on startup if the actual resource
units exceed the limit resource units. If the limit is exceeded by 110% then the station will not boot at all. This limit
is normally only specified on SoftJACE license files.
guestEnabled="true" - (AX-3.8 only) Must be present and true, or else the station’s UserService has its built-in user “guest” hidden upon first
station start up, as a security measure. Only hosts licensed as “demo hosts” in AX-3.8 can enable and use the guest user—thus
it is unavailable on any host with a “non-expiring” license.
The web feature must be present to start the WebService in a running station (to access the web server via an HTTP connection). If not licensed, the server is set to fault with appropriate faultCause. If the feature is enabled, then WebServlets and spy pages are always available.
Full Workbench can connect to a station (via Fox connection) even if the web feature is disabled.
<feature name="web" expiration="never" ui="true" ui.wb="true" ui.wb.admin="true" parts="AX-DEMO"/>
ui="true" - If the ui flag is false, then all access to ServletViews via "/ord" are disabled (with exception to spy pages).
ui.wb="true" - If the ui.wb flag is false, then all user accounts using an WbProfile are disabled (including thin client views, but with
exception to spy pages). Only thin client accounts operate when ui.wb is false; other accounts do not automatically degrade.
Views which aren't licensed return 403 Forbidden.
The workbench feature must be present to start the full version of Workbench (for example, a copy of Tridium's Niagara Workbench or an OEM-specific Workbench-based application). If the admin flag is false, then all views requiring admin access are unavailable. This feature is included for PC platforms only, with the sole exception of a SoftJACE.
<feature name="workbench" expiration="never" admin="true" parts="AX-DEMO"/>
This enables an AX-3.7 or later host for Bajascript, a Javascript API (read and write) for Niagara data access from Javascript enabled environment like web browsers. Along with the mobile feature, this license feature is required for mobile application support.
<feature name="box" expiration="never" session.limit="none" parts="ENG-WORKSTATION"/>
Enables SSL (Secure Socket Layer) operation.
<feature name="crypto" expiration="never" ssl="true" parts="SP-SSL"/>
Although the crypto feature is used to license SSL connectivity in any NiagaraAX release since AX-3.3, note the SSL implementation changed completely in AX-3.7—for example, the crypto module is no longer used. See the sections below for more details.
Starting in AX-3.7, SSL and TLS (Secure Socket Layer and Transport Layer Security) architecture in NiagaraAX changed to a “platform based” foundation, with certificates and exemptions accessed and managed using platform based tools. SSL connections are now possible for all NiagaraAX connectivity, including platform connections, station (Fox) connections, and web browser (WebService) connections. For complete details, refer to the NiagaraAX SSL Connectivity Guide.
Prior to AX-3.7, SSL (Secure Socket Layer) connectivity in NiagaraAX used a “station based” model, with an associated “CryptoService”
from the crypto module. Only web browser access of a station using Hx profiles could effectively use SSL. For details on this outdated architecture,
refer to the Engineering Notes document NiagaraAX CryptoService (SSL).
This feature enables the Energy Suite application and the associated reports, data points and meters.
<feature name="eas" expiration="never" allCostReports="true" allE2Reports="true" brand="MyBrand" costMeter.limit="none" dataPoint.limitt="none" parts="AX-DEMO"/>allCostReports="true" - If set to “true" all Cost Profiler Reports are enabled. When set to "false" there are additional feature items for each of the specific Cost Profiler Reports that are enabled.
allE2Reprots="true" - If set to “true" all E2 Profiler Reports are enabled. When set to "false" there are additional feature items for each of the specific E2 Profiler Reports that are enabled.
costMeter.limit="none" - Designates the maximum number of Cost Profiler Meters that may be configured in the VES Application, where “none” means unlimited.
This features enables the NiagaraAX station to send email messages to an SMTP server. If the feature is not present then the service and all its incoming and outgoing accounts are marked as fault. No email can be sent or received if not licensed.
<feature name="email" expiration="never" parts="AX-DEMO"/>
This features enables an AX-3.8 NiagaraAX station to operate in “FIPS 140 Mode” (Federal Information Processing Standard 140) using cryptographic software fully compliant with FIPS 140-2. A special FIPS distribution must be installed on the host.
<feature name="fips140-2" expiration="2014-03-13" lib="entrust" parts="PROTO-FIPS"/>
This feature enables the NiagaraAX Generic Appliance Application.
<feature name="genericAppliance" expiration="never" vendor.name="" parts="GA-GENERIC"/>
This feature enables an AX-3.8 “Hotspot” QNX-based JACE (JACE-3,-6,-7) to be able to join a wired IEEE 802.1X wired-authentication network.
<feature name="ieee8021x" expiration="never" parts="PROTO-8021X"/>
This feature enables an AX-3.8 host to use the LdapV3UserService or LdapV3ADUserService in place of the standard baja UserService.
These LDAPv3-compatible user services are available in the AX-3.8 ldap module, in addition to the former LDAPv2-compatible user services (which require no license feature).
If the kerberos attribute is “true”, the AX-3.8 host is licensed for Kerberos authentication with LDAPv3.
<feature name="ldapv3" expiration="never" kerberos="true" parts="ENG-WORKSTATION"/>
Refer to the NiagaraAX LDAP / Active Directory Guide for complete details.
This enables an AX-3.7 or later host to support the NiagaraAX Mobile application framework, for station support of web browser access from mobile devices like cell phones or tablets. The host also requires to be licensed with the box feature for Bajascript support.
<feature name="mobile" expiration="never" history="true" schedule="true" alarm="true" px="true" propsheet="true" parts="ENG-WORKSTATION"/>
Enables the operation of NiagaraAX host provisioning, typically used to automate routine maintenance of a NiagaraAX system such as JACE software upgrades, file distribution and backups. It applies to an Supervisor platform only. Provisioning uses the BatchJobService and a “network extension model” (e.g. a “ProvisioningExt” under the NiagaraNetwork), sourced respectively from modules batchJob and provisioningNiagara.
<feature name="provisioning" expiration="never" parts="AX-DEMO"/>
Required by a Workbench host to provision Sedona Framework devices, including operations Get App, Put App, Manage Kits, Backup App, and Restore App.
<feature name="sedonaProvisioning" expiration="never" parts="AX-DEMO"/>
Required by a Workbench host to open a Sox connection to a Sedona Framework device. Sox is the native protocol used to either program the App in the device, or to perform device provisioning.
<feature name="sox" expiration="never" parts="AX-DEMO"/>
Enables the NiagaraAX Tenant Billing Application.
<feature name="tenantBilling" expiration="never" tenant.limit="none" parts="S-TBS-AX"/>