Middleware brokering system

• US 7,216,181 B1
• Filed: 07/31/2001
• Issued: 05/08/2007
• Est. Priority Date: 07/31/2001
• Status: Expired due to Term

• Current Assignee: T-Mobile Innovations LLC (Deutsche Telekom AG)
• Original Assignee: Sprint Communications Company LP (Deutsche Telekom AG)
• Inventors: Lee, Wing, Potluri, Dora, Jannu, Shrikant, Tsai, Denis
• Primary Examiner(s): Caldwell; Andrew
• Assistant Examiner(s): BLAIR, DOUGLAS B
• Application Number:
  US09/919,436
• Time in Patent Office: 2,107 Days
• Field of Search: 709/206, 709/207, 709/218, 709/246, 709/217, 709/201, 709/204, 719/313, 719/315, 719/330
• US Class Current: 709/246
• CPC Class Codes: H04L 12/1859 adapted to provide push services, e.g. data channels
• CPC Class Codes: H04L 51/066 Format adaptation, e.g. format conversion or compression
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561

Abstract

The present invention, known as the Middleware Brokering System, brokers messages between middleware computing products. Each middleware service can send data to the Middleware Brokering System in its native data format and programming syntax. The Middleware Brokering System converts the data transmitted from the different platforms into a standard format known as a structured event. Messages are then transmitted to and stored in an underlying, commercially available publish/subscribe engine. The Middleware Brokering System contains internal logic that determines whether any subscribers are interested in the messages. If an interested subscriber is found, the Middleware Brokering System retrieves the message from the publish/subscribe engine, converts the data from the structured event into the native format of the receiving application, and sends the message to the appropriate application.

Claims

1. A method for asynchronous brokering of messages between middleware computing systems, comprising:

a) receiving a message sent from a first application into a first middleware computing system, the first middleware computing system facilitating data exchange among a first group of disparate applications comprising the first application and one or more applications;

b) converting the message from a native language format of the first application to a native language format of the first middleware computing system;

c) receiving the message sent from the first middleware computing system into a middleware brokering server;

d) converting the message from the native language format of the first middleware computing system to a standard format of the middleware brokering server;

e) converting the message from the standard format of the middleware brokering server to a native language format of a second middleware computing system, the second middleware computing system facilitating data exchange among a second group of disparate applications comprising a second application and one or more applications;

f) sending the message from the middleware brokering server to the second middleware computing system that receives the message;

g) converting the message from the native language format of the second middleware computing system to a native language format of the second application; and

h) sending the message from the second middleware computing system to the second application that receives the message.

2. The method of claim 1 wherein the sending first middleware computing system and the receiving second middleware computing system are selected from the group consisting of a mainframe system, a CORBA compliant system, and a JMS system.

3. The method of claim 2 wherein the sending first middleware computing system communicates with the middleware brokering server via point to point messaging and wherein the middleware brokering server communicates with the receiving second middleware computing system via publish and subscribe messaging.

4. The method of claim 3 wherein the sending first middleware computing system of a first message is the receiving second middleware computing system of a second message.

5. The method of claim 3 wherein the receiving second middleware computing system of a first message is the sending first middleware computing system of a second message.

6. The method of claim 3 wherein the publish and subscribe messaging further comprises a push-pull paradigm across at least one messaging channel.

7. The method of claim 6 further comprising designating quality of service attributes when configuring the channel.

8. The method of claim 1 wherein the message is converted from the native language format of the sending first middleware computing system by mapping a plurality of fields in the native format into corresponding fields in the standard format of the middleware brokering server.

9. The method of claim 8 wherein the native language format of the sending first middleware computing system is selected from the group consisting of a Cobol copybook, JMS TextMessage, JMS BytesMessage;

JMS MapMessage;

JMS ObjectMessage; and

JMS StreamMessage.

10. The method of claim 8 wherein the sending first middleware computing system is a mainframe system and the native language format is a COBOL copybook.

11. The method of claim 8 wherein the sending first middleware computing system is a JMS system and the native language format is a JMS MapMessage.

12. The method of claim 1 wherein the message is converted from the standard format of the middleware brokering server by mapping a plurality of fields in the standard format into corresponding fields in the native language format of the receiving second middleware computing system.

13. The method of claim 12 wherein the native language format of the receiving second middleware computing system is selected from the group consisting of a Cobol copybook, JMS TextMessage, JMS BytesMessage;

JMS MapMessage;

JMS ObjectMessage; and

JMS StreamMessage.

14. The method of claim 12 wherein the receiving second middleware computing system is a mainframe system and the native language format is a COBOL copybook.

15. The method of claim 12 wherein the receiving second middleware computing system is a JMS system and the native language format is a JMS MapMessage.

16. The method of claim 1 wherein the standard format of the middleware brokering server is a structured event message format.