Local Agent
Local Agent device driver effectively makes Iotellect Server to act as an Agent. It collects entities (variables/functions/events) from other local devices and/or system resources and exposes those entities to another Iotellect Server by connecting to it as an Agent.
 | On the side of another server (data recipient), communications are handled by Agent device driver which is a "peer" of Local Agent driver. |
Driver Information
Driver Plugin ID: | com.tibbo.linkserver.plugin.device.agentconnector |
Global Settings
None defined.
User Level Settings
None defined.
Device Account Properties
Connection Properties
Connection settings define how Local Agent communicates with a remote Iotellect Server:
Property | Description |
IP Address or Host Name | Address of remote Iotellect Server. |
Port | Port number to connect to. Should match Port number to listen for Agents global setting of the Agent device driver on the remote server for non-secure connection. Should match Port number to listen for secure Agent connections global setting of the Agent device driver on the remote server for secure connection. |
Use Secure Connection | Establish a secure SSL connection to above specified address and port. |
Use Data Compression | Use ZLIB compression to communicate between Agent and Iotellect Server. |
Owner | Name of user owning remote Agent device account. |
Name | Name of remote Agent device account. |
Password | Password defined in the remote Agent device account. If LDAP authentication and an LDAP login were specified on the remote Agent device, provide the LDAP password corresponding to the login. |
Certificate Trust Policy | Defines how to verify certificates provided via an SSL/TLS connection. |
Certificate | Alias of an SSL/TLS certificate to use for authentication. The certificate with that alias must exist in the Client Certificate storage of the Iotellect server. |
Send Updates Asynchronously | Any setting updates will be delivered immediately, there is no need to wait for the next synchronization cycle. |
Buffer Device Events | In case of Iotellect Server reboot, connection failure or similar issues delivering events can fail. Event buffering will accumulate undelivered events and will resend them once the connection is reestablished. |
Undelivered Events Expiration Period | Period after which an undelivered event will be erased from the Event Buffer, thus will not be sent on next connection. |
Pending Events Queue Capacity | When a mapped events rate is higher than Device can send, events are put at the special Pending Events Queue. It's maximum length is limited by this number. |
Maximum Command Executor Threads | Maximum number of command executor threads. This parameter is used to limit the Agent command execution pool. |
Send Keepalive Messages | Whether to send keepalive messages. |
Command Timeout | Maximum time to wait for a reply to an Iotellect protocol command. |
Exported Entities
This table defines what entities (variables/functions/events) will be exported to the remote Iotellect Server.
Property | Description | |
Context Mask | Mask of contexts those entities will be exposed by the remote Agent device account. | |
Group | Base group of entities (variables/functions/events) that will be exposed by the remote Agent device account. | |
 | If you need to export variables added by relative model the Group value should follow the format: custom|[model_name]|[variable group]. | |
Device Assets
Assets are not supported by the driver.
Device Settings
Local Agent's device setting variables are variables exposed to the remote server. However, their local editing is senseless, since they're just mapping variables of local contexts being exported.
Device Operations
Local Agent's device functions are functions exposed to the remote server. However, their local calls are senseless, since they're just mapping functions of local contexts being exported.
Device Events
Local Agent's device events are events exposed to the remote server. However, their local subscription and processing is senseless, since they're just mapping events of local contexts being exported.
Connection Handling
This driver makes the device Online if the connection to the remote server is established.
| The success or failure of remote Agents to authenticate on the local agent is not reflected in the connection status. The local Agent will remain in connected status even if the remote Agent is trying to use incorrect authentication credentials. |
| Local Agent device driver supports Agent auto-registration. The remote server will automatically create an account for this Agent upon first connection if the Automatically register device accounts for new Agents setting is enabled in the global configuration of Agent device driver on the remote server. |
Device Status
Additional status variable is provided by the driver:
Performance Metrics
Property | Description |
Pending Events Count | Displays how many events are in pending in Events Queue to be sent. |
Synchronization Details
The Local Agent driver doesn't read anything from the remote server. Instead, it sends requested variable values to the remote server, forwards their updates, serves incoming calls of exposed functions, and forwards exposed events.
Was this page helpful?