WIDGET RUNTIME ENGINE FOR ENTERPRISE WIDGETS

• US 20080141141A1
• Filed: 10/04/2007
• Published: 06/12/2008
• Est. Priority Date: 12/07/2006
• Status: Abandoned Application

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Browne, Denis J., Samson, Frederic, Moore, Dennis B., Wood, Eric R.B.
• Application Number:
  US11/867,655
• Publication Number:
  US 20080141141A1
• Time in Patent Office: Days
• US Class Current: 715/748
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces

Abstract

An Enterprise widget interface in a computing device that receives input from a portable logic module soliciting operations from a backend server separate from the computing device, sends requests to the backend server to execute the operation and receives responses from the backend server including data related to the execution of the operation. The Enterprise widget interface further sends the response related data to the portable logic module for rendering via a computing interface connected with the computing device.

Claims

1. An Enterprise widget interface accessible via a computing device comprising:

a receiver to receive an input from a widget runtime environment, the input to solicit an operation of a backend server separate from the computing device;

a request transmitter to send a request from the Enterprise widget interface to the backend server to execute the operation;

a response receiver to receive a response from the backend server, the response to include data related to the execution of the operation; and

a generator to generate a representation of the response, the representation to be displayed at the widget runtime environment via a computing interface connected with the computing device.

2. The Enterprise widget interface of claim 1, further comprising:

a security transmitter to receive the request from the request transmitter, encrypt the request, and transmit the request to the backend server via a secure communication path.

3. The Enterprise widget of claim 1, further comprising:

an encryptor to encrypt the request before the request is sent to the backend server; and

a decryptor to decrypt the response after the response is received from the backend server.

4. The Enterprise widget interface of claim 1, wherein the input from the widget runtime environment to originate at an Enterprise widget to execute within the widget runtime environment.

5. The Enterprise widget interface of claim 1, wherein the input from the widget runtime environment to be received from a widget engine within the widget runtime environment, the widget engine to support the execution of one or more widgets.

6. The Enterprise widget interface of claim 1, wherein the representation to be displayed at the widget runtime environment via the computing interface comprises the widget runtime environment to display the representation in association with an Enterprise widget operating within the widget runtime environment.

7. The Enterprise widget interface of claim 1, further comprising at least one of:

an Extended Markup Language (“

XML”

) translator to provide XML translation services to the Enterprise widget interface;

a Hyper-text transfer protocol (“

HTTP”

) translator to provide HTML translation services;

a Secure Sockets Layer (“

SSL”

) translator to provide SSL translation services; and

a Structured Query Language (“

SQL”

) translator to provide SQL translation services.

8. The Enterprise widget interface of claim 1, further comprising at least one service module selected from the group comprising:

a service tracking module to provide a list of available service modules accessible from the Enterprise widget interface;

a mash-up coordinator service module to coordinate communication between all available service modules and to join the functionality of the respective service modules;

a Single Sign On (“

SSO”

) service module to offload authentication security responsibilities from the Enterprise widget interface;

a persistence service module to provide data persistence functionality for Enterprise widgets connected with the Enterprise widget interface;

an auto-update service module to check for and receive updates from a remote source on behalf of the Enterprise widget interface and all connected widgets;

a feedback service module to provide usage statistics and diagnostic information to a remote destination on behalf of the Enterprise widget interface; and

a remote services module to connect the Enterprise widget interface with remove services not locally available at the computing interface.

9. The Enterprise widget interface of claim 1, further comprising at least one of:

a widget skins interface to enable the Enterprise widget interface to represent supplemental graphical overlays onto widgets connected with the Enterprise widget interface;

a plug-in interface to connect with supplemental plug-in modules;

an interpretation layer to connect the Enterprise widget interface with translators that convert data formats; and

a services director to connect the Enterprise widget interface with supplemental service modules.

10. A method in a computing device comprising:

receiving at an Enterprise widget interface within the computing device, an input from a portable logic module, the input soliciting an operation of a backend server separate from the computing device;

sending a request from the Enterprise widget interface to the backend server to execute the operation;

receiving at the Enterprise widget interface, a response from the backend server, the response including data related to the execution of the operation; and

sending the response from the Enterprise widget interface to the portable logic module for rendering by a computing interface connected with the computing device.

11. The method of claim 10, wherein the portable logic module is an Enterprise widget.

12. The method of claim 10, wherein the backend server operates on a secure network, the method further comprising:

negotiating at the Enterprise widget interface, a secure connection with the backend server via the secure network.

13. The method of claim 10, wherein sending the request from the Enterprise widget interface to the backend server comprises:

encrypting the request at the Enterprise widget interface; and

transmitting the encrypted request to the backend server via the secure network.

14. The method of claim 10, wherein sending the request from the Enterprise widget interface to the backend server comprises:

encoding the request on an encrypted transmission signal and;

transmitting the encrypted transmission signal to the backend server via the secure network.

15. The method of claim 10, wherein receiving at the Enterprise widget interface, the response from the backend server comprises:

receiving an encrypted response from the backend server; and

decrypting the response.

16. The method of claim 10, further comprising:

determining a communication path to the backend server.

17. The method of claim 16, wherein determining the communication path to the backend server comprises at least one of:

reading a portable logic module attribute specifying the communication path;

reading an Enterprise widget interface attribute specifying the communication path;

requesting the communication path from a backend data repository;

requesting the communication path from a backend database; and

requesting the communication path from an Enterprise widget interface server.

18. The method of claim 10, wherein the request includes a plurality of message components, wherein each message component is selected from a group of message components including a portable logic module identifier, a portable logic module type, a portable logic module environment identifier, a portable logic module state, portable logic module permissions, a portable logic module user identifier, portable logic module user credentials, portable logic module encryption keys, and portable logic module content request, or a combination thereof.

19. The method of claim 10, wherein the response includes a plurality of message components, wherein each message component is selected from a group of message components including portable logic module encryption keys, portable logic module authorization data, portable logic module attribute modifiers, portable logic module state changes, portable logic module input requests, portable logic module relationships, and portable logic module content, or a combination thereof.

20. A computing device comprising a machine-readable medium having instructions stored thereon that, when executed by a processor, cause the processor to perform operations comprising:

receiving at an Enterprise widget interface within the computing device, an input from a portable logic module, the input soliciting an operation of a backend server separate from the computing device;

sending a request from the Enterprise widget interface to the backend server to execute the operation;

receiving at the Enterprise widget interface, a response from the backend server, the response including data related to the execution of the operation; and

sending the response from the Enterprise widget interface to the portable logic module for rendering by a computing interface connected with the computing device.

21. The computing device of claim 20, wherein the portable logic module is an Enterprise widget.

22. The computing device of claim 20, wherein the backend server operates on a secure network, and wherein the instructions cause the processor to perform further operations comprising:

negotiating, at the Enterprise widget interface, a secure connection with the backend server via the secure network.

23. The computing device of claim 20, wherein sending the request from the Enterprise widget interface to the backend server comprises:

encrypting the request at the Enterprise widget interface; and

transmitting the encrypted request to the backend server via the secure network.

24. The computing device of claim 20, wherein the instructions cause the processor to perform further operations comprising:

determining a communication path to the backend server, wherein determining the communication path to the backend server comprises at least one of;

reading a portable logic module attribute specifying the communication path;

reading an Enterprise widget interface attribute specifying the communication path;

requesting the communication path from a backend data repository;

requesting the communication path from a backend database; and

requesting the communication path from an Enterprise widget interface server.