Enterprise computer system

• US 7,143,093 B1
• Filed: 12/15/1999
• Issued: 11/28/2006
• Est. Priority Date: 12/17/1998
• Status: Expired due to Term

• Current Assignee: Software AG USA Incorporated (Software AG)
• Original Assignee: WebMethods Incorporated (Software AG)
• Inventors: Jankowski, Steven M., Bracho, Rafael
• Primary Examiner(s): JUNG, DAVID YIUK
• Application Number:
  US09/464,378
• Time in Patent Office: 2,540 Days
• Field of Search: 707 1-206, 709100-332
• US Class Current: 1/1
• CPC Class Codes: G06F 2209/544 Remote
• CPC Class Codes: G06F 2209/547 Messaging middleware
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: H04L 63/105 Multiple levels of security
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

A scalable enterprise computer system having the capability to provide transaction security as well as providing subscription filtering is described. As a method of transacting an event in the enterprise computer system a connection with an information broker by the publishe established after which it is determined if the event registered with the information broker. Next, a subscription corresponding to the registered event by a subscriber is accepted by the information broker, after which a platform neutral event is created that is then populated with event content which is then published to and received by the information broker.

Claims

1. A method of transacting an event in an enterprise computer system, comprising:

(a) establishing a connection with an information broker by a publisher;

(b) determining if the event is registered with the information broker;

(c) accepting a subscription corresponding to a registered event by a subscriber

(d) creating a platform neutral event;

(e) populating the platform neutral event based upon the registered event;

(f) publishing the populated event to the information broker by the publisher; and

(g) receiving the published event by the information broker

wherein an event is a business event created by one resource and is of interest to another.

2. A method as recited in claim 1, further comprising:

(h) determining an event type that corresponds to the received event by the information broker;

(i) determing whether or not the event is a valid event based in part upon the event type;

(j) determining whether or not the connection is valid; and

(k) queueing the valid event to the subscriber when the connection is valid.

3. A method as recited in claim 2, wherein the determining (i) further comprises:

(l) determining whether or not the event type matches the subscription;

(m) determining whether or not an event security level is verified when the event type matches the subscription;

(n) determining whether or not an event content matches a content filter when the event security level is verified and when the event type matches the subscription; and

(o) determining whether or not an event authorization is valid when the event security level is verified and when the event type matches the subscription such that when the event authorization is valid, the event is the valid event.

4. A method as recited in claim 1, wherein the enterprise computer system includes a plurality of interconnected information brokers.

5. A method as recited in claim 4, wherein the content filter is an updateable content filter.

6. A method as recited in claim 5, wherein the content filter is updated by a user as needed.

7. A method as recited in claim 1, wherein the information broker includes a preprocessor suitably arranged to perform (h)–

(k).

8. A method as recited in claim 7, wherein the information broker further includes a preprocessor queue that couples the preprocessor to the content filter.

9. A method as recited in claim 8, wherein the enterprise computer system includes a plurality of subscribers.

10. A method as recited in claim 9 wherein each of the subscribers has an associated subscriber queue coupled thereto.