Remote user interface for external connections

• US 7,849,445 B2
• Filed: 12/20/2005
• Issued: 12/07/2010
• Est. Priority Date: 12/20/2005
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Tran, Duong-Han
• Primary Examiner(s): CHAVIS, JOHN Q
• Application Number:
  US11/314,887
• Publication Number:
  US 20070143301A1
• Time in Patent Office: 1,813 Days
• Field of Search: 717/124
• US Class Current: 717/124
• CPC Class Codes: G06F 11/362 Software debugging
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application

Abstract

Methods and systems for a remote user interface and remote debugging in a computer system comprising an application server and at least two client systems are provided. A first client operated by a user wishing to debug a remote application running between a second client and the application server registers at the application server. The application server invokes a user interface at the first client from the application system, based on information provided at registration. Using the present invention, in an SAP environment, developers can use the user interface for interactive actions and also debug running of an application, whether on an SAP or non-SAP system, from a remote location.

Claims

1. A method for remote debugging in a computer system comprising an application server and at least two client systems, the method comprising:

registering a first client at an application server;

running, from a second client, an application at the application server, wherein running the application comprises at least one transaction between the application server and the second client; and

invoking a user interface at the first client from the application server, the user interface monitoring the at least one transaction between the application server and the second client.

2. The method of claim 1, wherein the user interface monitors the at least one transaction by collecting information relating to the at least one transaction between the application server and the second client that may be used for debugging.

3. The method of claim 1, wherein registering a first client at an application server comprises passing to the application server from the first client information relating to one or more of a program ID, a server ID, a host name, and a service.

4. The method of claim 1, wherein registering a first client at an application server comprises:

registering a first client at an application server in secure mode by passing to the application server from the first client a server ID.

5. The method of claim 4, further comprising:

authenticating the first client based on the server ID.

6. The method of claim 1, wherein the user interface monitors the at least one transaction between the application server and the second client without influencing the program flow of the application.

7. A method for performing debugging in a computer system comprising an application server and at least two client systems, the method performed at a first client comprising:

registering at the application server;

receiving a request from the application server based on the information provided at registration;

invoking a user interface based on the request;

monitoring via the user interface at least one transaction between the application server and a second client.

8. The method of claim 7, wherein the user interface monitors the at least one transaction by collecting information relating to the at least one transaction between the application server and the second client that may be used for debugging.

9. The method of claim 7, wherein registering at the application server comprises passing to the application server information relating to one or more of a program ID, a server ID, a host name, and a service.

10. The method of claim 7, wherein registering at the application server comprises:

registering at an application server in secure mode by passing to the application server a server ID associated with the first client.

11. The method of claim 10, further comprising:

authenticating the first client at the application server based on the server ID.

12. A system comprising:

an application system that includes one or more application servers configured to provide an executable application;

an external system configured to run an application that comprises at least one transaction between the application system and the external system;

a client configured to register at an application system and invoke a user interface based on a request from the application system, the user interface monitoring the at least one transaction between the application server and the second client.

13. The method of claim 12, wherein the user interface monitors the at least one transaction by collecting information relating to the at least one transaction between the application server and the second client that may be used for debugging.

14. The system of claim 12, wherein the client is further configured to register at the application system by passing to the application system information relating to one or more of a program ID, a server ID, a host name, and a service.

15. The system of claim 12, wherein the client is further configured to register in secure mode by passing a server ID to the application system.

16. The system of claim 15, wherein the application system is further configured to authenticate the client based on the server ID.

17. The system of claim 12, wherein the user interface monitors the at least one transaction between the application system and the client without influencing the program flow of the application.