IP Library Granted Patent US 7,152,094
Granted Patent B1
US 7,152,094 · App. 09/919,425 · Granted Dec 19, 2006

Middleware brokering system adapter

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,152,094
App. No.
09/919,425
Granted
Dec 19, 2006
Kind
B1
Abstract

The present invention, known as the Middleware Brokering System Adapter, is a component useful with a Middleware Brokering System, which brokers messages between middleware computing products. Each middleware service can send data to and receive data from the Middleware Brokering System in its native data format and programming syntax. The Middleware Brokering System Adapter is a component of the Middleware Brokering System that transforms data messages from the native format of a middleware computing product or a mainframe computing system into a format known as a structured event and from a structured event into the native format of the middleware product or the mainframe system. In an embodiment of the invention, the Middleware Brokering System Adapter maps the fields of a Cobol copybook onto the fields of a structured event and the fields of a structured event onto the fields of a copybook. In an alternative embodiment, the Middleware Brokering System Adapter maps the fields of a Java Messaging Service MapMessage onto the fields of a structured event and the fields of a structured event onto the fields of a MapMessage.

Claims (29)

1. A method for brokering messages between middleware systems comprising:

communicating a message from a mainframe system in a Cobol copybook format;

mapping the message in Cobol copybook format onto the fields in a structured event format;

communicating the message converted from Cobol copybook format to structured event format to a middleware brokering system;

communicating a message from a JMS system in a JMS message format;

mapping the message in the JMS message format onto the fields in a structured event format;

communicating the message converted from the JMS message format to the structured event format to the middleware brokering system;

communicating a message from a CORBA system in the structured event format to the middleware brokering system;

using the middleware broker to determine the destination for each of the messages from the JMS, CORBA, and mainframe systems; and

directing each of the messages to the appropriate one of the JMS, CORBA, and mainframe systems.

2. The method of claim 1 further comprising:

converting the messages destined for the mainframe system from the structured event format to Cobol copybook format; and

converting the messages destined for the JMS system from structured event format to the JMS system.

3. The method of claim 1 further comprising:

registering each of the messages with a publish/subscribe engine; and

brokering the messages between the JMS, CORBA, and mainframe systems based on the messages that the JMS, CORBA, and mainframe systems have registered to receive.

4. The method of claim 1 wherein the JMS message format is selected from the group consisting of TextMessage, BytesMessage; MapMessage; ObjectMessage; and StreamMessage.

5. The method claim 1 wherein the domain name and type name portions of the message in the JMS message format are concatenated and placed in the JMSType field of a JMS MapMessage.

6. The method of claim 5 wherein the domain name portion of the concatenated JMSType field of the JMS MapMessage is mapped onto the domain name field of the structured event format.

7. The method of claim 6 further comprising the mapping of the type name portion of the concatenated JMSType field onto the type_name field of the structured event format.

8. The method of claim 7 further comprising the mapping of the JMSMessageID field of the JMS MapMessage onto a corresponding field in the variable header section of the structured event format.

9. The method of claim 8 further comprising the mapping of the JMSTimestamp field of the JMS MapMessage onto a corresponding field in the variable header section of the structured event format.

10. The method of claim 9 further comprising the mapping of the JMSDeliveryMode field of the JMS MapMessage onto a corresponding field in the variable header section of the structured event format.

11. The method of claim 10 further comprising the mapping of the properties section of the JMS MapMessage onto the filterable body section of the structured event format.

12. The method of claim 11 further comprising the mapping of the body section of the JMS MapMessage onto the remaining body section of the structured event format.

13. The method of claim 1 wherein a field of the Cobol copybook format containing the domain name is mapped onto the domain_name field of die structured event format.

14. The method of claim 13 further comprising the mapping of a field of the Cobol copybook format containing the type name onto the type-name field of the structured event format.

15. The method of claim 14 further comprising the mapping of a field of the Cobol copybook format containing the event name onto the event_name field of the structured event format.

16. The method of claim 15 further comprising the mapping of a freeform data field of the Cobol copybook format onto the remaining body section of the structured event format.

Assignments (4)
RELEASE OF SECURITY INTEREST Recorded Aug 23, 2022
From: DEUTSCHE BANK TRUST COMPANY AMERICAS
To: IBSV LLC; LAYER3 TV, LLC; PUSHSPRING, LLC; T-MOBILE CENTRAL LLC; T-MOBILE USA, INC.; ASSURANCE WIRELESS USA, L.P.; BOOST WORLDWIDE, LLC; CLEARWIRE COMMUNICATIONS LLC; CLEARWIRE IP HOLDINGS LLC; SPRINTCOM LLC; SPRINT COMMUNICATIONS COMPANY L.P.; SPRINT INTERNATIONAL INCORPORATED; SPRINT SPECTRUM LLC
Reel/Frame 062595/0001 →
TERMINATION AND RELEASE OF FIRST PRIORITY AND JUNIOR PRIORITY SECURITY INTEREST IN PATENT RIGHTS Recorded Apr 2, 2020
From: DEUTSCHE BANK TRUST COMPANY AMERICAS
To: SPRINT COMMUNICATIONS COMPANY L.P.
Reel/Frame 052969/0475 →
SECURITY AGREEMENT Recorded Apr 2, 2020
From: T-MOBILE USA, INC.; ISBV LLC; T-MOBILE CENTRAL LLC; LAYER3 TV, INC.; PUSHSPRING, INC.; BOOST WORLDWIDE, LLC; CLEARWIRE COMMUNICATIONS LLC; CLEARWIRE IP HOLDINGS LLC; CLEARWIRE LEGACY LLC; SPRINT COMMUNICATIONS COMPANY L.P.; SPRINT INTERNATIONAL INCORPORATED; SPRINT SPECTRUM L.P.; ASSURANCE WIRELESS USA, L.P.
To: DEUTSCHE BANK TRUST COMPANY AMERICAS
Reel/Frame 053182/0001 →
GRANT OF FIRST PRIORITY AND JUNIOR PRIORITY SECURITY INTEREST IN PATENT RIGHTS Recorded Mar 6, 2017
From: SPRINT COMMUNICATIONS COMPANY L.P.
To: DEUTSCHE BANK TRUST COMPANY AMERICAS
Reel/Frame 041895/0210 →