SYSTEM AND METHOD FOR SUPPORTING NAMESPACES IN A MULTITENANT APPLICATION SERVER ENVIRONMENT

• US 20160014212A1
• Filed: 07/14/2015
• Published: 01/14/2016
• Est. Priority Date: 07/14/2014
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: MORDANI, RAJIV, FEIGEN, LAWRENCE, ZHANG, LEIMENG, SHAN, GUOJUN, SHANNON, WILLIAM, LIN, YUN, CHEN, CHUNTAO
• Granted Patent: US 9,906,601 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 9/5077 Logical partitioning of resources; Management or configuration of virtualized resources specific details on emulation or internal functioning of virtual machines G06F9/455
• 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
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

In accordance with an embodiment, described herein is a system and method for supporting namespaces in a multitenant application server environment. The application server environment can include a domain with a plurality of partitions. A global namespace or JNDI tree bound to domain-level resources can maintain a collection of partition root nodes, with each partition root node being the root node of a partition JNDI tree. Each node in a partition JNDI tree is made partition-aware by including properties specific to a particular partition. An initial context for a partition can be created for use in dispatching resource lookup requests to the partition, and can be reused by other applications in accessing resources in the partition.

Claims

1. A system for supporting multiple Java naming and directory interface (JNDI) trees in an application server environment, comprising:

one or more computers, each including one or more microprocessors;

an application server environment on the computers, wherein the application server environment includes a domain with a plurality of partitions, and a global JNDI tree that maintains a collection of partition root naming nodes, wherein each partition naming nodes is associated a partition JNDI tree;

wherein the system, when receiving a request from an application for accessing resources in a particular partition, operates to

create an initial JNDI context associated with the particular partition, and

delegate JNDI operations from the application to a JNDI tree associated with the particular partition.

2. The system of claim 1, wherein the system further operates to examine information from the request and the collection of partition root naming nodes to identify the partition JNDI tree.

3. The system of claim 1, wherein the information from the request includes a provider URL that specifies information about the particular partition.

4. The system of the claim 1, wherein resources deployed in a partition are bound to an associated partition JNDI tree, wherein each node in the associated JNDI tree is partition-aware.

5. The system of claim 1, wherein the initial context, once created, is maintained as a context object for reuse by one or more other applications, wherein JNDI operations from the applications are directed to the partition associated with the context object.

6. The system of claim 5, the association between the context object and the partition is maintained by associating the context object with a name space of the partition.

7. The system of claim 5, wherein a plurality of callback functions are provided in the JNDI subsystem to enable the JNDI operations to be processed in a component invocation context of the partition.

8. A method system for supporting multiple Java naming and directory interface (JNDI) trees in an application server environment, comprising:

providing a domain in an application server environment, wherein the domain includes a plurality of partitions, and a global JNDI tree that maintains a collection of partition root naming nodes, wherein each partition root naming nodes is associated a partition JNDI tree specific to a partition;

receiving a request from an application for accessing resources in a particular partition;

creating an initial JNDI context associated with the particular partition; and

delegating JNDI operations from the application to a JNDI tree associated with the particular partition.

9. The method of claim 8, wherein the system further operates to examine information from the request and the collection of partition root naming nodes to identify the partition JNDI tree.

10. The method of claim 8, wherein the information from the request includes a provider URL that specifies information about the particular partition.

11. The method of the claim 8, wherein resources deployed in a partition are bound to an associated partition JNDI tree, wherein each node in the associated JNDI tree is partition-aware.

12. The method of claim 8, wherein the initial context, once created, is maintained as a context object for reuse by one or more other applications, wherein JNDI operations from the applications are directed to the partition associated with the context object.

13. The method of claim 12, the association between the context object and the partition is maintained by associating the context object to a name space of the partition.

14. The method of claim 12, wherein a plurality of callback functions are provided in the JNDI subsystem to enable the JNDI operations to be processed in a component invocation context of the partition.

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

providing a domain in an application server environment, wherein the domain includes a plurality of partitions, and a global JNDI tree that maintains a collection of partition root naming nodes, wherein each partition root naming nodes is associated a partition JNDI tree specific to a partition;

receiving a request from an application for accessing resources in a particular partition;

creating an initial JNDI context associated with the particular partition; and

delegating JNDI operations from the application to a JNDI tree associated with the particular partition.

16. The non-transitory computer readable storage medium of claim 15, wherein the system further operates to examine information from the request and the collection of partition root naming nodes to identify the partition JNDI tree.

17. The non-transitory computer readable storage medium of claim 15, wherein the information from the request includes a provider URL that specifies information about the particular partition.

18. The non-transitory computer readable storage medium of claim 15, wherein resources deployed in a partition are bound to an associated partition JNDI tree, wherein each node in the associated JNDI tree is partition-aware.

19. The non-transitory computer readable storage medium of claim 15, wherein the initial context, once created, is maintained as a context object for reuse by one or more other applications, wherein JNDI operations from the applications are directed to the partition associated with the context object.

20. The non-transitory computer readable storage medium of claim 19, the association between the context object and the partition is maintained by associating the context object to a name space of the partition.