Clarity

I am trying to troubleshoot a problem that occurs when a GEL script runs a Soap call, it would be really useful to get detailed logs of the SOAP being processed by the application. Does anyone know how I go about doing this?

On another note, does any one have any documentation on PPM Logging? I wouldn't mind finding out what all the Categories mean.

I normally do most of my gel script development outside of the background server i.e. developing  GEL scripts via a command line.  So I just up the logging to see what is happening when I run the gel script via the command line.

https://communities.ca.com/docs/DOC-231149717

If you what to see what is happening inside the background server, you will need to up the logging details for the class that is executing the gel script.

So you can add a logging level for a give class, say com.niku.union.web to trace, and have the log output appended to a given appender class.  This is sometimes limited as there are logging statements in classes that are not provided in the pull down.

So in my picture below, I have set a log for “any logging statements of trace and above” to be sent to the ../logs.trace.xml file for any log statements that occur in the com.niku.union.web class.

The nice thing about running GEL outside the process engine is that you have complete control of the logging level on any classes.  I also have a debug taglib that allows me to break within a IDE to see what the jelly context.  For example, I can view the jelly context before executing a given soap call.

https://communities.ca.com/thread/110574661

V/r,

Gene

Thanks, that is really useful information but I don't think problem is contained within the GEL script but actually the application. I have verified that the background sends the soap envelope to the application correctly (app and bg are on different servers) but on occasion the application returns a null pointer exception when processing the soap envelope. The envelope that is being sent to the application is correct as when I run the same document again it works. So something is going wrong on the application side. I want to be able to see the details of the application processing the soap envelope to help me pinpoint the problem.

So if you are not On-Demand (On-Demand try https://ClarityURL.com/niku/nu#action:security.logs), you could see if there is anything in the log file for those servers.

I would check the app-ca.log and the bg-ca.log to see if there was an exception logged.

As for the logging system, PPM uses log4j which has a lot of switches and features.

https://logging.apache.org/log4j/1.2/

You could also increase the logging volume via the NSA.  For example, the logs will contain Info logs.

V/r,

Gene

Is the application returning the null pointer exception a Clarity service?  Do you have an example stack trace that is OK to share?