IP Library Patent Application 12179730
Patent Application
App. No. 12/179,730

BUSINESS EVENT AGENTS

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 None
App. No.
12/179,730
Abstract

A system may include reception of a core event associated with a business object, evaluation of one or more rules based on the core event to identify a business event, construction of a message based on a mapping between the business object and an event interface, the mapping and the event interface associated with the business event and the business object; and publication of the message.

Claims (79)

1 . A method comprising:

receiving a core event associated with a business object;

evaluating one or more rules based on the core event to identify a business event;

constructing a message based on a mapping between the business object and an event interface, the mapping and the event interface associated with the business event and the business object; and

publishing the message.

2 . A method according to claim 1 , wherein the core event comprises a change condition.

3 . A method according to claim 1 , further comprising:

receiving a second core event associated with a second business object;

evaluating one or more rules based on the second core event to identify a second business event;

constructing a second message based on a second mapping between the second business object and the event interface, the second mapping and the event interface associated with the second business event and the second business object; and

publishing the second message.

4 . A method according to claim 1 , further comprising:

receiving a second core event associated with the business object;

evaluating the one or more rules based on the second core event to identify a second business event;

constructing a second message based on a second mapping between the business object and the event interface, the second mapping and the event interface associated with the business object and the second business event; and

publishing the second message.

5 . A method according to claim 1 , further comprising:

receiving a second core event associated with a second business object;

evaluating one or more rules based on the second core event to identify a second business event;

constructing a second message based on a second mapping between the second business object and a second event interface, the second mapping and the second event interface associated with the second business event and the second business object; and

publishing the second message.

6 . A method according to claim 5 , further comprising:

receiving a third core event associated with the business object;

evaluating the one or more rules based on the third core event to identify a third business event;

constructing a third message based on a third mapping between the business object and the event interface, the third mapping and the event interface associated with the business object and the third business event; and

publishing the third message.

7 . A method according to claim 5 , further comprising:

receiving a third core event associated with the business object;

evaluating the one or more rules based on the third core event to identify a third business event;

constructing a third message based on a third mapping between the business object and a third event interface, the third mapping and the third event interface associated with the business object and the third business event; and

publishing the third message.

8 . A method according to claim 1 , further comprising:

receiving a second core event associated with the business object;

evaluating one or more rules based on the second core event to identify a second business event;

constructing a second message based on a second mapping between the business object and a second event interface, the second mapping and the second event interface associated with the second business event and the business object; and

publishing the second message.

9 . A method according to claim 1 , wherein publishing the message comprises:

forwarding the message to a publish/subscribe infrastructure.

10 . A medium storing processor-executable program code, the program code to provide:

an event agent to:

receive a core event associated with a business object;

evaluate one or more rules based on the core event to identify a business event;

construct a message based on a mapping between the business object and an event interface, the mapping and the event interface associated with the business event and the business object; and

publish the message.

11 . A medium according to claim 10 , wherein the core event comprises a change condition.

12 . A medium according to claim 10 , the program code to provide:

a second event agent to:

receive a second core event associated with a second business object;

evaluate one or more rules based on the second core event to identify a second business event;

construct a second message based on a second mapping between the second business object and the event interface, the second mapping and the event interface associated with the second business event and the second business object; and

publish the second message.

13 . A medium according to claim 10 , the event agent further to:

receive a second core event associated with the business object;

evaluate the one or more rules based on the second core event to identify a second business event;

construct a second message based on a second mapping between the business object and the event interface, the second mapping and the event interface associated with the business object and the second business event; and

publish the second message.

14 . A medium according to claim 10 , the program code to provide:

a second event agent to:

receive a second core event associated with a second business object;

evaluate one or more rules based on the second core event to identify a second business event;

construct a second message based on a second mapping between the second business object and a second event interface, the second mapping and the second event interface associated with the second business event and the second business object; and

publish the second message.

15 . A medium according to claim 14 , the event agent further to:

receive a third core event associated with the business object;

evaluate the one or more rules based on the third core event to identify a third business event;

construct a third message based on a third mapping between the business object and the event interface, the third mapping and the event interface associated with the business object and the third business event; and

publish the third message.

16 . A medium according to claim 14 , the event agent further to:

receive a third core event associated with the business object;

evaluate the one or more rules based on the third core event to identify a third business event;

construct a third message based on a third mapping between the business object and a third event interface, the third mapping and the third event interface associated with the business object and the third business event; and

publish the third message.

17 . A medium according to claim 10 , the event agent further to:

receive a second core event associated with the business object;

evaluate one or more rules based on the second core event to identify a second business event;

construct a second message based on a second mapping between the business object and a second event interface, the second mapping and the second event interface associated with the second business event and the business object; and

publish the second message.

18 . A medium according to claim 10 , wherein publication of the message comprises:

forwarding of the message to a publish/subscribe infrastructure.

Assignments (2)
CHANGE OF NAME Recorded Aug 26, 2014
From: SAP AG
To: SAP SE
Reel/Frame 033625/0223 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 25, 2008
From: BAEUERLE, STEFAN A.; GETZNER, ROBERT; MEINERT, HOLGER; WEBER, FRANZ
To: SAP AG
Reel/Frame 021292/0836 →