Imagine a situation where you are banging your head trying to debug the PeopleCode to find out the root cause of an error/warning message appeared while doing transaction on a component. When the component is too big like JOB_DATA then its like looking for a needle in a haystack.
Fortunately, PeopleSoft has some sort solution for every problem and this particular case is not an exception. Do this to tackle it:
The sign on tracing can be enabled by just appending trace=y to the URL as shown below:
As soon as the parameter is appended press Enter and the tracing options will be available.
It is however very important to note that we must not check all the options under each category because:
Fortunately, PeopleSoft has some sort solution for every problem and this particular case is not an exception. Do this to tackle it:
- Enable the Sign on trace options
- Sign in and do the same transaction
- Retrieve the trace file generated in the app server
- Look for the place where the error/warning message has been produced
The sign on tracing can be enabled by just appending trace=y to the URL as shown below:
As soon as the parameter is appended press Enter and the tracing options will be available.
It is however very important to note that we must not check all the options under each category because:
- It will cause the portal to become very slow
- The generated trace file will be excessively huge
Therefore, If for example you want to debug an error occurred on the page then simply select the options as shown in the above image and go on. You can also change the selection based on the type of debug you want to perform.
Once you are done doing the transaction, its time to locate the trace file that have been generated. The trace file can be found under:
Once you are done doing the transaction, its time to locate the trace file that have been generated. The trace file can be found under:
