A transport is the mechanism that transfers the data that is generated when a trigger executes. A payload is the useful data that you are sending or receiving. The data can be any type including an engine serial number, machine torque reading, part count, and so forth. The transport type you assign to the transport map determines the parameters to set for the payload. A payload can be delivered to a message queue, relational database, TCP application program, and other enterprise application programs. The following lists each payload that can be specified and the transport that facilitates the payload.
| Payload type | Transport support | More information |
| ASCII message | JMS-based, WebSphere MQ, MSMQ, HTTP, and TCP. | Defining an ASCII message payload |
| Freeform text | JMS-based, WebSphere MQ, MSMQ, HTTP, and TCP. | Creating a payload of freeform text |
| XML | JMS-based, WebSphere MQ, MSMQ, HTTP, andTCP. | Defining the XML payload |
| Custom | JMS-based, WebSphere MQ, MSMQ, HTTP, and TCP. | Adding a custom payload |
| Map message | JMS-based | Adding a map message as the payload |
| XSD | JMS-based, WebSphere MQ, MSMQ, HTTP, and TCP. | Using an XSD payload |
| JSON | JMS-based, WebSphere MQ, MSMQ, HTTP, and TCP | Transport Map for a JSON format request |
| Not applicable | Relational database Supported databases: DB2, DB2400, MySQL, Oracle, MSSQL, RDM, PostgreSQL, SAP HANA. |
Database destined payloads |