Connectivity bundles

User Connectivity. Select an instance of User Connectivity if you want to make use of any user-defined connectivity plug-ins. For more information, see Using Connectivity Plug-ins.

Digital Event Services. You can use Software AG Designer to automatically generate Apama event types from digital event type definitions for use in the Apama project and, conversely, to export Apama event definitions in the Apama project as digital event types. You can also use Software AG Designer for configuring the connection to Digital Event Services. For more information, see Using the Digital Event Services connectivity bundle.

Note:
Digital Event Services integration is deprecated and the Digital Event Services transport connectivity plug-in will therefore be removed in a future release. It is recommended to instead use the correlator-integrated support for the Java Message Service (JMS).

Universal Messaging. Universal Messaging is Software AG's middleware service that delivers data across different networks. It provides messaging functionality without the use of a web server or modifications to firewall policy. In Apama applications, you can configure and use the connectivity provided by Universal Messaging. For more information, see Adding the Universal Messaging connectivity plug-in to a project.

Note:
The Universal Messaging transport connectivity plug-in is deprecated and will be removed in a future release. It is recommended to instead either use the MQTT transport connectivity plug-in or the correlator-integrated support for the Java Message Service (JMS).

MQTT. Apama supports MQTT, which is a publish/subscribe-based "lightweight" message protocol designed for communication between constrained devices, for example, devices with limited network bandwidth or unreliable networks. Select an instance of MQTT if you want to make use of the MQTT connectivity plug-in. For more information, see Adding the MQTT connectivity plug-in to a project.

HTTP Server. The HTTP server is a transport for use in connectivity plug-ins which external services can connect to over HTTP/REST. Select an instance of HTTP Server if you want to make use of the HTTP server connectivity plug-in. For more information, see Adding the HTTP server connectivity plug-in to a project.

HTTP Client. The HTTP client is a transport for use in connectivity plug-ins which can connect to external services over HTTP/REST, perform requests on them and return the response as an event. Select an instance of HTTP Client if you want to make use of the HTTP client connectivity plug-in. For more information, see Adding the HTTP client connectivity plug-in to a project.

Kafka. Apama supports Kafka, which is a distributed streaming platform. Select an instance of Kafka if you want to make use of the Kafka connectivity plug-in. For more information, see Adding the Kafka connectivity plug-in to a project.

Cumulocity IoT. Cumulocity IoT is used for communication with connected IoT devices. Select the Cumulocity Client for your version of Cumulocity. For further information, see Adding the Cumulocity IoT connectivity plug-in to a project.

Linked Resources is a node that is created after adding a connectivity bundle in the Project Explorer view. The Linked Resources node is located at project_name > Connectivity and Adapters > connectivity_bundle_name > Linked Resources. The Linked Resources node in the Project Explorer view contains the common configuration files shared by the connectivity bundle instances (only .yaml or .properties files, or both). The configuration files under Linked Resources node are included in the configuration to start the correlator in the order as they appear. After the linked resources are included in the configuration, referenced instance files for bundles are also included. If the connectivity bundles link to the same configuration files, then these files are included in the configuration only the first time they are referenced.