Granted Patent B2

US 9,373,094 · App. 14/182,218 · Granted Jun 21, 2016

Inventors: Vishal Chalana (Panchkula, IN); Amit Sharma (Chandigarh, IN); Piyush Nagar (Chandigarh, IN); Vishal Sharma (Meerut, IN); Vikram Chalana (Bothell, WA)

Assignee: Winshuttle, LLC

G06Q10/06G06F9/541H04L47/748

Abstract

Claims (84)

1. A dynamic-web-services-server-implemented method for publishing a dynamic web service, the method comprising:

receiving, by said dynamic-web-services server from a first enterprise-resource-planning client, a recorded transaction map describing a recorded transaction between said first enterprise-resource-planning client and an enterprise-resource-planning server, said recorded transaction map including metadata corresponding to a plurality of transaction fields;

generating, by said dynamic-web-services server, a service description framework for a new dynamic web service corresponding to said recorded transaction, including for each of said plurality of transaction fields, defining an input corresponding to the current transaction field and storing said defined input in said service description framework;

determining, by said dynamic-web-services server, a unique service identifier for invoking said new dynamic web service;

persisting, by said dynamic-web-services server, said unique service identifier, said service description framework, and said recorded transaction map in a data store;

receiving, by said dynamic-web-services server, a first request from a second enterprise-resource-planning client to invoke said new dynamic web service according to a package of input data, said first request indicating said unique service identifier, said package of input data being received in a first format according to a first calling mechanism;

retrieving, by said dynamic-web-services server, said recorded transaction map from said data store according to said unique service identifier;

according to said recorded transaction map, determining, by said dynamic-web-services server, at least one Enterprise Application API call for performing said recorded transaction, said at least one Enterprise Application API call requiring a second calling mechanism, different from said first calling mechanism;

repackaging, by said dynamic-web-services server, said package of input data in said first format into repackaged input data in a second format that complies with said second calling mechanism; and

invoking, by said dynamic-web-services server, an Enterprise Application server to perform said recorded transaction according to said second calling mechanism, said at least one Enterprise Application API call, and said repackaged input data.

2. The method of claim 1 , further comprising:

receiving a second request from said first enterprise-resource-planning client or said second enterprise-resource-planning client for said service description framework, said second request indicating said unique service identifier;

retrieving said service description framework from said data store according to said unique service identifier; and

sending said service description framework to said first enterprise-resource-planning client or said second enterprise-resource-planning client.

3. The method of claim 1 , further comprising:

receiving from said enterprise-resource-planning server process output data corresponding to the invocation of said enterprise-resource-planning server;

packaging said process output data according to said first calling mechanism into packaged process output data; and

providing said packaged process output data to said first enterprise-resource-planning client or said second enterprise-resource-planning client.

4. The method of claim 1 , wherein performing said recorded transaction according to said package of input data comprises invoking said at least one Enterprise Application API call according to said second calling mechanism and said repackaged input data.

5. The method of claim 1 , wherein:

said first calling mechanism comprises Simple Object Access Protocol (“SOAP”);

said first format comprises Extensible Markup Language (“XML”); and

said second calling mechanism comprises a remote function call (“RFC”).

6. The method of claim 1 , wherein:

said first calling mechanism conforms to Representational State Transfer (“REST”) constraints and uses HTTP methods; and

said second calling mechanism comprises a remote function call (“RFC”).

7. The method of claim 1 , wherein causing said recorded transaction to be invoked comprises invoking an Enterprise Application server to perform said recorded transaction.

8. The method of claim 1 , wherein said first request is received via a transaction client software process on said second enterprise-resource-planning client.

9. A computing apparatus for publishing a dynamic web service, the apparatus comprising a processor and a memory storing instructions that, when executed by the processor, configure the apparatus to:

receive, from a first enterprise-resource-planning client, a recorded transaction map describing a recorded transaction between said first enterprise-resource-planning client and an enterprise-resource-planning server, said recorded transaction map including metadata corresponding to a plurality of transaction fields;

generate a service description framework for a new dynamic web service corresponding to said recorded transaction, including for each of said plurality of transaction fields, defining an input corresponding to the current transaction field and storing said defined input in said service description framework;

determine a unique service identifier for invoking said new dynamic web service;

persist said unique service identifier, said service description framework, and said recorded transaction map in a data store;

receive a first request from a second enterprise-resource-planning client to invoke said new dynamic web service according to a package of input data, said first request indicating said unique service identifier, said package of input data being received in a first format according to a first call mechanism;

retrieve said recorded transaction map from said data store according to said unique service identifier;

according to said recorded transaction map, determine at least one Enterprise Application API call for performing said recorded transaction, said at least one Enterprise Application API call requiring a second call mechanism, different from said first call mechanism;

repackage said package of input data in said first format into repackaged input data in a second format that complies with said second call mechanism; and

