Posted: 2 Apr 2018 11:55 EDT Last activity: 14 May 2018 12:57 EDT
Pega screen Pop up : HTTP Long Polling
Currently we are using the HTTP Long polling mechanism to show the pop up for an incoming message (Not using Pega supported CTI Platforms, CTI system will call the exposed Pega webservice and the service activity calls the Push Notification API pega.getPushNotificationsUtils().publishEvent to send the event to the CSR browser). My question is can we use this websocket based events to show the pop up ?
The only thing changed is the transport mechanism from longpoll to websockets, so you should still be able to implement your custom solution. Please keep in mind that Pegacall 731 is when support for websockets started. Web sockets is not a part of 718 PRPC. I highly recommend upgrading to Pegacall 731 and the proper supporting software versions (prpc, framework, etc..)
Posted: 3 years ago
Posted: 11 Apr 2018 5:51 EDT
Manjunatha HV (ManjuHV)
Founder and Principal Pega Consultant
Thanks Keith. Is there any way that we can use of websockets in CPM 7.1.3 by implementing the custom solution ? If so, what is the starting point that I need to start customizing. I do have a very limited knowledge on the concepts of websockets. Any insights would be of great help. We started looking into this as HTTP Long Polling mechanism is not working 100% always in PROD.
The pop up issue is occurring because the connections do not stay alive permanently in the HTTP Long polling mechanism. The connection drops because of number of issues (Requestor Retrieval, Authentication Time out, Load Balancer refresh, Session recovery etc. and it’s very hard to replicate and debug this issue) Any suggestions for this one please ?
Websockets showed up in PRPC a few releases prior to PRPC 731, but Pegacall did not support it until Pegacall 731 / PRPC 731. Websocket support is not back ported into any other pegacall release, so if that is something you are looking at using I would suggest upgrading. A good starting point would be the pegacall 731 documentation. Unfortunately I do not have any other suggestions on how to start digging into the websocket code short of tracing requests and connecting the dots.