RECOGNITION OF AND SUPPORT FOR MULTIPLE VERSIONS OF AN ENTERPRISE CANONICAL MESSAGE MODEL

• US 20110153767A1
• Filed: 12/17/2009
• Published: 06/23/2011
• Est. Priority Date: 12/17/2009
• Status: Active Grant

• Current Assignee: ServiceNow Incorporated
• Original Assignee: International Business Machines Corporation
• Inventors: Pendergrass, Harry T., Coldicott, Peter Alan, Lane, Eoin
• Granted Patent: US 8,631,071 B2
• Time in Patent Office: Days
• US Class Current: 709/207
• CPC Class Codes: G06F 8/10 Requirements analysis; Specification techniques
• CPC Class Codes: G06F 8/24 Object-oriented

Abstract

A method of recognizing and supporting multiple versions of a canonical message model in a service oriented architecture industry model repository comprising determining differences between at least one first version of a message model and at least one other version of the message model; mapping the differences between the different versions of the message models to the SOA IMR; and providing the mapping of the differences between the message models to a message access service, mapping of differences between the message models are applied and updated to the later of the message models to support the versions of the canonical message models seamlessly.

Claims

1. A method of recognizing and supporting multiple versions of a canonical message model in a service oriented architecture (SOA) industry model repository (IMR) comprising a meta model service associated with a physical asset repository, the meta model service comprising at least one topic map meta model with data specific to a particular topic or industry vertical included within an information model repository common meta-meta model, the information model repository common meta-meta model included within a meta-meta-meta model with a topic map based index, the method comprising:

a) determining differences between at least one first version of a canonical message model and at least one other version of the canonical message model;

b) mapping the differences between the at least one first version of a canonical message model and the at least one other version of the canonical message model to the SOA IMR;

c) providing the mapping of the differences between the at least one first version of a canonical message model and the at least one other canonical message model to a message access service, and

d) using mapping of differences between the at least one first version of a canonical message model and the at least one other version canonical message model is applied and updated to the later of the at least one first version of a canonical message model and the at least one other version of the canonical message model to support the versions of the canonical message models seamlessly.

2. The method of claim 1, wherein determining differences between at least one first version of a canonical message model and at least one other version of the canonical message model further comprises ingesting the at least one first version of the canonical message model and at least one other version of the canonical message model using the SOA IMR and creating linkages between the at least one first version of a canonical message model and the at least one other version of the canonical message model.

3. A computer system for a service oriented industry model repository architecture, the system comprising:

a CPU, a computer readable memory, a computer readable storage media storing a plurality of computer readable memory, a plurality of service oriented architecture (SOA) industry model repositories (IMR) comprising a meta model service associated with a physical asset repository, the meta model service comprising;

at least one topic map meta model with data specific to a particular topic or industry vertical included within an information model repository common meta-meta model, the information model repository common meta-meta model included within a meta-meta-meta model with a topic map based index;

first program instructions for determining differences between at least one first version of a canonical message model and at least one other version of the canonical message model;

second program instructions for mapping the differences between the at least one first version of a canonical message model and the at least one other version of the canonical message model to the SOA IMR;

third program instructions for providing the mapping of the differences between the at least one first version of a canonical message model and the at least one other canonical message model to a message access service, and

fourth program instructions for using mapping of differences between the at least one first version of a canonical message model and the at least one other version canonical message model is applied and updated to the later of the at least one first version of a canonical message model and the at least one other version of the canonical message model to support the versions of the canonical message models seamlessly;

the first, second, third, and fourth program instructions are stored on the computer readable storage media for execution by the CPU via the computer readable memory.

4. The system of claim 3, wherein the first program instructions further comprises ingesting the at least one first version of the canonical message model and at least one other version of the canonical message model using the SOA IMR and creating linkages between the at least one first version of a canonical message model and the at least one other version of the canonical message model.

5. A computer program product for a service oriented industry model repository architecture, the computer program product comprising:

a computer readable storage media storing a plurality of computer readable memory, a plurality of a service oriented architecture (SOA) industry model repositories (IMR) comprising a meta model service associated with a physical asset repository, the meta model service comprising;

at least one topic map meta model with data specific to a particular topic or industry vertical included within an information model repository common meta-meta model, the information model repository common meta-meta model included within a meta-meta-meta model with a topic map based index;

first program instructions for determining differences between at least one first version of a canonical message model and at least one other version of the canonical message model;

second program instructions to mapping the differences between the at least one first version of a canonical message model and the at least one other version of the canonical message model to the SOA IMR;

third program instructions to providing the mapping of the differences between the at least one first version of a canonical message model and the at least one other version of the canonical message model to a message access service; and

fourth program instructions for using mapping of differences between the at least one first version of a canonical message model and the at least one other version canonical message model is applied and updated to the later of the at least one first version of a canonical message model and the at least one other version of the canonical message model to support the versions of the canonical message models seamlessly;

the first, second, third, and fourth program instructions are stored on the computer readable storage media.

6. The computer program product of claim 5, wherein the first program instructions further comprises ingesting the at least one first version of the canonical message model and at least one other version of the canonical message model using the SOA IMR and creating linkages between the at least one first version of a canonical message model and the at least one other version of the canonical message model.