Middleware for business transactions

• US 7,003,482 B1
• Filed: 12/10/1999
• Issued: 02/21/2006
• Est. Priority Date: 12/10/1999
• Status: Expired due to Term

• Current Assignee: Computer Sciences Corporation (DXC Technology Company)
• Original Assignee: Computer Sciences Corporation (DXC Technology Company)
• Inventors: Quintana, Erica, Margoscin, Edward, Williamson, Gerald A., Zarley, Debra K.
• Primary Examiner(s): PATEL, JAGDISH
• Application Number:
  US09/459,260
• Time in Patent Office: 2,265 Days
• Field of Search: 705/35, 709/218, 709/219, 709/250, 717/127, 717/136, 717/137, 718/19
• US Class Current: 705/35
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes

Abstract

A middleware program provides an interface between an input channel and a business transaction server. The middleware program receives data and commands from an interface program that is coupled to an input channel. The middleware program validates the data, orders the data, transforms the data into a form required by the server, sends the data to the server, and the middleware program receives the results of the business transaction from the server. The middleware program transforms the results into a form required by the interface program and sends the results to the interface program. The interface program displays the results. The middleware program may reduce the time required to create an interface to a channel. The middleware program moves business logic out of the server or legacy program and into a middle layer that may be easily integrated with many different types of visual or non-visual user interfaces. The architecture of the middleware program allows the middleware program to be easily used with a variety of different types of channels.

Claims

1. A system comprising:

a server configured to process business transactions;

a domain manager;

a middleware program communicatively coupled to the server, wherein the middleware program comprises a domain file, the domain file comprising a plurality of serialized files generated by the domain manager from a domain source file, the domain source file comprising source definitions for a plurality of domains required by the system to process the business transaction, wherein each of the plurality of serialized files comprises a list of allowable values of a domain associated with one or more business transactions;

a channel communicatively coupled to the middleware program and to the server; and

an interface program communicatively coupled to the channel and to the middleware program, wherein the interface program is configured to receive data from the channel and to receive a command that will initiate a business transaction and transmit the command to the middleware program;

wherein the interface program receives the data from the channel and transmits the data to the middleware program;

wherein the middleware program determines whether portions of the received data include allowable values based on one of plurality of serialized files, and wherein the middleware program transforms the data into a form required by the server and transmits the transformed data to the server, wherein the server performs the business transaction after the command to initiate the business transaction has been transmitted to the middleware program and the transformed data is transmitted to the server.

2. The system of claim 1, wherein the middleware program receives a result from the business transaction server and transfers the result to the interface program.

3. The system of claim 1, wherein the channel comprises a kiosk.

4. The system of claim 1, wherein the channel comprises a computer terminal.

5. The system of claim 1, wherein the channel comprises a telephone call center.

6. The system of claim 1, wherein the channel comprises an electronic data transfer system.

7. The system of claim 1, wherein a local area network communicatively couples the channel to the server.

8. The system of claim 1, wherein a wide area network communicatively couples the channel to the server.

9. The system of claim 1, wherein portions of the domain file may be changed without changing code of the middleware program.

10. The system of claim 1, wherein the middleware program generates an error code if the portions of the received data include values that are not allowable values.

11. The system of claim 1, wherein the middleware program transfers data to a plurality of business transaction servers during the processing of a business transaction.

12. The system of claim 1, wherein the middleware program comprises computer code written in an object-oriented programming language.

13. The system of claim 1, wherein the middleware program is extendable without altering source code of the middleware program.

14. The system of claim 13, wherein an extension to the middleware program comprises computer code that is stored in a package and run when the middleware program runs.

15. The system of claim 1, wherein the middleware program overrides an order of data of an object model with an order of data required by the business transaction server before transferring the data to the business transaction server.

16. A carrier medium that stores program instructions, wherein the program instructions are computer-executable to implement a method comprising:

