Classification and modelling of exception types for integration middleware systems

• US 9,406,040 B2
• Filed: 08/13/2014
• Issued: 08/02/2016
• Est. Priority Date: 08/13/2014
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Ritter, Daniel, Sosulski, Jan
• Primary Examiner(s): Ho, Andy
• Assistant Examiner(s): SEYE, ABDOU K
• Application Number:
  US14/458,824
• Publication Number:
  US 20160048790A1
• Time in Patent Office: 720 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: G06Q 10/06316 Sequencing of tasks or work
• CPC Class Codes: G06Q 10/067 Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

The present disclosure describes methods, systems, and computer program products for modeling exception flows in an integration system. One computer-implemented method includes identifying, by operation of an application integration system, an exception corresponding to an integration operation of an integration process, determining, by operation of the application integration system, a type of the exception, determining, by operation of the application integration system, one or more exception handling patterns for the type of the exception, and configuring, by operation of the application integration system, an exception flow of the integration process based on the one or more exception handling patterns.

Claims

1. A computer-implemented method of an application integration system comprising:

identifying, by operation of an application integration system, an exception corresponding to an integration operation of an integration process;

determining, by operation of the application integration system, a type of the exception;

determining, by operation of the application integration system, one or more exception handling patterns for the type of the exception, wherein a failover router process is used to react on non-callable exception handling patterns within a sequence of integration patterns by calling alternative integration pattern channels without requiring external configuration messages, and wherein the alternative integration pattern channels are modeled explicitly; and

configuring, by operation of the application integration system, an exception flow of the integration process based on the one or more exception handling patterns.

2. The method of claim 1, comprising classifying exceptions into a plurality of types.

3. The method of claim 1, comprising providing a visualization of the exception flow.

4. The method of claim 1, wherein the exception handling patterns are syntactically mapped to Business Process Model and Notation (BPMN) and its execution semantics.

5. The method of claim 1, wherein the type of the exception comprises one or more of an activity failure, a message flow failure, a timeout, resource unavailability, an external event, or a constraint violation.

6. The method of claim 1, wherein the one or more exception handling patterns comprise one or more of a retry pattern, a failover router, a compensation sphere, an exception sphere, a dead letter channel, or an invalid message channel.

7. The method of claim 1, wherein the exception flow is configured to realize one or more of a quality of service (QoS), a message exchange pattern (MEP), or an enterprise integration pattern (EIP) integration logic.

8. A non-transitory, computer-readable medium storing computer-readable instructions executable by a computer and configured to:

identify an exception corresponding to an integration operation of an integration process;

determine a type of the exception;

determine one or more exception handling patterns for the type of the exception, wherein a failover router process is used to react on non-callable exception handling patterns within a sequence of integration patterns by calling alternative integration pattern channels without requiring external configuration messages, and wherein the alternative integration pattern channels are modeled explicitly; and

configure an exception flow of the integration process based on the one or more exception handling patterns.

9. The medium of claim 8, comprising instructions to classify exceptions into a plurality of types.

10. The medium of claim 8, comprising instructions to provide a visualization of the exception flow.

11. The medium of claim 8, wherein the exception handling patterns are syntactically mapped to Business Process Model and Notation (BPMN) and its execution semantics.

12. The medium of claim 8, wherein the type of the exception comprises one or more of an activity failure, a message flow failure, a timeout, resource unavailability, an external event, or a constraint violation.

13. The medium of claim 8, wherein the one or more exception handling patterns comprise one or more of a retry pattern, a failover router, a compensation sphere, an exception sphere, a dead letter channel, or an invalid message channel.

14. The medium of claim 8, wherein the exception flow is configured to realize one or more of a quality of service (QoS), a message exchange pattern (MEP), or an enterprise integration pattern (EIP) integration logic.

15. A system, comprising:

a memory;

at least one hardware processor interoperably coupled with the memory and configured to;

identify an exception corresponding to an integration operation of an integration process;

identify a type of the exception;

determine one or more exception handling patterns for the type of the exception, wherein a failover router process is used to react on non-callable exception handling patterns within a sequence of integration patterns by calling alternative integration pattern channels without requiring external configuration messages, and wherein the alternative integration pattern channels are modeled explicitly; and

configure an exception flow of the integration process based on the one or more exception handling patterns.

16. The system of claim 15, wherein the at least one hardware processor configured to provide a visualization of the exception flow.

17. The system of claim 15, wherein the exception handling patterns are syntactically mapped to Business Process Model and Notation (BPMN) and its execution semantics.

18. The system of claim 15, wherein the type of the exception comprises one or more of an activity failure, a message flow failure, a timeout, resource unavailability, an external event, or a constraint violation.

19. The system of claim 15, wherein the one or more exception handling patterns comprise one or more of a retry pattern, a failover router, a compensation sphere, an exception sphere, a dead letter channel, or an invalid message channel.

20. The system of claim 15, wherein the exception flow is configured to realize one or more of a quality of service (QoS), a message exchange pattern (MEP), or an enterprise integration pattern (EIP) integration logic.