Server and web browser terminal emulator for persistent connection to a legacy host system and method of operation

• US 6,233,541 B1
• Filed: 04/29/1998
• Issued: 05/15/2001
• Est. Priority Date: 04/01/1996
• Status: Expired due to Term

• Current Assignee: OpenConnect Systems Incorporated (Rocket Software Incorporated)
• Original Assignee: OpenConnect Systems Incorporated (Rocket Software Incorporated)
• Inventors: Clark, Stephen J., Armstrong, Eric P., Kuhn, Daniel B., Toye, Gene E., Sharif, Mohammad K., Ratliff, Stanley M., Butts, Thomas H., Burris, Stuart H. Jr.
• Primary Examiner(s): Stamber, Eric W.
• Assistant Examiner(s): FREJD, RUSSELL WARREN
• Application Number:
  US09/069,522
• Time in Patent Office: 1,112 Days
• Field of Search: 703/27, 703/26, 703/23, 709/246, 709/218, 709/206, 709/203, 709/227, 709/228, 709/313, 705/9, 707/1, 370/466, 370/469, 710/105
• US Class Current: 703/27
• CPC Class Codes: G06F 13/107 Terminal emulation
• CPC Class Codes: G06F 16/972 Access to data in other repository systems, e.g. legacy data or dynamic Web page generation
• CPC Class Codes: G06F 9/54 Interprogram communication
• CPC Class Codes: H04L 67/08 specially adapted for terminal emulation, e.g. Telnet
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/75 Indicating network or usage conditions on the user display
• CPC Class Codes: H04L 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• CPC Class Codes: H04L 69/162 involving adaptations of sockets based mechanisms secure socket layer H04L63/168
• CPC Class Codes: H04L 69/169 Special adaptations of TCP, UDP or IP for interworking of IP based networks with other networks protocols for interworking, protocol conversion H04L69/08
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A computer network environment (10) allowing connection of a client system (36) to a legacy host system (18,19) using a server (26) is provided. The computer network environment (10) includes a legacy host system (18,19) having TCP/IP connectivity. The legacy host system (18,19) is operable to support a terminal session for access to the legacy host system (18,19). The computer network environment (10) also includes a server system (24) executing a client thread (28) under a server (26). The client thread (28) is operable to communicate with the legacy host system (18,19) across a persistent TCP/IP socket connection (30). The computer network environment (10) further includes a client system (36) executing an applet process (42) under a web browser (38). The applet process (42) is operable to communicate with the client thread (28) across another persistent TCP/IP socket connection (44) and is operable to provide a terminal session to a user of the client system (36). This terminal session is supported by a persistent connection allowing real-time bidirectional communication with the legacy host system (18,19).

Claims

1. A server for providing a persistent connection between a client system and a host system for terminal emulation, comprising:

a client thread operable to communicate with a host system across a first persistent connection; and

applet code operable to create an applet process executing under a web browser on a client system, the server operable to download the applet code to the client system in response to receiving a uniform resource locator associated with the host system, and, when executed by the client system, the applet process operable to communicate with the client thread across a second persistent connection and to provide a terminal session to a user of the client system, such that the terminal session is supported by a persistent connection allowing communication with the host system.

2. The server of claim 1, wherein the server comprises a process executed by a separate server system.

3. The server of claim 2, wherein the client thread and the applet process are operable to communicate using a data flow based upon a specified communication protocol.

4. The server of claim 3, wherein the client thread is further operable to interface between a data flow used by the host system and the data flow used by the applet process.

5. The server of claim 1, wherein the applet code comprises executable code for a JAVA applet to be executed under a JAVA-capable web browser.

6. The server of claim 2, wherein the first and second persistent connections are persistent TCP/IP socket connections.

7. The server of claim 4, wherein the client thread is operable to communicate using a TN3270 data flow and the applet process is operable to provide a 3270 type terminal session.

8. The server of claim 4, wherein the client thread is operable to communicate using a TN5250 data flow and the applet process is operable to provide a 5250 type terminal session.

9. The server of claim 4, wherein the client thread is operable to communicate using an NVT data flow and the applet process is operable to provide an NVT type terminal session.

10. The server of claim 4, wherein the client thread is operable to communicate using a VT220 data flow and the applet process is operable to provide a VT220 type terminal session.

11. A web browser terminal emulator, comprising:

an applet process executing under the web browser, the applet process executed in response to selection of a uniform resource locator associated with a host system, the applet process operable to communicate with the host system across a persistent connection and to provide a terminal session to a user of the client system, such that the terminal session is supported by the persistent connection allowing communication with the host system.

12. The web browser terminal emulator of claim 11, wherein the applet process is created by applet code downloaded to the client system from a server in response to selection of the uniform resource locator associated with the host system.

13. The web browser terminal emulator of claim 12, wherein the applet process is operable to communicate using a data flow based upon a specified communication protocol.

14. The web browser terminal emulator of claim 13, further comprising a client thread operable to interface between a data flow used by the host system and the data flow used by the applet process.

15. The web browser terminal emulator of claim 11, wherein the applet process comprises a JAVA applet executing under a JAVA-capable web browser.

16. The web browser terminal emulator of claim 11, wherein the persistent connection is a persistent TCP/IP socket connection.

17. The web browser terminal emulator of claim 11, wherein the applet process is operable to provide a 3270 type terminal session.

