SYSTEM AND METHOD FOR MULTITENANCY STORE IN A MULTITENANT APPLICATION SERVER ENVIRONMENT

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

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: BARNES, THOMAS, XIAO, DONGBO, KING, DONALD L. Jr.
• Granted Patent: US 10,476,938 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 41/5041 characterised by the time relationship between creation and deployment of a service
• CPC Class Codes: H04L 41/5093 wherein the managed service relates to messaging or chat services
• 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/1001 for accessing one among a plurality of replicated servers

Abstract

In accordance with an embodiment, a system and method provides a messaging service in a multitenant application server environment. Deployable resources are usable within the multitenant environment and groupings of resources are defined by resource group templates within a domain. One or more partitions are provided, each partition providing an administrative and runtime subdivision of the domain that can be associated with a tenant. Java message service (JMS) resources are defined within a resource group template or a resource group, and instantiated within a partition to enable messaging for applications deployed within the partition and between partitions. Integrating JMS in a multitenant application server environment further includes a custom store defined within each of the resource group templates for use by the JMS resources. Components of the custom store are fully partition scoped and exist in an isolated JNDI name-space and use fully partition scoped runtime MBeans and configuration MBeans.

Claims

1. A system for supporting messaging in a multitenant application server environment, comprising:

one or more computers, including the multitenant application server environment executing thereon;

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

one or more resource group templates, which define groupings of deployable resources within a domain, and

one or more partitions, wherein each partition provides an administrative and runtime subdivision of the domain, that can be associated with a tenant; and

wherein one or more Java message service (JMS) resources can be defined within a resource group template or a resource group, and instantiated within a partition from the one or more partitions to enable messaging for applications deployed within the partition and between the one or more partitions; and

a custom store defined within each of the one or more resource group templates for use by the one or more JMS resources,

wherein components of the custom store are fully partition scoped and exist in an isolated JNDI name-space and use fully partition scoped runtime MBeans and configuration MBeans.

2. The system of claim 1, wherein import and export of partitioned file store data is prevented, as is migration of file store data from one cluster of servers to another.

3. The system of claim 1, wherein the one or more JMS resources includes JMS connection factories and their child resources associated with the partition for which they are configured.

4. The system of claim 1, wherein the one or more JMS resources includes default connection factories that can be available to applications in partitions.

5. A method for supporting messaging in a multitenant application server environment, comprising:

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

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

one or more resource group templates, which define groupings of deployable resources within a domain, and

one or more partitions, wherein each partition provides an administrative and runtime subdivision of the domain that can be associated with a tenant; and

wherein one or more Java message service (JMS) resources can be defined within a resource group template or a resource group, and instantiated within a partition from the one or more partitions to enable messaging for applications deployed within the partition and between the one or more partitions; and

a custom store defined within each of the one or more resource group templates for use by the one or more JMS resources,

wherein components of the custom store are fully partition scoped and exist in an isolated JNDI name-space and use fully partition scoped runtime MBeans and configuration MBeans.

6. The method of claim 5, wherein import and export of partitioned file store data is prevented, as is migration of file store data from one cluster of servers to another.

7. The method of claim 5, wherein the one or more JMS resources includes JMS connection factories and their child resources associated with the partition for which they are configured.

8. The method of claim 5, wherein the one or more JMS resources includes default connection factories that can be available to applications in partitions.

9. 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 multitenant application server environment, together with

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

one or more resource group templates, which define groupings of deployable resources within a domain, and

one or more partitions, wherein each partition provides an administrative and runtime subdivision of the domain that can be associated with a tenant; and

wherein one or more Java message service (JMS) resources can be defined within a resource group template or a resource group, and instantiated within a partition from the one or more partitions to enable messaging for applications deployed within the partition and between the one or more partitions; and

a custom store defined within each of the one or more resource group templates for use by the one or more JMS resources,

wherein components of the custom store are fully partition scoped and exist in an isolated JNDI name-space and use fully partition scoped runtime MBeans and configuration MBeans.

10. The non-transitory computer readable storage medium of claim 9, wherein import and export of partitioned file store data is prevented, as is migration of file store data from one cluster of servers to another.

11. The non-transitory computer readable storage medium of claim 9, wherein the one or more JMS resources includes JMS connection factories and their child resources associated with the partition for which they are configured.

12. The non-transitory computer readable storage medium of claim 9, wherein the one or more JMS resources includes default connection factories that can be available to applications in partitions.