JAXB MBean Wrapper for WS-Management CIM Interoperability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

There is a need for a method to utilize Java Management Extensions (JMX) MBeans to implement Web Services Management (WS-Management) Common Information Model (CIM) resources in a way that allows exposed MBeans to follow a standard XML schema defined externally to the Java platform, enabling effective monitoring and control of system resources across complex distributed systems.

Innovation Solution

The method involves generating Java API for XML Binding (JAXB)-serializable Java beans to create an MBean that wraps system resources from non-Java models, allowing for the serialization of these resources in XML and mapping JMX notifications to WS events, thereby enabling the exposure of system resources conforming to external XML schemas.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If JMX MBeans are used to manage system resources, then monitoring and control capabilities are improved, but interoperability with non-Java management models is limited

Engineering Contradiction:
Improvemonitoring and control capabilitiesVSAvoidinteroperability with non-Java management models
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces JAXB beans as an intermediary layer between JMX MBeans and WS-Management CIM resources. The MBean wraps a JAXB bean, which in turn represents the external management resource. This intermediary structure allows JMX to manage resources while maintaining compatibility with external XML schemas through the JAXB binding layer.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The MBean is designed to serve multiple functions: it acts as a JMX manageable resource, wraps a JAXB bean for XML serialization, and represents an external management resource. This multi-functionality enables a single component to bridge different management paradigms (JMX, JAXB, WS-Management) without requiring separate implementation for each.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If external XML schemas are followed for MBean exposure, then interoperability is improved, but control over serialization is lost

Engineering Contradiction:
ImproveinteroperabilityVSAvoidcontrol over serialization
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The JAXB bean automatically handles XML serialization based on the external schema through JAXB annotations and bindings. The MBean leverages this self-service capability of JAXB to maintain schema compliance without manual intervention, while the MBean itself retains control over the wrapped bean instance and its lifecycle.

Inventive Principle:
Principle #25Self-service

3Manufacturing precision

If JAXB beans are generated from XML schemas, then schema compliance is improved, but integration with JMX requires additional wrapping complexity

Engineering Contradiction:
Improveschema complianceVSAvoidintegration complexity
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

The architecture implements a nested structure where the MBean (JMX component) wraps the JAXB bean (XML binding component), which in turn represents the external management resource. This nesting allows each layer to maintain its own functionality while integrating with the outer layer, reducing the need for complex cross-layer coordination.

Inventive Principle:
Principle #7Nested doll (Nesting)

Data Source

PatentUS8132189B1WS-management resource MBean wrapper for JAXB beans
Publication Date: 2012.03.06 ORACLE AMERICAN INC
  • US8132189B1 patent drawing
  • US8132189B1 patent drawing
  • US8132189B1 patent drawing

AI summary

An approach is provided in embodiments of the present invention for utilizing Java™ Management Extensions (JMX) as a back end to “instrument” (i.e. monitor and control) computer system resources, including servers, devices, and applications etc., within standard resource management model(s) that are external to Java™. For example, JMX can be used as a back end to instrument WS-Management resources—in particular, JMX MBeans can be used to implement Common Information Model (CIM) WS-Management resources.