AsyncAPI Specification Support
TIBCO BusinessEvents supports the industry-adopted AsyncAPI specification, which allows an interaction between event-driven, APIs-based applications in a consistent and standard manner. The AsyncAPI specification is a machine-readable format for defining the message exchange patterns as per consumers for event-driven APIs and works over any protocol. For details, see AsyncAPI documentation.
You can export your TIBCO BusinessEvents project using the AsyncAPI specification that can be consumed by another TIBCO BusinessEvents project or a third-party product in a different ecosystem and generate resources.
TIBCO BusinessEvents can parse an imported AsyncAPI specification and create the required project artifacts based on its contents: the concepts, events (with or without payload), channels, destinations, and shared resources.
In TIBCO BusinessEvents, property-based configurations artifacts for Kafka, shared resources for HTTP and both for JMS channels can be exported and imported by using the AsyncAPI specification. For Kafka and JMS channels, there must be a one-to-one mapping between channel destination and topic, queue.
- Concept TTL and Event TTL
- Channel SSL section
- SSL fields
- Pageflow type for HTTP Channel
- Description field for a channel, destination, event, and shared connection
For details about the supported versions, see the Readme.txt file available at the TIBCO BusinessEvents Enterprise Edition® Product Documentation page.