Each transport type is supported by the Transaction Server component, including the details of the following:
- Communication and interface protocol for the enterprise application
- Operations (or actions) if applicable. For example, the database transport supports Select, Insert, Update, Delete, etc. operations.
- Data type conversions between the data in the runtime system and the data in the enterprise application
- Request store and forward support if applicable
- Mapping log support if applicable.
This allows you to create your IoT solution using your enterprise applications in a vendor neutral methodology. The triggers (application logic) and your devices can be shielded from the majority of the enterprise application connectivity details, while still providing the two way enterprise application access required by your M2M solution.
The information in these sections provides the details for the supported transport types.
Assumptions
The general tasks that apply to all transport types are documented in the first several sections of Transports. It is assumed that you are familiar with those general tasks.
The tasks that apply to building your IoT solution's application logic in triggers are documented in Projects and triggers. Information related to using trigger actions to access your enterprise applications is documented in those sections.
What's Inside