Client server system with thin client architecture

• US 20020065879A1
• Filed: 05/30/2001
• Published: 05/30/2002
• Est. Priority Date: 11/30/1998
• Status: Abandoned Application

• Current Assignee: Siebel Systems Inc. (Oracle Corporation)
• Original Assignee: Siebel Systems Inc. (Oracle Corporation)
• Inventors: Arnalz, Gilberto, Hahn, Samuel Shin-Yi, Katchour, Ernst, Rothwein, Thomas M., Ambrose, Jesse, Coker, John L., Diec, Thanh
• Application Number:
  US09/866,877
• Publication Number:
  US 20020065879A1
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 16/10 File systems; File servers
• CPC Class Codes: G06F 9/50 Allocation of resources, e.g. of the central processing unit [CPU]
• CPC Class Codes: G06F 9/54 Interprogram communication
• CPC Class Codes: H04L 63/02 for separating internal from external traffic, e.g. firewalls
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226

Abstract

Web based client-server systems with thin client architecture. More specifically, it relates to a method and system for transferring service requests and responses to the requests between a thin client and an enterprise server in a client-server system. Preferably the interconnection is a persistent interconnection.

Claims

1. A client server system comprising a thin client interface residing on at least one client and a an object manager and an application residing on one or more servers, said object manager interposed between said client and said application server, and said application server comprising one or more of business objects, and business components.

2. The client-server system of claim 1 wherein the application server comprises a database server.

3. The client-server system of claim 1 wherein object manager run-time engines that operate on the business objects and business components.

4. The client-server system of claim 3 wherein the business objects and business components comprise applets and application objects.

5. The client-server system of claim 3 wherein object manager run time engines enforce repository-defined business processes and rules.

6. The client-server system of claim 1 having application objects executing on the client.

7. The client-server system of claim 1 having user interface objects executing on the client.

8. The client-server system of claim 1 comprising session-based network protocols connecting the client to the object manager.

9. A method of connecting a client and one or more servers in a client server network, wherein said client is a thin client, and said one or more servers comprise an object manager and an application residing on one or more servers, said object manager interposed between said client and said application server, and said application server comprising one or more of business objects, and business components, instantiating said one or more business objects and establishing a session based network connection between the thin client and the one or more servers.

10. The method of claim 9 comprising instantiating object manager run-time engines to operate on the business objects and business components.

11. The method of claim 9 wherein the business objects and business components comprise applets and application objects.

12. The method of claim 9 wherein object manager run time engines enforce repository-defined business processes and rules.

13. The method of claim 9 wherein application objects execute on the client.

14. The method of claim 9 wherein the user interface objects execute on the client.