|
Java in the management sphere, Part 1
From its inception, the Java platform has been a natural choice for potential system and network management applications -- yet the platform seems to have been relatively slow to mature, providing neither a ubiquitous management framework nor an abundance of applications in that problem space.
|
|
Java in the management sphere, Part 2
The Java platform has been relatively slow to mature in the management arena, providing neither a ubiquitous management framework nor an abundance of applications in that problem space. In the second installment of this three-part series, Max Goff takes you through Java's short history and its emergence into the management arena with two technologies: JMX (formerly JMAPI) and Java DMK
|
|
Java in the management sphere, Part 3
Although a natural choice for developers in system and network management, the Java platform has been relatively slow to mature, providing neither a ubiquitous framework nor an abundance of applications in that space. In the final installment of a three-part series, Max Goff speculates on the future of management applications and shows how the Java community is making strides with Java extensions -- JMX, Jini and Jiro -- in this expanding arena.
|
|
Enabling Component Architectures with JMX
Java Management Extensions (JMX) has been in development at Sun Microsystems for several years, formerly named JMAPI, and lately has been increasingly associated with the management of the J2EE platform as an underlying architecture for J2EE servers.
|
|
Overview of WebLogic JMX Services
To provide open and extensible management services, WebLogic Server implements the Sun Microsystems, Inc. Java Management Extensions (JMX) 1.0 specification. All WebLogic Server resources are managed through these JMX-based services, and third-party services and applications that run within WebLogic Server can be managed through them as well.
|
|
Tivoli's Implementation of the JMX Specification
TMX4J is Tivoli's implementation of the JavaTM Management Extensions (JMX) Specification, which defines architecture, design patterns, APIs, and services for application and network management in Java. TMX4J implements all of the specified JMX interfaces and classes but has yet to be tested for complete conformance by the JMX Technology Compatibility Kit.
|
|
Superior app management with JMX : Integrate JMX, a reusable configuration framework, with your JSPs
Ever heard of JMX? If you think it's just a sideline framework, think again. Java Management Extensions (JMX) is becoming a core part of application development and management. Many J2EE vendors, such as JBoss, Enhydra, and WebLogic, are using it. Read on for an introduction to JMX, followed by a hands-on example for using it with JSP. Take a step forward in implementing JMX into your own development environment.
|
|
Communicating with JMX Agents
You had your first exposure to working with an MBean server by using the HTML
adapter you registered on the server. Previous chapters reminded you how JMX
uses protocol adapters and connectors to enable a JMX agent for use by the out-side
world.
|
|
JMX Tutorial
The intention of this tutorial is, to make the readers familiar with the features supported by AdventNet Agent Toolkit, for JMX agents. The power of the Tools, present in the toolkit and the Rich agent features, are illustrated in this tutorial by developing a Reference Implementation Agent for a Web-Server application. With this implementation, you can view the statistics and performance of the application and also configure them from a remote place using a manager.
|
|
J2EE via JMX - Managing EJBs using JMX Agent
Enterprise JavaBeans is a state-of-the-art architecture for developing, deploying and managing reliable enterprise applications in production environment. However managing these EJBs or having client access using management protocols like SNMP,HTTP becomes very essential , especially for entity beans. AdventNet JMX architecture provides solution to manage entity EJBs using protocols like SNMP, HTTP, TL1, RMI, Corba.
|
|
AdventNet Agent Toolkit Java/JMX Edition 5.0
Most of the management systems are built from top to bottom either by SNMP, TL1 or HTTP. They leverage the specific facilities offered by the selected management protocol. For example, application server vendors are keen at SNMP for their management needs. Similarly TL1 is a man-machine management protocol deployed in broadband and access networks, including SONET networks. New technologies such as WDM and xDSL sometimes use the TL1 protocol for management of network equipment.
|
|
Score big with JSR 77, the J2EE Management Specification
The Java Community Process (JCP) has released the proposed final draft for the J2EE Management Specification, or Java Specification Request (JSR) 77. The specification's core is based on the model of managed objects, which Dirk Laessig explains in this article. JSR 77 also defines an Enterprise JavaBeans (EJB) component for easily accessing these managed objects.
|
|
OpenWings
This document defines the Openwings Management framework. The purpose of this
framework is to provide management of Openwings components and services. Since one
of the major goals of Openwings is the ability to build systems that require zero-administration
at run-time, most of the management services are maintenance purposes or
to configure policies prior to deploying the system.
|
|
JMX and J2EE servers, a match in heaven?
JMX or Java Management eXtenstions are a new standard from Sun. It basically defines standards for writing JMX objects, also called MBeans and defines a standard for the container that hosts these MBeans. It's possible for a JMX client to invoke methods and access attributes on an MBean using the container. It's also possible for a client to register with another MBean and receive notifications from the MBean. So far, we're just taking about an application using a JMX container so that it can host MBean components in the application.
|
|
Dynamic Management for the Service Age
Corporations and service providers are facing new challenges to manage
service-driven environments in all industry segments. In these environments, the
managed resources (which can indifferently be applications, devices, services or
network policies) appear, move and disappear across the network, as they are
created, installed, activated and used at a pace never experienced before.
|
|
Java Management Extensions for application management
Modern enterprise systems are composed of both centralized and distributed applications. Many of these applications are business-critical, creating the need for their control and management by existing management systems. A single suite of uniform instrumentation for manageability is needed to make this cost-effective. The Java™ Management Extensions Agent and Instrumentation Specification, v 1.0, describes an isolation layer between an information technology resource and an arbitrary (enterprise-specific) set of management interfaces and systems.
|
|
CODEONLINE
The purpose of this document is to specify the architecture of the MONNI platform. The chosen design
principles are introduced, and the philosophy behind the architecture is explained. Document explains
the framework so that the referenced API and Rational Rose model can be better understood.
|
|
Performance Management in Component-Oriented Systems
Developers often lack the time or knowledge to
profoundly understand the performance issues in large-scale
component-oriented enterprise applications. This
situation is further complicated by the fact that such
applications are often built using a mix of in-house and
Commercial-Off-The-Shelf (COTS) components.
company to achieve a competitive advantage in their
markets.
|
|
Support Readiness Document
Java™ Dynamic Management Kit,
Version 5.0
This document provides support readiness information for the JavaÔ Dynamic
Management Kit (JDMK), Version 5.0.
|
|
Application Server Management: AD Implications
Gartner estimates that 40 percent of unplanned downtime results from application failures (see "Making Smart Investments to Reduce Downtime"). These failures can be caused by programming bugs, performance issues or changes to applications that result in breakage. Although many vendors offer solutions to provide Java application instrumentation after the fact (that is, in production), the best time to do this is during the initial development process (see "Application Server Management: Availability/Performance").
|
|
The Management of J2EE (and .NET) Applications
One of the fastest growing segments in infrastructure management has been application management.
This is a consequence of the focus on user productivity and confirms the fact that more and more we are
moving away from device-centric management. Within this segment today, J2EE platform management
is only a very thin slice, and .NET management is almost non-existent. But, if we believe that this is the
next big thing in application architecture, then we may well see this area converted into a bigger slice of
the pie, and eventually, envision most of the application management segment being dedicated to J2EE
and .NET applications.
|