Systems and/or methods for standards-based messaging

• US 20100251262A1
• Filed: 03/31/2009
• Published: 09/30/2010
• Est. Priority Date: 03/31/2009
• Status: Active Grant

• Current Assignee: Software AG
• Original Assignee: Software AG
• Inventors: Holar, Elliot, Rokicki, Derek
• Granted Patent: US 8,301,687 B2
• Time in Patent Office: Days
• US Class Current: 719/314
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion

Abstract

The example embodiments disclosed herein relate to application integration techniques built around the publish-and-subscribe model (or one of its variants). In certain example embodiments, a first standards-based messaging protocol (e.g., the JMS messaging protocol) may be used to create a trigger so that a message envelope according to a second standards-based messaging protocol (e.g., SOAP) may be communicated over the first standards-based messaging transport layer. In other words, in certain example embodiments, a trigger according to a first protocol (e.g., JMS) may have a message according to a second protocol (e.g., SOAP) associated therewith so as to enable the message to be communicated over the first protocol'"'"'s transport layer. The trigger may be configured to receive a message from a web service consumer via the JMS messaging protocol and pass it to the web service stack for dispatch to the web service provider. Similarly, for a request-reply web service exchange pattern, the trigger may be configured to send the reply message from the web service provider, as returned by the web service layer, to the web service consumer via the JMS messaging protocol.

Claims

1. An application integration system configured to exchange messages via a message broker, comprising:

a message consumer configured to receive a runtime message from a message producer via a client queue of the message broker in accordance with a context retrieved from a context pool, the message consumer being configured to use a transport protocol and having a message envelope associated therewith, the message envelope being formatted in accordance with a second messaging protocol, a runtime trigger being further configured to extract the message envelope from the runtime message; and

a web service stack configured to receive the message envelope extracted by the runtime trigger by the message consumer and further configured to invoke an appropriate service from a plurality of possible services in accordance with instructions included with the message envelope.

2. The system of claim 1, wherein the runtime trigger is further configured to acknowledge receipt of the runtime message after the at least one appropriate service is invoked by sending an acknowledgement message to the message producer via the message broker.

3. The system of claim 2, wherein a plurality of acknowledgement messages are sent to the message producer in batch.

4. The system of claim 1, wherein the runtime trigger is a JMS trigger.

5. The system of claim 1, wherein the second messaging protocol is SOAP.

6. The system of claim 1, wherein the runtime trigger is configured to receive a SOAP message envelope over a JMS transport protocol.

7. The system of claim 1, wherein the runtime trigger further comprises header information comprising a name of a destination to which a response message should be sent, a priority associated with the runtime trigger, an indication as to whether the runtime trigger is persistent, and/or a lifetime of the runtime trigger.

8. The system of claim 1, wherein the runtime trigger is associated with a web service descriptor (WSD) at design time.

9. The system of claim 8, wherein the WSD is created from a web service definition language (WSDL) document.

10. The system of claim 9, wherein the runtime trigger includes header information regarding how the WSDL document is to be interpreted.

11. An application integration system configured to exchange messages via a message broker, comprising:

a web service connector configured to invoke a remote web service using a runtime trigger by generating a runtime message to be delivered to a message consumer through a client queue of the message broker, the runtime message being sent over a transport protocol and having a message envelope associated therewith, the message envelope being formatted in accordance with a second messaging protocol; and

a dispatcher configured to receive the runtime message from the web service connector and send the runtime message to the broker via a connection retrieved from a connection pool, wherein;

the web service connector is generated from a web service descriptor (WSD),

the WSD specifies at least a format of the runtime message envelope, as well as a destination, and

the message broker is configured to place any received runtime messages into the client queue for the message consumer.

12. The system of claim 11, wherein the message broker is further configured to return acknowledgement messages received from the message consumer to the web service connector via one of the connections in the connection pool.

13. The system of claim 11, wherein the runtime trigger is a JMS trigger.

14. The system of claim 11, wherein the second messaging protocol is SOAP.

15. The system of claim 11, wherein the web service connector is configured to transport a SOAP message envelope over a JMS transport protocol.

16. The system of claim 11, wherein the WSD is generated from a predefined Web Service Definition Language (WSDL) document.

17. The system of claim 16, wherein the WSDL document describes web services that are accessible over a network, including information the web service connector needs to send data to, invoke, and receive data from, the web service.

18. The system of claim 11, wherein the web service connector is generated based at least in part on one or more web service endpoints.

19. An application integration system configured to exchange messages via a message broker, comprising:

a web service connector configured to invoke a remote web service using a runtime trigger by generating a runtime message to be delivered to a message consumer through a client queue of the message broker, the runtime message being sent over a transport protocol and having a message envelope associated therewith, the message envelope being formatted in accordance with a second messaging protocol; and

a dispatcher configured to receive the runtime message from the web service connector and send the runtime message to the broker via a connection retrieved from a connection pool, wherein;

the message consumer is configured to receive the runtime message from the producer in accordance with a context retrieved from a context pool,

a runtime trigger is configured to extract the message envelope from the runtime message; and

a web service stack is configured to receive the message envelope extracted by the runtime trigger and further configured to invoke an appropriate service from a plurality of possible services in accordance with instructions included with the message envelope,

the web service connector is generated from a web service descriptor (WSD) at design time, the WSD specifying at least a format of the runtime message envelope, as well as a destination, and

the message broker is configured to place any received runtime messages into the client queue for the message consumer.

20. The system of claim 19, wherein the message envelope is a SOAP message envelope, the runtime trigger is a JMS trigger, and the SOAP message envelope is sent over a JMS transport to or from the JMS trigger.

21. In an application integration system, a messaging method comprising:

providing a message broker configured to deliver messages from a message producer to a message consumer;

enabling a web service connector, the web service connector being configured to invoke a remote web service in communication with the message consumer using a runtime trigger by generating a runtime message to be delivered to the message consumer through a client queue of the message broker;

sending, via a dispatcher connected to the web service connector, the runtime message to the message broker using a connection retrieved from a connection pool, the runtime message being sent over a transport protocol and having a message envelope associated therewith, the message envelope being formatted in accordance with a second messaging protocol;

receiving, at the message consumer, the runtime message from the producer via the broker in accordance with a context retrieved from a context pool;

extracting the message envelope from the runtime message;

passing the message envelope from the message consumer to a web service stack; and

invoking, via the web service stack, an appropriate service from a plurality of possible services operably connected to the web service stack in accordance with instructions included with the message envelope,

wherein the message broker is configured to place any received runtime messages into the client queue for the message consumer.

22. The method of claim 21, wherein the message envelope is a SOAP message envelope, the runtime trigger is a JMS trigger, and the SOAP message envelope is sent over a JMS transport to or from the JMS trigger.

23. The method of claim 21, further comprising generating the web service connector from a web service descriptor (WSD) at design time, the WSD specifying at least a format of the runtime message envelope, as well as a destination.

24. The method of claim 23, further comprising generating the WSD at design time from a predefined Web Service Definition Language (WSDL) document and/or one or more web service endpoints,

wherein the WSDL document describes web services that are accessible over a network, including information the web service connector needs to send data to, invoke, and receive data from, the web service.

25. The method of claim 21, further comprising acknowledging receipt of the transported message through the message broker following the invoking of and/or processing by the at least one appropriate service.