Common gateway which allows JAVA applets to make program calls to OLTP applications executing on an enterprise server reference to co-pending applications

• US 6,397,220 B1
• Filed: 10/01/1998
• Issued: 05/28/2002
• Est. Priority Date: 10/01/1998
• Status: Expired due to Term

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Unisys Corporation
• Inventors: Freed, Jeremy A., Deisinger, Mark V.
• Primary Examiner(s): Alam, Hosain T.
• Application Number:
  US09/164,759
• Time in Patent Office: 1,335 Days
• Field of Search: 707/1-4,513,10,100-103 709/217-219,203
• US Class Current: 707/607
• 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: 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/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: Y10S 707/99932 Access augmentation or optimizing
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure

Abstract

Method and apparatus for an application program running on a Web browser to make service requests to a service routine running on an On-Line Transaction Processing (OLTP) system. When the application program requests a service on the OLTP system, the input data format required for the requested service is passed to the application program. The application program submits a service request to the service routine in the input data format, and receives a result of the service routine processing the service request in the output data format. The input and output data formats allow the application program to complete additional processing of the result in the output data format and make subsequent service requests to the OLTP system.

Claims

1. In a data processing system wherein a browser is coupled to a server and the server is coupled to a transaction processing system, the transaction processing system including one or more databases wherein each one of a number of service routines resident on the transaction processing system performs one or more operations on data stored in the one or more databases, the improvement comprising:

a. an interface coupled to the server wherein the browser initiates a selected one of the number of service routines through said interface, said interface providing a result of the transaction processing system executing said selected one of the number of service routines to the browser in a format which allows the browser to perform a number of operations on said result.

2. A data processing system wherein a user interfaces with a browser which is coupled to a server, the server being coupled to a transaction processing system, the transaction processing system including one or more databases wherein each one of a number of service routines resident on the transaction processing system performs one or more operations on data stored in the one or more databases, comprising:

a. an application program executable on the browser; and

b. an interface coupled to the server wherein said application program initiates a selected one of the number of service routines through said interface, said interface providing a result of the transaction processing system executing said selected one of the number of service routines to said application program in a format which allows said application program to perform a number of operations on said result.

3. A data processing system according to claim 2 wherein said application program initiates a selected one of the number of service routines through said interface by sending a one of a number of input view requests to the server, said interface receiving said one of said number of input view requests only if said one of said number of input view requests is a predetermined type, said interface sending a corresponding one of a number of input view definitions to said application program in response to said one of said number of input view requests, said corresponding one of said number of input view definitions defining an input data format required for said corresponding one of said number of service routines.

4. A data processing system according to claim 3 wherein said application program builds an input screen on the browser using said input view definition, said input view definition defining said input data format by defining a number of input fields, each one of said number of input fields accepting one or more input data entries from the user to be provided in said input data format by said application program to said corresponding one of said number of service routines.

5. A data processing system according to claim 3 further comprising a server extension coupled to said interface, said server extension determining if said one of said number of input view requests is said predetermined type by comparing a portion of said one of said number of input view requests to a known portion, said known portion corresponding to said predetermined type, said server extension sending said one of said number of input view requests to said interface if said portion of said one of said number of input view requests is equal to said known portion.

6. A data processing system according to claim 5 wherein said one of the number of input view requests comprises an address path, a portion of said address path being said portion of said one of said number of input view requests.

7. A data processing system according to claim 6 wherein said portion of said address path is a path prefix.

8. A data processing system according to claim 6 wherein the server extension is a WebTx server extension.

9. A data processing system according to claim 5 wherein said interface is a JGate interface, said server extension sending said one of said number of input view requests to said JGate interface when said predetermined type is a JGate view type.

10. A data processing system according to claim 5 wherein the data processing system wherein said application program is written in the Java programming language.

11. A data processing system according to claim 10 wherein said application program written in said Java programming language is a Java applet.

12. A data processing system according to claim 3 wherein the application program is downloaded from the browser to the server.

