Posted: 22 Aug 2016 5:09 EDT Last activity: 21 Feb 2017 23:40 EST
Native Kafka Queue support and websocket implementation
As far as I see there isn't any native support for Kafka APIs in Pega. Thus, I've two questions;
Is it in the road map of product management to support (native) Apache Kafka queues?
Anybody ever implemented a Kafka queue integration via WebSockets?
Business case I am working on is this:
Business requirement: As a Pega Marketing strategy designer, I would like to send a push notification to my customers, based on their geo-location. For example, if they are in the vicinity of their main branch, send them a text message reminding their e.g. home loan applicaiton. Specification: Inhouse mobile application retrieves customer's geo-location at each login and this data is published to a Kafka Queue. Kafka Queue is the enterprise solution that provides all real time feeds such POS transactions, web logins, and ge-location data. Implementation: Subscribe to a Kafka Queue / topic, receive the data and act accoridngly i.e trigger a strategy/offer flow in Pega Marketing.
Please let me know the right way of listening/subscribing to a Kafka queue in Pega. Once integrated successfully, to invoke a strategy and/or an offer flow in Pega Marketing should be relatively easy
***Updated by Moderator: Lochan. Removed user added helpme and Ask the Expert tags. Apologies for confusion, shouldn't have been an end-user option***
Unfortunately, Kafka does not implement the JMS standards. There have been some discussions recently (6/2016) and it appears there is nothing on the roadmap for specific support in the product at this time. There is speculation that you could import Kafka client libs and create Java Connectors or write custom java utilities to get mesages. Having a listener is more complicated, however.
Then, I would like to raise an Enhancement Request for the customer. Even if ER is rejected, I need to provide an explanation. Hoping actually that it is developed soon because I know two Pega Marketing customers which are deliberately looking for this listener API.
From a technical perspective, it should work. However, KafkaQ is the enterprise message broker of the Bank. Therefore, their architects are expecting all external applications (e.g. Pega) to subscribe to related topics. As of today, there are 16 external systems and it is not an option to tell Kafka administrators to call every single service. The expectation is other way around; external services must listen Kafka.
Even we have similar requirement of listening or subscribing the kafka topic from pega. I could see we have no roadmap to support this for now in product (let me know if i am wrong), do we have any alternative way to support this other that writing custom java connector.
Posted: 3 years ago
Updated: 3 years ago
Posted: 21 Feb 2017 23:24 EST Updated: 21 Feb 2017 23:40 EST
Thank you for your query. I see that you have asked this question 2 times in this discussion and once in another discussion. I have deleted the other 2 duplicates to avoid confusion. Let me update you about the roadmap part of your question.
This discussion talks about an enhancement raised, you can see the request ID under the Related Support Case Number field above in the original post. I had a check into the request on our internal portal and it looks like it is definitely in our roadmap. Detailed information regarding this cannot be revealed on PSC since is can be subjected to change and is strictly internal. However, you could check with your Pega Account Executive, who is the best person for you to talk with regarding this. Please refer the request ID mentioned in the original post when in discussion with the Account Executive.