receiving data from one interface program of a plurality of interface programs, wherein each interface program is communicatively coupled to one of a plurality of channels, wherein the data is received by the interface program from the channel to which it is coupled;

determining whether a portion of received data includes values in a list of allowable values in a serialized file using the middleware program, wherein the serialized file is one of a plurality of serialized files in a domain file generated by a domain manager from a domain source file, the domain source file comprising source definitions for a plurality of domains required by a system to process a business transaction, wherein each of the plurality of serialized files comprises a list of allowable values of a domain associated with one or more business transactions;

if the portion of received data does not include values in a list of allowable values, notifying the user interface and receiving corrected data;

if the portion of received data includes values in a list of allowable values, transforming the data into a form required by the business transaction server using the middleware program and transferring the transformed data to a business transaction server;

wherein the program instructions comprise a plurality of objects, wherein at least one of the plurality of objects is used in determining whether the portion of received data includes values in a list of allowable values.

17. The carrier medium of claim 16, wherein the channel comprises a kiosk.

18. The carrier medium of claim 16, wherein the channel comprises a computer terminal.

19. The carrier medium of claim 16, wherein the channel comprises a telephone call center.

20. The carrier medium of claim 16, wherein the channel comprises an electronic data transfer system.

21. The carrier medium of claim 16, wherein a local area network communicatively couples the channel to the server.

22. The carrier medium of claim 16, wherein a wide area network communicatively couples the channel to the server.

23. The carrier medium of claim 16, further comprising a separate set of computer instructions that extend the functionality of the set of computer instructions.

24. The carrier medium of claim 16, wherein the program instructions are further computer-executable to implement:

receiving a result from the business transaction server;

inflating the result; and

transferring the result to the interface program.

25. The carrier medium of claim 16, wherein the middleware program overrides an order of data of an object model with an order of data required by the business transaction server before transferring the data to the business transaction server.

26. A method of performing a business transaction on a computer system using a user interface program, a middleware program, and a business transaction server, the method comprising:

entering data into a channel that communicatively couples to the user interface;

transferring the data to the middleware program;

providing a domain file, the domain file comprising a plurality of serialized files generated by a domain manager from a domain source file, the domain source file comprising source definitions for a plurality of domains required by the computer system to perform the business transaction, wherein each of the plurality of serialized files comprises a list of allowable values of a domain associated with one or more business transactions;

determining whether a portion of the data includes values in a list of allowable values in one of the serialized files using the middleware program,

if the portion of the data does not include values in a list of allowable values, notifying the user interface and receiving corrected data;

if the portion of the data includes values in a list of allowable values;

transforming the data into a form required by the business transaction server using the middleware program;

transferring the transformed data to the business transaction server using the middleware program; and

processing the transformed data using the business transaction server.

27. The method of claim 26, further comprising transferring results from the business transaction server to the middleware program, and transferring results from the middleware program to the user interface.

28. The method of claim 27, wherein the middleware program transforms the results into a form recognizable to the user interface program before transmitting the results to the user interface.

29. The method of claim 26, further comprising generating an error code if an entered data value is not included in the list of allowable values.

30. The method of claim 26, wherein the middleware program determines if all required data to process the business transaction is present before transferring the data to the business transaction server, and wherein the middleware program generates an error code if all the required data is not present before the data is transferred to the business transaction server.

31. The method of claim 26, wherein the middleware program orders the data into an order required by the business transaction server before transferring the data to the business transaction server.

32. The method of claim 26, wherein the middleware program transfers data to and receives results from a plurality of business transaction servers during processing of the business transaction.

33. The method of claim 26, wherein the business transaction server comprises a legacy program.

34. The method of claim 26, further comprising determining if the received data comprises data required to perform the initiated business transaction.

35. The method of claim 26, further comprising placing the received data in order prior to transferring the data to the server.

36. The method of claim 26, wherein the middleware program overrides an order of data of an object model with an order of data required by the business transaction server before transferring the data to the business transaction server.