How to capture HTTP inbound request when using HTTP Service?
How to capture HTTP inbound request and use it inside Pega?
We need this to only log those inbound requests which cause an error in the end of the process. If we log all inbound requests, the log file is overfilled too quickly and we have performance issues.
We see the request we need in tracer, but it disappears from clipboard before the first activity runs, so we cannot get hold of it:
https://pdn.pega.com/system/files/HTTPRequestInTracer.png (adding a link as image embedding does not work here)
For example, we can capture inbound request for Service SOAP rules - the request is available in pxRequestor.pxReqSOAPEnvelope, but we cannot find similar property for Service HTTP.
If you have any idea, please, let us know.
@Pega team, maybe you know a way, how to get hold of the request or you plan to make a change to keep it in clipboard a little longer?
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Pegasystems Inc.
US
You'll have to get hold of the HTTP object in Authentication activity via HTTPServletRequest object.
test=((javax.servlet.http.HttpServletRequest)tools.getRequestor().getRequestorPage().getObject("pxHTTPServletRequest")).getParameter("Test");
IT
SK
Hello, DHEEV,
thanks a lot - it is great idea to do it inside Authentication activity, however, I still did not manage to make the above code to give me the input XML so far... If I try to print test - it is always equal to null.
I tried the following (did not help):
test=((javax.servlet.http.HttpServletRequest)tools.getRequestor().getRequestorPage().getObject("pxHTTPServletRequest")).getParameter("requestparameters"); // returns null
and
test = ((javax.servlet.http.HttpServletRequest)tools.getRequestor().getRequestorPage().getObject("pxHTTPServletRequest")).toString(); // returns com.pega.pegarules.priv.authentication.RequestFacade@8a210131
If you have any other idea, please, let me know.
IT
SK
Hi, Santosh,
It seems to be impossible at the moment with HTTP-service, not sure about REST. The work around mentioned before - map the input to the property before parsing it - might be implemented or you may switch to using SOAP service, however, this does not solve the issue.
Dell Computadores DO Brasil Ltda
BR
Hello, I´m facing the same issue. Trying to get request parameter inside Authentication Activity without success. Request object returns com.pega.pegarules.priv.authentication.RequestFacade@8a210131. Altough I´m able to get request header data. Is there any solution or workaround for that?
Pegasystems Inc.
US
IT
SK
Hello, Cleber,
We have solved this issue, but right now I do not have access to the code and cannot check exact way.
You have access to request headers within authentication activity if you use HTTP service instead of SOAP (this was the reason we used it). You should find the right way to get these parameters and as far as I understand you have found such way already.
If you want to have the access to request itself:
We did not find a way to obtain the full request with headers and body in Pega (the object is removed right after parsing before we can intervene). However, as a workaround you may change the mapping in Service HTTP rule to map to clipboard property instead of parse rules. Within the activity which is called from Service HTTP rule you may call the method apply-parse-xml to parse it after you use original request for your purposes.
Let me know if you have any more queries.
Kind regards,
Ivan