System and method for interfacing with a legacy computer system

• US 20040054812A1
• Filed: 09/13/2002
• Published: 03/18/2004
• Est. Priority Date: 09/13/2002
• Status: Abandoned Application

• Current Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Hodaie, Payman, Liang, Jiasen
• Application Number:
  US10/242,734
• Publication Number:
  US 20040054812A1
• Time in Patent Office: Days
• US Class Current: 709/250
• CPC Class Codes: G06Q 10/087 Inventory or stock management, e.g. order filling, procurement or balancing against orders

Abstract

A novel system and method for interfacing with legacy systems is provided. An enterprise server or host server hosts a front-end interface to a user. The front-end interface is operable to obtain information from the user that is otherwise required to operate the legacy systems. After collecting the information from the user, the enterprise server can then interface with one or more legacy systems, thereby accessing the functionality of the legacy system(s) thereby obviating the need to replace the legacy system with an updated system customized to the enterprise server. A method for recovering a system that interfaces with a legacy system is also provided.

Claims

1. A system for interfacing with at least one legacy system, comprising:

at least one host server for connection to a client, said host server for executing a software interface for receiving a client request and delivering responses to said client;

said at least one host server additionally for executing a legacy software application having a predefined set of user inputs and for performing a first task based on said inputs, said software interface being customized to provide at least a portion of said inputs to said legacy software application based on information derived from said client request; and

,

said at least one host server additionally for executing an additional software application for performing a second task based on information derived from said client request and in cooperation with the performance of said first task,

said at least one host server additionally keeping a action record respective to said client request, said action log for reconciling the performance of said tasks upon an initialization of said at least one host server if said tasks are interrupted prior to a desired completion of said tasks.

2. The system according to claim 1 wherein said host server is a vendor server, said legacy software application is a legacy on-line payment software application and said first task is the processing of an on-line payment.

3. The system according to claim 2 wherein said additional software application is a delivery system and said second task is a delivery of a requested product to a customer using said client and said cooperation is an operation based on determining whether said on-line payment can be successfully processed prior to managing said delivery.

4. The system according to claim 3 wherein said delivery is preformed by an on-line download of software to said client.

5. The system according to claim 3 wherein when said system is reinitialized and said action log indicates that said payment has been processed but said product has not been delivered, then said legacy software application is instructed to reverse said on-line payment.

6. The system according to claim 3 wherein when said system is reinitialized and said action log indicates that said payment has been pre-approved but said product has not been delivered, then said second software application is instructed to commence said delivery.

7. The system according to claim 1 wherein said additional software application is a second legacy software application having a predefined second set of user inputs and for performing said second task based on information derived at least in part from said second set inputs and in cooperation with said first task.

8. The system according to claim 1 wherein said legacy software application is a user authentication system.

9. The system according to claim 1 wherein said at least one host server includes a first server, a second server and a third server interconnected by a local area network, and wherein said software interface, said legacy software application and said additional software application are executed on each of said servers respectively.

10. A method of interfacing with a legacy software application comprising the steps of:

receiving a user request;

opening a action record specific to said user request, said action record containing information for recovering a performance of said user request upon an interruption thereof;

commencing a legacy action based on information derived from said user request, said legacy action being preformed by a legacy software application;

performing a second action based on information derived from said user request and a successful commencement of said legacy action;

completing said legacy action if said second action is successful;

closing said action log upon a failure of said commencement of said legacy action or a successful performance of said second action; and

,

presenting an output to said user conveying information of said failure or said success.

11. The method according to claim 10 wherein said user request is a request from a customer for a product and includes payment information, said legacy action an on-line payment performed by a legacy software application, and said commencement includes obtaining approval of said payment.

12. The method according to claim 11 wherein said second action is a delivery of a requested product to said customer upon a successful approval of said payment.

13. The method according to claim 12 wherein said delivery is performed by an on-line download of software to said client.

14. The method according to claim 11 wherein said approval is a preapproval and said completing step is an instruction to said legacy software application to debit said customer'"'"'s account.

15. The method according to claim 11 wherein said approval is an actual debiting of said customer'"'"'s account said completing step is either:

an update of said action log to validate said debiting on successful performance of said second action;

or,

an instruction to said said legacy software application to reverse said debiting on an unsuccessful performance of said second action.

16. The method according to claim 10 wherein said second action is a second legacy action.

17. The method according to claim 10 wherein said legacy software application is a user authentication system.

18. A method of recovering a set of actions wherein at least one of said actions includes a task performed by a legacy software application comprising the steps of:

receiving a record in a log generated during an initial attempt to perform said actions, said log representing the status of performance of said actions; and

,

determining, based on said record, whether one of said actions was performed when a second one of said actions should also having been performed and said second one of said actions not having been performed; and

,

either recommencing performance of one or more of said actions so as to reconcile said actions or generating an exception report usable to reconcile said actions.

19. The method according to claim 18 wherein one of said actions includes an on-line payment performed by said legacy software application.

20. The method according to claim 19 wherein a second one of said actions includes delivery software for delivering a requested product to a customer based on a successful completion of an on-line payment, and said reconciliation includes ensuring that said product was delivered if said on-line payment was successfully performed.