Application Management

The Applications View provides a list of all defined Customer Applications, with controls for provisioning new or modifying existing.

The view can be customized by pinning statistics cards for up to three separate apps, as well as changing the columns shown in the table.

Join Statistics

Join success and error statistics are also included in the table to assist in troubleshooting potential Application Device issues. These are hidden by default, but can be set to visible in the table settings dialog.

Application Provisioning

Creating an Application requires the following information:

Field Descriptions

Field	Description
Application EUI	A unique identifier; may be based on Customer's OUI
Name	A human-readable identifier
Join EUI	A unique identifier that will default to the same value as the Application EUI but may be set manually as needed
Notifier Type	The default setting will include all northbound traffic for the entire application for each configured Notifier
Account	A value that should be set to the Customer's account as appropriate. Defaults to the Operator's Account
Default Contract	The Contract that will be used by default for Devices associated with this Application. Available values are determined by the selected Account.
Contracts	Contracts that will be associated with this Application
Application Payload	Options for database storage treatment of the Application payload field of Device uplinks Available options are Store Encrypted, Store Decrypted and Do Not Store.
Display AppCmds In Details	A true or false value to toggle display of Application Commands for protocols such as Application Clocksync, Fragmentation, Firmware Management, etc. in the message field of Base Station and Device events. The field checkbox is only enabled if the Application Payload option is set to Do Not Store or Store Decrypted.
Mode	Options to Enable, Disable the Application or to set it to Listen Only. These options control whether the Application forwards Device traffic or processes data without forwarding.
Allow Traffic on LVN	A true or false value to toggle forwarding Application traffic on the LoraWan Virtual Network. When false, the Application operates on a private network.
Network ID	A 24-bit number that identifies the LoRaWan network that will carry Application traffic.
Default Device Profile	The named LoRaWAN settings configuration that will be used by default for Devices associated with this Application.
Tags	One or more comma separated strings that can be used to identify the Application.
Description	A user-defined string that provides custom details about the Application.

Join Servers

When an Application is created, a new Join Server is created unless the Join Server is created separately and manually associated with the Application.

Join Servers provisioned in conjunction with Applications can be accessed by changing the table's focus in the upper left hand of the view. Columns displayed for this table can be customized as well.

New Join Servers are added with the Create Join Servers dialog. To add a new Join Server, click the button at the top of the table and fill in the required information.

Join Servers are modified using the Edit Join Servers dialog. Some fields cannot be modified once a Join Server is created and are disabled when editing. Click the button to edit a Join Server.

Join Servers may also be removed if necessary. Click the button to remove the selected Join Server. A confirmation dialog is displayed to verify that the deletion is desired.

Field Descriptions

Field	Description
Join EUI	The unique 16 hexadecimal character identifier for the Join Server.
Name	A user friendly name for the Join Server.
Mode	The configured status of the Join Server, Enabled or Disabled.
Account	The account that the Join Server is linked to. This impacts visibility of the Join Server for Application Providers.
White List	A list of Device EUIs or EUI patterns that indicate which Devices are allowed to connect to the Join Server
Join Server Types	Join Server types are discrete Join Server implementations with variations in connection requirements.
Tags	Informational text added to the Join Server model to facility search and identification.
Description	User defined text that provides helpful information about the Join Server.

Application Notifiers

Application Notifier behavior can be configured to apply to all Devices on an Application, a combination of Application and Devices or exclusively to Devices (Notification Targets are assigned directly to Devices). Applications can also be configured to forward Layer 2 uplinks.

Application Alerts

Application Alerts can be enabled or disabled for an Application during creation or edited later. The Alert configuration settings are presented in a sub-tab of the Create/Edit Application dialog.

Alert Settings

Setting	Description
Minimum Notification Threshold	This is the minimum number of northbound notifications that must be sent. If the number of northbound notification falls below this threshold, an Application alert will be raised.
Maximum Notification Threshold	This is the maximum number of northbound notifications that should be sent. If the number of northbound notifications exceeds this threshold, an Application alert will be raised.
Maximum Dropped Notification Threshold	This is the maximum number of allowed dropped northbound notifications. If the number of dropped northbound notifications exceeds this threshold, an Application alert will be raised.
Maximum Errors Threshold	This is the maximum number of northbound notifications that can result in an error response. If the number of error received in response to northbound notifications is exceeded, an Application alert will be raised.
Period Before Registration 2FA Token Expiration Alerts (ms)	The time in milliseconds before a Registration token expires that Application alerts will start being raised to warn of the approaching expiration. This setting is only available for Extended or Unlimited Use tokens.

Application Feature and Port Configuration

Multicast and FUOTA can be enabled or disabled for an Application in the Feature and Port Protocol Configuration tab. Additionally port and protocol version can be set for each of the 5 supported protocols. These settings are hidden by default, but are displayed by clicking on the Advanced toggle button .

Deleting an Application

An Application can be deleted by selecting a row and clicking on the button. The user must type the Application EUI to confirm the delete. Only one application can be deleted at a time. Deleting an application will also delete the join server if the join server is not shared. An application cannot be deleted if a registered device or joined device is using it.

Authentication Token Management

From the Applications table, select a row and click the button to edit an Application's Two Factor Authentication Token settings. The edit dialog shows the status information for the most recently issued token and allows changing settings for future tokens.

These can also be edited from the Application details view.

Field Descriptions

Name	Description
Token Use Count	The number of times a token can be used for registration before it expires. The Unlimited option allows unlimited token use until it expires.
Token Time to Live	The amount of time the token is valid until it expires. A preview of what the expiration date will be is provided below that to help determine exactly when the token will expire.
Current Token Information	Describes the current outstanding token. If one has not been generated yet, then this section will be blank.
Auth Token	Displays a masked version of the current token.
Status	Indicates whether the token is still valid or not.
Generated	The timestamp of when the token was generated.
Expires	The timestamp of when the token will expire.
Last Used	The timestamp of when the token was last used.
Uses Remaining	The total number of uses remaining before the token expires, unlimited means there is no limit.