System and method for JMS integration in a multitenant application server environment

• US 10,103,946 B2
• Filed: 09/25/2015
• Issued: 10/16/2018
• Est. Priority Date: 01/21/2014
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Xiao, Dongbo, Barnes, Thomas, Zhao, David, Wang, Jigang, He, Lily, Bhat, Padmanabha
• Primary Examiner(s): Yohannes, Tesfay
• Application Number:
  US14/865,733
• Publication Number:
  US 20160094498A1
• Time in Patent Office: 1,117 Days
• Field of Search: 709204, 709206, 709224, 709227, 370352
• CPC Class Codes: G06F 9/46 Multiprogramming arrangements
• CPC Class Codes: G06F 9/5061 Partitioning or combining of resources
• CPC Class Codes: H04L 41/0843 based on generic templates
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 41/122 of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV]
• CPC Class Codes: H04L 41/20 Network management software packages
• 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, a system and method provides a messaging service in a multitenant application server environment. Deployable resources are usable within the multitenant application server environment and groupings of resources are defined by resource group templates within a domain. One or more partitions are provided, with 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 foreign JMS server feature which maps remotely hosted JMS connection factories and JMS destinations into a local partition'"'"'s JNDI, so that bridges and applications in turn gain access to these resources by looking them up in this name-space.

Claims

1. A system for integrating a Java Message Service (JMS) application programming interface (API) in a multitenant 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 a domain of the application server environment, and

a plurality of partitions, wherein each partition provides an administrative and runtime subdivision of the domain that can be associated with a tenant, and wherein each partition includes a data source declared for use by applications deployed to the partition;

a directory service API configured to allow a client to look up data and objects via a name-space associated with each partition of the plurality of partitions;

a foreign JMS server within a partition from the plurality of partitions which maps resources including JMS connection factories and JMS destinations hosted remotely from the partition into a name-space associated with the partition, so that bridges and applications can access the resources by looking up names of the resources in the directory service API via the name-space associated with the partition;

wherein the foreign JMS server automatically decorates configuration and deployment MBean names with the partition name; and

wherein the foreign JMS server is usable to customize configurable attributes for the partition via overrides containing property key values; and

a database associated with the partition and isolated from others of the plurality of partitions;

wherein a name for a data source identified by the directory service API is configured in the foreign JMS server to enable a client to connect with the database associated with the partition via a Java Database Connectivity (JDBC) API connection provided by the data source.

2. The system of claim 1, wherein the foreign JMS server can be configured to reference the JNDI name of a hosted data source.

3. The system of claim 2, wherein the hosted data source is hosted at an application server.

10. The system of claim 1, wherein a JMS connection factory is returned to the client that contains a Uniform Resource Locator (URL) that is specific to the database associated with the partition with which the client is communicating.

11. The system of claim 10, wherein if the URL is not configured in the foreign JMS server mapping, the URL is configured to be automatically determined based on the data source name that is specified in the foreign JMS server and a configuration of the partition.

12. The system of claim 1, wherein bridges and applications access resources by looking up the resources in the directory service API via the name-space associated with a partition ID, and

wherein each partition is isolated from the other of the plurality of partitions by one of

inclusion of the partition ID on a thread when the JMS API is called from upon a deployment runtime, and

a context object identifying the partition.

19. The system of claim 1, further comprising:

a port dedicated for use by the partition;

wherein resources associated with JMS are accessible, via the port, to a legacy application that is not designed for a partitioned application server environment and that is instantiated in the domain or another of the plurality of partitions; and

wherein resources associated with JMS are accessible, via one or both of the port and a partition-specific URL, to an application that is designed for a partitioned application server environment and that is instantiated in the domain or another of the plurality of partitions.

4. A method for integrating Java Message Service (JMS) application programming interface (API) in a multitenant 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 a domain of the application server environment,

a plurality of partitions, wherein each partition provides an administrative and runtime subdivision of the domain that can be associated with a tenant, and wherein each partition includes a data source declared for use by applications deployed to the partition;

providing a directory service API configured to allow a client to look up data and objects via a name-space associated with each partition of the plurality of partitions;