13. A data processing system according to claim 2 wherein said application program executes a selected one of the number of service routines resident on the transaction processing system through said interface by sending a one of a number of service requests to the server, said one of said number of service requests having one or more input data entries in an input data format wherein said input data format is required for said selected one of said number of service routines, said interface sending said one of said number of service requests having said input format to said selected one of said number of service routines only if said one of said number of service requests is a predetermined type so that said selected one of said number of service routines can perform the one or more operations using the input data on the data stored in the one or more databases.

14. A data processing system according to claim 13 wherein the server further comprises a server extension coupled to said interface, said server extension determining if said one of said number of service requests is said predetermined type by comparing a portion of said one of said number of service requests to a known portion, said server extension sending said one of said number of service requests to said interface if said portion of said one of said number of service requests is equal to said known portion.

15. A data processing system according to claim 13 wherein said interface receives a result of the transaction processing system executing said selected one of the number of service routines in an output data format which corresponds to said corresponding one of said number of service routines, said interface providing said result to said application program so that said application program can perform a number of operations on said result.

16. A data processing system according to claim 15 wherein the user provides one or more input data entries in said input data format to said application program, said application program using said one or more input data entries to perform said number of operations on said result.

17. A data processing system according to claim 16 wherein said application program sends another one of said number of service requests to the server, said another one of said number of service requests having said one or more input data entries in said input data format, said input data format corresponding to said corresponding one of said number of service routines, said interface receiving said one of said number of service requests only if said one of said number of service requests is the same type as said interface.

18. A data processing system according to claim 17 wherein said application program receives a corresponding one of a number of output view definitions from said selected one of said number of service routines, said corresponding one of said number of output view definitions defining an output data format required for said application program to receive said result.

19. A data processing system according to claim 18 wherein said application program builds an output screen on the browser using said output view definition, said output view definition defining said output data format by defining a number of output fields, each one of said number of output fields accepting one or more data items and displaying said one or more output items in said output screen, said result being comprised of said one or more data items.

20. A data processing system according to claim 18 wherein said application program sends another one of said number of service requests to the server, said another one of said number of service requests having said one or more input data entries in said input data format, said input data format corresponding to said selected one of said number of service routines, said interface receiving said one of said number of service requests only if said one of said number of service requests is said predetermined type.

21. A data processing system according to claim 20 wherein each one of said number of service requests comprises an address path, a portion of said address path being said portion of said one of said number of service requests.

22. A data processing system according to claim 21 wherein said portion of said address path is a path prefix.

23. A data processing system according to claim 22 wherein the server extension is a WebTx server extension.

24. A data processing system according to claim 20 wherein said interface is a JGate interface, said server extension sending said one of said number of input view requests to said JGate interface when said predetermined type is a JGate view type.

25. A data processing system according to claim 20 wherein the data processing system wherein said application program is written in the Java programming language.

26. A data processing system according to claim 25 wherein said one of said number of application programs written in said Java programming language is a Java applet.

27. A data processing system according to claim 12 wherein the application program is downloaded from the browser to the server.

28. A data processing system wherein a browser is coupled to a server and the server is coupled to a transaction processing system, a number of application programs which are executable on the browser, the transaction processing system including one or more databases wherein each one of a number of service routines resident on the transaction processing system performs one or more operations on data stored in the one or more databases, comprising:

a. a number of interfaces coupled to the server wherein a one of the number of application programs initiates a selected one of the number of service routines through a one of said number of interfaces, said one of said number of interfaces providing a result of the transaction processing system executing said selected one of the number of service routines to said one of the number of application programs in a format which allows said one of the number of application programs to perform a number of operations on said result.

29. A data processing system according to claim 28 wherein said one of the number of application programs initiates a selected one of the number of service routines through said one of said number of interfaces by sending a one of a number of input view requests to the server, said one of said number of interfaces receiving said one of said number of input view requests only if said one of said number of input view requests is the same type as said one of said number of interfaces, said one of said number of interfaces sending a corresponding one of a number of input view definitions to said one of the number of application programs in response to said one of said number of input view requests, said corresponding one of said number of input view definitions defining an input data format required for said corresponding one of said number of service routines.

