# US 2003/0069969 A1 · Method and apparatus for using java dynamic proxies to interface to generic, bean-like management entities

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2003/0069969 A1
- Document ID: US20030069969A1
- Status: Published application
- Kind: A1
- Application number: 10/255,422
- Filed: 2002-09-26
- Published: 2003-04-10
- Earliest claimed: 2001-09-28
- Assignees: BEA Systems, Inc.
- Inventors: Benjamin Jean-Baptiste Renaud
- Web page: https://patentgrep.com/patent/US20030069969A1

## CPC

- H04L 41/0226: Mapping or translating multiple network management protocols
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Dynamic management proxies provide type-safe, intuitive, and flexible interfaces to management entities. In an embodiment, a strongly-typed user interface is defined for each management entity. The dynamic proxy receives user requests via this user interface. The dynamic proxies converts user requests into generic requests in compliance with the management entities generic interface. The generic requests are communicated to the management entity via the generic interface. Dynamic management proxies are created at runtime. This allows the management interface to be seamlessly extended.

## Claims

### Claim 1

A proxy for controlling a management entity, comprising:
an application interface that communicates with an application, wherein the application interface includes at least one application function associated with the management entity for operating on a portion of the management entity;
a function translator that produces at least one management function corresponding to an application function; and
a management interface that communicates with the management entity via the corresponding management functions.

### Claim 2 (depends on 1)

The proxy of claim 1, wherein:
each application function associated with the management entity utilizes a specific data type associated with the management entity.

### Claim 3 (depends on 1)

The proxy of claim 1, wherein:
the portion of the management entity is a management attribute.

### Claim 4 (depends on 1)

The proxy of claim 1, wherein:
the portion of the management entity is a management function.

### Claim 5 (depends on 1)

The proxy of claim 1, wherein:
the management entity is a Java MBean.

### Claim 6 (depends on 5)

The proxy of claim 5, wherein:
the MBean is associated with a run-time operation.

### Claim 7 (depends on 5)

The proxy of claim 5, wherein:
the MBean is associated with a network resource.

### Claim 8 (depends on 1)

The proxy of claim 1, wherein:
the function translator and the management interface comprise a Java invocation handler.

### Claim 9 (depends on 1)

The proxy of claim 1, wherein:
the application is a management application.

### Claim 10 (depends on 1)

The proxy of claim 1, wherein:
the application is a MBean Server.

### Claim 11 (depends on 5)

The proxy of claim 5, wherein:
the management interface communicates management functions to the management entity via an MBean Server.

### Claim 12 (depends on 5)

The proxy of claim 5, wherein:
the management interface communicates management functions to the management entity via an MBeanHome.

### Claim 13 (depends on 2)

The proxy of claim 2, wherein:
the management interface receives a data response to at least one of the communicated management functions from the management entity;
the function translator converts the data response to the specific data type utilized by the application function associated with the management entity; and
the application interface communicates the converted data response to the application via the application function.

### Claim 14

A method for creating a proxy for controlling a management entity, comprising:
(a) retrieving entity information describing the management entity in response to an application request;
(b) evaluating the entity information to determine a management entity type instantiated by the management entity; and
(c) creating a proxy adapted to the management entity type and associated with the management entity.

### Claim 15 (depends on 14)

The method of claim 14, wherein Step (c) comprises:
creating an interface class object specifying an application interface associated with the management entity type;
creating an instance of an invocation handler associating at least the application interface with a corresponding management interface; and
invoking a proxy creation method on at least the instance of the invocation handler and the interface class object to create a proxy object associated with the management entity.

### Claim 16 (depends on 14)

The method of claim 14, wherein:
the application request specifies a management entity.

### Claim 17 (depends on 16)

The method of claim 16, further comprising the step of:
returning the proxy object to the application.

### Claim 18 (depends on 14)

The method of claim 14, wherein:
the application request specifies the value of at least one management attribute.

### Claim 19 (depends on 18)

The method of claim 18, wherein Step (a) further comprises:
locating management entities having the specified management attribute; and
retrieving entity information for a located management entity matching the value of the specified management attribute.

### Claim 20 (depends on 19)

The method of claim 19, further comprising the step of:
returning the proxy object to the application in an iterator;

### Claim 21 (depends on 14)

The method of claim 14, wherein:
the management entity is a Java MBean.

### Claim 22 (depends on 21)

