Server for communicating with multi-mode devices using multi-mode applications
US-9277033-B2 · Mar 1, 2016 · US
US9614803B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9614803-B2 |
| Application number | US-201414197429-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 5, 2014 |
| Priority date | Jun 28, 2013 |
| Publication date | Apr 4, 2017 |
| Grant date | Apr 4, 2017 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A method, system, and/or computer program product manages message connections in a computer infrastructure. A processor connects a client to a messaging component over a connection. Identification information of a destination message queue that the client intends to communicate to the messaging component is provided, and a reference of the destination message queue is received. Based on the received reference, a respective messaging component that has the destination message queue localized is identified.
Opening claim text (preview).
What is claimed is: 1. A method implemented in a computer infrastructure for management of message connections, the method comprising: connecting, by one or more processors, a client to a first messaging component over a connection, wherein the first messaging component is implemented on a first computer; providing identification information of a destination message queue that the client intends to communicate to, wherein the destination message queue is used in a point to point messaging system, wherein the destination message queue is located on a second messaging component on a second computer, and wherein the second messaging component has been selected by a workload management component in the first messaging component in the first computer to store the destination message queue; receiving a reference of the destination message queue, wherein the reference identifies the second messaging component upon which the destination message queue is located; identifying, based on the reference, the second messaging component that has the destination message queue localized thereon; in response to determining that the destination message queue is not located in the first messaging component, using the reference to route the connection from the client to the second messaging component that has the destination message queue localized thereon, wherein a session connection between the client and the second messaging component that has the destination message queue localized thereon is transparently routed to the second messaging component by using the connection from the client to the first computer as a proxy connection to the second computer and the second messaging component. 2. The method of claim 1 , further comprising: comparing the reference of the destination message queue and a connection reference of the connection to determine if the destination message queue is localized at a messaging component to which the client is connected. 3. The method of claim 1 , further comprising: distributing, by workload management components on the first computer and the second computer, a communication session workload between the first messaging component and the second messaging component. 4. The method of claim 1 , wherein the connection between the client and the first messaging component is via a Java Message Service Application Program Interface (JMS API), wherein the connection represents an open TCP/IP socket between the client and the first messaging component. 5. The method of claim 1 , further comprising: creating at least one session using the connection; creating a message producer and a message consumer for a communication session; specifying the destination message queue for the communication session; and providing the identification information of the destination message queue for the communication session to a messaging component to which the client is connected. 6. The method of claim 1 , wherein the reference is determined from a routing table comprising information about the first and second messaging components. 7. The method of claim 5 , wherein a plurality of messaging components of the communication session are interconnected via a bus.
Related publications grouped by family.
Answers are generated from the same data shown on this page.