OTA configuration (otasettings.xml)

Open the otasettings.xml file with a text editor of your choice. Preferably, you can use a dedicated XML editor, as the Senseforce Edge XML files are supported by a rich set of XML schemas, allowing configuration validation inside the editor.

Example configuration

Mandatory settings

Setting	Description
IsActive	Set to true, if the edge instance should be controllable over the air.
ServerUrl	Url of the over the air server. Contact Senseforce for your server details.
Username/Password	Username and password to authenticate with the OTA server. Contact Senseforce for your credentials
InstanceIdentifier	Identifies your machine in the Senseforce OTA manager. The following format is required: tenant/machineIdentifier. If your company is called MyCompany at Senseforce and your machine is called Machine1, use the following InstanceIdentifier: MyCompany/Machine1

<?xml version="1.0" encoding="utf-8"?>
<OtaSettings xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
             xsi:schemaLocation="https://senseforce.io/ configurations/Schemas/otasettings.xsd">
	<!--
		If true a connection to an OtaServer will be establsihed and the application can
		be controlled remote from the Senseforce platform.
		-->
	<IsActive>true</IsActive>
	<!--
		The url to the ota server.
		-->
	<ServerUrl>https://jupiter.senseforce.io:8080/hubs/ota</ServerUrl>
	<!--
		This is the username which will be used along with the password to authenticated against the server.
		Each user can have multiple globally unique instances assigned. Each of this instances is identified by a
		instance identifier. This instance identifier must be unique along all globally available instance identifiers.
		Choose wisely.
		-->
	<Username>username</Username>
	<Password>password</Password>
	<InstanceIdentifier>tenant/thingId</InstanceIdentifier>

  
  <!--<Proxy>
    <Address>http://139.5.71.80:23500</Address>
    <BypassOnLocal>false</BypassOnLocal>
    <Domain></Domain> <!-- Optional Proxy server domain -->
		<Username></Username> <!-- Optional Proxy server user name -->
		<Password></Password> <!-- Optional Proxy server password -->
  </Proxy>-->

	<!--
		If true all filesystem actions are limited to the core directory.
		-->
	<EnsureAllFilesystemTasksAreCoreRelative>true</EnsureAllFilesystemTasksAreCoreRelative>
	<!--
		Here you  can define tasks which are forbidden on this client (blacklisting).
		-->
	<ForbiddenTasks></ForbiddenTasks>

	<Logger>
		<FilePath>$(LunaAppDataPath)Logs</FilePath>
		<FileName>ota.log</FileName>
		<!--LogLevel: Debug,Information,Warning,Error,Critical,None-->
		<LogLevel>Debug</LogLevel>
	</Logger>
</OtaSettings>

Advanced settings

Setting	Description
Proxy	Define proxy server address and optional domain, username an
EnsureAllFilesystemTasksAreCoreRelative	If set to true, the edge software only operates on file paths inside the edge configuration or binary path. Set to true.
ForbiddenTasks	Defines in a comma-separated list which tasks can't be executed. Possible entries are: System operations CopyDirectory CopyFile DownloadFile ListDirectoryContent ReadFile RemoveDirectory RemoveFile WriteFile Luna config operations ReadLunaLogsAndPluginConfigurations ReadLunaPluginConfiguration ReadLunaPluginMapping WriteLunaPluginConfiguration WriteLunaPluginMapping Luna plugin operations GetAllPluginStates GetPluginState StartPlugin StopPlugin Luna operations ShutdownLuna StartLunaAgent StopLunaAgent UpdateLuna Utility operations ConsoleBeep GetPerformanceIndicator UnzipFile To each entry also the suffix "Task" has to be added.

For further details on the Logger-section see

Edge Logging

2KB

otasettings.xml

Example otasettings.xml