The HTTP Server-Side Monitor is enabled and displayed by default when you deploy to the Tomcat Web Server. For the Glassfish application server, you must enable it manually. If the HTTP Server-Side 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 Server-Side Monitor:
The HTTP Server-Side Monitor is now enabled and will appear when you deploy your application.
To enable the HTTP Server-Side Monitor for servers that are started outside the IDE:
![]() |
The Glassfish application server has its own schema2beans.jar. Therefore, when you are using the Glassfish application server, only copy httpmonitor.jar to your web application's WEB-INF/lib folder. |
<filter> <filter-name>HTTPMonitorFilter</filter-name> <filter-class>org.netbeans.modules.web.monitor.server.MonitorFilter</filter-class> <init-param> <param-name>netbeans.monitor.ide</param-name> <param-value>name-of-host-that-runs-IDE:port-of-internal-HTTP-server </param-value> </init-param> </filter> <filter-mapping> <filter-name>HTTPMonitorFilter</filter-name> <url-pattern>/*</url-pattern> <dispatcher>REQUEST</dispatcher> <dispatcher>FORWARD</dispatcher> <dispatcher>INCLUDE</dispatcher> <dispatcher>ERROR</dispatcher> </filter-mapping>
<filter> <filter-name>HTTPMonitorFilter</filter-name> <filter-class>org.netbeans.modules.web.monitor.server.MonitorFilter</filter-class> <init-param> <param-name>netbeans.monitor.ide</param-name> <param-value>name-of-host-that-runs-IDE:port-of-internal-HTTP-server </param-value> </init-param> </filter> <filter-mapping> <filter-name>HTTPMonitorFilter</filter-name> <url-pattern>/*</url-pattern> </filter-mapping>
<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>