PackagePackageA library you install and call yourself.See every one →What this type is →independently maintainedindependently maintainedPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →
INVIXO/abapMQ
An MQTT client implemented in ABAP, supporting protocol version 3.1.1, so an ABAP program can publish and subscribe to a broker; it requires ABAP 750sp01 and installs through abapGit.
ABAP has no built-in MQTT client, so this project implements the protocol directly inside the stack: an MQTT 3.1.1 client an ABAP program can use to publish and subscribe to a broker. It requires ABAP version 750sp01 and installs through abapGit.
Facts
Last pushLicenceMIT
Where it sits
Lives in
Provides
Event MeshABAPEvent MeshEmitting and consuming business events across systems through brokers, including subscriptions and mapping application events to broker topics. Work that must survive a request, including deferred processing and retries, belongs to [async processing](capability:async-processing).
Who is behind it
INVIXO Consulting Group A/SINVIXO Consulting Group A/SMaintains this
In the atlas: maintains 1@INVIXOmaintainerLars HvamContributes to this
In the atlas: maintains 13, contributes to 92, wrote 1@larshpJacques NomssiContributes to this
In the atlas: contributes to 4@nomssiUwe FetzerContributes to this
In the atlas: maintains 1, contributes to 5@se383 contributors
In the atlas: maintains 1@INVIXOmaintainerLars HvamContributes to this
In the atlas: maintains 13, contributes to 92, wrote 1@larshpJacques NomssiContributes to this
In the atlas: contributes to 4@nomssiUwe FetzerContributes to this
In the atlas: maintains 1, contributes to 5@se383 contributors
Before choosing this
Signals
ActivityQuietNo published releases; repository quiet for 68 months
It publishes no releases, and its repository has been quiet for at least 24 full months. This may be normal for stable software; check whether its current state still fits your use.
Conditions
PolicySAP API Policy 4.2026a§ 2.2.2, 3, FAQ 12, FAQ 27, FAQ 38from Event MeshAn ABAP event integration exposes inbound access to SAP APIs or becomes a systematic or large-scale extraction or replication path. An outbound notification or callback alone is not enough.
- § 2.2.2 AI call sequences and data extraction. Outside SAP-endorsed architectures, data services or expressly identified pathways, the policy prohibits specified agentic API use and systematic or large-scale extraction.
- § 3 Monitoring and remedies. SAP states that it may monitor API use and take enforcement actions when use does not comply with the documentation and policy.
- § FAQ 12 Outbound interfaces. The accompanying FAQ distinguishes external consumption of SAP-provided services from outbound notifications or callbacks sent by an SAP system, which it places outside this policy's scope.
- § FAQ 27 Custom-developed APIs. Customer-namespace ABAP interfaces are not prohibited merely because they are custom, but their underlying SAP dependencies and usage pattern still determine whether the use aligns with the policy.
- § FAQ 38 Large-scale data access. Large-scale extraction and replication must use access mechanisms and patterns documented for that purpose rather than treating a transactional or custom API as a general bulk-data surface.
Direction and usage pattern decide the policy relevance. Customer ABAP code may publish events outward, but it must not be used to bypass SAP API controls or substitute a custom event stream for a documented bulk-data pathway.
SAP API Policy 4.2026a →What it declares
Every artifact
- Type
- Package
- Origin
- Independently maintained
As a package
- Where it runs
- does not say
- Distributed through
- abapGit
Connections
Group by
NodeRelationBasis
Functional
Event MeshEvent MeshEmitting and consuming business events across systems through brokersSAP and community, narrow by design
provides
stated
provides Event Mesh
Implements an MQTT 3.1.1 client in ABAP for publishing and subscribing to a broker.
“MQTT client implemented in ABAP”
Emitting and consuming business events across systems through brokers
Download
README
quoted from INVIXO/abapMQ under MIT, readOthers providing
Compare all 4 on the Event Mesh page →Event MeshEvent MeshEmitting and consuming business events across systems through brokers, including subscriptions and mapping application events to broker topics. Work that must survive a request, including deferred processing and retries, belongs to async processing.SAP and community, narrow by design
- cesar-sap/abap_kafka_rest_proxycesar-sap/abap_kafka_rest_proxyAn ABAP connector that produces and consumes data to and from Kafka through the Confluent Kafka REST Proxy, since SAP NetWeaver ABAP has no native Kafka client; tested on ABAP 7.5x.independent, abapABAP connector to Kafka through the Confluent Kafka REST Proxy
- gregorwolf/AWS_SNS4ABAPgregorwolf/AWS_SNS4ABAPAn ICF handler that receives Amazon SNS notifications in an ABAP system as an HTTPS subscriber endpoint, leaving what happens to a notification once it arrives to the caller.independent, abapICF handler receiving Amazon SNS notifications in an ABAP system
- MQBAMQBAAn implementation of MQTT publish/subscribe in ABAP, with a broker inside the system built on ABAP Push Channels and ABAP Messaging Channels, and a bridge to external non-SAP brokers.independent, abapMQTT publish/subscribe in ABAP with an external broker bridge
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
discovered viaAdded by hand
first seen in the atlas
ecosystem and domainabap, integration-and-messaging
abaplint
issues under its own abaplint configuration182
lines3,312
statements1,622
objects26
files65
analysed, master
abaplint version2.120.84
read fromabaplint.app,
Contributors
History in the atlas
- First seen.
For your agent
- Ref
artifact:invixo-abapmq- JSON
- /artifacts/invixo-abapmq.json
- MCP
- Connecting an agent