System and method for flexible publishing and consumption of data between disparate applications

1. A system comprising:

a processor-based device;

a first application executing on said processor-based device;

a first adapter interfaced with said first application, said first adapter is configured to publish data of said first application for consumption by another application, wherein said first adapter publishes said data of said first application according to a publishing regime not natively supported by said first application, wherein said another application does not natively support consumption of said data of said first application published by said first adapter, and wherein said publishing regime not natively supported by said first application comprises at least one of: (a) a publishing schedule not natively supported by said first application, and (b) a data content not natively published by said first application; and

a second adapter communicatively interfaced with said another application, wherein said second adapter enables said another application to consume said data of said first application published by said first adapter, wherein said second adapter maintains a consumption log that identifies at least the last successful consumption by said another application of said data of said first application published by said first adapter, wherein said second adapter defines a consuming regime to be used for consumption by said another application of said data of said first application published by said first adapter, wherein said first and second adapters communicate directly with each other in an adapter common communication bus format, and wherein said consuming regime differs from the publishing regime according to which the first adapter publishes the data of the first application.

2. The system of claim 1 wherein said publishing regime not natively supported by said first application comprises:

a data format not natively supported by said first application.

3. The system of claim 1 wherein said publishing regime not natively supported by said first application comprises:

a publishing schedule not natively supported by said first application; and

data content not natively published by said first application.

4. The system of claim 1 wherein said publishing regime not natively supported by said first application comprises:

a data format not natively supported by said first application; and

a publishing schedule not natively supported by said first application.

5. The system of claim 1 wherein said first adapter is further configured to aggregate data from a plurality of different data stores of said first application for publishing.

6. The system of claim 1 wherein said publishing regime specifies at least one of the following:

a published format to be used for receipt by said second adapter of said data published by said first adapter, and a consumption schedule according to which said data published by said first adapter is to be consumed by said second adapter.

7. The system of claim 1 wherein said second adapter translates said data published by said first adapter into a format natively supported by said another application.

8. A method comprising:

communicatively interfacing a first adapter to a first application that is executing on a processor-based device;

said first adapter publishing data of said first application, for consumption by another application, according to a publishing regime not natively supported by said first application, wherein said another application does not natively support consumption of said data of said first application published by said first adapter and wherein said publishing data according to said publishing regime not natively supported by said first application comprises publishing said data according to a publishing schedule not natively supported by said first application;

communicatively interfacing a second adapter to said another application, wherein said second adapter enables said another application to consume said data of said first application published by said first adapter, wherein said second adapter maintains a consumption log that identifies at least the last successful consumption by said another application of said data of said first application published by said first adapter, wherein said second adapter defines a consuming regime to be used for consumption by said another application of said data of said first application published by said first adapter, wherein said first and second adapters communicate directly with each other in an adapter common communication bus format, and wherein said consuming regime differs from the publishing regime according to which the first adapter publishes the data of the first application.

9. The method of claim 8 wherein said publishing data according to said publishing regime not natively supported by said first application comprises:

publishing said data in a data format not natively supported by said first application.

10. The method of claim 8 wherein said publishing data according to said publishing regime not natively supported by said first application comprises:

publishing data content not natively published by said first application.

11. The method of claim 8 further comprising:

said first adapter aggregating said data from a plurality of different data stores of said first application.

12. The method of claim 8 further comprising:

said second adapter translating said data published by said first adapter into a format natively supported by said another application.

13. The method of claim 8 wherein said first adapter comprises software executing on a processor-based device for performing said publishing.

14. A system comprising:

a processor-based device;

a first application executing on said processor-based device;

a means, communicatively interfaced with said first application, for publishing data of said first application for consumption by another application, wherein the publishing means publishes said data of said first application according to a publishing regime not natively supported by said first application, wherein said another application does not natively support consumption of said data of said first application published by said first adapter, and wherein said publishing regime not natively supported by said first application comprises publishing data content not natively published by said first application;

a means, communicatively interfaced with said another application, for enabling said another application to consume said data of said first application published by said means for publishing data, wherein said consuming means enables said another application to consume said data of said first application published by said publishing means, wherein said consuming means maintains a consumption log that identifies at least the last successful consumption by said another application of said data of said first application published by said publishing means, wherein said consuming means defines a consuming regime to be used for consumption by said another application of said data of said first application published by said publishing means, wherein said publishing means and consuming means communicate directly with each other in an adapter common communication bus format, and wherein said consuming regime differs from the publishing regime according to which said publishing means publishes the data of the first application.

15. The system of claim 14 wherein said publishing regime not natively supported by said first application further comprises at least one selected from the group consisting of:

publishing said data in a data format not natively supported by said first application, and publishing said data according to a publishing schedule not natively supported by said first application.

16. The system of claim 14 wherein the publishing means is configurable as to at least one of publishing schedule and publishing format.

17. The system of claim 14 wherein said publishing means comprises software executing on said processor-based device.

18. A system comprising:

a processor-based device;

a first application executing on said processor-based device;

a second application that desires to consume data from said first application;

a publishing adapter communicatively interfaced with said first application, said publishing adapter is configured to publish data of said first application; and

a consuming adapter communicatively interfaced with said second application, wherein said consuming adapter maintains a consumption log that identifies at least the last successful consumption of said data of said first application by said second application,

wherein said publishing adapter communicates said published data directly with said consuming adapter in an adapter common communication bus format,

wherein said publishing adapter publishes said data of said first application according to a publishing regime that is not natively supported by said first application; and

wherein said publishing regime that is not natively supported by said first application comprises at least one of: (a) a publishing schedule not natively supported by said first application, and (b) data content not natively published by said first application,

wherein said publishing and consuming adapters communicate directly with each other in an adapter common communication bus format, and wherein said consuming regime differs from the publishing regime according to which the publishing adapter publishes the data of the first application.

19. The system of claim 18 wherein said second application desires to consume said data according to a different regime than a regime in which said first application publishes said data.

20. The system of claim 19 wherein the publishing adapter publishes said data of said first application according to a publishing regime not natively supported by said first application.

21. The system of claim 18 wherein the consuming adapter determines the data to obtain from the publishing adapter based at least in part on said consumption log.

22. The system of claim 21 wherein said consuming adapter obtains any changes in said data since the last successful consumption of said data by said second application.

23. A system comprising:

a processor-based device;

a first application executing on said processor-based device;

a second application that desires to consume data from said first application;

a publishing adapter communicatively interfaced with said first application, said publishing adapter is configured to publish data of said first application according to a publishing regime not natively supported by said first application, wherein said publishing regime comprises at least one of: (a) a publishing schedule not natively supported by said first application, and (b) data content not natively published by said first application; and

a consuming adapter communicatively interfaced with said second application, said consuming adapter is configured to access said published data for consumption by said second application,

wherein said consuming adapter enables said another application to consume said data of said first application published by said publishing adapter, wherein said consuming adapter maintains a consumption log that identifies at least the last successful consumption by said another application of said data of said first application published by said publishing adapter, wherein said consuming adapter defines a consuming regime to be used for consumption by said another application of said data of said first application published by said publishing adapter, wherein said publishing and consuming adapters communicate directly with each other in an adapter common communication bus format, and wherein said consuming regime differs from the publishing regime according to which the publishing adapter publishes the data of the first application.

24. The system of claim 23 wherein said consuming adapter is configured to translate said published data to a format natively supported by said second application.