Learn how to create a topic with Streams and automatically publish content with Streams HTTP Poller publisher. Also learn, as a consumer, how to subscribe to a topic using server-sent events (SSE).
Move data in real-time with Streams
Contribute to Axway Streams documentation
The Open Beta enables you to suggest edits and create issues for any page of the documentation using a GitHub account. To learn more, see the contribution guidelines.
The role of each documentation website in the Open Beta is as follows:
- Axway Open Documentation on Netlify (https://axway-open-docs.netlify.app/) - Specific product documentation sets are available on this website for contribution using GitHub and Netlify CMS.
- Axway Documentation Portal (https://docs.axway.com/) - All Axway documentation is available on this website in read-only format.
All contributions are first published on Axway Open Documentation, and shortly after on the Axway Documentation Portal, so that the latest documentation is always available on both websites.
This website contains the documentation set for Streams.
Browse all documentation for Streams with the left navigation menu.
Streams is a publish/subscribe (pub/sub) messaging service where the senders of messages are decoupled from the receivers of messages.
Learn how to use the different types of Publishers supported by Streams.
Learn how to use the different types of Subscribers supported by Streams.
The Streams Topics API provides programmatic access to efficiently manage pub/sub topics.
Install Streams and learn how to upgrade an existing installation.
Install Streams on-premise, or deploy in your private cloud.
This section describes how the the product was developed in a secure way, and provides a link to the Streams Security guide.
Understand the metrics provided by Streams
This guide provides information for capacity planning and outlines performance results for common use cases for Streams.
Release notes for Axway Streams.
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.