US6915519B2
Expired / Lapsed
US
⏱️ 0.0 years remaining
Pluggable JMS providers in a J2EE server
Assignee: International Business Machines Corp
•
Filing: 2001-07-12
•
Granted: 2005-07-05
•
Expires: 2021-07-12
Abstract
Abstract A method for allowing an enterprise application server to integrate and make use of any messaging product or products that support a standard messaging service interfaces. In a first phase of the method, an administrator creates and installs a new messaging provider on an application server, creates new messaging resource objects such as connection factories and destinations, and then binds these into the original namespace of the default messaging provider. An application which references the new messaging provider is then deployed onto the application server. Then, when the application program is executing, it may perform a lookup for the new messaging service, which the application server performs through the default context factory to obtain a new messaging object, which is then handed to the requesting application for use as needed. This method of indirection allows the application server to integrated and use any messaging service, not just the default messaging server originally integrated by the application server vendor.
Inventors
- 👤 Leigh Allen Williamson
- 👤 Roger L. Cundiff, Jr.
- 👤 Thomas Edward Musta
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-10-30 17:58
CPC Classifications
G; G06; G06F; G06F9/00; G06F9/06; G06F9/46; G06F9/54; G06F9/546; G06F9/465
Claims Analysis
Total Claims: 24
Claim 1
Independent Claim
146 words
A method of providing an extension to a default set or messaging resource functions in an enterprise application server, said application server having a default context factory class, said method comprising the steps of: providing an alternate extension messaging service provider on an application server node, said extension messaging service provider having a name, description, initial context factory, and a provider universal resource locator (URL), said application server node also having a default messaging service; creating one or more extension connection factories and destination resources; binding references to said extension connection factories and destination resources into a namespace; creating extension connection factory and destination resources in an application server administration domain; and subsequently accessing and using by an application program said alternate extension messaging service provider, connection factory and destination resources through performance of an indirect naming service lookup through said application server default context factory.
Claim 2
Independent Claim
146 words
A method of providing an extension to a default set or messaging resource functions in an enterprise application server, said application server having a default context factory class, said method comprising the steps of: providing an alternate extension messaging service provider on an application server node, said extension messaging service provider having a name, description, initial context factory, and a provider universal resource locator (URL), said application server node also having a default messaging service; creating one or more extension connection factories and destination resources; binding references to said extension connection factories and destination resources into a namespace; creating extension connection factory and destination resources in an application server administration domain; and subsequently accessing and using by an application program said alternate extension messaging service provider, connection factory and destination resources through performance of an indirect naming service lookup through said application server default context factory.
Claim 3
Dependent Claim
35 words
The method as set forth in claim 1 wherein said step of providing a extension messaging service provider on an application server node includes the step of specifying a classpath on said application server node.
Claim 4
Dependent Claim
37 words
The method as set forth in claim 2 wherein said step of specifying a classpath on an application server node includes specifying a location of the extension messaging service provider's jar file on said application server node.
Claim 5
Dependent Claim
29 words
The method as set forth in claim 2 wherein said step of specifying a classpath on an application server node includes specifying a naming service binding mechanism class name.
Claim 6
Dependent Claim
36 words
The method as set forth in claim 1 wherein said step of creating extension connection factory and destination resources in an application server administration domain includes specifying a name, description, and an external naming service name.
Claim 7
Dependent Claim
39 words
The method as set forth in claim 5 wherein said step of specifying a name, description, and an external naming service name includes specifying a location where said extension connection factory and destination resources were bound into said namespace.
Claim 8
Dependent Claim
25 words
The method as set forth in claim 1 wherein said step of providing an extension messaging service provider comprises providing a Java Messaging Service provider.
Claim 9
Dependent Claim
161 words
A computer readable medium encoded with software for providing an extension to a default set of messaging resource functions in an enterprise application server computer system, said application server having a default context factory class, said software when executed by an application server to perform the following steps: provide an alternate extension messaging service provider on an application server node, said extension messaging service provider having a name, description, initial context factory, and a provider universal resource locator (URL), said application server node also having a default messaging service; create one or more extension connection factories and destination resources; bind references to said extension connection factories and destination resources into a namespace; create extension connection factory and destination resources in an application server administration domain; and subsequently access and use by an application program of said alternate extension messaging service provider, connection factory and destination resources through performance of an indirect naming service lookup through said application server default context factory.
Claim 10
Dependent Claim
161 words
A computer readable medium encoded with software for providing an extension to a default set of messaging resource functions in an enterprise application server computer system, said application server having a default context factory class, said software when executed by an application server to perform the following steps: provide an alternate extension messaging service provider on an application server node, said extension messaging service provider having a name, description, initial context factory, and a provider universal resource locator (URL), said application server node also having a default messaging service; create one or more extension connection factories and destination resources; bind references to said extension connection factories and destination resources into a namespace; create extension connection factory and destination resources in an application server administration domain; and subsequently access and use by an application program of said alternate extension messaging service provider, connection factory and destination resources through performance of an indirect naming service lookup through said application server default context factory.
Claim 11
Dependent Claim
37 words
The computer readable medium as set forth in claim 8 wherein said software for providing a extension messaging service provider on an application server node includes the software for specifying a classpath on said application server node.
Claim 12
Dependent Claim
41 words
The computer readable medium as set forth in claim 9 wherein said software for specifying a classpath on an application server node includes software for specifying a location of the extension messaging service provider's jar file on said application server node.
Claim 13
Dependent Claim
33 words
The computer readable medium as set forth in claim 9 wherein said software for specifying a classpath on an application server node includes software for specifying a naming service binding mechanism class name.
Claim 14
Dependent Claim
40 words
The computer readable medium as set forth in claim 8 wherein said software for creating extension connection factory and destination resources in an application server administration domain includes software for specifying a name, description, and an external naming service name.
Claim 15
Dependent Claim
43 words
The computer readable medium as set forth in claim 12 wherein said software for specifying a name, description, and an external naming service name includes software for specifying a location where said extension connection factory and destination resources were bound into said namespace.
Claim 16
Dependent Claim
29 words
The computer readable medium as act forth in claim 8 wherein said software for providing an extension messaging service provider comprises software for providing a Java Messaging Service provider.
Claim 17
Dependent Claim
143 words
A extension system for a default set of messaging resource functions in an enterprise application server, said application server having a default context factory class, said extension system comprising: an alternate extension messaging service provider on an application server node, said extension messaging service provider having a name, description, initial context factory, and a provider universal resource locator (URL), said application server node also having a default messaging service; one or more extension connection factories and destination resources; bound references to said extension connection factories and destination resources in a namespace; extension connection factory and destination resources created in an application server administration domain; and an application program interface for accessing and using by an application program said alternate extension messaging service provider, connection factory and destination resources through performance of an indirect naming service lookup through said application server default context factory.
Claim 18
Dependent Claim
143 words
A extension system for a default set of messaging resource functions in an enterprise application server, said application server having a default context factory class, said extension system comprising: an alternate extension messaging service provider on an application server node, said extension messaging service provider having a name, description, initial context factory, and a provider universal resource locator (URL), said application server node also having a default messaging service; one or more extension connection factories and destination resources; bound references to said extension connection factories and destination resources in a namespace; extension connection factory and destination resources created in an application server administration domain; and an application program interface for accessing and using by an application program said alternate extension messaging service provider, connection factory and destination resources through performance of an indirect naming service lookup through said application server default context factory.
Claim 19
Dependent Claim
26 words
The extension system as set forth in claim 15 wherein said extension messaging service provider includes a specification of a classpath on said application server node.
Claim 20
Dependent Claim
37 words
The extension system as set forth in claim 16 wherein said specification of a classpath on an application server node includes a location specification of the extension messaging service provider's jar file on said application server node.
Claim 21
Dependent Claim
29 words
The extension system as set forth in claim 16 wherein said specification of a classpath on an application server node includes a naming service binding mechanism class name specification.
Claim 22
Dependent Claim
30 words
The extension system as set forth in claim 15 wherein said extension connection factory and destination resources includes a specification of a name, description, and an external naming service name.
Claim 23
Dependent Claim
39 words
The extension system as set forth in claim 19 wherein said specification of a name, description, and an external naming service name includes a location specification where said extension connection factory and destination resources are bound into said namespace.
Claim 24
Dependent Claim
21 words
The extension system as set forth in claim 15 wherein said extension messaging service provider comprises a Java Messaging Service provider.
References Cited (Backward Citations)
US5265206A
Cited
US6167432A
Cited
US6003094A
Cited
US6633923B1
Cited
US20020004848A1
Cited
US20020004850A1
Cited
US20030005117A1
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2008-07-04 | 2009-01-03 | 2009-07-05 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2012-07-04 | 2013-01-03 | 2013-07-05 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2016-07-04 | 2017-01-03 | 2017-07-05 | $7700.00 | Window Closed / Lapsed |