invoke an Enterprise Application server to perform causing said recorded transaction according to said second call mechanism, said at least one Enterprise Application API call, and said repackaged input data.

10. The apparatus of claim 9 , wherein the memory stores further instructions that further configure the apparatus to:

receive a second request from said first enterprise-resource-planning client or said second enterprise-resource-planning client for said service description framework, said second request indicating said unique service identifier;

retrieve said service description framework from said data store according to said unique service identifier; and

send said service description framework to said first enterprise-resource-planning client or said second enterprise-resource-planning client.

11. The apparatus of claim 9 , wherein the memory stores further instructions that further configure the apparatus to:

receive from said enterprise-resource-planning server process output data corresponding to the invocation of said enterprise-resource-planning server;

package said process output data according to said first call mechanism into packaged process output data; and

provide said packaged process output data to said first enterprise-resource-planning client or said second enterprise-resource-planning client.

12. The apparatus of claim 9 , wherein perform said recorded transaction according to said package of input data comprises invoking said at least one Enterprise Application API call according to said second call mechanism and said repackaged input data.

13. The apparatus of claim 9 , wherein:

said first call mechanism comprises Simple Object Access Protocol (“SOAP”);

said first format comprises Extensible Markup Language (“XML”); and

said second call mechanism comprises a remote function call (“RFC”).

14. The apparatus of claim 9 , wherein:

said first call mechanism conforms to Representational State Transfer (“REST”) constraints and uses HTTP methods; and

said second call mechanism comprises a remote function call (“RFC”).

15. The apparatus of claim 9 , wherein causing said recorded transaction to be invoked comprises invoking an Enterprise Application server to perform said recorded transaction.

16. The apparatus of claim 9 , wherein said first request is received via a transaction client software process on said second enterprise-resource-planning client.

17. A non-transient computer-readable storage medium having stored thereon instructions that, when executed by a processor, configure the processor to:

receive, from a first enterprise-resource-planning client, a recorded transaction map describing a recorded transaction between said first enterprise-resource-planning client and an enterprise-resource-planning server, said recorded transaction map including metadata corresponding to a plurality of transaction fields;

generate a service description framework for a new dynamic web service corresponding to said recorded transaction, including for each of said plurality of transaction fields, defining an input corresponding to the current transaction field and storing said defined input in said service description framework;

determine a unique service identifier for invoking said new dynamic web service;

persist said unique service identifier, said service description framework, and said recorded transaction map in a data store;

receive a first request from a second enterprise-resource-planning client to invoke said new dynamic web service according to a package of input data, said first request indicating said unique service identifier, said package of input data being received in a first format according to a first call mechanism;

retrieve said recorded transaction map from said data store according to said unique service identifier;

according to said recorded transaction map, determine at least one Enterprise Application API call for performing said recorded transaction, said at least one Enterprise Application API call requiring a second call mechanism, different from said first call mechanism;

repackage said package of input data in said first format into repackaged input data in a second format that complies with said second call mechanism; and

invoke an Enterprise Application server to perform said recorded transaction to be performed according to said second call mechanism, said at least one Enterprise Application API call, and said repackaged input data.

18. The storage medium of claim 17 , having stored thereon further instructions that further configure the processor to:

receive a second request from said first enterprise-resource-planning client or said second enterprise-resource-planning client for said service description framework, said second request indicating said unique service identifier;

retrieve said service description framework from said data store according to said unique service identifier; and

send said service description framework to said first enterprise-resource-planning client or said second enterprise-resource-planning client.

19. The storage medium of claim 17 , having stored thereon further instructions that further configure the processor to:

receive from said enterprise-resource-planning server process output data corresponding to the invocation of said enterprise-resource-planning server;

package said process output data according to said first call mechanism into packaged process output data; and

provide said packaged process output data to said first enterprise-resource-planning client or said second enterprise-resource-planning client.

20. The storage medium of claim 17 , wherein perform said recorded transaction according to said package of input data comprises invoking said at least one Enterprise Application API call according to said second call mechanism and said repackaged input data.

21. The storage medium of claim 17 , wherein:

said first call mechanism comprises Simple Object Access Protocol (“SOAP”);

said first format comprises Extensible Markup Language (“XML”); and

said second call mechanism comprises a remote function call (“RFC”).

22. The storage medium of claim 17 , wherein:

said first call mechanism conforms to Representational State Transfer (“REST”) constraints and uses HTTP methods; and

said second call mechanism comprises a remote function call (“RFC”).

23. The storage medium of claim 17 , wherein causing said recorded transaction to be performed comprises invoking an Enterprise Application server to perform said recorded transaction.

24. The storage medium of claim 17 , wherein said first request is received via a transaction client software process on said second enterprise-resource-planning client.

Assignments (9)

Continuity (4)