This section describes the topic structure for Data and Metadata. The recommended structure of topic naming is as follows:
ie/{payloadType}/{encoding}/{msgStructureScheme}/{msgStructureSchemeVersion}/{provideAppInstanceId}/{payloadMsgType}
and it is made of the following elements:
ie/{payloadType}/{encoding}/{msgStructureScheme}/{msgStructureSchemeVersion}/{provideAppInstanceId}/{payloadMsgType}/{accessmode}/{connectionname}/{collectionname}
The following table explains the above elements:
| Element | Description | Possible Values |
|---|---|---|
| payloadType | This indicates what the payload contains. | 'd' for data 'm' for metadata |
| encoding | This indicates payload encoding. | 'j' for JSON |
| msgStructureScheme | This indicates payload format schema model. | simatic |
| msgStructureSchemeVersion | This indicates payload format schema version number | v1 |
| provideAppInstanceId | This indicates unique id of provider app. | 'slmp' for SLMP instance 1 |
| payloadMsgType | This indicates payload message content. | 'dp': DataPoints for PLC Variables (process image) |
| accessmode | This is an app specific element. This indicates the purpose of the payload SLMP Connector as it would support both read and write of Data Points. | 'r' for Read from Connectors 'w' for write to Connectors |
| connectionname | This is an app specific element. This indicates unique name provided in Connector for a connection to a PLC in SLMP Connector. | Paintshop1PLC |
| collectionname | This is an app specific element. This indicates the collection name. | 'default' for Tags published in bulk mode |