Granted Patent B2

US 8,516,554 · App. 13/666,344 · Granted Aug 20, 2013

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

Assignee: Winshuttle, LLC

Abstract

Claims (78)

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

receiving, by the dynamic-web-services server from an Enterprise Application client, a recorded transaction map describing a recorded transaction between said Enterprise Application client and an Enterprise Application server, said recorded transaction map including metadata corresponding to a plurality of transaction fields, wherein said Enterprise Application client comprises an Enterprise resource planning (“ERP”) client, and wherein said Enterprise Application server comprises an ERP server;

automatically generating, by the 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 the dynamic-web-services server, a unique service identifier for invoking said new dynamic web service;

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

providing, by the dynamic-web-services server, said unique service identifier to said Enterprise Application client;

receiving, by the dynamic-web-services server, a first request from said Enterprise Application 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 the dynamic-web-services server, said recorded transaction map from said data store according to said unique service identifier;

according to recorded transaction map, determining, by the 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 the 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

using said at least one Enterprise Application API call, invoking, by the dynamic-web-services server, a remote 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 Enterprise Application 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 Enterprise Application client.

3. The method of claim 1 , further comprising:

receiving from said Enterprise Application server process output data corresponding to the invocation of said Enterprise Application 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 Enterprise Application 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. A dynamic-web-services-serving apparatus comprising a processor and a memory having stored therein instructions that when executed by the processor, configure the apparatus to perform a method for publishing a dynamic web service, the method comprising:

receiving, from an Enterprise Application client, a recorded transaction map describing a recorded transaction between said Enterprise Application client and an Enterprise Application server, said recorded transaction map including metadata corresponding to a plurality of transaction fields, wherein said Enterprise Application client comprises an Enterprise resource planning (“ERP”) client, and wherein said Enterprise Application server comprises an ERP server;

automatically generating 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 a unique service identifier for invoking said new dynamic web service;

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

providing said unique service identifier to said Enterprise Application client;

receiving a first request from said Enterprise Application 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 said recorded transaction map from said data store according to said unique service identifier;

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

repackaging 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

using said at least one Enterprise Application API call, invoking a remote 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.

7. The apparatus of claim 6 , the method further comprising:

receiving said second request from said Enterprise Application 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 Enterprise Application client.

8. The apparatus of claim 6 , the method further comprising:

receiving from said Enterprise Application server process output data corresponding to the invocation of said Enterprise Application 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 Enterprise Application client.

9. The apparatus of claim 6 , 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.

10. The apparatus of claim 6 , 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”).

11. A non-transient computer-readable storage medium having stored therein instructions that when executed by a processor, configure the processor to perform a method for publishing a dynamic web service, the method comprising:

receiving, from an Enterprise Application client, a recorded transaction map describing a recorded transaction between said Enterprise Application client and an Enterprise Application server, said recorded transaction map including metadata corresponding to a plurality of transaction fields, wherein said Enterprise Application client comprises an Enterprise resource planning (“ERP”) client, and wherein said Enterprise Application server comprises an ERP server;

automatically generating 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 a unique service identifier for invoking said new dynamic web service;

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

providing said unique service identifier to said Enterprise Application client;

receiving a first request from said Enterprise Application 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 said recorded transaction map from said data store according to said unique service identifier;

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

repackaging 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

using said at least one Enterprise Application API call, invoking a remote 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.

12. The storage medium of claim 11 , the method further comprising:

receiving said second request from said Enterprise Application 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 Enterprise Application client.

13. The storage medium of claim 11 , the method further comprising:

receiving from said Enterprise Application server process output data corresponding to the invocation of said Enterprise Application 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 Enterprise Application client.

14. The storage medium of claim 11 , 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.

15. The storage medium of claim 11 , 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”).

Assignments (9)

Continuity (3)