System and method for providing user context support in a native transaction platform

• US 8,190,710 B2
• Filed: 06/23/2009
• Issued: 05/29/2012
• Est. Priority Date: 06/23/2009
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Chen, Wei, Zhu, Sheng
• Primary Examiner(s): JEAN, FRANTZ B
• Application Number:
  US12/490,250
• Publication Number:
  US 20100325198A1
• Time in Patent Office: 1,071 Days
• Field of Search: 709/203, 709/217, 709/219, 709/223
• US Class Current: 709/219
• CPC Class Codes: G06F 11/0715 in a system implementing multitasking multitasking per se G06F9/46
• CPC Class Codes: G06F 11/0751 Error or fault detection not based on redundancy power supply failures G06F1/30; network fault management H04L41/06
• CPC Class Codes: G06F 9/466 Transaction processing

Abstract

According to an embodiment, the present invention provides a computer-readable storage medium comprising processor executable codes. The computer-readable storage medium includes code for receiving information from a client entity at a server entity over a network. The computer-readable storage medium includes code for providing a server process at the service, the server process including one or more process threads. The computer-readable storage medium includes code for providing a first context associated the one or more process threads. The computer-readable storage medium includes code for receiving a user request from the client entity for a user thread, the user thread being associated with the service process. The computer-readable storage medium includes code for generating the user thread at the server entity.

Claims

1. A non-transitory computer-readable storage medium comprising processor executable codes, the computer-readable storage medium comprising:

code for receiving information from a client entity at a TUXEDO server entity over a network, wherein the TUXEDO server entity uses a managed thread pool model and each thread is associated with its own context and stop and start of each thread is managed by a TUXEDO framework, and wherein the information includes information required by the TUXEDO server entity to ensure proper execution;

code for providing a server process at a service, the server process including one or more process threads which are from the managed thread pool;

code for providing a first context associated with the one or more process threads being managed by the TUXEDO framework, wherein the context is configured to store the information required by the TUXEDO server entity to ensure proper execution;

code for receiving a user request from the client entity for a user thread, the user thread being associated with the service process and a TUXEDO application;

code for generating the user thread at the TUXEDO server entity;

code for allocating memory for a user context at the TUXEDO server entity;

code for associating the user thread to the user context; and

code for storing the information associated with the user thread in the user context.

2. The non-transitory computer-readable storage medium of claim 1 further comprising code for generating an error message if the memory is unavailable for the user context.

3. The non-transitory computer-readable storage medium of claim 1, wherein the user thread is associated with the server process.

4. The non-transitory computer-readable storage medium of claim 1 further comprising:

code for receiving a user request for terminating the user thread;

code for terminating the user thread;

code for deallocating the memory for the user context.

5. The non-transitory computer-readable storage medium of claim 1 further comprising code for terminating conversations associated with the user thread.

6. The non-transitory computer-readable storage medium of claim 1 wherein the user request comprises an API call.

7. The non-transitory computer-readable storage medium of claim 1 wherein the server entity comprises a network interface for receiving the user request from a communication network.

8. The non-transitory computer-readable storage medium of claim 1 further comprising code for providing a return value if the user context is generated.

9. A system for providing services, the system comprising:

a communication network;

a first client entity, the first client entity being communicative coupled to the communication network;

a TUXEDO server entity, wherein the TUXEDO server entity uses a managed thread pool model and each thread is associated with its own context and stop and start of each thread is managed by a TUXEDO framework, and wherein the TUXEDO server entity includes information required by the TUXEDO server entity to ensure proper execution, the server entity comprising;

a network interface being communicative coupled to the first entity through the communication network;

a processor for running at least a server process for the TUXEDO server entity, the server processing having one or more process threads which are from the managed thread pool; and

a memory for storing thread contexts;

wherein the server entity is configured to;

receive a user request from the first client entity for a first user thread, the first user thread being associated with the server process and a TUXEDO application;

generate the first user thread;

allocate memory for a first user context, the first user context being associated with the first user thread being managed by the TUXEDO framework, wherein the context is configured to store the information required by the TUXEDO server entity to ensure proper execution;

associate the first user context to the first user context;

store information associated with the first user thread at the first user context.

10. The system of claim 9 wherein the memory comprises a buffer memory.

11. The system of claim 9 further comprising a second client entity, wherein the processor is configure to allocate memory a second user context associate for the second client entity, the second user context being associated with the server process.

12. The system of claim 9 wherein the one or more processes threads and the first user processes share the same server process.

13. The system of claim 9 wherein the server entity sends an error message if the memory is unavailable for the first user context.

14. The system of claim 9 wherein the server entity is enabled with user thread and user context functions.

15. A method for providing services, the method comprising:

receiving information from a client entity at a TUXEDO server entity over a network, wherein the TUXEDO server entity uses a managed thread pool model and each thread is associated with its own context and stop and start of each thread is managed by a TUXEDO framework, and wherein the information includes information required by the TUXEDO server entity to ensure proper execution;

providing a server process at a service, the server process including one or more process threads which are from the managed thread pool;

providing a first context associated with the one or more process threads being managed by the TUXEDO framework, wherein the context is configured to store the information required by the TUXEDO server entity to ensure proper execution;

receiving a first user request from the client entity for a user thread, the user thread being associated with the service process and a TUXEDO application;

processing the first user request;

generating the user thread at the TUXEDO server entity;

determining an availability of a memory;

allocating a predetermined amount of memory for a user context at the TUXEDO server entity if the memory is available;

associating the user thread to the user context; and

storing the information associated with the user thread in the user context.

16. The method of claim 15 wherein the first user request comprises a specification of the predetermined amount of memory.

17. The method of claim 15 wherein the first user request comprises an API call.

18. The method of claim 15 further comprising:

receiving a second user request for terminating the user thread;

processing the second user request;

terminating the user thread in response to the second user request;

de-allocating the predetermined amount of memory after terminating the user thread.