30. A data processing system according to claim 29 wherein the server further comprises a server extension coupled to said number of interfaces, said server extension determining if said one of said number of input view requests is the same type as said one of said number of interfaces by comparing a portion of said one of said number of input view requests to each one of a number of known portions, each said one of said number of known portions corresponding to a unique one of said number of interfaces, said one of said number of input view requests being the same type as said one of said number of interfaces if said portion of said one of said number of input view requests is equal to said one of said number of known portions corresponding to said one of said number of interfaces.

31. A data processing system according to claim 28 wherein said one of the number of application programs executes a selected one of the number of service routines through said one of said number of interfaces by sending a one of a number of service requests to the server, said one of said number of interfaces receiving said one of said number of service requests only if said one of said number of service requests is the same type as said one of said number of interfaces.

32. A data processing system according to claim 31 wherein the server further comprises a server extension coupled to said number of interfaces, said server extension determining if said one of said number of service requests is the same type as said one of said number of interfaces by comparing a portion of said one of said number of service requests to each one of a number of known portions, each said one of said number of known portions corresponding to a unique one of said number of interfaces, said one of said number of service requests being the same type as said one of said number of interfaces if said portion of said one of said number of service requests is equal to said one of said number of known portions corresponding to said one of said number of interfaces.

33. A data processing system wherein a browser is coupled to a server and the server is coupled to a transaction processing system, a number of application programs which are executable on the browser, the transaction processing system including one or more databases wherein each one of a number of service routines resident on the transaction processing system performs one or more operations on data stored in the one or more databases, comprising:

a. initiation means coupled to the server, a one of the number of application programs initiating a selected one of the number of service routines by sending a one of a number of input view requests to the server, said initiation means receiving said one of said number of input view requests only if said one of said number of input view requests is the same type as said initiation means, said initiation means sending a corresponding one of a number of input view definitions to said one of the number of application programs in response to said one of said number of input view requests, said corresponding one of said number of input view definitions defining an input data format required for said corresponding one of said number of service routines;

b. execution means coupled to the server, said one of the number of application programs executing a selected one of the number of service routines through said execution means by sending a one of a number of service requests to the server, said one of said number of service requests having said input data format for said corresponding one of said number of service routines, said execution means receiving said one of said number of service requests only if said one of said number of service requests is the same type as said execution means, said execution means providing a result of the transaction processing system executing said selected one of the number of service routines to said one of the number of application programs in an output data format which allows said one of the number of application programs to perform a number of operations on said result; and

c. selection means coupled to the server, said selection means determining if said one of said number of input view requests is the same type as said initiation means by comparing a portion of said one of said number of input view requests to each one of a number of known portions, said one of said number of input view requests being the same type as said initiation means if said portion of said one of said number of input view requests is equal to said one of said number of known portions corresponding to said initiation means, said selection means determining if said one of said number of service requests is the same type as said execution means by comparing a portion of said one of said number of service requests to each one of a number of known portions, said one of said number of service requests being the same type as said execution means if said portion of said one of said number of service requests is equal to said one of said number of known portions corresponding to said execution means.

34. A method for completing one or more transactions on a transaction processing system from an application program resident on a browser wherein the browser and an interface are coupled to a server and the server is coupled to the transaction processing system, each one of a number of service routines resident on the transaction processing system performing the one or more transactions, the method comprising the steps of:

a. initiating a selected one of the number of service routines through the interface from the application program; and

b. providing a result of the transaction processing system executing the selected one of the number of service routines from the transaction processing system through the interface to the application program in a format which allows the application program to perform a number of operations on said result.

35. A method for initiating one or more operations on data stored in a transaction processing system wherein a user interfaces with a browser which is coupled to a server, an interface being coupled to the server and the server being coupled to the transaction processing system, an application program which is executable on the browser, the transaction processing system including one or more databases wherein each one of a number of service routines resident on the transaction processing system performs one or more operations on data stored in the one or more databases, the method comprising the steps of:

