IPMonitor is a Java utility you can use to collect trace information containing the session data flowing between a client and a host. You can enable IPMonitor tracing either manually or by using the Problem Determination window in Advanced Options in the Deployment Wizard. IPMonitor is an intermediary between a client and a host. The client connects to IPMonitor, while IPMonitor connects to the host. IPMonitor then records session data flowing between the client and the host. You can use IPMonitor as a Java application or as a Java applet.
before you can recreate the problem and capture the trace information. The user does not need to send the trace file to the admin because the trace is stored on the Host On-Demand Server.
IPMonitor captures encrypted data and plays it back properly, but since the data is
encrypted, it cannot be used for debugging. To debug the trace correctly, before
you run the IPMonitor, you must disable TLS or SSL in the session that is used for the trace. If
TLS or SSL is not turned off, the data captured by IPMonitor is encrypted and is not
usable for problem determination. To turn off TLS or SSL, do the following:
|
Differences between automatic mode and normal mode include:
IPMonitor
HTML parameter, and must include the
problem determination components. As a Host On-Demand Administrator, you can modify an
HTML file so that a user can access it. The user can recreate the problem and capture
trace information without your involvement. IPMonitor in automatic mode starts
automatically immediately after the session starts.While this version of IPMonitor is easier for the user to use and involves less administrative effort, the user is locked into the host, port and trace file path specified in the HTML file.
While this version of IPMonitor allows greater flexibility in changing the host or port to trace, there is more administrative effort to configuring IPMonitor.
Related topics: