Question
UBS
GB
Last activity: 16 Oct 2018 7:29 EDT
PegaCHAT technical queries based on v7.1.3 implementation
We did a PoC last year to implement PegaCHAT v7.1.3 with PegaCS v7.1.4 on Pega platform v7.1.9.
Below is the list of issues identified -
1. DNS script to balance DB load was not working to support HA architecture.
2. Pega chat server was unable to send authentication cookie/header to our Web application server.
3. There was a limitation on the Pre-Chat questions and data masking of responses.
4. Position of Pega Chat logo was not modifiable in last version.
5. Certificate exchange between Pega server and Pega CHAT server was not working except overriding the JVM argument in Websphere and the same resulting SMA non-functional.
6. Pega chat client was unable to connect to Apache Reverse proxy server due to secure tunnel failing.
I would like to understand if these issues were addressed in latest version of PegaCHAT (v7.31) and if yes is there are documentation available?
Accepted Solution
Pegasystems Inc.
US
Hello,
This is to recap our discussion in the meeting last week:
We did a PoC last year to implement PegaCHAT v7.1.3 with PegaCS v7.1.4 on Pega platform v7.1.9.
Below is the list of issues identified -
1. DNS script to balance DB load was not working to support HA architecture.
Discussed the fact PostGres is capable of managing HA architecture today. Our cloud environment uses HA architecture and to review PostGres online documentation re: HA. In addition we will have discussion with cloud team as a knowledge sharing session.
2. Pega chat server was unable to send authentication cookie/header to our Web application server.
This is an item we will have a follow- up meeting with and Pega is looking to add in future roadmap and not present in Pega Chat 7.31.
3. There was a limitation on the Pre-Chat questions and data masking of responses.
Hello,
This is to recap our discussion in the meeting last week:
We did a PoC last year to implement PegaCHAT v7.1.3 with PegaCS v7.1.4 on Pega platform v7.1.9.
Below is the list of issues identified -
1. DNS script to balance DB load was not working to support HA architecture.
Discussed the fact PostGres is capable of managing HA architecture today. Our cloud environment uses HA architecture and to review PostGres online documentation re: HA. In addition we will have discussion with cloud team as a knowledge sharing session.
2. Pega chat server was unable to send authentication cookie/header to our Web application server.
This is an item we will have a follow- up meeting with and Pega is looking to add in future roadmap and not present in Pega Chat 7.31.
3. There was a limitation on the Pre-Chat questions and data masking of responses.
Requested additional information via email and in the meeting since the question is unclear on what the limitation is.
4. Position of Pega Chat logo was not modifiable in last version.
This can be modified via CSS by client.
5. Certificate exchange between Pega server and Pega CHAT server was not working except overriding the JVM argument in Websphere and the same resulting SMA non-functional.
Certificate exchange should not be required in 7.31 version.
6. Pega chat client was unable to connect to Apache Reverse proxy server due to secure tunnel failing.
Unsure as Pega does not have SME experience with specific proxy servers.
I would like to understand if these issues were addressed in latest version of PegaCHAT (v7.31) and if yes is there are documentation available?