The JConsole which is part of the Oracle JDK, under the /bin
folder of the JDK installation, is a generic monitoring client which allows to see JMX
attributes and use JMX operations in a generic way.
Here, we use the JConsole only as one example of a monitoring application which supports JMX. The
information shown in the JConsole can also be used and accessed by other Monitoring
solutions as long as they provide a way to use JMX.
For the JConsole, complete the following steps to see the JMX information from Talend ESB:
Procedure
-
Type in
jconsole
from a command line window. (or start the
jconsole.exe directly from
{JAVA_HOME}/bin/jconsole.exe
in Windows, for example.
-
Set remote JMX URL by selecting Remote
Process and click Connect. This
opens the Java Monitoring & Management
Console.
The default URL for
Talend ESB
is:
Remote Process
|
service:jmx:rmi://localhost:44444/jndi/rmi://localhost:1099/karaf-trun
|
Username
|
tadmin
|
Password
|
tadmin
|
-
Once connected to the service, click the tab called MBeans.
-
Explore the Talend ESB related
MBeans:
- org.apache.camel - contains all information about Routes which run on
the Container. If no Routes are deployed, this node will not show in the
list.
- org.apache.cxf - shows all information about (SOAP/REST) Services
running on the Container which uses Apache CXF as Web framework (for
example, as the ESB Data Services do). Please be aware that this node
only shows in case a service has received at least one request.
- org.apache.activemq - shows all metric and management operations for the
message broker (Apache ActiveMQ).
- org.apache.karaf - shows the metric and management operations for the
Talend Runtime Container (based on Apache Karaf).
- TalendAgent (commercial editions only) - shows the Operating System and
Data Integration JobServer information.
Results
There are additional MBeans which can be seen and
used even so the above five are the most important ones for ESB.