As pre one of the PDN integration lesson, below things happen during service processing,
1.The service listener is responsible for sensing that an incoming request has arrived. This functionality is sometimes provided by the underlying Web or Application Server, and sometimes provided by a PRPC Listener.
2.The service listener receives the request and instantiates the “Service API” to provide communication with PRPC. Then, via the Service API, control is handed to PRPC.
3.PRPC looks up the service package and related service rule, using the access group that is specified in the service package.
4.It then establishes the service requestor, and optionally performs authentication based on security credentials that are passed in the request. Once authenticated, service processing continues using the authenticated user’s access group, not the access group that is contained in the service package.
5.The request is mapped onto the clipboard according to the specifications contained in the service rule.
6.Control is passed to the service activity, which provides the logic for the service.
7.When your service activity completes, control is returned to the Service API.
8.The service rule maps the clipboard data to form the response data.
9.The Service API then cleans up the requestor that it previously created, and returns control to the service listener.
10.Finally, the service listener sends the response.
I want to know if we can see how step 1 and 2 gets executed. Is there anything where we can see setting for service listener which call service API?
We have similar requirement from client to capture end to end process time when any surrounding systems call pega soap service.
Problem Statement :
In our claims Pega application there are multiple surrounding systems which are acessing information stored at pega databse via calling Soap service. We have exposed one Service SOAP from Pega and all other systems are comsuming the same. The current issue that we are facing during open enrollment period multiple slowness issues have been reported from surrounding systems, but no one is able to identify where the actual slowness is occuring.
Therefore client want us to capture the total processing time in Pega starting from the request rceive in Pega till the response goes out from Pega.
Approach : To address this issue we are looking for what is the best possible approach to capture end to end processing time in Pega. Is there a configuration that we can enable to capture this in Log, or what will be the best possible place ( e.g. Service activity) to put some code to capture time.Although we tries puting a code inside Service activity which capture date time begining( 1st step) and at the end ( last step) of the activity, but this does not serve our purpose.
Thank you for posting your query on PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write a Post button that’s available on the top right pane of this page. Once created, please reply back here with the URL of the new post.
We have also sent you a private message opening up a communication channel in case you have any further questions.