providing a foreign JMS server within a partition from the plurality of partitions which maps JMS connection factories and JMS destinations hosted remotely from the partition into a name-space associated with the partition, so that bridges and applications can access the resources by looking up names of the resources in the directory service API via the name-space associated with the partition;

wherein the foreign JMS server automatically decorates configuration and deployment MBean names with the partition name; and

wherein the foreign JMS server is usable to customize configurable attributes for the partition via overrides containing property key values; and

providing a database associated with the partition and isolated from others of the plurality of partitions;

wherein a name for a data source identified by the directory service API is configured in the foreign JMS server to enable a client to connect with the database associated with the partition via a Java Database Connectivity (JDBC) API connection provided by the data source.

5. The method of claim 4, wherein the foreign JMS server can be configured to reference the JNDI name of a hosted data source.

6. The method of claim 5, wherein the hosted data source is hosted at an application server.

13. The method of claim 4, wherein a JMS connection factory is returned to the client that contains a Uniform Resource Locator (URL) that is specific to the database associated with the partition with which the client is communicating.

14. The method of claim 13, wherein if the URL is not configured in the foreign JMS server mapping, the URL is configured to be automatically determined based on the data source name that is specified in the foreign JMS server and a configuration of the partition.

15. The method of claim 4, wherein bridges and applications access resources by looking up the resources in the directory service API via the name-space associated with a partition ID, and

wherein each partition is isolated from the other of the plurality of partitions by one of

inclusion of the partition ID on a thread when the JMS API is called from upon a deployment runtime, and

a context object identifying the partition.

20. The method of claim 4, further comprising:

providing a port dedicated for use by the partition;

wherein resources associated with JMS are accessible, via the port, to a legacy application that is not designed for a partitioned application server environment and that is instantiated in the domain or another of the plurality of partitions; and

wherein resources associated with JMS are accessible, via one or both of the port and a partition-specific URL, to an application that is designed for a partitioned application server environment and that is instantiated in the domain or another of the plurality of partitions.

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

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

a plurality of partitions, wherein each partition provides an administrative and runtime subdivision of the domain that can be associated with a tenant, and wherein each partition includes a data source declared for use by applications deployed to the partition;

providing a directory service API configured to allow a client to look up data and objects via a name-space associated with each partition of the plurality of partitions;

providing a foreign JMS server within a partition from the plurality of partitions which maps JMS connection factories and JMS destinations hosted remotely from the partition into a name-space associated with the partition, so that bridges and applications can access the resources by looking up names of the resources in the directory service API via the name-space associated with the partition;

wherein the foreign JMS server automatically decorates configuration and deployment MBean names with the partition name; and

wherein the foreign JMS server is usable to customize configurable attributes for the partition via overrides containing property key values; and

providing a database associated with the partition and isolated from others of the plurality of partitions;

wherein a name for a data source identified by the directory service API is configured in the foreign JMS server to enable a client to connect with the database associated with the partition via a Java Database Connectivity (JDBC) API connection provided by the data source.

8. The non-transitory computer readable storage medium of claim 7, wherein the foreign JMS server can be configured to reference the JNDI name of a hosted data source.

9. The non-transitory computer readable storage medium of claim 8, wherein the hosted data source is hosted at an application server.

16. The non-transitory computer readable storage medium of claim 7, wherein a JMS connection factory is returned to the client that contains a Uniform Resource Locator (URL) that is specific to the database associated with the partition with which the client is communicating.

17. The non-transitory computer readable storage medium of claim 16, wherein if the URL is not configured in the foreign JMS server mapping, the URL is configured to be automatically determined based on the data source name that is specified in the foreign JMS server and a configuration of the partition.

18. The non-transitory computer readable storage medium of claim 7, wherein bridges and applications access resources by looking up the resources in the directory service API via the name-space associated with a partition ID, and

wherein each partition is isolated from the other of the plurality of partitions by one of

inclusion of the partition ID on a thread when the JMS API is called from upon a deployment runtime, and

a context object identifying the partition.