System and method for context propagation in application servers and transaction-based systems

• US 20050262100A1
• Filed: 05/16/2005
• Published: 11/24/2005
• Est. Priority Date: 05/19/2004
• Status: Abandoned Application

• Current Assignee: BEA Systems Incorporated (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Piper, Andrew
• Application Number:
  US11/129,899
• Publication Number:
  US 20050262100A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 2209/5016 Session
• CPC Class Codes: G06F 9/5027 the resource being a machine, e.g. CPUs, Servers, Terminals
• CPC Class Codes: G06F 9/544 Buffers; Shared memory; Pipes
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services

Abstract

A system and method is provided for context propagation within application servers, messaging systems, and transaction-based systems. Context Areas allow users, both internal and external to the system, to associate information with an application which is then carried along with every request. Downstream components can add to or modify this information, so that it can be carried back to the originator. Common use-cases for this functionality include diagnostics monitoring, application transactions, application load-balancing, and indeed any situation where information needs to be carried out-of-band. The ability to propagate out-of-band information prevents the pollution of user APIs and also allows the adding of information to read-only (i.e. 3rd-party) components. A system and method for context propagation in application servers and transaction-based systems.

Claims

1. A system for context propagation within application servers, comprising:

a first component for communicating requests to an application executing at an application server; and

a ContextArea that allow users to associate context information with an application which is then propagated with every request.

2. The system of claim 1 wherein the first component is a client.

3. The system of claim 1 wherein the system includes a second component down-stream that can modify the context information.

4. The system of claim 3 wherein the modified context information is communicated back to the first component using an out-of-band communication.

5. The system of claim 1 wherein the system can provide transport-specific context information for use in marshaling requests on those transports

6. The system of claim 3 wherein an administrator can configure the system to add diagnostic information to request entering the system.

7. A method for context propagation within application servers, comprising the steps of:

communicating requests from a first component to an application executing at an application server; and

mapping the requests at a ContextArea that allow users to associate context information with an application which is then propagated with every request.

8. The method of claim 7 wherein the first component is a client.

9. The method of claim 7 wherein the system includes a second component down-stream that can modify the context information.

10. The method of claim 9 wherein the modified context information is communicated back to the first component using an out-of-band communication.

11. The method of claim 7 wherein the system can provide transport-specific context information for use in marshaling requests on those transports

12. The method of claim 9 wherein an administrator can configure the system to add diagnostic information to requests entering the system.