System and method for dynamically caching dynamic multi-sourced persisted EJBs

• US 7,249,131 B2
• Filed: 09/05/2002
• Issued: 07/24/2007
• Est. Priority Date: 09/06/2001
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: Initiate Systems, Inc. (International Business Machines Corporation)
• Inventors: Smith, David, Skufca, Jim, Bugh, Rob, Buslawski, John A.
• Primary Examiner(s): Mofiz; Apu
• Assistant Examiner(s): DAYE, CHELCIE L
• Application Number:
  US10/064,974
• Publication Number:
  US 20030065826A1
• Time in Patent Office: 1,783 Days
• Field of Search: 707/3, 707/10, 707/100, 707/104.1, 705/1, 705/8, 705/36, 709/201, 709/202, 709/223, 709/246, 711/209, 715/513, 719/310, 719/315
• US Class Current: 1/1
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: G06F 9/4493 Object persistence
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

Dynamic Multi-sourced Persisted Enterprise Java Bean (EJB) instances are dynamically created on aJ2EE compliant Application Server to access data contained in multiple data source systems. This Dynamic Multi-sourced Persisted EJB is a general class responsible for dynamically aggregating source system information and caching it based on a Context definition. Individual EJB attributes that include mapping, caching and security definitions are mapped to individual pieces of data in source systems by the Context definition. A caching definition can be reloaded during execution as desired. Applications can access the Dynamic Multi-sourced Persisted EJB directly, or use a Session EJB to create a static interface to the dynamically mapped, cached and secured data. Bi-directional synchronization of the cache between client and source system data and modifications of data attributes are achieved without recoding, recompiling and redeploying of custom coded solutions.

Claims

1. A method computer-implemented for dynamically caching Dynamic Multi-sourced Persisted EJB attributes, comprising:

creating a context definition containing attributes representing collections of source system data;

specifying in an attribute caching element whether each attribute in the context definition is to be cached in a persistent data cache;

storing the context definition in a persistent data cache;

creating an instance of a Dynamic Multi-sourced Persisted EJB;

applying the attributes in the context definition to the created instance of the Dynamic Multi-sourced Persisted EJB;

accessing cached data by the Dynamic Multi-sourced Persisted EJB instance without requiring EJB compilation and deployment; and

bi-directionally synchronizing persistent cache data from clients and from data sources.

2. The method of claim 1, further comprising:

specifying whether each attribute in the context definition is mapped to a field in a data source;

identifying a data source system table where the attribute value is located if the attribute is mapped; and

specifying access security requirements for each attribute in the context definition.

3. The method of claim 1, wherein the step of storing the context definition comprises dynamically creating a persistent cache table in the persistent data cache for managing context attributes during EJB Bean Managed Persistence lifecycle.

4. The method of claim 3, wherein the step of storing the context definition comprises dynamically creating a persistent Map/Cache/Secure Table in the persistent data cache.

5. The method of claim 1, further comprising reloading a context definition for updating attribute caching requirements during execution and keeping cache data synchronized and updated with client and back-end data.

6. The method of claim 5, wherein the reloading of the context definition is performed during execution on demand.

7. The method of claim 5, wherein the reloading of the context definition is performed during execution on a schedule.

8. The method of claim 5, wherein the step of reloading the context definition comprises:

detecting differences between the stored context definition and the reloaded context definition for identifying changes in the context definitions; and

rebuilding persistent cache database tables containing context definitions for incorporating changes in the context definition.

9. The method of claim 8, wherein the step of rebuilding the persistent data cache context definitions comprises:

locking a cache database table to external users;

creating a new cache database table containing new context definitions;

copying data from the existing cache database table into the new database table;

deleting the existing cache database table;

renaming the new cache database table to replace the deleted database table; and

unlocking the cache database.

10. The method of claim 1, wherein the persistent data cache is a relational database.

11. The method of claim 1, further comprising:

creating and loading a new context definition containing new attributes;

applying the new attributes to the Dynamic Multi-sourced Persisted EJB instance for mapping the new attributes to source system data fields during runtime;

recreating the persistent data cache; and

immediately sending new attribute data to clients.

12. The method of claim 1, further comprising representing the context definition as an XML document.

13. The method of claim 1, further comprising storing source and client data designated to be cached in the persistent data cache.

14. The method of claim 1, further comprising keeping data in the cache synchronized and updated with the most recent data from clients to source systems, and from source systems to clients.

15. The method of claim 1, further comprising:

creating and loading a new context definition containing new attributes;

applying the new attributes to the Dynamic Multi-sourced Persisted EJB instance;

recreating a Map/Cache/Secure Table in the persistent data cache for storing context definitions; and

immediately sending new attribute data to clients.

16. The method of claim 1, wherein the step of creating an instance of a Dynamic Multi-sourced Persisted EJB comprises creating and accessing an instance of a Dynamic Multi-sourced Persisted EJB from an external application using generic method calls of an application programming interface selected from the group consisting of create( ), find( ), getAttr( ), getAttrs( ), getGuid( ), setAttr( ), setAttrs( ) and retrieveNewAndDeletedContexts( ).

17. The method of claim 16, further comprising performing runtime checks prior to executing a method call including querying a security engine to determine if the method call is authorized and querying back-end adapters to determine if there are pending back-end mapped data updates for keeping cache data synchronized and updated with back-end mapped data.

