Pluggable state meta-data processors based on meta information modeling in a service oriented architecture

• US 20050050311A1
• Filed: 08/28/2003
• Published: 03/03/2005
• Est. Priority Date: 08/28/2003
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Joseph, Joshy, Maguire, Thomas R.
• Granted Patent: US 7,693,973 B2
• Time in Patent Office: Days
• US Class Current: 713/1
• CPC Class Codes: G06F 16/40 of multimedia data, e.g. slideshows comprising image and additional audio data retrieval of still image data G06F16/50; retrieval of audio data G06F16/60; retrieval of video data G06F16/70
• CPC Class Codes: G06F 16/907 Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually

Abstract

A method and system for managing service state data of a service in a service-oriented architecture by establishing a pluggable meta-data processor comprising: establishing a platform independent, extensible meta-data information model to define meta-data about service state data; establishing an extensible meta-data definition comprising an extensible set of service state data attributes; configuring one or more extensible semantic processors; configuring a controller meta-data processor; and defining contracts among the semantic processors.

Claims

1. A method for managing service state data of a service in a service-oriented architecture by establishing a pluggable meta-data processor comprising:

establishing a platform independent, extensible meta-data information model to define meta-data about service state data;

establishing an extensible meta-data definition comprising an extensible set of service state data attributes;

configuring one or more extensible semantic processors;

configuring a controller meta-data processor; and

defining contracts among said semantic processors.

2. The method of claim 1 further including configuring platform dependent models to facilitate semantic processing of said service state meta-data based on said meta-data information model.

3. The method of claim 1 wherein said a meta-data information model defines meta-data for said service state data.

4. The method of claim 1 wherein said a meta-data information model provides meta-data syntax to ensure validation, versioning, compatibility, and consistency and wherein said meta-data information model is indicative of schema or meta-data for said service state meta-data.

5. The method of claim 1 wherein said a meta-data information model provides meta-data semantics for at least one of:

service state data constraints, qualifiers and data access mechanisms and rules for processing said meta-data semantics; and

meta-data processing of workflow information.

7. The method of claim 1 wherein said a meta-data information model provides meta-data extensibility.

8. The method of claim 1 wherein said service state data attributes include state data qualifiers, constraints, and access mechanisms;

and templates.

9. The method of claim 1 wherein said establishing includes definition for service state data qualifiers comprising:

enabling expression of state change notification qualifiers, said qualifiers including notification of a change in state results;

enabling definition and expression of security requirements on a service state discovery and notification;

enabling expression of transaction requirements, said transaction requirements including enable/disable transaction; and

providing a framework to link to a transaction coordinator and define transaction scope said transaction scope including a service developer controlled transaction, a service controlled transaction, and a gateway managed transaction on state data.

10. The method of claim 1 wherein said establishing includes definition for service state data constraint comprising;

enabling expression of constraints on mutability;

enabling expression of constraints on a validity of said service state data through life time constraints, said life time constraints including at least one of, time to live (TTL), time to activate, available from, available until, good from, good until and immutable until;

enabling cardinality on said service state data; and

enabling and specification of a relationship among said service state data, said specification supporting complex queries and state management.

11. The method of claim 1 wherein said establishing includes definition for service state data access mechanisms comprising:

enabling a flexible callback mechanism on said service state data and expression thereof through meta-data;

establishing a data push mechanism for service state data update with expression of said constraints through meta-data;

establishing other extensible data access mechanisms on said service state data, said other extensible data access mechanisms including direct access to said service state data in a database;

direct access to said service state data through SNMP, CIM, Web services; and

establishing an extensible custom template mechanism for service state data access based on service requirements;

said service state data access based on service requirements including a service template for custom scripts.

12. The method of claim 1 wherein said configuring one or more semantic processors comprises establishing a generic processor configured to be operate under one or more contracts with at least one of said controller meta-data processor and another semantic processor.

13. The method of claim 1 wherein said semantic processors are platform dependent based on platform specific modeling artifacts.

14. The method of claim 1 wherein said controller meta-data processor is a service specific processor configured to define contracts among said semantic processors and control flow of data therebetween.

15. The method of claim 1 wherein said controller meta-data processor provides a meta-data or service state data repository.

6. The method of claim I wherein said a meta-data information model defined meta-data relationships.

16. A system for managing service state data of a service in a service-oriented architecture by establishing a pluggable meta-data processor comprising:

a means for establishing a platform independent, extensible meta-data information model to define meta-data about service state data;

a means for establishing an extensible meta-data definition comprising an extensible set of service state data attributes;

a means for configuring one or more extensible semantic processors;

a means for configuring a controller meta-data processor; and

a means for defining contracts among said semantic processors.

17. A storage medium encoded with a machine-readable computer program code, said code including instructions for causing a computer to implement a method for managing service state data of a service in a service-oriented architecture by establishing a pluggable meta-data processor, the method comprising:

establishing a platform independent, extensible meta-data information model to define meta-data about service state data;

establishing an extensible meta-data definition comprising an extensible set of service state data attributes;

configuring one or more extensible semantic processors;

configuring a controller meta-data processor; and

defining contracts among said semantic processors.