SYSTEM AND METHOD FOR JMX SUPPORT IN A MULTITENANT APPLICATION SERVER ENVIRONMENT

• US 20160094404A1
• Filed: 09/24/2015
• Published: 03/31/2016
• Est. Priority Date: 09/25/2014
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Bower, Peter, Sahoo, Sanjeeb, Islam, Nazrul, Nevins, Byron, Kasso, Christopher, Pan, QIANHONG, Mordani, Rajiv, Hossain, MD. Sazzad, Tabbasum, Rehana, Balasubramanyam, Yamini Kalyandurga
• Granted Patent: US 10,051,043 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 41/28 Restricting access to network management systems or functions, e.g. using authorisation function to access network configuration
• CPC Class Codes: H04L 41/5041 characterised by the time relationship between creation and deployment of a service
• CPC Class Codes: H04L 43/14 using software, i.e. software packages network security related monitoring H04L63/1408
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46

Abstract

In accordance with an embodiment, described herein is a system and method for JMX support in an application server environment. An exemplary method can provide, at one or more computers, including an application server environment executing thereon, a plurality of deployable resources which can be used within the application server environment, one or more partitions, a plurality of managed beans, each managed beans being a partition level managed bean or a domain level managed bean, each partition level managed bean originating at an originating partition of the one or more partitions, and a JMX framework comprising an API and a managed bean server. The plurality of managed beans can be registered at the managed bean server, with the partition level managed beans being decorated with an identifier.

Claims

1. A system for JMX support in an application server environment, comprising:

one or more computers, including an application server environment executing thereon, together with

a plurality of deployable resources which can be used within the application server environment,

one or more partitions, wherein each partition provides an administrative and runtime subdivision of a domain,

a plurality of managed beans, wherein each of the plurality of managed beans is a partition level managed bean or a domain level managed bean, each partition level managed bean originating at an originating partition of the one or more partitions, and

a JMX framework, wherein the JMX framework comprises an API and a managed bean server, wherein each of the plurality of managed beans is registered at the managed bean server; and

wherein each partition level managed bean registered at the managed bean server is decorated with an identifier, the identifier indicating the originating partition of the partition level managed bean.

2. The system of claim 1, wherein the JMX framework is configured to receive a request from a partition administrator, via a partition specific URL, to access one or more of the plurality of managed beans registered at the managed bean server.

3. The system of claim 2, wherein the API is configured to, based at least upon the partition specific URL, restrict access to the plurality of managed beans registered at the managed bean server.

4. The system of claim 3, wherein restricting access to the plurality of managed beans registered at the managed bean server comprises:

determining an association between the partition specific URL and a requesting partition of the one or more partitions and;

based upon the determination, allowing access to partition level managed beans decorated with a decorator associated with the requesting partition of the one or more partitions.

5. The system of claim 4, wherein the decorator associated with the requesting partition is hidden from the partition administrator.

6. The system of claim 1, wherein the application server environment comprises a multi-tenant application server environment, and wherein the system can associate the one or more partitions with a tenant, for use by the tenant.

7. The system of claim 1, wherein the JMX framework is configured to receive a request from a system administrator, via a global URL, to access one or more of the managed beans, and, based upon a determination by the API that the request was received via the global URL, allow access to the plurality of managed beans registered at the managed bean server.

8. A method for JMX support in an application server environment, comprising:

providing, at one or more computers, including an application server environment executing thereon,

a plurality of deployable resources which can be used within the application server environment,

one or more partitions, wherein each partition provides an administrative and runtime subdivision of a domain,

a plurality of managed beans, wherein each of the plurality of managed beans is a partition level managed bean or a domain level managed bean, each partition level managed bean originating at an originating partition of the one or more partitions, and

a JMX framework, wherein the JMX framework comprises an API and a managed bean server;

registering, at the managed bean server, the plurality of managed beans; and

decorating each partition level managed bean registered at the managed bean server with an identifier, the identifier indicating the originating partition of the partition level managed bean.

9. The method of claim 8, further comprising:

receiving a request, from a partition administrator via a partition specific URL, to access one or more of the plurality of managed beans registered at the managed bean server.

10. The method of claim 9, wherein the API is configured to, based upon the partition specific URL, restrict access to the plurality of managed beans registered at the managed bean server.

11. The method of claim 10, the restricting access to the plurality of managed beans registered at the managed bean server comprises:

determining an association between the partition specific URL and a requesting partition of the one or more partitions and;

based upon the determination, allowing access to partition level managed beans decorated with a decorator associated with the requesting partition of the one or more partitions.

12. The method of claim 11, further comprising:

hiding, from the partition administrator, the decorator associated with the requesting partition.

13. The method of claim 8, wherein the application server environment comprises a multi-tenant application server environment, and wherein the system can associate the one or more partitions with a tenant, for use by the tenant.

14. The method of claim 8, further comprising:

receiving a request, from a system administrator via a global URL, to access one or more of the plurality of managed beans registered at the managed bean server; and

based upon a determination by the API that the request was received via the global URL, allowing access to the plurality of managed beans registered at the managed bean server.

15. A non-transitory computer readable storage medium, including instructions stored thereon for JMX support in an application server environment which when read and executed by one or more computers cause the one or more computers to perform steps comprising:

providing, at one or more computers, including an application server environment executing thereon,

a plurality of deployable resources which can be used within the application server environment,

one or more partitions, wherein each partition provides an administrative and runtime subdivision of a domain,

a plurality of managed beans, wherein each of the plurality of managed beans is a partition level managed bean or a domain level managed bean, each partition level managed bean originating at an originating partition of the one or more partitions, and

a JMX framework, wherein the JMX framework comprises an API and a managed bean server;

registering, at the managed bean server, the plurality of managed beans; and

decorating each partition level managed bean registered at the managed bean server with an identifier, the identifier indicating the originating partition of the partition level managed bean.

16. The non-transitory computer readable storage medium of claim 15, the steps further comprising:

receiving a request, from a partition administrator via a partition specific URL, to access one or more of the plurality of managed beans registered at the managed bean server.

17. The non-transitory computer readable storage medium of claim 16, wherein the API is configured to, based upon the partition specific URL, restrict access to the plurality of managed beans registered at the managed bean server.

18. The non-transitory computer readable storage medium of claim 17, the steps further comprising:

determining an association between the partition specific URL and a requesting partition of the one or more partitions and;

based upon the determination, allowing access to partition level managed beans decorated with a decorator associated with the requesting partition of the one or more partitions.

19. The non-transitory computer readable storage medium of claim 18, the steps further comprising:

hiding, from the partition administrator, the decorator associated with the requesting partition.

20. The non-transitory computer readable storage medium of claim 15, the steps further comprising:

receiving a request, from a system administrator via a global URL, to access one or more of the plurality of managed beans registered at the managed bean server; and

based upon a determination by the API that the request was received via the global URL, allowing access to the plurality of managed beans registered at the managed bean server.