18. The method of claim 1, wherein the step of creating an instance of a Dynamic Multi-sourced Persisted EJB comprises creating and accessing an instance of a Dynamic Multi-sourced Persisted EJB from an external application through a Session EJB Wrapper using traditional method calls of an application programming interface selected from the group consisting of create( ), getAttributeName( ) and setAttributeName( ).

19. The method of claim 18, further comprising performing runtime checks prior to executing a method call including querying a security engine to determine if the method call is authorized and querying back-end adapters to determine if there are pending back-end mapped data updates for keeping cache data synchronized and updated with back-end mapped data.

20. A computer-readable medium containing instructions for controlling a computer system to implement the method of claim 1.

21. A computer-implemented system for dynamically caching Dynamic Multi-sourced Persisted EJB attributes, comprising:

means for creating a context definition containing attributes representing collections of source system data;

an attribute caching element for specifying whether an attribute in the context definition is to be cached in a persistent data cache;

means for storing the context definition in a persistent data cache;

means for creating an instance of a Dynamic Multi-sourced Persisted EJB;

means for applying the attributes in the context definition to the created instance of the Dynamic Multi-sourced Persisted EJB;

means for accessing cached data by the Dynamic Multi-sourced Persisted EJB instance without requiring EJB compilation and deployment; and

means for bi-directionally synchronizing persistent cache data from clients and from data sources.

22. The system of claim 21, wherein each attribute comprises:

an element specifying whether each attribute in the context definition is mapped to a field in a data source;

an element identifying a data source system table where the attribute value is located if the attribute is mapped; and

an element specifying access security requirements for each attribute in the context definition.

23. The system of claim 21, wherein the means for storing the context definition comprises a dynamically created persistent cache table in the persistent data cache for managing context attributes during EJB Bean Managed Persistent lifecycle.

24. The system of claim 23, wherein the persistent cache table comprises a Map/Cache/Secure Table.

25. The system of claim 21, further comprising means for reloading a context definition for updating attribute caching requirements during execution and means for keeping cache data synchronized and updated with client and back-end data.

26. The system of claim 25, wherein the context definition is reloaded during execution on demand.

27. The system of claim 25, wherein the context definition is reloaded during execution on a schedule.

28. The system of claim 21, wherein the persistent data cache is a relational database.

29. The system of claim 21, wherein the context definition is an XML document.

30. The system of claim 21, further comprising the persistent data cache for storing selected source and client data.

31. The system of claim 21, wherein the means for creating an instance of a Dynamic Multi-sourced Persisted EJB comprises means for creating and accessing an instance of a Dynamic Multi-sourced Persisted EJB from an external application using generic method calls of an application programming interface selected from the group consisting of create( ), find( ), getAttr( ), getGuid( ), setAttr( ), setAttrs( ) and retrieveNewAndDeletedContexts( ).

32. The system of claim 31, further comprising means for performing runtime checks prior to executing a method call including means for querying a security engine to determine if the method call is authorized and means for querying back-end adapters to determine if there are pending back-end mapped data updates, for keeping cache data synchronized and updated with back-end mapped data.

33. The system of claim 21, wherein the means for creating an instance of a Dynamic Multi-sourced Persisted EJB comprises means for creating and accessing an instance of a Dynamic Multi-sourced Persisted EJB from an external application through a Session EJB Wrapper using traditional method calls of an application programming interface selected from the group consisting of create( ), getAttributeName( ) and setAttributeName( ).

34. The system of claim 33, further comprising means for performing runtime checks prior to executing a method call including means for querying a security engine to determine if the method call is authorized and means for querying back-end adapters to determine if there are pending back-end mapped data updates, for keeping cache data synchronized and updated with back-end mapped data.

35. The system of claim 21, wherein the means for sending attribute data to clients comprises means for sending attribute data to client applications running on web browsers and sending attribute data to trusted Java applications running on client machines.

36. A computer-implemented system for dynamically mapping Dynamic Multi-sourced Persisted EJB attributes to source system resources, comprising:

an application server including contexts connected to JMS adapters;

a data cache connected to the contexts in the application server for providing BMP data for mapping Dynamic Multi-sourced Persisted EJB attributes to back-end system data fields;

system adapters for connecting JMS adapters to back-end systems; and

an XML data storage device for providing context definition documents to the contexts and JMS adapters in the application server and to the system adapters.

37. The system of claim 36, wherein the contexts include Dynamic Multi-sourced Persisted EJB instances and Session EJB Wrappers.

38. A computer-implemented system for dynamically caching Dynamic Multi-sourced Persisted EJB attributes, comprising:

a context definition containing attributes representing collections of source system data;

an attribute caching element for specifying whether an attribute in the context definition is to be cached in a persistent data cache;

a persistent data cache for storing the context definition;

an instance of a Dynamic Multi-sourced Persisted EJB;

the attributes in the context definition applied to the created instance of the Dynamic Multi-sourced Persisted EJB;

the Dynamic Multi-sourced Persisted EJB instance accessing cached data without requiring EJB compilation and deployment; and

persistent cache data being bi-directionally synchronized from clients and from data sources.