MESSAGE HANDLING IN A SERVICE-ORIENTED ARCHITECTURE

• US 20100100777A1
• Filed: 10/20/2008
• Published: 04/22/2010
• Est. Priority Date: 10/20/2008
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Ziegler, Carsten
• Granted Patent: US 8,020,051 B2
• Time in Patent Office: Days
• US Class Current: 714/57
• CPC Class Codes: G06F 11/327 Alarm or error message display

Abstract

A service call to a backend system is initiated by a user interface in a service-oriented architecture. Thereafter, a service answer is received from the backend system encapsulating a backend error object. The backend error object is mapped to a front end error object. A front end error message can later be presented to a user in the user interface that is derived from the front end error object. Related apparatus, systems, techniques and articles are also described.

Claims

1. An article comprising a tangible machine-readable storage medium embodying instructions that when performed by one or more machines result in operations comprising:

initiating a service call to a backend system by a user interface in a service-oriented architecture;

receiving a service answer from the backend system encapsulating a backend error object;

mapping the backend error object to a front end error object; and

presenting a front end error message derived from the front end error object in the user interface.

2. An article as in claim 1, wherein the mapping comprises accessing a mapping table mapping backend error objects to front end error objects.

3. An article as in claim 2, wherein the mapping table comprises a backend error preview for each backend error object.

4. An article as in claim 2, wherein the mapping table comprises a front end error preview characterizing the front end error message.

5. An article as in claim 1, wherein the backend error object comprises a short text description characterizing an error and a long text description characterizing the error, the long text description containing more characters than the short text description.

6. An article as in claim 1, wherein the backend error object characterizes a severity of a corresponding error.

7. An article as in claim 1, wherein the tangible machine-readable storage medium further embodies instructions that when performed by one or more machines result in operations comprising:

initiating, by the user interface, a service based on variables encapsulated in the backend error object to obtain error information to include in the front end error message.

8. An article as in claim 1, wherein the front end error object includes all attributes of the backend error object.

9. An article as in claim 1, wherein the front end error object includes a subset of attributes of the backend error object and additional attributes not included in the backend error object.

10. An article as in claim 1, wherein a backend error message in the backend error object cannot be overrun and is required to be presented in the front end error message.

11. A computer-implemented method comprising:

initiating a service call to a backend system by a user interface in a service-oriented architecture;

receiving a service answer from the backend system encapsulating a backend error object;

mapping the backend error object to a front end error object; and

presenting, in the user interface, a front end error message derived from variables in the front end error object.

12. A method as in claim 11, wherein the mapping comprises accessing a mapping table mapping backend error objects to front end error objects.

13. A method as in claim 12, wherein the mapping table comprises a backend error preview for each backend error object.

14. A method as in claim 12, wherein the mapping table comprises a front end error preview characterizing the front end error message.

15. A method as in claim 11, wherein the backend error object comprises a short text description characterizing an error and a long text description characterizing the error, the long text description containing more characters than the short text description.

16. A method as in claim 11, wherein the backend error object characterizes a severity of a corresponding error.

17. A method as in claim 11 further comprising:

initiating, by the user interface, a service based on variables encapsulated in the backend error object to obtain error information to include in the front end error message.

18. A method as in claim 11, wherein the front end error object includes all attributes of the backend error object.

19. A method as in claim 11, wherein the front end error object includes a subset of attributes of the backend error object and additional attributes not included in the backend error object.

20. A system comprising:

a front end system comprising a user interface; and

a backend system coupled to the front end system via TCP/IP in a service-oriented architecture;

the front end system initiating a service call to the backend system via the user interface;

the backend system generating a service answer to the service call that includes a backend error object;

the front end system mapping the backend error object to a front end error object so that a front end error message derived from the front end error object can be presented in the user interface, the front end error message being different than a backend error message included in the backend error object.