NON-INTRUSIVE ASSET MONITORING FRAMEWORK FOR RUNTIME CONFIGURATION OF DEPLOYABLE SOFTWARE ASSETS

• US 20090094584A1
• Filed: 10/04/2007
• Published: 04/09/2009
• Est. Priority Date: 10/04/2007
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: WHITLEY, MICHAEL D., WAGNER, JASON, SCHELL, BENJAMIN M., DHEAP, VIJAY
• Application Number:
  US11/867,473
• Publication Number:
  US 20090094584A1
• Time in Patent Office: Days
• US Class Current: 717/130
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network

Abstract

The present invention discloses a solution for metering, monitoring, and monetizing software assets. The solution can include a step of registering a software asset with a monitoring service. A unique identifying key for the software asset can be generated during registration. The software asset can then be instrumented for the monitoring service. The instrumentation can reference the software asset by the unique key. Specifics of the set of metrics that are to be monitored by the monitoring service for the software asset can be runtime, development time, and/or deployment time configurable. The instrumented software asset can convey transaction data to the monitoring server when used by clients. Analyzed results produced by the monitoring service pertaining to the software assets based upon the transaction data can be provided to authorize users of vendors associated with the software asset.

Claims

1. A method for monitoring software assets comprising:

registering a software asset with a monitoring service;

instrumenting the software asset for the monitoring service, wherein the instrumentation references the software asset by the unique key, wherein specifics of the a set of metrics that are to be monitored by the monitoring service for the software asset are runtime configurable, wherein the instrumented software asset conveys transaction data to the monitoring server when used by clients, and wherein analyzed results produced by the monitoring service pertaining to the software assets based upon the transaction data are provided to authorized users of vendors associated with the software asset.

2. The method of claim 1, wherein the set of metrics are initially established when registering the software asset, said method further comprising:

receiving a unique generated key for the software asset as a result of the registration.

3. The method of claim 1, further comprising:

changing the set of metrics for the software asset by making changes to the set of metrics within the monitoring service,

the monitoring service conveying a changed set of requirements to the software asset; and

the software asset integrating the changed set into the instrumentation, wherein thereafter the conveyed transaction data comprises data specified within the changed set.

4. The method of claim 1, wherein the specifics of the set of metrics are deployment time, runtime, and development time configurable.

5. The method of claim 1, wherein said software asset comprises at least one of content, a widget, a mashup, a service oriented architecture (SOA) application, and a Web 2.0 environment, and wherein consumers use of the software assets and information pertaining to a relationship between the consumers and the vendors is hidden to ensure the vendor maintains ownership of the relationship.

6. The method of claim 1, wherein the monitoring service comprises an application program interface (API), wherein the vendor is able to instrument a software asset with a call to the API that specifies the set of metrics.

7. The method of claim 1, further comprising:

registering at least one consumer of the software asset with the monitoring service; and

monetizing usage of the software asset for the registered at least one consumer using the monitoring service.

8. The method of claim 1, further comprising:

capturing metrics at a plurality of points of a delivery cycle of the software asset;

conveying messages including the captured metrics to the service along with the unique key identifying the software asset; and

the monitoring service correlating the messages using the unique key.

9. The method of claim 1, wherein said steps of claim 1 are performed by at least one machine in accordance with at least one computer program stored in a computer readable media, said computer programming having a plurality of code sections that are executable by the at least one machine.

10. A method for monitoring software assets comprising:

serving at least one software asset to a plurality of clients, wherein said software asset comprises instrumentation for a monitoring service;

each client using the software asset within a client-side interface; and

each client conveying transaction data associated with a use of the software asset to the monitoring service in accordance with specifics of the instrumentation, wherein the monitoring service is a software service executing within a monitoring server, wherein analyzed results produced by the monitoring service pertaining to the software assets based upon the transaction data are provided to authorized users of vendors associated with the software asset, and wherein a set of metrics that are to be monitored by the monitoring service for the software asset are configurable by the vendor associated with the software asset.

11. The method of claim 10, wherein said at least one software asset comprises a plurality of software assets, wherein monitored metrics for each of the plurality of assets is separately configurable by an associated vendor.

12. The method of claim 11, wherein at least two of the software assets are simultaneously present within at least one of the client-side interfaces, and wherein the client-side interface comprises at least one of a mashup and a portal, wherein said two software assets are discrete components of the mashup or the portal.

13. The method of claim 10, said at least one software asset comprises at least one of content, a widget, a mashup, a service oriented architecture (SOA) application, and a Web 2.0 environment, and wherein consumers using of the software assets and information pertaining to a relationship between the consumers and the vendors is hidden to ensure the vendor maintains ownership of the relationship.

14. The method of claim 10, wherein the monitoring service comprises an application program interface (API), wherein the vendor is able to instrument a software asset with a call to the API that specifies the set of metrics, and wherein the set of metrics are runtime, development time, and deployment time configurable.

15. The method of claim 10, further comprising:

registering at least one consumer of the software asset with the monitoring service; and

monetizing usage of the software asset for the registered at least one consumer using the monitoring service.

16. The method of claim 10, wherein said steps of claim 10 are performed by at least one machine in accordance with at least one computer program stored in a computer readable media, said computer programming having a plurality of code sections that are executable by the at least one machine.

17. A system for software assets comprising:

a monitoring service configured to track usage, recognize content flows, and to monetize transactions for a plurality of software assets, wherein each software asset is able to be registered with the monitoring service, which permits metrics for the monitoring service to be configured to monitor different metrics on an asset-by-asset basis, wherein metric specifics for each of the monitored assets are configurable by vendors associated with each of the software assets, and wherein the monitoring service is a software service stored in a machine readable medium executable by a computing device.

18. The monitoring framework of claim 17, further comprising:

an application program interface (API) for the monitoring service, wherein the vendor is able to instrument a software asset with a call to the API that specifies the set of metrics to be monitored for the software assets.

19. The method of claim 17, wherein said software assets comprise content, widgets, mashups, service oriented architecture (SOA) applications, and Web 2.0 environments, and wherein metric specifics are configurable by the vendors at runtime, at development time, and at deployment time.

20. The monitoring framework of claim 17, wherein the monitoring framework permits consumers using of the software assets and information pertaining to a relationship between the consumers and the vendors to remain hidden to ensure the vendor maintains ownership of the relationship.