JMS Provider With Plug-Able Business Logic

• US 20090313338A1
• Filed: 03/14/2007
• Published: 12/17/2009
• Est. Priority Date: 03/18/2006
• Status: Active Grant

• Current Assignee: Metafluent LLC
• Original Assignee: Metafluent LLC
• Inventors: MacGaffey, Andrew, Lankford, Peter
• Granted Patent: US 8,161,168 B2
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: H04L 45/00 Routing or path finding of packets in data switching networks routing or path finding in wireless networks H04W40/00
• CPC Class Codes: H04L 45/24 Multipath
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066

Abstract

The invention provides plug-in framework, enabling embedding of content-based processes to in a messaging paradigm provider service. In the preferred embodiment, the messaging paradigm is JMS and the invention provides a plug-able framework embedded in a JMS Provider. The plug-able server is particularly suited for efficient and secure transmission of real-time, streaming data.

Claims

1. A computer implemented client-server system, said system having a messaging service provider (Provider) infrastructure including domain specific implementations of a corresponding messaging paradigm comprising:

A) a Provider implementation comprised of a Provider Client Library;

B) a Server application that supports plug-able plug-in implementations of the Provider messaging paradigm; and

C) mechanisms that are plug-able and which function to allocate and manage connections and sessions with Provider clients, and which activate the appropriate plug-in when a topic or queue is requested, according to the destination namespace mappings that have been configured.

2. A system as in claim 1 wherein said Provider infrastructure further includes a mechanism of establishing a Client Session in a particular Application Context.

3. A system as in claim 2 wherein in said Provider infrastructure said mechanism for establishing said Application Context is by means of a JMS server plug-in and wherein said Client session is a JMS Client Session.

4. A system as in claim 3 wherein said Provider infrastructure further includes a mechanism for mapping other plug-ins into the destination namespace and where said mechanism is a plug-in.

5. A system as in claim 3 wherein said Provider infrastructure further includes a mechanism for implementation of the standard JMS messaging paradigm and wherein said plug-in provides for passive routing of messages generated by JMS client applications.

6. A system as in claim 3 wherein said Provider infrastructure further includes a mechanism for publish/subscribe access to streaming content by means of an optimized wire transfer protocol wherein said mechanism is a plug-in and wherein said plug-in actively generates messages providing said content.

7. A system as in claim 3 wherein said Provider infrastructure further includes a mechanism for FAST protocol implementation carried in a JMS StreamMessage payload wherein said mechanism is a plug-in and wherein said a plug-in operably communicates with managed content.

8. A system as in claim 3 wherein said Provider infrastructure further includes a mechanism for publish/subscriber access to multiple streams of streaming content over a single JMS destination and wherein said mechanism is a plug-in.

9. A system as in claim 3 wherein said Provider infrastructure further includes mechanisms for transformation of any of RMDS, Wombat, and IBM WebSphere Front Office message protocols and formats into a JMS MapMessage protocol.

10. A system as in claim 3 wherein said Provider infrastructure further includes a mechanism for redirecting publish/subscribe requests for the purpose of load-balancing across multiple servers and where said mechanism is a plug-in.

11. A system as in claim 3 wherein said Provider infrastructure further includes a mechanism for transformation of JMS MapMessage protocol messages to and from TIBCO Rendezvous and where said mechanism is a plug-in.

12. The system as in claim 1 wherein said Provider infrastructure further includes a mechanism for transformation of IBM MQSeries messages to and from JMS MapMessage protocol over JMS queues.

13. A system as in claim 1 wherein said Provider infrastructure further includes a mechanism for transformation of messages to and from other JMS Providers and where said mechanism is a plug-in.

14. A system as in claim 1 further including computer memory storing instructions to cause a computer to perform a method, said method comprising the steps of:

a) optimizing JMS MapMessage protocol;

b) optimizing client-side JMS Provider mechanisms for;

i) decoding JMS MapMessage protocol; and

ii) making client- side use transparent to JMS Client Applications where said client-side JMS Provider relies on dynamically provisioned data dictionaries supplied by server-side plug-ins for the compression/decompression of an efficient wire protocol from and to the standard JMS MapMessage.

15. A system as in claim 1, wherein in said client-server system the Provider is a JMS Provider, and where a JMS Client Application initiates a session and wherein the session initialization is accomplished by performance of the steps of:

1. creating connection, where said connection creation step is performed by a JMS Client Application;

2. establishing connection with server, where said server connection step is performed by Client Network Connection;

3. authenticating client, where said client authentication step is performed by a JMS Server;

4. creating session, where said session creation step is performed by said JMS Client Application;

