com.sap.cds:cds-feature-enterprise-messaging

A CAP Java feature that connects a CAP messaging service to SAP Event MeshEvent MeshserviceManaged queues and topics over AMQP, MQTT and a REST gateway, and the bus SAP's own applications publish their business events to.sap official, btp, activated by setting the service's kind to enterprise-messaging, and looks up the bound instance.

Connects a CAP messaging service to SAP Event MeshEvent MeshserviceManaged queues and topics over AMQP, MQTT and a REST gateway, and the bus SAP's own applications publish their business events to.sap official, btp, one of the optional application features that build on the CAP Java runtimecom.sap.cds:cds-services-bompackageThe Maven bill of materials for CAP Java, pinning every com.sap.cds module in a release, from the API and core runtime to the Spring Boot starters and the CQN engine, to the same version.sap official, cap. Adding the Maven dependency and setting a messaging service's kind to enterprise-messaging in application.yaml is what activates it; CAP then looks up the bound SAP Event Mesh instance and creates a CAP messaging service for it. It stops at the broker connection: message shape, topic prefixing and the file-based broker used for local testing without a bound service are core messaging support the feature builds on rather than something it adds. On Cloud Foundry the bound instance is read from the platform's service binding, which com.sap.cds:cds-feature-cloudfoundrycom.sap.cds:cds-feature-cloudfoundrypackageA CAP Java feature that reads the environment variables of SAP BTP, Cloud Foundry at start-up and resolves bound service credentials from them, so the other features find their bindings.sap official, cap supplies.