The $Server Node item in the Tree View is used to group all the configuration items in an application.
Based on the application, it is possible for different options to be available in the $Server context menu when right-clicking.
Table of Contents |
---|
Manage License
Some applications are required to be licensed.
To manage the license, right-click the $Server > Manage License
The Manage License window will show.
If no License is active, you will see a No License message, otherwise you will see an expiration date.
License Request
To download a license request, right-click the $Server > Manage License
You can click the Download License Request button to download a file which contains specific information that AUTOSOL will use to generate a License for your installation. Contact AUTOSOL with this file in order to get more information.
Upload License
To upload a LICENSE, right-click the $Server > Manage License > Click Browse
You will need to browse to an LICENSE that you have previously obtained from AUTOSOL.
Once the file is loaded, the Upload new License button will become available.
Click Upload new License. The LICENSE will be applied to your application.
Options
All $Server items in all applications should have an Options menu. Administrative options for the whole application will appear here
Configuration Import/Export
One of the available options is the ability to import/export all configuration for the application.
Export
To Export, right-click the $Server > Options > Click Download Export
You will get a file named export.json
You can re-import this file to this install later, use it as a backup, or import onto a different installation.
Import
To Import, right-click the $Server > Options > Click Browse
You will need to browse to an export.json that you have previously obtained.
Once the file is loaded, the Import button will become available.
Click Import. The configuration will be applied to your application.
Note |
---|
The Import function currently wipes and replaces all existing application configuration data with the data contained in the uploaded export.json file |
...
It is also used to connect the Edge device to the Universal App Manager. It is configured by right clicking and selecting Properties.
Table of Contents |
---|
General
...
Name
This name should be a unique identifier for this Edge device as it will be used in the Tree View of the Edge Manager and Universal App Manager.
Compress MQTT Payload
This determines if configuration data sent over MQTT is compressed or sent in plain text. It is advised that you keep this enabled unless troubleshooting.
MQTT
...
This is where we set up the Broker connection used for the Universal App Manager. These settings will not be used to publish data from Edge ACM, only to remotely configure the system.
Connection Retries
The number of attempts to reconnect to the current broker. If -1 it will attempt to reconnect to the first broker on the list indefinitely.
Connection Retry Interval (ms)
The ammount of time to wait between retries of your broker connection.
Brokers
The brokers that have been added to your system. Using the + button will add a broker to the list.
Enable Broker
Determines of the Node will attempt to communicate with the broker.
Note: if the Connection Retries are set to -1 the node will only ever attempt to communicate with the first enabled broker.
Broker IP
The IP address of the MQTT Broker
Broker Port
The port of the MQTT Broker, default 1883
Keep Alive
The maximum time between messages to the MQTT broker. If the broker does not hear from the node in that time, a node death will be published.
Delete
The trash can icon will delete the broker entry.
Info
...
Information on the device you are currently connected to.