Chris Malek is a PeopleTools® Technical Consultant with two decades of experience working on PeopleSoft enterprise software projects. He is available for consulting engagements.
About Chris Work with ChrisIntroducing a small but powerful PeopleSoft bolt-on that makes web services very easy. If you have a SQL statement, you can turn that into a web service in PeopleSoft in a few minutes.
PeopleSoft developers often need to turn on “tracing” which can be invaluable to see what is happening behind the scenes. In your PeopleCode handler code you can programmatically turn on tracing using something like the follow PeopleCode.
/* change based on your tracing preferences */
SetTraceSQL(3);
/* change based on your tracing preferences */
SetTracePC(4044);
The confusing thing when turning on tracing using the method above is where the trace actually ends-up. When you initial tracing from the sign-on page or the “Utilities” pages in Peoplesoft a separate file is usually generated on the app server. When you start a trace with PeopleCode using the SetTraceSQL or SetTracePC function, the trace output are often inside the app server .log file not an individual *.tracesql file.
I have seen some variation on this across tools releases as well as operating systems. I have not been able to find any Oracle documentation on this.