Dynamic web services system and method
A Dynamic Web Service server may facilitate custom Enterprise Application interface development with little or no developer input by dynamically creating a web service for performing a particular transaction according to a transaction map. An Enterprise Application client device may create a transaction map by “recording” a transaction between an Enterprise Application client and an Enterprise Application server and mapping transaction fields to a custom interface generated to collect data for re-performing the recorded transaction. The Enterprise Application client device may call the dynamic web service, and the Dynamic Web Service server may then perform the recorded transaction using input data collected in the custom interface.
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 said first enterprise-resource-planning client or 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;
using said at least one Enterprise Application API call, invoking, by said 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; and
receiving from said enterprise-resource-planning server process output data corresponding to the invocation of said enterprise-resource-planning server.
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:
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:
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”).
5. 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 said first enterprise-resource-planning client or 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;
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 calling mechanism, different from said first calling mechanism;
repackage said package of input data in said first format into repackaged input data in a second format that complies with said second calling mechanism;
using said at least one Enterprise Application API call, invoke 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; and
receive from said enterprise-resource-planning server process output data corresponding to the invocation of said enterprise-resource-planning server.
6. The apparatus of claim 5 , 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.
7. The apparatus of claim 5 , wherein the memory stores further instructions that further configure the apparatus to:
package said process output data according to said first calling 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.
8. The apparatus of claim 5 , 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”).
9. 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 said first enterprise-resource-planning client or 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;
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 calling mechanism, different from said first calling mechanism;
repackage said package of input data in said first format into repackaged input data in a second format that complies with said second calling mechanism;
using said at least one Enterprise Application API call, invoke 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; and
receive from said enterprise-resource-planning server process output data corresponding to the invocation of said enterprise-resource-planning server.
10. The storage medium of claim 9 , 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.
11. The storage medium of claim 9 , having stored thereon further instructions that further configure the processor to:
package said process output data according to said first calling 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 storage medium 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”).