Question
Red Alpha, LLC
US
Last activity: 12 Oct 2023 12:52 EDT
Pega Platform 8.8.3 chat bot without cloud based Digital Messaging Service
First I will specify that I've already read the following and they do not answer the question, despite me having the same requirement:
https://support.pega.com/question/how-host-web-chatbot-digital-messaging-pega-user-portal-88-v
My customer requirement is that the Pega instance and all users are on an enclosed on premises network with NO ACCESS to the public internet or cloud. Therefore, Pega cannot connect in any way to the cloud based Digital Messaging Service. We would like to use the Chat Bot on a Pega hosted Portal and we are running Pega Platform version 8.8.3. Therefore Legacy Webchat is not an option as a Channel as it has been removed. We previously demonstrated using Platform version 7.4 that we could use the Chat Bot as everything could be hosted locally. Can we do the same in Platform version 8.8.3? Or MUST the chat connect to a cloud hosted Digital Messaging Service for some reason, rendering this feature no longer viable to wholly on premises users? If it can be done, please guide me to a configuration for including the chat bot in a platform based portal (using Theme Cosmos).
Thanks in advance!
Accepted Solution
Updated: 12 Oct 2023 12:52 EDT
Pegasystems Inc.
US
@JonathanB9941 Hi Jonathan, thanks for your question. In Pega 8.8.3 you must connect to the Digital Messaging Service to leverage our chat, messaging and IVA capabilities. As part of our overall strategy to shift towards microservices as part of the Pega Platform, the breadth of our Chat and Messaging capabilities is dependent on using Digital Messaging which is hosted on a Multi-tent AWS native cloud. Keep in mind that the service does not store any messaging data at rest, and rather it encrypts it and sends it into the Pega Platform. After transit is complete, the encrypted data is purged from both S3 and DynamoDB within the hour. Keep in mind that the endpoints the Pega instance is connecting to is secured by a unique ID and JSON web token, and that any message forwarded to the instance would go through it's own VPC gateway specific to the client application.
Updated: 12 Oct 2023 12:51 EDT
Red Alpha, LLC
US
@FranklinMarkley Thank you for the response! This answers my question, for sure. Unfortunately like I mentioned, we have no external network connectivity at all so can not use the solution with this architecture. If it's ok, can I contact you off forum/direct to discuss requirements and possible solutions?