Generic context service in a distributed object environment

• US 20070033640A1
• Filed: 07/22/2005
• Published: 02/08/2007
• Est. Priority Date: 07/22/2005
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Zou, Chendong, Mei, Xiaochun, Herness, Eric
• Application Number:
  US11/187,291
• Publication Number:
  US 20070033640A1
• Time in Patent Office: Days
• US Class Current: 726/5
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Abstract

A context framework allows context propagation over synchronous invocation and asynchronous invocation. A context carrier is created for each thread. A set of application programming interfaces allow software components to store and retrieve context entries. By referring to the context carrier and creating a new context carrier when a new thread is started, context can flow both upstream and downstream along the invocation chain.

Claims

1. A computer implemented method for context propagation, the computer implemented method comprising:

responsive to invoking a first software component, creating a first context carrier associated with a first session;

creating a first context entry in the first context carrier, wherein the first context entry stores context information associated with the first software component; and

responsive to the first software component invoking a second software component, propagating the context information associated with the first software component to the second software component using the first context carrier.

2. The computer implemented method of claim 1, wherein the first context carrier has a unique identifier associated with the first session and wherein the first context entry is identified by a key.

3. The computer implemented method of claim 2, wherein the first software component invokes the second software component synchronously and wherein the second software component accesses the first context entry using the unique identifier and the key.

4. The computer implemented method of claim 1, wherein the first software component invokes the second software component asynchronously by generating an invocation message.

5. The computer implemented method of claim 4, wherein propagating the context information associated with the first software component comprises embedding the context information associated with the first software component in the invocation message.

6. The computer implemented method of claim 5, further comprising:

running the second software component in a second session;

creating a second context carrier associated with the second session; and

creating a second context entry in the second context carrier, wherein the second context entry stores the context information associated with the first software component.

7. The computer implemented method of claim 6, further comprising:

terminating the first software component; and

deleting the first context carrier.

8. The computer implemented method of claim 6, further comprising:

returning a reply message from the second software component to the first software component, wherein the reply message has embedded therein the context information associated with the first software component;

invoking the first software component;

creating a third context carrier associated with the first session; and

creating a third context entry in the third context carrier, wherein the third context entry stores the context information associated with the first software component.

9. A data processing system comprising:

a hardware platform;

a distributed component runtime environment running on the hardware platform, wherein the distributed component runtime environment includes a context manager comprising;

a context carrier creation function that creates a context carrier associated with a given session;

a context entry set function that stores a context entry associated with a given software component in a context entry in the context carrier;

a context entry get function that gets context data from a given context entry.

10. The data processing system of claim 9, wherein the context manager comprises a set of application programming interfaces.

11. The data processing system of claim 9, wherein the distributed component runtime environment is a service-oriented architecture container.

12. The data processing system of claim 11, wherein the service-oriented architecture container runs in a virtual machine on the hardware platform.

13. A computer program product, comprising:

a computer usable medium having computer usable program code for context propagation, the computer usable program code comprising;

computer usable program code, responsive to invoking a first software component, for creating a first context carrier associated with a first session;

computer usable program code for creating a first context entry in the first context carrier, wherein the first context entry stores context information associated with the first software component; and

computer usable program code, responsive to the first software component invoking a second software component, for propagating the context information associated with the first software component to the second software component using the first context carrier.

14. The computer program product of claim 13, wherein the first context carrier has a unique identifier associated with the first session and wherein the first context entry is identified by a key.

15. The computer program product of claim 14, wherein the first software component invokes the second software component synchronously and wherein the second software component accesses the first context entry using the unique identifier and the key.

16. The computer program product of claim 13, wherein the first software component invokes the second software component asynchronously by generating an invocation message.

17. The computer program product of claim 16, wherein the computer usable program code for propagating the context information associated with the first software component comprises the computer usable program code for embedding the context information associated with the first software component in the invocation message.

18. The computer program product of claim 17, further comprising:

computer usable program code for running the second software component in a second session;

computer usable program code for creating a second context carrier associated with the second session; and

computer usable program code for creating a second context entry in the second context carrier, wherein the second context entry stores the context information associated with the first software component.

19. The computer program product of claim 18, further comprising:

computer usable program code for terminating the first software component; and

computer usable program code for deleting the first context carrier.

20. The computer program product of claim 18, further comprising:

computer usable program code for returning a reply message from the second software component to the first software component, wherein the reply message has embedded therein the context information associated with the first software component;

computer usable program code for invoking the first software component;

computer usable program code for creating a third context carrier associated with the first session; and

computer usable program code for creating a third context entry in the third context carrier, wherein the third context entry stores the context information associated with the first software component.