Improve Application Management With JMX
Leverage JMX technology and existing tools to boost the operations management capabilities of your business applications.
Tutorial Details:
The explosion of enterprise computing in the last decade has led to the proliferation of large-scale, server-based applications, many of which are deployed within a complex mixture of software and hardware components. As the scope and complexity of applications grow, capabilities for efficient and flexible management of their proper operation become increasingly essential to the success of business activities. On one hand, systems administrators face the challenge of managing a diverse amalgam of system- and application-specific components, each with its own set of administration facilities. On the other hand, managers and decision makers seeking to improve business processes need appropriate tools for business activity monitoring (BAM).
The development of custom application management software follows a common pattern, but it\'s nontrivial and it usually requires considerable effort. Moreover, it leads to inconsistent, incompatible, and platform-dependent solutions that put an unnecessary burden on both application developers and system operators. These and similar considerations have led to the development of the Java Management Extensions (JMX) API, a Java Community Process (JCP) specification geared toward the simplification and standardization of the runtime management infrastructure of enterprise Java applications.
I\'ll first examine the concepts and architecture behind JMX technology, then outline several informal examples of JMX use. Finally, I\'ll present a concrete programming example to show how you can combine JMX with aspect-oriented programming (AOP) technology to instrument your application without disrupting core business logic.
JMX Concepts and Architecture
JMX is conceptually simple, yet bears the fruit of years of domain experience and research. In a nutshell, JMX defines a standard means for applications to expose management functionality, a process called instrumentation, and a standard management middle tier, the JMX agent, which acts as a single point of entry to management components. So, application management in JMX is architecturally divided into three levels (see Figure 1):
* Instrumentation level: The level at which applications expose their management functionality. Application instrumentation relies on a few naming conventions and Java interfaces, and is completely independent of the particular JMX agent or management application operating it.
* Agent level: A container of instrumented entities and a set of standard management services. The agent is the core of a JMX implementation. In addition to delivering the services mandated by the specification, implementations can provide extensions, most notably in the form of protocol adaptors and connectors for remote access.
* Management level: The client level, encompassing various management applications. These include generic tools providing direct access to one or several distributed JMX agents, application-specific solutions that rely on particular domain knowledge, and scripting environments for management automation.
Read
Tutorial at: Click here to view the tutorial
Rate Tutorial: Improve Application Management With JMX
View Tutorial: Improve Application Management With JMX
Related
Tutorials:
 Create automated and distributed
management applications with Jiro
technology, Part 1 - JavaWorld February
Create automated and distributed
management applications with Jiro
technology, Part 1 - JavaWorld February 2000
|
JavaWorld
December 1999
JavaWorld
December 1999
|
Product Review:
Kawa 4.0 -
JavaWorld June
2000
Product Review:
Kawa 4.0 -
JavaWorld June
2000
|
J2EE project
dangers! - JavaWorld March 2001
J2EE project
dangers! - JavaWorld March 2001
|
Superior app management with JMX - JavaWorld June
Integrate JMX, a reusable configuration framework, with your JSPs
|
J2EE or J2SE?
JNDI works with both
J2EE or J2SE?
JNDI works with both
|
Score big with
JSR 77, the J2EE Management Specification
Score big with
JSR 77, the J2EE Management Specification
|
Rumble in the
jungle: J2EE versus .Net, Part
1
Rumble in the
jungle: J2EE versus .Net, Part
1
|
Best tools for
mobile application development
Best tools for
mobile application development
|
Welcome to the WfMOpen project
WfMOpen is a J2EE based implementation of a workflow facility (workflow engine) as proposed by the Workflow Management Coalition (WfMC) and the Object Management Group (OMG).
|
High-availability mobile applications
High-availability mobile applications
|
Improve Application Management With JMX
Improve Application Management With JMX
Leverage JMX technology and existing tools to boost the operations management capabilities of your business applications.
|
Eclipse plugin
eva/3 Application Builder
for visual development and database management
Eclipse plugin eva/3 Application Builder for visual development and database management.
|
eva/3 Application Builder supports eclipse 3
What is eva/3 Application Builder?
eva/3 Application Builder assumes responsibility for the design of
forms and reports via an integrated GUI Builder, the execution
of procedures and the handling of diverse relational SQL databases
through JDBC int
|
Monitoring Local and Remote Applications Using JMX 1.2 and JConsole
Monitoring Local and Remote Applications Using JMX 1.2 and JConsole
The latest release of Java, J2SE 5.0 (codenamed Tiger), adds core support for the Java Management Extensions (JMX) 1.2 into the Java standard libraries. This article walks you through h
|
Java Application Instrumentation with Log4J
Java Application Instrumentation with Log4J
Application metrics, such as performance metrics, are key to understanding and improving application efficiency. Profiling and monitoring tools yield valuable information on CPU and resource usage, including OS
|
XML Messaging Using JBoss
It\'s common practice to share data using FTP, but an increasingly popular alternative is to use a messaging service. As always, each approach has its own pros and cons, depending on the nature of "what to share," how easy it is to implement the technolog
|
A first look at Apache Geronimo
Start developing and deploying J2EE apps on the first open source J2EE server. When released, Geronimo will be the first J2EE-certified open source server. This article will give you the basics you need for developing and deploying J2EE applications on Ge
|
Using JConsole to Monitor Applications
JConsole is the Java Monitoring and Management Console, a new graphical tool shipped in J2SE JDK 5.0. This article describes how JConsole can be used to observe information about an application running on the Java platform, with an overview of the J2SE 5.
|
Getting Started with Java Management Extensions (JMX): Developing Management and Monitoring Solutions
The Java Management Extensions (JMX) API is a standard specification developed through the Java Community Process (JCP) as JSR 3 for managing and monitoring applications and services.
|
|
|
|
