Establishing Connections
When you connect your JMX client to Windchill, you connect to a specific servlet engine, server manager or method server JVM process. From each connection, you are able to manage a different set of actions. To get an overall picture of your entire Windchill system, connect to each JVM process in your environment.
|
|
The JConsole graphing and charting capabilities only apply to the JVM to which you are connected.
|
When you are using JConsole on the same machine and as the same user under which a process is running, the process appears in the list of local JMX-monitorable processes upon startup. The server manager and method servers process names are recognizable. The Tomcat servlet engine is now located within the method server and servlet engine process can be found within the method server process.
The following sections provide some additional information about your connections.
Server Manager Connections
The server manager connection provides you with high-level information such as total memory consumption, local and remote server calls, heap memory usage, live threads, logging options for the server manager, and email notifications.
Since method servers have a more unpredictable life cycle than server managers and use dynamically selected port numbers for JMX communication, server managers proxy their method servers’ MBeans by default. Thus, by connecting to a server manager, you can manage and monitor its method servers as well. However, when you require detailed information about a method server, you should connect directly to the specific method server.
|
|
JConsole does not pick up on the proxied MBean’s monitoring memory, and so on, from method server JVMs when targeting the server manager. Also, the proxy arrangement involves an extra inter-process hop and has somewhat lower performance and higher overhead.
|
Consider monitoring the server manager through the ServerManager monitoring MBean that is in this connection. The MethodServers monitoring MBean allows you to monitor method servers from the server manager.
For additional information about the ServerManager MBean, see the section ServerManager (Monitors) in
Windchill MBeans.
For additional information about the MethodServers MBean, see the section MethodServers (Monitors) in
Windchill MBeans.
Method Server Connections
A method server connection provides details about that specific method server, such as the specific method server memory usage, method server logging options, and email notifications. A method server connection also provides information about its embedded Tomcat servlet engine (see the Catalina node).
Consider monitoring the method server through the MethodContexts monitoring MBean that is in this connection. For additional information about the MethodContexts MBean, see the section MethodContexts (Monitors) in
Windchill MBeans.
Consider monitoring the servlet requests through the ServletRequests MBean that is in this connection. For additional information about the ServletRequests MBean, see the section ServletRequests (Monitors) in
Windchill MBeans.
Identifying a Method Server Port Number and JMX URL for Remote Access
When JConsole is run under a different user or on a remote machine, connecting to the method server requires the JMX port number of the full JMX URL. Most other JMX consoles require the full JMX URL for local monitoring as well.
You can obtain the necessary JMX URLs from MBeans in the server manager that represents and controls the JMX proxy connections to the method servers. These MBeans have ObjectNames with the following pattern:
com.ptc:wt.processGroup=MethodServers,methodServer=MethodServer.processId
These MBeans appear in JConsole as the following in the JConsole MBean tree:
com.ptc > MethodServers > MethodServer.processId
The RemoteJmxUrl attribute of each of these MBeans provides the necessary remote JMX connection URL.
