Mechanism for Implementation of Endpoints as JMX MBeans in an Integrated Media and JAVA EE Application Server

• US 20100223614A1
• Filed: 02/27/2009
• Published: 09/02/2010
• Est. Priority Date: 02/27/2009
• Status: Active Grant

• Current Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Original Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Inventors: Bhayani, Amit, Kulikov, Oleg
• Granted Patent: US 8,615,607 B2
• Time in Patent Office: Days
• US Class Current: 718/1
• CPC Class Codes: G06F 2009/45587 Isolation or security of virtual machine instances
• CPC Class Codes: G06F 9/45504 Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects

Abstract

In one embodiment, a mechanism for implementation of endpoints as Java™ Management Extensions (JMX) MBeans in an integrated media and Java™ Enterprise Edition (JAVA EE) application server is disclosed. In one embodiment, a system includes an integrated application server including a media server and Java™ Enterprise Edition (JAVA EE) deployed in a single Java™ virtual machine (JVM), and one or more endpoints in the media server deployed as Java Management Extension (JMX) Mbeans.

Claims

1. A system, comprising:

an integrated application server including a media server and Java™

Enterprise Edition (JAVA EE) deployed in a single Java™

virtual machine (JVM); and

one or more endpoints in the media server deployed as Java Management Extension (JMX) Mbeans.

2. The system of claim 1, wherein the integrated application server includes a microkernel architecture based on JMX.

3. The system of claim 2, further comprising one or more management interfaces communicably coupled to the integrated application server to provide interfaces to one or more management applications that manage the media server using a decoupled invocation technique specified by the JMX architecture.

4. The system of claim 3, wherein the one or more management application may be located in same JVM as the media server.

5. The system of claim 1, wherein the one or more endpoints in the media server communicate with one another via one or more local in-VM pass-by reference semantics.

6. The system of claim 3, wherein the one or more endpoints deployed as JMX Mbeans emit a notification to be consumed by at least one of other endpoints of the one or more endpoints and the one or more management applications.

7. The system of claim 1, wherein the one or more endpoints include at least one of a T1 line endpoint, an E1 line endpoint, a fax line endpoint, a Time Division Multiplexing line endpoint, an Interactive Voice Response (IVR) endpoint, an Announcement endpoint, a Conference endpoint, an Echo endpoint, and a Packet Relay endpoint.

8. The system of claim 1, wherein each endpoint of the one or more endpoints includes a timer that generates a sequence of time marks, wherein at each time mark the endpoint provides a request to the media server to generate a chunk of real-time media that represents a time interval [T*n−

T*(n+1)] seconds, where T is period of packetization and n is a number of timer marks in T.

9. A computer-implemented method, comprising:

implementing media logic for an endpoint as an endpoint implementation object;

associating the endpoint implementation object with a Java Management Extensions (JMX) Managed Bean (MBean) to provide interaction capabilities for the endpoint with a JAVA Enterprise Edition (JAVA EE) application server; and

installing the endpoint as a JAVA EE service.

10. The method of claim 9, further comprising registering the endpoint with a Java Naming and Directory Interface (JNDI) service.

11. The method of claim 9, wherein the endpoint is hosted by a media server of an integrated application server including the media server and Java™

Enterprise Edition (JAVA EE) that are deployed in a single Java™

virtual machine (JVM).

12. The method of claim 11, wherein the integrated application server includes a microkemel architecture based on JMX.

13. The method of claim 11, wherein the endpoint emits a notification to be consumed by at least one of other endpoints and one or more management applications that manage the media server using a decoupled invocation technique specified by the JMX architecture.

14. The method of claim 9, wherein the endpoint includes at least one of a T1 line endpoint, an E1 line endpoint, a fax line endpoint, a Time Division Multiplexing line endpoint, an Interactive Voice Response (IVR) endpoint, an Announcement endpoint, a Conference endpoint, an Echo endpoint, and a Packet Relay endpoint.

15. The method of claim 11, wherein the endpoint includes a timer that generates a sequence of time marks, wherein at each time mark the endpoint provides a request to the media server to generate a chunk of real-time media that represents a time interval [T*n−

T*(n+1)] seconds, where T is period of packetization and n is a number of timer marks in T.

16. An article of manufacture comprising a machine-readable storage medium including data that, when accessed by a machine, cause the machine to perform operations comprising:

implementing media logic for an endpoint as an endpoint implementation object;

associating the endpoint implementation object with a Java Management Extensions (JMX) Managed Bean (MBean) to provide interaction capabilities for the endpoint with a JAVA Enterprise Edition (JAVA EE) application server; and

installing the endpoint as a JAVA EE service.

17. The article of manufacture of claim 16, wherein the machine-readable storage medium includes data that, when accessed by the machine, cause the machine to perform further operations comprising registering the endpoint with a Java Naming and Directory Interface (JNDI) service.

18. The article of manufacture of claim 16, wherein the endpoint is hosted by a media server of an integrated application server including the media server and Java™

Enterprise Edition (JAVA EE) that are deployed in a single Java™

virtual machine (JVM).

19. The article of manufacture of claim 18, wherein the endpoint emits a notification to be consumed by at least one of other endpoints and one or more management applications that manage the media server using a decoupled invocation technique specified by the JMX architecture.

20. The article of manufacture of claim 16, wherein the endpoint includes at least one of a T1 line endpoint, an E1 line endpoint, a fax line endpoint, a Time Division Multiplexing line endpoint, an Interactive Voice Response (IVR) endpoint, an Announcement endpoint, a Conference endpoint, an Echo endpoint, and a Packet Relay endpoint.