The method of claim 21, wherein:
the MBean is associated with a run-time operation.

### Claim 23 (depends on 21)

The method of claim 21, wherein:
the MBean is associated with a network resource.

### Claim 24 (depends on 21)

The method of claim 21, wherein:
the entity information is retrieved from an MBean Server.

### Claim 25

A system for managing services of a distributed processing system, comprising:
a management entity of a specific management entity type associated with a service of the distributed processing system and having a management entity interface;
an application having an application interface; and
a management entity proxy for communicating information between the management entity and the application, wherein communication with the management entity is via the management entity interface, and wherein communication with the application is via the application interface.

### Claim 26 (depends on 25)

The system of claim 25, wherein:
the management entity interface includes at least one management entity function disassociated with the specific entity type; and
the application interface includes at least one application function associated with the specific management entity type.

### Claim 27 (depends on 26)

The system of claim 26, wherein:
the communication via the management entity interface utilizes the management entity function; and
the communication via the application interface utilizes the application function.

### Claim 28 (depends on 26)

The system of claim 26, wherein:
the application function utilizes a specific data type associated with the specific management entity.

### Claim 29 (depends on 28)

The system of claim 28, wherein:
the management entity function utilizes a general data type disassociated with the specific management entity.

### Claim 30 (depends on 29)

The system of claim 29, wherein:
the management entity proxy converts information to the general data type for communication with the management entity; and
the management entity proxy converts information to the specific data type for communication with the application.

### Claim 31 (depends on 25)

The system of claim 25, further comprising:
a management entity handler for communicating information between the management entity and the management entity proxy.

### Claim 32 (depends on 31)

The system of claim 31, wherein:
the management entity handler is comprised of a Java MBean Server.

### Claim 33 (depends on 32)

The system of claim 32, wherein:
the management entity handler is further comprised of an MBeanHome .

### Claim 34 (depends on 25)

The system of claim 25, wherein:
the service of the distributed processing system associated with the management entity is a management attribute.

### Claim 35 (depends on 25)

The system of claim 25, wherein:
the service of the distributed processing system associated with the management entity is a management function.

### Claim 36 (depends on 25)

The system of claim 25, wherein:
the management entity is a Java MBean.

### Claim 37 (depends on 36)

The system of claim 36, wherein:
the service of the distributed processing system is a run-time operation.

### Claim 38 (depends on 36)

The system of claim 36, wherein:
the service of the distributed processing system is a network resource.

### Claim 39 (depends on 36)

The system of claim 36, wherein:
the management entity proxy includes a Java invocation handler.

### Claim 40 (depends on 36)

The system of claim 36, wherein:
the application is an MBean Server.

### Claim 41

A method for converting functions of a strongly-typed interface to functions of a generic interface, comprising:
receiving a function invocation from the strongly-typed interface;
identifying the function invocation as an invocation of a function of a specific function type;
selecting at least one generic function of the generic interface corresponding to the specific function type; and
invoking the generic function.

### Claim 42 (depends on 41)

The method of claim 41, further comprising:
in the step of receiving, receiving a function argument of a first data type associated with the function invocation;
converting the function argument to a generic function argument of a second data type associated with the generic function; and
in the step of invoking, invoking the generic function with the generic function argument.

### Claim 43 (depends on 41)

The method of claim 41, further comprising:
receiving a generic function response of a first data type from the generic function;
converting the generic function response to a function response of a second data type associated with the function invocation from the strongly-typed interface; and
responding to the received function invocation with the function response of the second data type.

### Claim 44 (depends on 41)

The method of claim 41, wherein:
the generic function is a Java JMX function.

### Claim 45 (depends on 14)

An article of manufacture including an information storage medium wherein is stored information, the information comprising:
a group of processor readable instructions adapted to operate on a processing device, wherein the group of processor readable instructions are adapted to operate the processing device according to the method of claim 14.

### Claim 46 (depends on 41)

An article of manufacture including an information storage medium wherein is stored information, the information comprising:
a group of processor readable instructions adapted to operate on a processing device, wherein the group of processor readable instructions are adapted to operate the processing device according to the method of claim 41.

### Claim 47

A proxy for controlling a management entity, comprising:
an application interface means for communicating with an application, wherein the application interface means includes at least one application function associated with the management entity for operating on a portion of the management entity;
a function translator means for producing at least one management function corresponding to an application function; and
a management interface means for communicating with the management entity via the corresponding management functions.
