Implementation of endpoints as JMX MBeans in an integrated media and JAVA EE application server

• US 8,615,607 B2
• Filed: 02/27/2009
• Issued: 12/24/2013
• 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
• Primary Examiner(s): Keehn, Richard G
• Application Number:
  US12/395,501
• Publication Number:
  US 20100223614A1
• Time in Patent Office: 1,761 Days
• Field of Search: 709/250
• US Class Current: 709/250
• 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:

a memory;

a processing device to execute a Java™

virtual machine (JVM) from the memory;

an integrated application server executable from the memory by the processing device, the integrated application server deployed in the JVM and comprising;

a media server deploying one or more endpoints as Java Management Extension (JMX) MBeans; and

a Java TM Enterprise Edition (JAVA EE) application server sharing a common microkernel architecture with the media server via installation of the one or more endpoint JMX MBeans of the media server as logically-separate services of a microkernel of the JAVA EE application server; and

one or more management interfaces communicably coupled to the integrated application server, the one or more management interfaces to manage the one or more endpoints via interactions with the JMX MBeans of the one or more endpoints installed as logically-separate services of the microkernel of the JAVA EE application server.

2. The system of claim 1, wherein the common microkernel architecture is based on JMX.

3. The system of claim 2, wherein the one or more management interfaces further 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 is located in the JVM that the media server implementation is located.

5. 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 or the one or more management applications.

6. 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.

7. The system of claim 1, wherein the one or more endpoints comprise at least one of a T1 line endpoint, an El 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, or a Packet Relay endpoint.

8. The system of claim 1, wherein each endpoint of the one or more endpoints comprises 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 portion of 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:

executing, by a computing device, media logic for an endpoint as an endpoint implementation object, wherein the endpoint is deployed in a media server of the computing device;

associating, by the computing device, 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;

installing, by the computing device, the JMX MBean associated with the endpoint as a logically-separate service of a microkernel of the JAVA EE application server, wherein the installing the JMX Mbean associated with the endpoint as a JAVA EE microkernel service creates an integrated application server comprising the media server and the JAVA EE application server sharing a common microkernel architecture on the computing device; and

managing, by one or more management interfaces communicably coupled to the integrated application server, the one or more endpoints via interactions with the JMX MBeans of the one or more endpoints installed as logically-separate services of the microkernel of the JAVA EE application server.

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 media server implementation and the JAVA EE application server are deployed in a single Java™

virtual machine (JVM) to create the integrated application server.

12. The method of claim 11, wherein the endpoint comprises 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 portion of 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.

13. The method of claim 9, wherein the common microkernel architecture is based on JMX.

14. The method of claim 13, wherein the endpoint emits a notification that is consumed by at least one of other endpoints or one or more management applications that manage the media server using a decoupled invocation technique specified by the common microkernel architecture based on JMX.

15. The method of claim 9, wherein the endpoint comprises at least one of a T1 line endpoint, an El 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, or a Packet Relay endpoint.

16. A non-transitory machine-readable storage medium including data that, when accessed by a processing device, cause the computing device to perform operations comprising:

executing, by the processing device of a computing device, media logic for an endpoint as an endpoint implementation object, wherein the endpoint is deployed in a media server of the computing device;

associating, by the computing device, 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;

installing, by the computing device, the JMX MBean associated with the endpoint as a logically-separate service of a microkernel of the JAVA EE application server, wherein the installing the JMX Mbean associated with the endpoint as a JAVA EE microkernel service creates an integrated application server comprising the media server and the JAVA EE application server sharing a common microkernel architecture on the computing device; and

managing, by one or more management interfaces communicably coupled to the integrated application server, the one or more endpoints via interactions with the JMX MBeans of the one or more endpoints installed as logically-separate services of the microkernel of the JAVA EE application server.

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

18. The non-transitory machine-readable storage medium of claim 16, wherein the media server and the JAVA EE application server are deployed in a single Java™

virtual machine (JVM) to create the integrated application server.

19. The non-transitory machine-readable storage medium of claim 18, wherein the endpoint emits a notification that is consumed by at least one of other endpoints or one or more management applications that manage the media server using a decoupled invocation technique specified by the common microkernel architecture based on JMX.

20. The non-transitory machine-readable storage medium of claim 16, wherein the endpoint comprises at least one of a T1 line endpoint, an El 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, or a Packet Relay endpoint.