Tracing JSP output

[Former Member]

Is there a straightforward way to get a trace of the output of a JSP/Servlet web application? By output, I mean a trace of the exact bytes being sent to the client via HTTP.

This does not have to be selective--it would be fine to enable full tracing of all JSP output (because I am running on a test system with minimal traffic).

Any suggestions?

Thanks!

Jeff Gilmore

[Former Member]

Ivaylo,

I saw this property in the documentation, but I have not been able to find it in the Visual Administrator tool. I looked under the properties tab for the HTTP service and I see all of the properties listed in that document <i>except</i> the "httpTrace" property.

I could see the log destination for HTTP Trace in the "Log Configurator" section, but have not found a place where I can set the trace property itself.

Can you point me to it?

Thanks!

[Former Member]

Hi Jeffrey,

the httpTrace property is available since Web AS 6.40 SP4! Could it be possible that you are using an older version? If so, you'd need to upgrade. (this property is available in the Sneak preview 2 that can be downloaded from the SDN).

Regards,

Ivo

[Former Member]

Hi Jeffrey,

first of all, which version of the J2EE Engine are you using - 6.20 or 6.40?

As for 6.40, there is a property (called HttpTrace) of the HTTP Provider Service on dispatcher that enables traces of HTTP request and responses. For a description of the property and possible values, see the reference manual:

http://help.sap.com/saphelp_nw04/helpdata/en/52/46f6a089754e3a964a5d932eb9db8b/frameset.htm

You can change the value of this property using the Visual Administrator tool.

Hope that helps!

[former_member321450]

Hi Jeff,

try using a http tunnel, it should be easy to get one on the net somewhere.

Best Regards,

André

[Former Member]

You can see what gets sent to the page by doing a 'view > source' on your browser (but I'm sure you knew that!). That leaves the http headers, though. What I've done in the past was use another client-side tool called "Naviscope". You direct your browser to use Naviscope as a proxy server, and it records details about the http headers.

I don't know about how best to handle it on the server side. I suppose you could subclass whatever you are using as 'out', and have that dump everything to a log file, but again, you'd be missing the header details.

Dale