a. initiating a selected one of the number of service routines from the application program by sending a one of a number of input view requests to the server, the interface receiving said one of said number of input view requests only if said one of said number of input view requests is the same type as the interface;

b. sending a corresponding one of a number of input view definitions to the application program from said server in response to said one of said number of input view requests, said corresponding one of said number of input view definitions defining an input data format required for said corresponding one of said number of service routines; and

c. building an input screen on the browser using said input view definition, said input view definition defining said input data format by defining a number of input fields, each one of said number of input fields accepting one or more input data entries from the user to be provided in said input data format by the application program to said corresponding one of said number of service routines.

36. A method according to claim 35 wherein step (b) further comprises the step of determining if said one of said number of input view requests is the same type as the interface by comparing a portion of said one of said number of input view requests to each one of a number of known portions, said one of said number of input view requests being the same type as the interface if said portion of said one of said number of input view requests is equal to said one of said number of known portions corresponding to the interface.

37. A method according to claim 36 wherein the interface is a JGate interface.

38. A method according to claim 35 wherein step (b) further comprises the step of downloading the application program from the browser to the server.

39. A method for initiating one or more operations on data stored in a transaction processing system wherein a user interfaces with a browser which is coupled to a server, an interface being coupled to the server and the server being coupled to the transaction processing system, an application program which is executable on the browser, the transaction processing system including one or more databases wherein each one of a number of service routines resident on the transaction processing system performs one or more operations on data stored in the one or more databases, the method comprising the steps of:

a. sending a one of a number of service requests from the application program to the server, said one of said number of service requests having one or more input data entries in an input data format wherein said input data format is required for said corresponding one of said number of service routines, the interface receiving said one of said number of service requests only if said one of said number of service requests is the same type as the interface;

b. sending said one of said number of service requests to said selected one of the number of service routines if the interface received said one of said number of service requests;

c. executing said selected one of the number of service routines;

d. providing a result of the transaction processing system executing said selected one of the number of service routines to the interface in an output data format which corresponds to said corresponding one of said number of service routines; and

e. providing said result to the application program from the interface, the application program performing a number of operations on said result in said output data format.

40. A method according to claim 39 wherein step (e) further includes the user providing one or more input data entries in said input data format to the application program, the application program using said one or more input data entries to perform said number of operations on said result.

41. A method according to claim 39 wherein step (e) further includes the application program sending another one of said number of service requests to the server, said another one of said number of service requests having said one or more input data entries in said input data format, said input data format corresponding to said corresponding one of said number of service routines, the interface receiving said one of said number of service requests only if said one of said number of service requests is the same type as the interface.

42. A method according to claim 39 wherein step (e) further comprises the steps of:

a. sending a corresponding one of a number of output view definitions to the application program from said corresponding one of said number of service routines, said corresponding one of said number of output view definitions defining an output data format required for the application program to receive said result; and

b. building an output screen on the browser using said output view definition, said output view definition defining said output data format by defining a number of output fields, each one of said number of output fields accepting one or more data items and displaying said one or more data items in said output screen, said result being comprised of said one or more data items.

43. A method according to claim 39 wherein step (e) further comprises the steps of:

a. sending a corresponding one of a number of input view definitions to the application program from said server, said corresponding one of said number of input view definitions defining said input data format required for said corresponding one of said number of service routines; and

b. building an input screen on the browser using said input view definition, said input view definition defining said input data format by defining a number of input fields, each one of said number of input fields accepting one or more input data entries from the user to be provided in said input data format to the application program, the application program using said one or more input data entries to perform said number of operations on said result.

44. A method according to claim 39 wherein step (b) further comprises the step of determining if said one of said number of service requests is the same type as the interface by comparing a portion of said one of said number of service requests to each one of a number of known portions, said one of said number of service requests being the same type as the interface if said portion of said one of said number of service requests is equal to said one of said number of known portions corresponding to the interface.

45. A method according to claim 39 wherein step (b) further comprises the step of downloading the application program from the server to the browser.

46. A method according to claim 44 wherein the interface is a JGate interface.