KB Article #177353

Capturing STDERR Output from 3rd-Party API Gateway Extensions


-- Certain 3rd-party products like CA SiteMinder log their debug output to stderr, which is not captured in API Gateway trace files.


* The API Gateway logs with log4j, which does not have a native way to capture stderr. Instead, normal Unix methods will need to be employed to capture this output. So you have to start the instance from the command line via startinstance and redirect the stderr stream, rather than starting the gateway with the init.d scripts. The following command will run an API Gateway instance in the background, redirecting its stderr output to a file named stderr.log:

startinstance -g "group" -n "instance" 2> stderr.log &

Instance should be replaced with the name of the API Gateway instance and group should be replaced with the name of the group to which that instance belongs.