5. establishing session with server, where said establishing session with server step is performed by Client Network Session;

6. locating requested application context, where said locating requested application context step is performed by Server Network Connection;

7. obtaining plug-in associated with requested context where obtaining plug-in step is performed by Server Network Connection; and

8. allocating session and initialize session resources, where said allocation is arbitrary and extensible and is performed by one or more plug-ins.

16. A system as in claim 1, wherein in said client-server system, the Provider is a JMS Provider, and where at least one subscription is initialized and wherein subscription initialization comprises the steps of:

1. requesting topic, said step of requesting topic performed by JMS Client Application;

2. allocating topic, said step of allocating topic performed by Client Network Session;

3. registering topic subscriber, said step of registering topic subscriber performed by JMS Client Application;

4. authorizing subscription, said step of authorizing subscription performed by Client Network Session;

if subscription is authorized, go to step 6;

5. if step 4 fails;

processing authorization failure and then end, said step of processing authorization failure performed by JMS Client Application;

6. registering listener, said step of registering listener performed by JMS Client Application;

7. sending subscription request to server, said step of sending subscription request to server performed by Client Network Session;

8. getting destination from factory, said step of getting destination from factory performed by Server Network Session;

9. checking cache, said step of checking cache performed by Destination Factory;

9a if not cached, allocating topic, (said step of allocating topic performed by DestinationFactory) and go to step 10;

9b if cached, obtaining subscriber reference, said step of obtaining subscriber reference performed by Server NetworkSession;

10. allocating topic subscriber, said step of allocating topic subscriber performed by server side representation of topic that client application sees; and

11. registering session subscriber, where said step of registering session subscriber is performed by Server Network Session.

17. The system as in claim 16 wherein step 8 is performed by Mapping Plug-in, where said Mapping plug-in performs searching of other plug-ins for a first match that can provide a topic with the requested name.

18. The system according to claim 1 further including a Managed Content Plug-in, said Managed Content Plug-in causing performance of the steps of:

1. getting destination from factory (said step of getting destination from factory performed by Server Network Session);

2. checking cache (said step of checking cache performed by Content Topic Factory) and if not cached;

2a. getting Template parameters from Topic name (said step of getting Template parameters from Topic name performed by Content Topic Factory);

2b. obtaining Content Instance from Template (said step of obtaining Content Instance from Template performed by Content Topic Factory);

2c. allocating Distribution Adapter for Topic (said step of allocating Distribution Adapter for Topic performed by MapMessage Adapter Factory);

2d. initialing Adapter with content (said step of initializing Adapter with content performed by Content topic factory);

2e. initializing field adapters (said step of initializing field adapters performed by Map Message adapter);

2f. allocating Content topic (said step of allocating Content topic performed by Content Topic Factory);

2g. starting Adapter (said step of starting Adapter performed by Content Topic Factory);

2h. registering for Content Events (said step of registering for Content Events performed by Map Message Adapter);

3. obtaining subscriber reference (said step of obtaining subscriber reference performed by Server Network Session);

4. allocating Topic subscriber (said step of allocating Topic subscriber performed by Content Topic);

5. determining if session initialized (said step of determining if session initialized performed by Map Message Adapter);

6. initializing Session (said step of initializing Session performed by Map Message Adapter); and

7. registering Session Subscriber (said step of registering Session Subscriber performed by-Server Network Session).

19. A system as in claim 1, wherein the Provider supports market data semantics such as image/update datastreams and data condition advisories using JMS Message properties such that said infrastructure can determine when a new subscriber attaches to said infrastructure and said infrastructure automatically send images/update datastreams and data condition advisories without a specific request from subscriber and further automatically generates status messages as necessary to correctly inform the subscribing application of changes in data state.

20. A system, as in claim 19, wherein the JMS Messaging properties include a Message Type property, a State property )which includes status and data condition in a single property), a Text property, a Data Stream Identifier property, and a Next and Previous Stream Identifier properties.

21. A system as in claim 1 wherein the Provider is a JMS Provider and where the JMS Provider can, through a single API and by means of one or more plug-ins having various implementations, provide consolidated business functionalities, said functionalities including inter-application messaging, market data submission/publication and transactional messaging.

22. A system as in claim 1 wherein the Provider is a JMS Provider and where the JMS Provider includes plug-ins, where each plug-in interfaces directly with at least one transactional system, so that a JMS client application can engage in transactions with multiple underlying transactional systems through a single API such that latency is minimized.

23. A system as in claim 1 wherein the Provider is a JMS Provider and where the JMS Provider includes a content plug-in that engages in transactions for publish operations, such that transactional integrity is preserved across one or more publish operations.