SCRIPTING WEB SERVICES

• US 20140297725A1
• Filed: 01/31/2014
• Published: 10/02/2014
• Est. Priority Date: 11/23/2010
• Status: Active Grant

• Current Assignee: PTC Inc.
• Original Assignee: Axeda (PTC Inc.)
• Inventors: Biron, Joseph L. III
• Granted Patent: US 9,172,745 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 9/45512 Command shells
• CPC Class Codes: H04L 41/22 comprising specially adapted graphical user interfaces [GUI]
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context

Abstract

A process performed on a server includes configuring the server to enable script for a Web service to be defined dynamically, where the Web service includes an application program interface (API) for enabling access by, and interaction with, a computer program executing on a device other than the server. The process also includes compiling the script to produce machine-executable code for the Web service, receiving a call from the computer program to the Web service, executing the machine-executable code in response to the call to produce an output, and sending the output to the device.

Claims

1-17. -17. (canceled)

18. A method performed on one or more servers, comprising:

enabling a client to define a Web service dynamically;

storing, in memory on the one or more servers, code for different versions of script corresponding the Web service, the different versions including at least one earlier version of the script and at least one later version of the script;

receiving a call to the Web service from a device;

identifying a version of the script corresponding to the Web service;

executing, on the one or more servers, code corresponding to the version of the script to implement the Web service, the code producing an output; and

sending the output to the device.

19. The method of claim 18, wherein enabling a client to define a Web service dynamically comprises storing, in the one or more servers, code to generate a graphical user interface (GUI) into which the script is entered;

and

wherein the method further comprises;

receiving a request for the GUI;

outputting the GUI in response to the request; and

receiving the script via the GUI.

20. The method of claim 18, wherein each version of the script has a security context, the security context comprising a JAVA classloader that restricts the script to using an approved set of classes and interfaces.

21. The method of claim 20, further comprising:

authenticating the call by authenticating a user who owns the account;

wherein the security context is modifiable.

22. A method performed on one or more servers, comprising:

configuring the one or more servers to enable dynamic definition of a Web service, the Web service enabling access by, and interaction with, a monitoring agent;

receiving, from a client associated with the monitoring agent, script defining the Web service, the script being stored in different versions in memory on the one or more servers, the different versions including at least one earlier version of the script and at least one later version of the script;

compiling a version of the script on the one or more servers to produce machine-executable code for the Web service, the machine-executable code defining a context among multiple contexts for the script;

receiving a call to the Web service from the monitoring agent;

executing the machine-executable code based on the call, wherein execution of the machine-executable code produces an output; and

sending the output to the monitoring agent

23. The method of claim 22, wherein configuring the one or more servers comprises storing, in the one or more servers, code to generate a graphical user interface (GUI) into which the script is entered;

and

wherein the method further comprises;

receiving a request for the GUI;

outputting the GUI in response to the request; and

receiving the script via the GUI.

24. The method of claim 22, wherein configuring the one or more servers comprises:

storing, in the one or more servers, a compiler for compiling the script; and

storing, in the one or more servers, a database to store information corresponding to the machine-executable code.

25. The method of claim 22, wherein configuring the one or more servers comprises storing, in the one or more servers, machine-executable code that, when executed, enables receipt of the script.

26. The method of claim 22, wherein the call comprises a HyperText Transfer Protocol (HTTP) command, the HTTP command identifying the script in accordance with a convention defined by a proprietor of the script.

27. The method of claim 22, further comprising sending the output to a device or system other than the monitoring agent.

28. The method of claim 22, wherein the monitoring agent communicates with the one or more servers over a communication path that is at least partially wireless.

29. The method of claim 22, wherein the call comprises instructions to access a functionality of the Web service.

30. One or more non-transitory machine-readable storage media storing instructions that are executable on one or more servers to perform operations comprising:

enabling a client to define a Web service dynamically;

storing, in memory on the one or more servers, code for different versions of script corresponding the Web service, the different versions including at least one earlier version of the script and at least one later version of the script;

receiving a call to the Web service from a device;

identifying a version of the script corresponding to the Web service;

executing, on the one or more servers, code corresponding to the version of the script to implement the Web service, the code producing an output; and

sending the output to the device.

31. The one or more non-transitory machine-readable storage media of claim 30, wherein enabling a client to define a Web service dynamically comprises storing, in the one or more servers, code to generate a graphical user interface (GUI) into which the script is entered;

and

wherein the operations comprise;

receiving a request for the GUI;

outputting the GUI in response to the request; and

receiving the script via the GUI.

32. The one or more non-transitory machine-readable storage media of claim 30, wherein each version of the script has a security context, the security context comprising a JAVA classloader that restricts the script to using an approved set of classes and interfaces.

33. The one or more non-transitory machine-readable storage media of claim 32, wherein the operations comprise:

authenticating the call by authenticating a user who owns the account;

wherein the security context is modifiable.

34. One or more non-transitory machine-readable storage media storing instructions that are executable on one or more servers to perform operations comprising:

configuring the one or more servers to enable dynamic definition of a Web service, the Web service enabling access by, and interaction with, a monitoring agent;

receiving, from a client associated with the monitoring agent, script defining the Web service, the script being stored in different versions in memory on the one or more servers, the different versions including at least one earlier version of the script and at least one later version of the script;

compiling a version of the script on the one or more servers to produce machine-executable code for the Web service, the machine-executable code defining a context among multiple contexts for the script;

receiving a call to the Web service from the monitoring agent;

executing the machine-executable code based on the call, wherein execution of the machine-executable code produces an output; and

sending the output to the monitoring agent

35. The one or more non-transitory machine-readable storage media of claim 34, wherein configuring the one or more servers comprises storing, in the one or more servers, code to generate a graphical user interface (GUI) into which the script is entered;

and

wherein the operations comprise;

receiving a request for the GUI;

outputting the GUI in response to the request; and

receiving the script via the GUI.

36. The one or more non-transitory machine-readable storage media of claim 34, wherein configuring the one or more servers comprises:

storing, in the one or more servers, a compiler for compiling the script; and

storing, in the one or more servers, a database to store information corresponding to the machine-executable code.

37. The one or more non-transitory machine-readable storage media of claim 34, wherein configuring the one or more servers comprises storing, in the one or more servers, machine-executable code that, when executed, enables receipt of the script.

38. The one or more non-transitory machine-readable storage media of claim 34, wherein the call comprises a HyperText Transfer Protocol (HTTP) command, the HTTP command identifying the script in accordance with a convention defined by a proprietor of the script.

39. The one or more non-transitory machine-readable storage media of claim 34, wherein the operations comprise sending the output to a device or system other than the monitoring agent.

40. The one or more non-transitory machine-readable storage media of claim 34, wherein the one or more servers are configured to communicate with the monitoring agent over a communication path that is at least partially wireless.

41. The one or more non-transitory machine-readable storage media of claim 34, wherein the call comprises instructions to access a functionality of the Web service.