Question
FE Credit
VN
Last activity: 8 May 2024 12:18 EDT
Best practice to manage traffic external connectors
Hi all,
My app has some SOAP connectors to external service, which I mean I use external service, not expose service for other application to use. Any suggest to manage the traffic my app has made to external service?
Information we need to manage:
- time frame: a week
- Traffic: how many call per week by status (i.e. success or fail or time out), response time, requestor
As now I have some idea but need your expertise to analyse
- use PDC -> but in PDC we can only alert for exceeding time interaction, we need all overview
- add data transform/ activity when call SOAP service to log into a table -> this approach may be synchronous and affect the end user if the logging data transform/ activity suddenly fail
Please give me some advice. Thank you!
Accepted Solution
Updated: 8 May 2024 12:18 EDT
Pegasystems Inc.
GB
to manage and monitor the traffic from your application to an external service using SOAP connectors, you can use Pega Predictive Diagnostic Cloud (PDC). PDC can provide you with detailed metrics about your connectors, including the number of calls per week, the status of these calls (success, fail, timeout), and response times. For a more detailed analysis, you can also consider logging the necessary information into a table in your Pega application. You can create an activity or data transform that executes after the SOAP service call, logging the necessary details such as status, response time, and requestor. Please note that while this approach provides detailed, custom logging, it could potentially impact performance if not implemented correctly. It's important to ensure that the logging activity or data transform is designed to handle exceptions and failures gracefully, to avoid impacting the end user experience.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
Data management and integration > SOAP
SOAP Connector takes lot of time.
to manage and monitor the traffic from your application to an external service using SOAP connectors, you can use Pega Predictive Diagnostic Cloud (PDC). PDC can provide you with detailed metrics about your connectors, including the number of calls per week, the status of these calls (success, fail, timeout), and response times. For a more detailed analysis, you can also consider logging the necessary information into a table in your Pega application. You can create an activity or data transform that executes after the SOAP service call, logging the necessary details such as status, response time, and requestor. Please note that while this approach provides detailed, custom logging, it could potentially impact performance if not implemented correctly. It's important to ensure that the logging activity or data transform is designed to handle exceptions and failures gracefully, to avoid impacting the end user experience.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
Data management and integration > SOAP
SOAP Connector takes lot of time.
Building high performance Customer Service applications > Integration and connectors
[Video]: Using PDC to address performance bottlenecks