18. The web browser terminal emulator of claim 11, wherein the applet process is operable to provide a 5250 type terminal session.

19. The web browser terminal emulator of claim 11, wherein the applet process is operable to provide an NVT type terminal session.

20. The web browser terminal emulator of claim 11, wherein the applet process is operable to provide a VT220 type terminal session.

21. A computer network environment allowing connection of a client system to a host system for terminal emulation, the computer network environment comprising:

a host system operable to support a terminal session for access to the host system; and

a client system executing an applet process under a web browser in response to selection of a uniform resource locator associated with the host system, the applet process operable to communicate with the host system across a persistent connection and to provide a terminal session to a user of the client system, such that the terminal session is supported by the persistent connection allowing communication with the host system.

22. The computer network environment of claim 21, further comprising a server system executing a client thread under a server, the client thread operable to communicate with the host system and the applet process.

23. The computer network environment of claim 22, wherein the applet process is operable to communicate using a data flow based upon a specified communication protocol.

24. The computer network environment of claim 23, wherein the client thread is operable to interface between a data flow used by the system and the data flow used by the applet process.

25. The computer network environment of claim 21, wherein the host system comprises a mainframe computer system.

26. The computer network environment of claim 21, wherein the host system comprises a mid-range computer system.

27. The computer network environment of claim 21, wherein the host system comprises a computer workstation executing a UNIX environment.

28. The computer network environment of claim 21, wherein the applet process comprises a JAVA applet executing under a JAVA-capable web browser.

29. The computer network environment of claim 21, wherein the persistent connection is a persistent TCP/IP socket connection.

30. The computer network environment of claim 21, wherein the applet process is operable to provide a 3270 type terminal session.

31. The computer network environment of claim 21, wherein the applet process is operable to provide a 5250 type terminal session.

32. The computer network environment of claim 21, wherein the applet process is operable to provide an NVT type terminal session.

33. The computer network environment of claim 21, wherein the applet process is operable to provide a VT220 type terminal session.

34. A method for connecting a client system to a host system for terminal emulation, comprising:

executing an applet process under a web browser on the client system in response to selection of a uniform resource locator associated with a host system;

connecting the applet process to the host system across a persistent connection;

communicating between the applet process and the host system across the persistent connection; and

providing a terminal session to a user of the client system by the applet process, such that the terminal session is supported by the persistent connection allowing communication with the host system.

35. The method of claim 34, further comprising downloading executable code for the applet process to the client system in response to the selection of a uniform resource locator associated with the host system.

36. The method of claim 34, wherein connecting the applet process to the host system is accomplished using a client thread executing under a server.

37. The method of claim 36, wherein communicating between the client thread and the applet process is accomplished using a data flow based upon a specified communication protocol.

38. The method of claim 34, wherein executing the applet process comprises executing a JAVA applet under a JAVA-capable web browser.

39. The method of claim 34, wherein providing a terminal session comprises providing a 3270 type terminal session.

40. The method of claim 34, wherein providing a terminal session comprises providing a 5250 type terminal session.

41. The method of claim 34, wherein providing a terminal session comprises providing an NVT type terminal session.

42. The method of claim 34, wherein providing a terminal session comprises providing a VT220 type terminal session.

43. A method for load-balancing across multiple servers for providing a persistent connection between a client system and a host system for terminal emulation, comprising:

receiving a uniform resource locator from a client system;

interpreting the uniform resource locator to identify a selected host system;

selecting a server from a plurality of servers to manage a connection with the client system;

providing redirect information to the client system, the redirect information identifying the selected server;

downloading executable code for an applet process to the client system from the selected server;

executing the applet process under a web browser on the client system;

connecting the applet process to the selected host system across a persistent connection supported by the selected server;

communicating between the applet process and the host system across the persistent connection; and

providing a terminal session to a user of the client system by the applet process, such that the terminal session is supported by the persistent connection allowing communication with the host system.

44. The method of claim 43, wherein selecting a server is based upon a current load of each of the plurality of servers.

45. A computer-implemented terminal session emulator for providing browser-based client system access to a host application running on a host system, comprising:

applet code operable to create an applet process executing on the client system, said applet code being downloadable from a web server in response to receipt of a uniform resource locator associated with the host; and

an emulation server operable to negotiate a persistent connection between the host system and the client system, and further operable to perform data conversions that modify a data stream associated with the host application between a client data format associated with the applet process and a host data format associated with the host application.

46. The emulator of claim 45, wherein the client data format and the host data format are different communication protocols.

47. The emulator of claim 45, wherein the client data format and the host data format are encrypted and decrypted data formats.

48. The emulator of claim 45, wherein the client data format and the host data format are compressed and decompressed data formats.

49. The emulator of claim 45, wherein said emulation server is implemented at the host system.

50. The emulator of claim 45, wherein said emulation server is implemented at the web server.

51. The emulator of claim 45, where said emulation server communicates with said host system via a TN interface associated with said host system.

52. The emulator of claim 45, wherein the applet code comprises executable code for a JAVA applet to be executed under a JAVA-capable web browser.

53. The emulator of claim 45, wherein the persistent connection is a persistent TCP/IP connection.

54. The emulator of claim 45, wherein said data format modifies a 3270 data stream.

55. The emulator of claim 45, wherein said data format modifies a 5250 data stream.