"createInput"
JSON hub "createInput" action creates a new FairCom Edge input
The "createInput" action creates a new input. It configures a service to collect tags from a data source and insert those tags into an integration table.
Note
A tag is a piece of named data with an associated value. For example, the tag temperature 70 includes both the named data temperature and the value 70. In JSON, a tag is a JSON property, such as "temperature": 70. In a SQL table, a tag is a data field, such as a field named temperature with a value of 70.
An input is a service that collects data using a protocol to an integration table in the FairCom server.
For example, the OPC UA service can collect data from an external OPC UA source and write that data to an integration table in FairCom Edge.
An input is a mapping from a service to an integration table.
The action,
"createInput", is the only way to create this mapping. If the mapping already exists, this action returns an error. To modify an existing input, use the"alterInput"action.Each input, typically, has its own dedicated integration table, but multiple inputs may insert records into the same integration table.
An input can be mapped to only one integration table, however:
Different inputs can be created to map the same service to different integration tables.
A transform can optionally extract data from the integration table and write this data to another integration table.
When an input is created, if the specified integration table does not exist, FairCom Edge creates it.
An input can only insert records into an integration table because an integration table is designed to be a historical log of data collection events.
An input always and only writes data to the
"source_payload"field of a newly inserted record.Transforms can take data from the
"source_payload"field (or from other fields in the table), transform it, and place the results in other fields, such as user-defined fields.
Request example
Minimal request
{
"authToken": "PPnssHDPSSoDlVGZGEYFNehVmI1R8jTvbwhv25DGbKORXETW0iUqPGZwmaW469Gc",
"api": "hub",
"action": "createInput",
"params": {
"inputName": "modbusTCPOne",
"serviceName": "modbus",
"tableName": "modbusTableTCP",
"settings": {
"modbusProtocol": "TCP",
"modbusServer": "127.0.0.1",
"modbusServerPort": 1505,
"modbusDataCollectionIntervalMilliseconds": 15000,
"propertyMapList": [
{
"propertyPath": "temperature",
"modbusDataAddress": 1199,
"modbusDataAccess": "holdingregister",
"modbusUnitId": 5,
"modbusDataLen": 1
},
{
"propertyPath": "volume",
"modbusDataAddress": 1299,
"modbusDataAccess": "holdingregister",
"modbusUnitId": 5,
"modbusByteOrder": "ABCD",
"modbusDataLen": 2
},
{
"propertyPath": "status",
"modbusDataAddress": 1199,
"modbusDataAccess": "coil",
"modbusUnitId": 5,
"modbusDataLen": 1
}
]
},
"ownerName": "admin"
},
"requestId": "00000007"
}
{
"authToken": "anAuthorizationTokenFromTheServer",
"api": "hub",
"action": "createInput",
"params": {
"database": "ctreeSQL",
"inputName": "modbusTCP",
"serviceName": "modbus",
"tableName": "modbusTableTCP",
"settings": {
"modbusProtocol": "TCP",
"modbusServer": "127.0.0.1",
"modbusServerPort": 1505,
"modbusDataCollectionIntervalMilliseconds": 15000,
"propertyMapList": [
{
"propertyPath": "temperature",
"modbusDataAddress": 1199,
"modbusDataAccess": "holdingregister",
"modbusUnitId": 5,
"modbusDataLen": 1
},
{
"propertyPath": "volume",
"modbusDataAddress": 1299,
"modbusDataAccess": "holdingregister",
"modbusUnitId": 5,
"modbusByteOrder": "ABCD",
"modbusDataLen": 2
},
{
"propertyPath": "status",
"modbusDataAddress": 1199,
"modbusDataAccess": "coil",
"modbusUnitId": 5,
"modbusDataLen": 1
}
]
},
"ownerName": "admin",
"retentionPolicy": "autoPurge",
"retentionPeriod": 4,
"retentionUnit": "week",
"metadata": {}
},
"requestId": "00000007"
}{
"result": {},
"requestId": "00000007",
"errorCode": 0,
"errorMessage": ""
}{
"result": {},
"requestId": "00000008",
"errorCode": 0,
"errorMessage": ""
}Use the createInput JSON API action to create a new FairCom Edge input
The "params" property is an object that contains an action's parameters. Each action defines its own required and optional properties.
"params" properties summaryProperty | Description | Default | Type | Limits (inclusive) | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
databaseName | contains the name of a database | Defaults to the | string | 1 to 64 bytes | |||||||
inputName | specifies the unique name of an input. | Required - No default value | string | 1 to 64 bytes | |||||||
exists primarily for the user interface to find integration information |
| object | May contain any number and type of user-defined properties | ||||||||
specifies the unique name of a schema in a database | Defaults to the default Owner Name set during | string | 1 to 64 bytes | ||||||||
specifies the number of retention units, which controls how long data is retained – see |
| integer |
| ||||||||
specifies how messages persist |
| string |
| ||||||||
purges expired messages each time this unit cycles – see |
| string |
| ||||||||
specifies the name of a service that collects data from an external source and inserts it into an integration table | Required - No default value | string | 1 to 64 bytes | ||||||||
contains properties needed to configure the data source of the specified plugin | {} | object |
| ||||||||
specifies the variant type format of the |
| string |
| ||||||||
specifies the name of a table | Optional- No default value | string | 1 to 64 bytes |
The "metadata" property is an optional JSON object. It exists primarily for the user interface to find integration information. By default, it is an empty JSON object.
It contains a flexible set of properties.
It typically contains tags and description properties.
Example
{
"description": "",
"tags": [""],
"yourOwnProperties": "usage, purpose, notes, location, etc.",
}
The "ownerName" property is an optional string from 1 to 64 bytes that specifies the account that owns an object.
The "retentionPeriod" property specifies how many units of data to retain. It must be an integer value from 1 to 100. It refers to the unit of time specified by the "retentionUnit" property — for example, if "retentionPeriod" is 14 and "retentionUnit" is "day", then message data is retained for 14 days. This property is optional.
If not specified, the default found in the services.json file is used. Initially, it is 4 (weeks).
Automatically purging data is important to ensure that retained data does not consume all storage and shut down the computer. The default value of 4 weeks allows FairCom's servers to store 1 TB of messages when 200 topics send one 2K message per second.
Note
If the value is not an integer from
1to100, FairCom's servers set it to the default value.Smaller numbers improve SQL performance.
Each time the
"retentionPeriod"cycles, FairCom's servers automatically and efficiently delete expired data.FairCom's servers only use the
"retentionPeriod"property when the"retentionPolicy"is"autoPurge".The
"retentionPeriod"can be changed to retain fewer or more messages. Changing it does not necessarily destroy existing data, but data may expire more quickly or be retained longer.The
"retentionPeriod"and"retentionUnit"properties control data granularity as well as the retention time. In other words,"retentionPeriod"defines how many sets of data are stored, and"retentionUnit"defines how often data is purged.For example, if
"rententionPeriod"is set to14, the server stores 14 sets of data. At the beginning of the 15th cycle, the server automatically purges the oldest set of data. If"retentionUnit"is set today, then data will be purged daily. If set to"week", then data will be purged weekly.The current calendar date affects purging.
FairCom's servers automatically purge all retained data that has expired. This is noticeable when FairCom's servers come online after having been offline for a long time. When a server comes back online, it automatically purges all expired data.
For example, if a FairCom server is offline for four weeks when it comes online, it will completely purge all retained data that has a retention time of less than 4 weeks.
The "retentionPolicy" property controls how messages are persisted. This property is optional.
If not specified, the default found in the services.json file is used. Initially, it is "autoPurge".
retentionPolicy values:"autoPurge"This is the default. It is automatically applied when a new topic is created. It is preferred because it allows FairCom's servers to automatically remove messages that are older than the retention time. This helps ensure message data does not consume all storage space. It also minimizes storage costs and speeds up data access. The server partitions a table into multiple files so it can efficiently delete expired files.
"neverPurge"This stores messages on disk and never removes them. This is useful when you need the entire history of the message stream. If message velocity is high, this can consume all storage space and cause an outage. The server creates a non-partitioned table, which is slightly faster than a partitioned table because it stores all records in one file.
"doNotPersist"This stores messages only in RAM, where they are transmitted more quickly. Undelivered messages are lost when FairCom's servers stop and restart. No transforms can be applied to the payload. Message data cannot be bridged across protocols.
Important
Changing the "retentionPolicy" property value to "doNotPersist" removes all existing message history for the topic because it changes how messages are stored on disk.
Each time this unit cycles, FairCom purges expired messages. For example, if you want a week's worth of messages to be purged once a week, set "retentionUnit" to "week" . This property is optional.
If not specified, the default found in the services.json file is used. Initially, it is "week".
This property is used in concert with
"retentionPeriod"to determine retention time."retentionUnit"values:"minute""hour""day""week""month""year""forever"
Note
For best performance, set the
"retentionUnit"to a value that keeps"retentionPeriod"between5and30.When you set
"retentionUnit"property to"forever"the server does not purge messages. This setting is the same as setting"retentionPolicy"to"neverPurge".FairCom MQ only uses the
"retentionUnit"property when the"retentionPolicy"is"autoPurge".
The "serviceName" property contains the name of a FairCom input or output service. This property is required.
See the "params" topic of each specific service for the requirements of this property.
"MODBUS""SIEMENSUDT2JSON""OPCUA"
Note
The SQL, JSON RPC, and REST services can automatically query any integration table in FairCom's servers without requiring configuration.
Note
MQTT always represents both input and output services. This is because once a topic is created and assigned to an integration table, any MQTT client can publish messages to it and subscribe to those messages.
The "settings" property contains properties that are specific for each connector type. Settings for Modbus are different than settings for OPC UA, and so forth. See the API reference "params" property of each connector for details of the "settings" property for that connector.
Connector-specific "settings"
The "sourcePayloadFormat" property is an optional string that defines the variant type format of the "source_payload" field. When omitted or set to null, it defaults to "binary".
This property is a string containing the following enumerated values:
"binary""json""utf8""siemensUDT""jpeg""xml"
This property is a hint to the server about the format and type of the MQTT message payload.
This property does not cause server to validate the MQTT payload to see if it matches the type you set. The server stores the payload as is without validation. For example, if you set the type to
"json", it does not stop the server from receiving and storing a non-JSON value or invalid JSON document in the source payload.The FairCom Edge Explorer application may use the value of this property to determine the default way to display a topic's payload.
The transform engine may use the value of this property to help it transform the source payload.
The "tableName" property contains the name of the table in the database where the event occurred. It is a non-zero-length string.
A table name may contain up to 64 ASCII characters and must not start with a number.
A table in DBnotify is defined by "databaseName", "ownerName" and "tableName" or by "dataFilePath".