Systems and/or methods for standards-based messaging
First Claim
1. An application integration system having one or more processors and 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 configured to use the transport protocol to receive the message envelope, extract the message envelope from the runtime message, and transmit the message envelope that is formatted according to the second messaging protocol; and
a web service stack configured to receive, via the one or more processors, the transmitted 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.
1 Assignment
0 Petitions
Accused Products
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.
-
Citations
25 Claims
-
1. An application integration system having one or more processors and 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 configured to use the transport protocol to receive the message envelope, extract the message envelope from the runtime message, and transmit the message envelope that is formatted according to the second messaging protocol; and a web service stack configured to receive, via the one or more processors, the transmitted 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. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10)
-
-
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 the runtime trigger configured to use the transport protocol to receive the message envelope, extract the message envelope from the runtime message, and transmit the message envelope that is formatted according to the 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. - View Dependent Claims (12, 13, 14, 15, 16, 17, 18)
-
-
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 the runtime trigger configured to use the transport protocol to receive the message envelope, extract the message envelope from the runtime message, and transmit the message envelope that is formatted according to the 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. - View Dependent Claims (20)
-
-
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 and the runtime trigger configured to use the transport protocol to receive the message envelope; 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, formatted according to the second messaging protocol, 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. - View Dependent Claims (22, 23, 24, 25)
-
Specification