Enhanced call-back service using rule engine

• US 7,962,436 B2
• Filed: 02/28/2008
• Issued: 06/14/2011
• Est. Priority Date: 02/28/2008
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Sandfuchs, Thorsten, Ziegler, Carsten, Brelage, Christian
• Primary Examiner(s): Holmes; Michael B
• Assistant Examiner(s): Hill; Stanley K
• Application Number:
  US12/039,187
• Publication Number:
  US 20090222394A1
• Time in Patent Office: 1,202 Days
• Field of Search: None
• US Class Current: 706/47
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

An enhanced call-back service, in which a local rule engine is caused to be capable of invoking a rule defined at an external rule engine, and a function provided by the local rule engine is exposed as a call-back service. At the call-back service and from the external rule engine, a request to interact with the function is received, and, using the call-back service, an interaction is provided between the external rule engine and the function.

Claims

1. A computer-implemented method comprising:

transmitting, from a local rule engine to an external rule engine, a schema document that defines an input to and an output of the external rule engine, the schema document being used by the external rule engine to define a rule;

exposing, as a call-back service, a function provided by the local rule engine, wherein the function is capable of invoking the rule defined at the external rule engine;

receiving, at the call-back service and from the external rule engine, a request to interact with the function; and

providing, using the call-back service, an interaction between the external rule engine and the function.

2. The method of claim 1, wherein the call-back service comprises a web service.

3. The method of claim 1, further comprising registering the schema document to bind the function with a data type,

wherein the function comprises a look-up function.

4. The method of claim 3, wherein, during a design time of the external rule engine:

receiving the request to interact with the function further comprises receiving a request for a list of look-up functions provided via the call-back service; and

providing the interaction further comprises transmitting, to the external rule engine, a response providing the list of look-up functions including the function.

5. The method of claim 4, wherein, during a run-time of the external rule engine:

receiving the request to interact with the function further comprises receiving, from the external rule engine, a request for instance data, the request identifying the schema document, the function, and a parameter; and

providing the interaction further comprises transmitting, to the external rule engine, the instance data resulting from processing the request using the function.

6. The method of claim 1, wherein, during a design time of the external rule engine:

receiving the request to interact with the function further comprises receiving a request for a list identifying pre-defined data types used by the function; and

providing the interaction further comprises transmitting, to the external rule engine, a response providing the list of pre-defined data types used by the function.

7. The method of claim 6, wherein, during a run-time of the external rule engine:

receiving the request to interact with the function further comprises receiving, from the external rule engine, a request for instance data associated with an identified data type on the list identifying pre-defined data types; and

providing the interaction further comprises transmitting, to the external rule engine, the instance data associated with the identified type.

8. The method of claim 1, wherein the function comprises a conversion function.

9. The method of claim 8, wherein, during a design time of the external rule engine:

receiving the request to interact with the function further comprises receiving a request for a list of conversion functions provided via the call-back service; and

providing the interaction further comprises transmitting, to the external rule engine, a response providing the list of conversion functions including the function.

10. The method of claim 9, wherein, during a run-time of the external rule engine:

receiving the request to interact with the function further comprises receiving, from the external rule engine, a request for instance data, the request identifying the function, a source unit identifier, and a data value; and

providing the interaction further comprises transmitting, to the external rule engine, the instance data resulting from processing the request using the function.

11. The method of claim 1,

wherein the function comprises a log execution trace function;

and

wherein, during a run-time of the external rule engine;

receiving the request to interact with the function further comprises receiving, from the external rule engine, a request identifying a previously received call from the local rule engine to the external rule engine, and an execution trace logging execution of the call, and

providing the interaction further comprises storing the received execution trace at the local rule engine.

12. The method of claim 1, further comprises registering the function with the call-back service,

wherein the function provided by the local rule engine comprises an internal local rule engine function or an external back-end function implemented by a back-end system.

13. The method of claim 12, wherein, during a design time of the external rule engine:

receiving the request to interact with the function further comprises receiving a list of functions registered with the call-back service; and

providing the interaction further comprises transmitting, to the external rule engine, a response providing the list of functions including the external back-end function.

14. The method of claim 13, wherein, during a run-time of the external rule engine:

receiving the request to interact with the function further comprises receiving, from the external rule engine, a back-end call; and

providing the interaction further comprises;

passing the back-end call to the back-end system, and

transmitting, to the external rule engine, a response resulting from processing the back-end call using the external back-end function.

15. The method of claim 12, wherein, during a design time of the external rule engine:

receiving the request to interact with the function further comprises receiving a list of functions registered with the call-back service; and

providing the interaction further comprise transmitting, to the external rule engine, a response providing the list of functions including the internal local rule engine function.

16. The method of claim 15, wherein, during a run-time of the external rule engine:

receiving the request to interact with the function further comprises receiving, from the external rule engine, a local rule engine call; and

providing the interaction further comprises;

passing the local rule engine call to the local rule engine, and

transmitting, to the external rule engine, a response resulting from processing the local rule engine call using the local rule engine function.

17. A device comprising a processor configured to:

transmit, from a local rule engine to an external rule engine, a schema document that defines an input to and an output of the external rule engine, the schema document being used by the external rule engine to define a rule;

expose, as a call-back service, a function provided by the local rule engine, wherein the function is capable of invoking the rule defined at the external rule engine;

receive, at the call-back service and from the external rule engine, a request to interact with the function; and

provide, using the call-back service, an interaction between the external rule engine and the function.

18. A computer program product, tangibly embodied in a machine-readable medium, the computer program product comprising instructions that, when read by a machine, operate to cause data processing apparatus to:

transmit, from a local rule engine to an external rule engine, a schema document that defines an input to and an output of the external rule engine, the schema document being used by the external rule engine to define a rule;

expose, as a call-back service, a function provided by the local rule engine, wherein the function is capable of invoking the rule defined at the external rule engine;

receive, at the call-back service and from the external rule engine, a request to interact with the function; and

provide, using the call-back service, an interaction between the external rule engine and the function.