Question
Virtusa
NL
Last activity: 2 Mar 2017 7:24 EST
Calling connect-soaps parallely
I need to fetch data from multiple connect soap methods and should show this data on screen,I am already running these connectors in run-in-parallel mode and connect wait method after that,still it is taking considerable time for these services to respond and fetch values.I wish to know is there any other way to improve the performance and fetch details faster when using multiple connect-SOAPs
Pegasystems Inc.
IN
Hello
Have you checked the performance via SOAP UI ?
If the call thru SOAP UI tool also shows delay then this could be an issue with your external service provider.
Also, I recommend you to check the ALERT log file to see whether there is any PEGA0020 alert or not.
Updated: 28 Feb 2017 5:49 EST
Virtusa
NL
I am able to see multiple PEGA0020 alerts, more than 30 when I run a single case.
i am calling external services in loop as well.
I wish to know is there any way to call multiple services asynchronously so that performance can be improved
Including additional content from Duplicate thread:
Calling connectors in Loop
I have a requirement where I need to fetch details from one connect-soap,depending on the results fetched from this connect-soap; For Example if I get 15 results from first connect-soap I need to call second connect-soap 15 times by passing the values from first connect soap. I am looking for an approach to improve the performance for calling these connectors in loop as it taking considerable time.
I am able to see many PEGA0020 alerts as well which are an indication that external services are not that fast enough.
***Moderator Edit: Vidyaranjan | Copied content from duplicate thread and included it along with the latest comment in the original discussion***
Pegasystems Inc.
IN
Hello
When you talk about overall performance improvement, the first thing you have to focus is to eliminate this PEGA0020 Alert
For a single case if you get more than 30 such alert then there must be something with the response time from your external services.
Examine the connector to determine why responses are taking so long. Are you trying to get huge amount of data each tiem you are talking to the external .
As I have pointed out in my last comment, have you checked the behavior with SOAP UI. I understand that you are tryign to do a looping kind of mechanism but if your response for single call is not optimum then looping will make it more worse.
So first try to fix the basic response time problem
Coming to the point of running them asynchronusly, well, you have mentioned, "if I get 15 results from first connect-soap I need to call second connect-soap 15 times by passing the values from first connect soap." That means you need to map the response data and then based on that you are going to call the other connectors.
The option to run the request asynchronusly is to enable the "Request Only" option under the Service tab. You can select this option to specify the connector is to send the SOAP message and end the connection without waiting for a response (operate asynchronously). If you select this option, the connector does not wait for a response even if you configure data mappings on the Response tab.
Hello
When you talk about overall performance improvement, the first thing you have to focus is to eliminate this PEGA0020 Alert
For a single case if you get more than 30 such alert then there must be something with the response time from your external services.
Examine the connector to determine why responses are taking so long. Are you trying to get huge amount of data each tiem you are talking to the external .
As I have pointed out in my last comment, have you checked the behavior with SOAP UI. I understand that you are tryign to do a looping kind of mechanism but if your response for single call is not optimum then looping will make it more worse.
So first try to fix the basic response time problem
Coming to the point of running them asynchronusly, well, you have mentioned, "if I get 15 results from first connect-soap I need to call second connect-soap 15 times by passing the values from first connect soap." That means you need to map the response data and then based on that you are going to call the other connectors.
The option to run the request asynchronusly is to enable the "Request Only" option under the Service tab. You can select this option to specify the connector is to send the SOAP message and end the connection without waiting for a response (operate asynchronously). If you select this option, the connector does not wait for a response even if you configure data mappings on the Response tab.
When you clear this option it means that the connector has to wait for a response (operate synchronously) which is required for your case. So I dont think you can do it asynchronusly.