Setting Up the HTTP Monitor

See Also

The HTTP Monitor is enabled and displayed by default when you deploy to the Tomcat Web Server. For the Sun Java System Application Server, you must enable it manually. If the HTTP Monitor does not display or if it does not show the session data for a running web application, ensure that it is enabled as described below.

To manually display the HTTP Monitor:

To enable the HTTP Monitor for servers that are started from the IDE:
  1. Right-click your server's node in the Runtime window's Servers node.
  2. Choose Properties.
  3. Select the Enable HTTP Monitor checkbox.
  4. If the server is running, stop and restart it.
  5. For the Sun Java System Application Server, right-click the HTTP Server node in the Runtime window and choose Start HTTP Server.

The HTTP Monitor is now enabled and will appear when you deploy your application.

To enable the HTTP Monitor for servers that are started outside the IDE:

  1. Copy the following two files to your web application's WEB-INF/lib folder: The SJS Application Server has its own schema2beans.jar. Therefore, when you are using the Sun Java System Application Server, only copy httpmonitor.jar to your web application's WEB-INF/lib folder.
    tip 
  2. Add the filter declaration that is appropriate for your servlet's version to the top of your web application's WEB-INF/web.xml file. Filters and filter mapping entries must come first in a deployment descriptor.
  3. To monitor the data records from a web application using more than one IDE, add a second init-param entry as follows:
      <init-param>
      <param-name>netbeans.monitor.register</param-name>
      <param-value>
      other-IDE-host:other-HTTP-server-port,
      another-IDE-host:another-HTTP-server-port</param-value>
      </init-param>
    
  4. Right-click the HTTP Server node in the Runtime window and choose Start HTTP Server.
See Also
About the HTTP Monitor
Working with the HTTP Monitor
Analyzing Session Data
Saving Session Data
Replaying Session Data

Legal Notices