UNIFIED WEB SERVICE URI BUILDER AND VERIFICATION

• US 20120246334A1
• Filed: 03/21/2011
• Published: 09/27/2012
• Est. Priority Date: 03/21/2011
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Yang, Li, Liensberger, Christian, Li, Chunjia
• Application Number:
  US13/052,717
• Publication Number:
  US 20120246334A1
• Time in Patent Office: Days
• US Class Current: 709/232
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion

Abstract

Verifying a translation middleware piece. A first request is provided to a front end user service using a protocol appropriate for the front end user service, including a translation middleware piece. The translation middleware piece translates requests provided to the front end service to requests for back-end data stores. A first response to the first request to the front end user service is received. A second request is provided to a back-end data store. The second request to the back-end data store is in a format appropriate for the back-end data store and includes elements that should return the same results as the first request to the front end user service. A second response to the second request to the back-end data store is received. Based on the responses, a functional state is determined for at least one of the, front end, the back-end, or the translation middleware piece.

Claims

1. In a computing environment, a method of improving a translation middleware piece, the method comprising:

providing a first request to a front end user service using a protocol appropriate for the front end user service, wherein the front end user service includes a translation middleware piece, and wherein the translation middleware piece translates requests provided to the front end service to requests for one or more back-end data stores;

receiving a first response to the first request to the front end user service;

providing a second request to a back-end data store, the second request to the back-end data store being in a format appropriate for the back-end data store and comprising elements that should return the same results as the first request to the front end user service; and

receiving a second response to the second request to the back-end data store;

based on the first and second responses, determining a functional state for at least one of the, front end, the back-end, or the translation middleware piece.

2. The method of claim 1, further comprising:

comparing the first and second responses; and

based on the comparison performing one of either determining that the translation middleware piece is functioning correctly, or determining the translation middleware piece is mal-functioning.

3. The method of claim 1, further comprising determining that one or more of the responses comprises an error and as such determining that at least one of the, front end, the back-end, or the translation middleware piece is malfunctioning.

4. The method of claim 1, further comprising based on the first and second responses updating the translation middleware piece to fix a malfunction.

5. The method of claim 1, further comprising based on the first and second responses, providing to a data store an indication of a problem with the data store.

6. The method of claim 1, wherein the first and second requests are generated as part of an automatic request generation process to achieve high coverage of request alternatives.

7. The method of claim 6, wherein the first and second requests are generated a part of a process that attempts to minimize the number of requests while attempting to maximizing coverage of alternatives.

8. The method of claim 7, wherein the requests first and second requests are generated in a limited fashion based on limitations defined in at least one of a range, an enums, a database schema, or a set of enumerated types.

9. The method of claim 1, wherein a malfunction of the translation middleware piece is determined based on an error from a data store.

10. The method of claim 1, wherein a malfunction of the translation middleware piece is determined based on one or more communication issues.

11. The method of claim 1, wherein a malfunction of the translation middleware piece is determined based on duplication of data items.

12. The method of claim 1, wherein a malfunction of the translation middleware piece is determined based on missing data items.

13. A physical computer readable storage medium comprising computer executable instructions that when executed by one or more processors, causes the following to be performed:

sending a first request to a front end user service using a protocol appropriate for the front end user service, wherein the front end user service includes a translation middleware piece, and wherein the translation middleware piece translates requests provided to the front end service to requests for one or more back-end data stores;

receiving a first response to the first request to the front end user service;

sending a second request to a back-end data store, the second request to the back-end data store being in a format appropriate for the back-end data store and comprising elements that should return the same results as the first request to the front end user service;

receiving a second response to the second request to the back-end data store; and

based on the first and second responses, determining a functional state for at least one of the, front end, the back-end, or the translation middleware piece.

14. The computer readable medium of claim 13, further comprising:

comparing the first and second responses; and

based on the comparison performing one of either determining that the translation middleware piece is functioning correctly, or determining the translation middleware piece is mal-functioning.

15. The computer readable medium of claim 13, further comprising determining that one or more of the responses comprises an error and as such determining that at least one of the, front end, the back-end, or the translation middleware piece is malfunctioning.

16. The computer readable medium of claim 13, further comprising based on the first and second responses updating the translation middleware piece to fix a malfunction.

17. The computer readable medium of claim 13, further comprising based on the first and second responses, providing to a data store an indication of a problem with the data store.

18. The computer readable medium of claim 13, wherein the first and second requests are generated as part of an automatic request generation process to achieve high coverage of request alternatives.

19. The computer readable medium of claim 13, wherein a malfunction of the translation middleware piece is determined based on an error from a data store.

20. A computing system comprising:

a middleware translation system, wherein the middleware translation system is configured to translate uniform requests to custom requests for a plurality of backend data stores, the backend data stores comprising one or more of databases or web services, wherein at least two or more of the data stores communicate using different protocols; and

a verification tool coupled to the middleware translation system, wherein the verification tool is configured to;

send a first request to the translation middleware piece which translates the first request to one or more requests to one or more back-end data stores;

receive a first response to the first request from the middleware translation piece;

send one or more second requests to the one or more back-end data stores, the one or more second requests to the one or more back-end data stores being in one or more formats appropriate for the back-end data store and comprising elements that should return the same results as the first request to the middleware translation piece;

receive one or more second responses to the one or more second requests to the one or more back-end data stores; and

based on a comparison of the first and second responses on a row by row basis, determine that the middleware translation piece is malfunctioning.