Is it possible in WSO2 API Manager, or maybe is it on the roadmap, to publish an async API, for example in Kafka, and manage it like other sync API with spec (Async API spec), security, analytics, etc?
I am not referring to websocket APIs, that I know it is already supported in WSO2 AM. It is event based asynchronous APIs.
I could not find any clear info about it onto wso2 website.
Async APIs support will be available in WSO2 APIM 4.0 which is planned to be released on Q1 2021.
Async API support is now released for WSO2 API Manager 4.0.0. It can be checked in the overview and about of the release officialy published a days ago.
https://apim.docs.wso2.com/en/4.0.0/get-started/about-this-release/
Related
When I Try to download WSO2 Process Server, It redirects me to API Manager.
The link is http://wso2.com/products/business-process-server
Is the WSO2 Process Server deprecated?
WSO2 Business Process Server(BPS) is now deprecated and discontinued. But you can still use it. WSO2 BPS was merged to WSO2 Enterprise Integrator a couple of years back as a different runtime. So if you want to use BPS capabilities you can download WSO2 EI from here and start the Business Process Profile. You can read more about the BPS Profile here.
Yes, the product is not available now.
You can migrate to EI 6.6.0 if you are using WSO2 BPS 3.6.0 - https://docs.wso2.com/display/EI660/Upgrading+from+WSO2+Business+Process+Server
In the latest EI/MI versions do not come with the BPS solution.
It's best to migrate to Micro-integrator 4.1.0 and use the latest capabilities of the enterprise integration. Micro-integrator is the latest version of the WSO2 ESB platform. However, it does not support BPS capabilities as moving forward, WSO2 will continue to provide only the interprise integration capabilities through the platform and for some of the features such as Message Broker and BPS have been deprecated. For use cases on Message Broker and BPS, you need to integrate with 3rd party products such as Camunda (for BPS) and RabbitMQ (for Message Broker).
WSO2 API Manager Version 4.0.0 is Working Fine With Choreo Analytics but Is there Any Way to Configure API Manager Version 4.0.0 with API-M Analytics Version 3.2.0?
No, this is not possible with API Manager 4.0.0.
The API Manager v4.0.0 has gone through a lot of architectural changes and the Handlers and implementations related to publishing Analytics Data to the APIM Analytics server have been removed. Therefore, with my understanding, it is not possible to achieve the same in the v4.0.0 environment.
With the API Manager 4.0 release, the API Analytics was completely revamped and offered as a cloud-based analytics solution to provide users with an unparalleled analytics experience. Therefore, integrating APIM Analytics 3.2.0 with APIM 4.0.0 is not a possible/advisable solution due to architectural constraints.
I am exploring options to pass custom/standard headers to downstream service using WSO2 Api Manager.
I have gone through mediation documentation, and had play around with WSO2 developer studio as well.
I see that the documentation of the latest version of API Manager- 3.0.0 and the actual product vary a lot and I ran into different issues as the WSO2 developer studio is still designed for older version of API Manager.
Can you guide me to proper documentation which holds true for API Manager 3.0.0 or a simple way to achieve header mapping for request and response from API Manager.
Currently I'm interested in building a (small?) Internet of Things project. During research I found WSO2, an open source platform. I decided to use it and searched for developed projects. I found one decent project!
This project uses MQTT as communication protocol, Raspberry Pi<->Message Broker, and Message Broker<->Complex Event Manager.
My questions are the following:
1) Does the current version of the WSO2 Message Broker (v2.2.0) already support MQTT? Because I can't find documentation of this version supporting MQTT.
2) According to some references the WSO2 Message Broker v3.x.x will support MQTT, is that correct and when will this version be released?
3) Are there any other possibilities to use the WSO2 platform components in combination with the MQTT protocol?
4) Are there any other documented Internet of Things projects that use the WSO2 platform?
According to this article:
The WSO2 MB team was working on adding MQTT support; WSO2’s Co-Founder
and CTO Paul Fremantle used this for MQTT interop test at EclipseCon,
in San Francisco in March 2014, where he presented a talk. We decided
that MQTT was the ideal message protocol for devices due to its open,
less message overhead nature.
According to this article:
Upcoming WSO2 Message Broker (MB) 3.x.x release will be supporting
MQTT in addition to AMQP.
There is a relevant source code in this repository.
You could find more information on the WSO2 Message Broker architecture and capabilities through referring the article,
http://wso2.com/library/articles/2015/10/article-using-wso2-message-broker-as-a-scalable-mqtt-broker/
To answer to you questions,
MQTT will be supported from broker 3.0.0 version. and currently in RC stage. This will be released soon.
It provides seamless integration with other WSO2 products. i.e WSO2 CEP (Complex Event Processor), WSO2 ESB (Enterprise Service Bus).
Until released, you can use the Beta version of WSO2 Message Broker 3.0.0 which supports MQTT to test out your project.
WSO2 Message Broker 3.0.0 Beta
The 2.2.0 version does not support MQTT.
Furthermore, since all WSO2 products are based on OSGI concept, you can integrate any of features available from any WSO2 product.
Installing Features via the UI
But if you're looking some simple integration, try integrating WSO2 ESB with MB using MQTT.
WSO2 ESB MQTT Inbound Protocol
I went thorough the features of WSO2 ESB. I noticed WSO2 Coud Connectors like Twitter, LinkedIn ..
I would like to know about any documents, wiki which supports this. I have the Auth Keys from Twitter. I want to do a simple twitter integration using WSO2 ESB.
Please share your thoughts.
Regards,
Guru
#gnanagurus
This is a new feature that will be released with WSO2 ESB 4.5.0. You can do 3rd party API integration very easily with this new feature. For example once the Twitter Connector Library is deployed in the ESB , you can feed the relevant OAuth keys directly and connect to Twitter Cloud seamlessly. Currently there are no publicly available docs. But please await we will be releasing this documentation soon with upcoming releases.
You can find the documentation on connectors from here. Twitter specific documentation can be found here.